Just did. 1.68 is broken also.
2 Likes
Below is the GitHub ticket. Can you post the requested logs there to help get it resolved?
Re-interviewing my devices got them back online.
1 Like
Confirm that 68 is borked too - no control of Fibaro devices.Rollback to 65 through a backup fixes it though.
Same - rolled back after 1.68 update and and now working again
EDIT: Went forward to 1.68 and ran a re-interview then a reboot and all seems working with latest updates.
I thought everything was working but my T6 thermostats werent reporting back properly. Tried to re-interview, then exclude and re-pair, but no luck. They just wouldnt operate properly. Rolled back to 1.65 and its operating properly again.
They really fubar’d things and I think they should just roll back to 1.65 and start over. At least it operates properly.
Having similar issues here. Managed to get most of the Dimers 2 and Doubles Switch 2s back with a re-interview and restart the add-on. However it also broke my Universal Binary sensors as they would not re-interview.
I posted a bug on Github and AlCalzone has come back very quickly with a fix. 0.1.70. I am not around to try it for a day or so. Any one else OK to try it?
Yes, Al has been super helpful. I was involved with one of those Github cases too. However, the good news is that this seems to be a bug that has been found and fixed. Here is the PR, and hopefully it will be implemented in the next core update tomorrow.
Fingers crossed that this fixes the issue. It looks right to me, but I am not a Zwave/HA expert.
Edit: As an aside, based on the description here, this could actually improve Zwave thermostat responsiveness in HA as well! We will see.
No luck with 0.1.70 either unfortunately. Rolling back to 0.1.65
I just upgraded to Home Assistant 2022.9 and my T6 z-wave thermostat issue is resolved. As an added bonus, HA responds faster to changes too.
1 Like
2022.9 solved my issue also.
I tried the upgrade to Home Assistant 2022.9 as well. Since one of the breaking changes was to have at least version 0.1.66 (zwave_js addon), I upgraded to version 0.1.70 (of zwave_js addon) [2022.9: Home Assistant Birthday Release! - Home Assistant]
The outcome from this exercise was, as I feared, a broken z-wave configuration. In my case I had to role back to
- Home Assistant 2022.8
- zwave_js addon 0.1.65
Restarting my Home Assistant server (or the entire Z-wave network) had no effect.
For me, the latest version of zwave_js addon that works is 0.1.65.
Did you take any, not mentioned, magic steps to make it work @jl_678 and @Rich37804 ? 
You may have to re-interview your devices.
I was running 1.65 and 2022.8 prior to the upgrade. I upgraded yesterday, and HA went to 2022.9 and zwave_js was automatically upgraded too.
After rebooting, things just came back. I did not need to reinterview anything. To be fair, it took a few minutes for the ZJS server to reload. In the past, I did not realize that it could take up to 5 minutes for the ZJS server to start.
I retried this with almost exactly the same steps. Anyway, now I have Home Assistant 2022.9 and the 0.1.70 version of the zwave_js addon (I had to update this manually).
After this I “HEAL NETWORK” followed by a system reboot:
Observations:
- If I try to switch on, for example, my first z-wave-switch from the GUI, it takes about 3 seconds and then it bounces back to the source setting. The real z-wave device is not affected
- If I switch on the real z-wave device on with a physical button, it takes less than 2 s before the action is reflected in the GUI
Here is an excerpt of my z-wave addon log after trying to switch a state from the GUI:
2022-09-08T18:25:16.594Z CNTRLR [Node 003] Timed out while waiting for a response from the node (ZW0201)
2022-09-08T18:25:38.766Z CNTRLR [Node 004] Timed out while waiting for a response from the node (ZW0201)
2022-09-08T18:25:41.449Z CNTRLR [Node 002] Timed out while waiting for a response from the node (ZW0201)
2022-09-08T18:25:42.670Z CNTRLR [Node 005] Timed out while waiting for a response from the node (ZW0201)
2022-09-08T18:25:43.822Z CNTRLR [Node 006] Timed out while waiting for a response from the node (ZW0201)
2022-09-08T18:25:45.022Z CNTRLR [Node 010] Timed out while waiting for a response from the node (ZW0201)
2022-09-08T18:25:46.118Z CNTRLR [Node 009] Timed out while waiting for a response from the node (ZW0201)
2022-09-08T18:25:47.486Z CNTRLR [Node 008] Timed out while waiting for a response from the node (ZW0201)
2022-09-08T18:25:48.629Z CNTRLR [Node 011] Timed out while waiting for a response from the node (ZW0201)
2022-09-08T18:25:49.786Z CNTRLR [Node 012] Timed out while waiting for a response from the node (ZW0201)
2022-09-08T18:25:51.045Z CNTRLR [Node 013] Timed out while waiting for a response from the node (ZW0201)
2022-09-08T18:25:56.074Z CNTRLR [Node 014] Timed out while waiting for a response from the node (ZW0201)
2022-09-08T18:26:47.657Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2022-09-08T18:26:48.882Z CNTRLR [Node 003] Timed out while waiting for a response from the node (ZW0201)
2022-09-08T18:28:22.004Z CNTRLR [Node 003] Timed out while waiting for a response from the node (ZW0201)
2022-09-08T18:28:45.911Z CNTRLR [Node 003] Timed out while waiting for a response from the node (ZW0201)
What else could be tried?
Reinterview the device. Select the entity, next to configure you will see the 3 dot menu icon. Select that then re-interview.
1 Like