I think there’s a regression in the latest ZwaveJS to MQTT addon. When I update to 0.46.0 my Honeywell T6 Zwave thermostats stop working properly, the setpoints no longer get updated in Home Assistant (which is then breaking other automation and creating user confusion due to inaccurate data).
I’m unsure where to open a bug report because the ZwaveJS to MQTT says to open it under HA Core unless someone specifically says otherwise, but I can reproduce this behavior updating ONLY ZwaveJS to MQTT and fix it by rolling back ONLY ZwaveJS to MQTT.
Test procedure:
Access a thermostat lovelace card
Increase or decrease a setpoint
Observe the actual device updates its setpoint
Observe lovelace card reverts to previous displayed setpoint
For troubleshooting, I also disabled my automation that sends updated values to the thermostat and the problem persists using just the climate entity to manipulate the temperature and no automation.
In my case, I am adjusting the “upstairs” thermostat and its Zwave ID 29. I’ve attached the log and the lovelace side by side so you can see the difference. In both cases I tried to adjust the heat and cool setpiont by 2 degrees. It doesn’t matter if you use the pop-out menu up/down or drag the dot around the circle the result is the same.
0.45.0:
Pushed 75 → 77
Pushed 69 → 67
After a moment, the thermostat and lovelace reflect the correct values
0.45.0:
Pushed 77 → 75
Pushed 67 → 69
After a moment, the thermostat on the wall shows the new setpoints, but Lovelace reverts back to the previous values.
Here is what the history also looks like on a normal day (4 “scheduled setpoints” plus a lot of tweaking depending on individual room temps being high or low) before and after - you can see with one exception (I think I restarted or something) it just stops reporting the setpoint values from then forward. Before the update you can clearly see each time-of-day change, the home/away mid-day change, the up/down jitter as my automations increment/decrement it to account for rooms being hotter/colder vs the thermostat. After the update its more or less a flat line.
Thanks for the detailed post. I was setting up my T6 thermostat using the HA zwavejs2mqtt add-on and noticed the same behavior. Under that version (v0.4.6) of the add-on the HA climate card does not sync the thermostat state as expected. Commands do appear to be passed from HA to the unit successfully.
Looking at the changelog for 0.46.0, the issue likely is either (1) the upgrade to zwavejs2mqtt to 7.0.0, or (2) the upgrade of the add-on base image to 12.2.3.
This is also broken for me the same exact way. I noticed if you go into the zwaveJS addon site and click
“refresh” for the section about setpoints it then updates HA.
Will be fixed in HA 2022.9, or downgrade to an add-on (restore backup) that has Z-Wave JS version 9.6.2 or lower, or use standalone zwavejs2mqtt v6.16.0.
Let me just add that all my Fibaro FGS-22x stopped working as well after the upgrade. Their state is recognized, but they do not perform the expected action (turn on / off).
Same here. I have around 35 Fibaro FGS-22x and FGD-22x modules and aroung 5 Aeotech nano modules. The Fibaro modules stopped responding (ZwaveJS2MQTT shows the instruction is sent to the node) but no state change happens. No problem with the Aeotec modules. This was on both 0.46.0 and 0.46.1
Still having same issue with the Fibaro modules after updating to 2022.9.2 and ZwaveJS2MQTT 0.46.1.
Aeotec devices perform as expected, but the Fibaro ones don’t change state.
ZwaveJS2MQTT logs show the server is successfully sending the commands, but the nodes don’t action them.
2022-09-12 21:42:47.536 INFO ZWAVE: Node 50: value updated: 38-1-currentValue 0 => 97
2022-09-12 21:42:47.537 INFO ZWAVE: Node 50: value updated: 38-1-targetValue 255 => 97
Thanks for the tip, yes after re-interviewing the devices all but two came back. I then re-interviewed those two again and they started to work correctly.
HA still wasn’t updating the status, but a restart fixed that.
