Zwave JS issue past 0.1.65

Configuration Z-Wave
1

I have an aeotec 5 stick and Figaro fgs223 relays, anything past version 65 basically doesn’t work (not using zwave2mqtt)

Log
Z-Wave JS
· UNKNOWN_FUNC_LOCK_ROUTE_RESPONSE (0x90)
· UNKNOWN_FUNC_GET_PRIORITY_ROUTE (0x92)
· UNKNOWN_FUNC_SET_PRIORITY_ROUTE (0x93)
· UNKNOWN_FUNC_UNKNOWN_0x98 (0x98)
· UNKNOWN_FUNC_UNKNOWN_0xB4 (0xb4)
· UNKNOWN_FUNC_WATCH_DOG_ENABLE (0xb6)
· UNKNOWN_FUNC_WATCH_DOG_DISABLE (0xb7)
· UNKNOWN_FUNC_WATCH_DOG_KICK (0xb8)
· UNKNOWN_FUNC_UNKNOWN_0xB9 (0xb9)
· UNKNOWN_FUNC_RF_POWERLEVEL_GET (0xba)
· UNKNOWN_FUNC_GET_LIBRARY_TYPE (0xbd)
· UNKNOWN_FUNC_SEND_TEST_FRAME (0xbe)
· UNKNOWN_FUNC_GET_PROTOCOL_STATUS (0xbf)
· UNKNOWN_FUNC_UNKNOWN_0xD2 (0xd2)
· UNKNOWN_FUNC_UNKNOWN_0xD3 (0xd3)
· UNKNOWN_FUNC_UNKNOWN_0xD4 (0xd4)
· undefined (0xee)
· UNKNOWN_FUNC_UNKNOWN_0xEF (0xef)
2022-09-04T10:56:46.037Z CNTRLR querying version info…
2022-09-04T10:56:46.049Z CNTRLR received version info:
controller type: Static Controller
library version: Z-Wave 3.95
2022-09-04T10:56:46.049Z CNTRLR querying protocol version info…
2022-09-04T10:56:46.066Z CNTRLR received protocol version info:
protocol type: Z-Wave
protocol version: 3.95.0
2022-09-04T10:56:46.067Z CNTRLR supported Z-Wave features:
2022-09-04T10:56:46.067Z CNTRLR querying controller capabilities…
2022-09-04T10:56:46.076Z CNTRLR received controller capabilities:
controller role: primary
is the SUC: true
started this network: true
SIS is present: true
was real primary: true
2022-09-04T10:56:46.077Z CNTRLR finding SUC…
2022-09-04T10:56:46.094Z CNTRLR This is the SUC
2022-09-04T10:56:46.095Z CNTRLR querying additional controller information…
2022-09-04T10:56:46.212Z CNTRLR received additional controller information:
Z-Wave API version: 5 (legacy)
Z-Wave chip type: ZW050x
node type Controller
controller role: primary
controller is the SIS: true
controller supports timers: false
nodes in the network: 1, 56, 57, 58, 59, 61, 62, 63, 64
2022-09-04T10:56:46.238Z CNTRLR [Node 001] Embedded device config loaded
2022-09-04T10:56:46.247Z CNTRLR [Node 056] Embedded device config loaded
2022-09-04T10:56:46.258Z CNTRLR [Node 057] Embedded device config loaded
2022-09-04T10:56:46.270Z CNTRLR [Node 058] Embedded device config loaded
2022-09-04T10:56:46.279Z CNTRLR [Node 059] Embedded device config loaded
2022-09-04T10:56:46.288Z CNTRLR [Node 061] Embedded device config loaded
2022-09-04T10:56:46.297Z CNTRLR [Node 062] Embedded device config loaded
2022-09-04T10:56:46.305Z CNTRLR [Node 063] Embedded device config loaded
2022-09-04T10:56:46.314Z CNTRLR [Node 064] Embedded device config loaded
2022-09-04T10:56:46.321Z CNTRLR setting serial API timeouts: ack = 1000 ms, byte = 150 ms
2022-09-04T10:56:46.331Z CNTRLR serial API timeouts overwritten. The old values were: ack = 1000 ms, byte = 15
0 ms
2022-09-04T10:56:46.331Z CNTRLR Interview completed
Starting server on 0.0.0.0:3000
2022-09-04T10:56:46.342Z CNTRLR [Node 001] The node is alive.
2022-09-04T10:56:46.343Z CNTRLR [Node 001] The node is ready to be used
2022-09-04T10:56:46.344Z CNTRLR » [Node 056] pinging the node…
2022-09-04T10:56:46.388Z CNTRLR » [Node 057] pinging the node…
2022-09-04T10:56:46.389Z CNTRLR » [Node 058] pinging the node…
2022-09-04T10:56:46.391Z CNTRLR » [Node 059] pinging the node…
2022-09-04T10:56:46.398Z CNTRLR » [Node 061] pinging the node…
2022-09-04T10:56:46.399Z CNTRLR » [Node 062] pinging the node…
2022-09-04T10:56:46.401Z CNTRLR » [Node 063] pinging the node…
2022-09-04T10:56:46.402Z CNTRLR » [Node 064] pinging the node…
ZwaveJS server listening on 0.0.0.0:3000
2022-09-04T10:56:46.434Z CNTRLR [Node 056] The node is alive.
2022-09-04T10:56:46.434Z CNTRLR [Node 056] The node is ready to be used
2022-09-04T10:56:46.436Z CNTRLR « [Node 056] ping successful
2022-09-04T10:56:46.464Z CNTRLR [Node 057] The node is alive.
2022-09-04T10:56:46.464Z CNTRLR [Node 057] The node is ready to be used
2022-09-04T10:56:46.466Z CNTRLR « [Node 057] ping successful
2022-09-04T10:56:46.493Z CNTRLR [Node 058] The node is alive.
2022-09-04T10:56:46.493Z CNTRLR [Node 058] The node is ready to be used
2022-09-04T10:56:46.496Z CNTRLR « [Node 058] ping successful
2022-09-04T10:56:46.523Z CNTRLR [Node 059] The node is alive.
2022-09-04T10:56:46.523Z CNTRLR [Node 059] The node is ready to be used
2022-09-04T10:56:46.525Z CNTRLR « [Node 059] ping successful
2022-09-04T10:56:46.581Z CNTRLR [Node 061] The node is alive.
2022-09-04T10:56:46.582Z CNTRLR [Node 061] The node is ready to be used
2022-09-04T10:56:46.584Z CNTRLR « [Node 061] ping successful
2022-09-04T10:56:46.736Z CNTRLR [Node 062] The node is alive.
2022-09-04T10:56:46.736Z CNTRLR [Node 062] The node is ready to be used
2022-09-04T10:56:46.739Z CNTRLR « [Node 062] ping successful
2022-09-04T10:56:46.939Z CNTRLR [Node 063] The node is alive.
2022-09-04T10:56:46.940Z CNTRLR [Node 063] The node is ready to be used
2022-09-04T10:56:46.942Z CNTRLR « [Node 063] ping successful
2022-09-04T10:56:46.999Z CNTRLR [Node 064] The node is alive.
2022-09-04T10:56:47.000Z CNTRLR [Node 064] The node is ready to be used
2022-09-04T10:56:47.000Z CNTRLR All nodes are ready to be used
2022-09-04T10:56:47.001Z CNTRLR « [Node 064] ping successful
New client
2022-09-04T10:57:13.293Z CNTRLR [Node 062] Timed out while waiting for a response from the node (ZW0201)
2022-09-04T10:57:26.827Z CNTRLR [Node 062] Timed out while waiting for a response from the node (ZW0201)
2022-09-04T10:57:34.348Z CNTRLR [Node 062] Timed out while waiting for a response from the node (ZW0201)
2022-09-04T10:57:40.722Z CNTRLR [Node 062] Timed out while waiting for a response from the node (ZW0201)

Any suggestions

2

Known issue - we have discussed in the 2022.8 Blog thread, and there are a number of posts on Github too.

See these for starters

Some people have success with re-interviewing devices, but I and others have had to restore backups, and revert to 0.1.65.

3

I have the same devices and had the same issue, I also rolled back to 0.1.65 for now.

FYI the new release 0.1.69 does not help.

4

Has any one tested 0.1.70?

5

I tried it and its still broken, I don’t have a working backup to go back to now :laughing:

Anyone know if I can reload 0.1.65, I could not find a way

6

I updated to 2022.9 and now all zwave is dead

7

Reinterview the devices. Go to the entity page, next to the configure button there is the 3 dot menu. Click that and re-interview the device.

8

I tried 0.1.70…

  1. Did a full backup
  2. Upgraded the ZWave-JS addon to 0.1.70
  3. As expected, the devices wouldn’t respond.
  4. I went through all the devices and did a re-interview. Took a few hours for it to complete.
  5. Some devices responded once, and then not, and others not at all ← at this point, I expected to have to role back to 0.1.65 again
  6. However, I tried a reboot of the server, and this worked. All devices are responding.

I have now upgraded to 2022.9 too and all is currently good.