Hi, I’ve recently noticed some strange behaviour with the updating of channels.
I have a switch inside my boiler, I use this to control my heating and this usually works flawlessly, recently this node had been going offline randomly yet the item shows as OFF even though it is ON. Switching the node off and on has no effect on the switch, yet the GUI and the logs think the item has actually changed state. This triggers both the
Item changed and the
Item received update.
I cannot remember this being like that, surely the node (or thing if you prefer), should post it’s status instead of the engine just assuming it has changed.
Last night my heating stayed on all night because my rule checks for the state and doesn’t turn it off unless it is on, and it thought it was off even though it was on.
The only solution I can think of to work around this behaviour is to have a cron constantly switching the node depending on it’s assumed state. I would rather not do this. Fixing the node so it doesn’t go offline is, of course, another solution, but I am kinda glad this has happened.
I’d include logs, but those logs would only show the system working perfectly, because the system is not getting its state from actual node state changes.
I’m not 100% certain, but I am sure this never happened before, there was always a delay in the GUIs while nodes were switching, now there is no delay, the system just assumes things went well.