DaveMDS / node-red-contrib-tasmota

Tasmota devices for NodeRed
MIT License
23 stars 9 forks source link

Nodes no longer report or forward device status in flows, instead show offline, BUT still control devices #46

Open digitydogs opened 1 year ago

digitydogs commented 1 year ago

I recently updated all of my device (40+) to tasmota 12.5 after being on 9.2/9.5 for quite some time. I am still able to control all of my lights and other devices via the nodes, but now they no longer report anything to do with the state/status, they also do not forward ANY flow information to debug nodes.

This means that any of my flows that rely on knowing the current status of a light are no longer able to function.

You can reproduce this by installing tasmota 12.5 onto a device and then configuring the node for that device. Attach a debug node to the output of the node. Send the node any commands. Your device will follow the commands, but the node will not indicate anything has happened, nor will it forward the change, or any incoming flow data out to to the debug node.

Would really appreciate a fix for this as a lot of my home automations are related to elderly care are rely on the status of devices from those nodes to function properly.

If I am able to figure out any further information as to the cause I will report back. This was working exactly as is on 9.2, and 9.5, the only thing that changed in my setup was updating to tasmota 12.5.

image image image image

DaveMDS commented 1 year ago

Hi, I cannot reproduce the issue. Upgraded right now my lights and switches to tasmota 12.5.0. They are all online and report the status correctly... :/

Did you upgrade something else in the mean time? nodered version?

digitydogs commented 1 year ago

Unfortunately I did not upgrade or change anything else to cause this, and was already on the latest NR3 prior to updating the Tasmota version.

I just updated my lights and the nodes stopped reporting, but everything else works.

Thanks for looking into it, if I ever figure out what caused this to happen when updating lights I'll report back.

DaveMDS commented 10 months ago

Any progress on this one?