Noticed that after updating the Node-Red event state nodes for the wifi devices are being triggered every 30 secs. Is this an intended behavior? The states are not changing, the same messages are being pushed every 30 secs. Tried it with several wifi devices, all report every 30 secs. ZigBee devices are not being affected.
The topicstart should include that if you have it installed already you can install the update by clicking “Check for updates”, then press “Minimize” and then wait untill a prompt is shown with the question whether you want to install the update.
My suggestion for improvement: show a download progress indicator somewhere while the download of the update is ongoing in the background. I have a rather slow internet connection and without looking at the download occupation in my router settings it looks like the iHost is doing nothing whilst it actually is downloading the Docker add-on update.
Hi. Just saw that V1.3.0 got released with the supported devices being extended with what I was waiting for. DUALR3 and TH16.
Several questions / feedback:
Any detailed changelog that you could share?
DUAL R3 has consumptions tracking feature, are there plans to have this sent to iHost as well?
TH16 (R2) related:
3.1. Sends over temp / humidity data but tracking is not enabled for these. Can this be configured so that datapoint are saved locally on iHost similar to other Zigbee temp / hum sensors?
3.2. In Node-Red the event-state for this device does not have any “State” that could be interrogated for. So any status changed cannot be integrated in Node-Red at the moment. See screenshot below
Update: Also these new devices are not selectable in the “Cast” function of IHost
Update1: In Node-Red the DUAL R3 states are somehow triggered twice when actioned from either iHost panel or via control-device node in Node-Red
Another issue with controlling DUAL R3 in Node-Red:
as there is no option to leave one of the channel on the old state, each time I try to turn on / off one of the channels I have to change the other one as well. This is not desired if they control two different things. In addition I get a lot of “Failed to connect. Check server configuration” messages for the control node. As I could figure it out it gives this failure due to two reasons
Either I am trying to change state of a channel which is already in that state
Either I am leaving the channel selection with “Please select” in a previous trigger, then the “toggleState” value becomes blank and not able to get status for it any more in Node-Red.
These are serious limitation on how to integrate the device in Node-Red.