The device is NSPanel can be synced to iHost via paral-sync add-on.
POW and DualR3 is wifi device, it’s not supported iHost, after all, iHost is a zigbee hub.
If you need to use them, please add them to you eWeLink app and synced them with smart-home add-on.
Power consumption is not supported in smart scene for now.
I think there were some misunderstandings after the translation.
iHost won’t act as a Wi-Fi access point/router to get Wi-Fi devices connected directly but connect to those devices on LAN via local API (partly local, old devices without LAN Mode must stay connected with WAN due to chipset and firmware limitation)
More power consumption features, including expanding the supported list are under evaluation. We appreciate your feedback and are sorry for the confusion made before.
As you have an iHost you can do this. Instal Node Red and then select the power outputting device; one of the options will be power. It’s a string so I’d just turn it into a JSON object, get the number and then send that number to a switch node after checking it was a number with a preceding switch node just in case it occasionally sends out error messages. That would work for live power. If you wanted energy use I’d bet there already was a Node Red Palette for that, but if not you’d need to do it yourself on Node Red.
I selected all and then just watched the debug node to see what it put out. I’m assuming the Power is just an oversight because I’m pretty sure it is there. Been a while since I did that but I just wondered what each device did so just selected one of each device and All.
Edited having read the latest post. My experiment was on either a POW R2 or newer POW. Don’t have a dual, so no idea what it puts out. I’d still put a debug node behind everything, select ALL and then watch the output to see what is available.
first you need to catch only the right output with a built in Switch Node. Probably set to “contains” “electric-power” but I always just try all the options till it works. Stick a Debug node behind it. Nodes do odd unexpected things. The Core Nodes : Node-RED
then turn that JSON String of letters into an JavaScript object with an also built in JSON Node Convert to/from JSON : Node-RED
built in Change Node and MOVE the date from that subsection into msg.payload. You can find the correct location of the original by sticking a debug node after the JSON object and copying the path using the 1st icon. I don’t know what the icon is supposed to be but if you hover over it then you will see “copy path”.
I think the first link contains this node and all basic nodes.
Now your main output will be just the Power and you can stick a standard Switch Node after it and do certain things whether it’s above or below a number. It uses just standard nomenclature like “>”. There’s a plus icon where you can add extra rules and outputs. I’m betting there’s an energy node that saves historical data too but haven’t had a look. You could do it yourself too but that’d be a pain if you don’t already have context storage on your non-volatile drive set up.
Edited to add. If you get loads of errors then you might want to stick an extra Switch Node before the last Switch Node. You can check the content of the message is a number and not null or error. You probably want to stick a Filter Node before too otherwise it’ll activate the switch loads and reevaluate the output each time, then again power probably varies a lot (Filter Node just stops repetition) so it might not do anything and so you could put Delay Node with a maximum rate of every 5s or something. The thing called a Delay node can be set to add no delay but have a maximum frequency instead. I think the name is misleading.
my enthusiasm was short lived: your solution works perfectly for the POW Elite but the Dual R3 is not sending info on the power consumption.
I see the ON/OFF messages but nothing for the power
I’m guessing that is because you get a power measurement for channel 1 and 2 independently, but I don’t have a dual to check.
Is there a general Channel 1 or 2 to select and watch the output of?
Possibly there is a way to synchronise each channel with a virtual device you have created with the register device node, but I can’t think of it straight away.
My guess is that the Power for each channel appears on the iHost but can’t be used as a trigger, meanwhile the in Node Red the power could trigger but does not appear? Is this correct? At first when the TRV was new the built in Scenes and NR outputs were different so I had pretend virtual devices to unify the devices. Then they improved both sides and my work around was rendered pointless.
Done a few checks on version 2.3:
I don’t find the Dual R3 power consumption anywhere in iHost or in Cast.
Power comsumption doesn’t exist in iHost rules.
In nodered the POW elite send messages with power consumption, but the Dual R3 doesn’t.