Z-Wave devices not updating status after shift to new controller

Configuration Z-Wave
1

Hi everyone, i’ve got a bit of a frustrating situation going on where after following a guide to move my Z-Wave devices from an Aeotec 500 series controller to a Zooz 700 series by using the shift function in PC Controller, my devices are no longer updating their statuses in Home Assistant.

The migration went fine and aside from the controller no longer being at node 1 (which I don’t believe is an issue) everything works fine when turning devices on and off from HA, but when turning them on/off manually from the switch, Home Assistant no longer updates the status.

I have run network healing and re-interviewed all nodes a couple of times. I have also shutdown my HA server and tried removing/re-connecting the controller, but unfortunately the issue persists.

As mentioned, i’m using a Zooz ZST10 700 series controller running firmware 7.18.3, which is connected via a 1m USB extension cable. I’m running HA 2023.9.2, Z-Wave JS 1.31.0 driver 11.14.2, Z-Wave JS UI 1.15.10

Below are some debug logs from turning a light on/off from HA and then again from the switch. It’s worth noting that I don’t see any logs at all when manually pressing the switch.

Subscribed to Z-Wave JS log messages…
2023-09-13T04:45:12.805Z DRIVER   all queues busy
2023-09-13T04:45:12.812Z SERIAL » 0x0103003bc7                                                         (5 bytes)
2023-09-13T04:45:12.813Z DRIVER » [REQ] [GetBackgroundRSSI]
2023-09-13T04:45:12.818Z SERIAL « [ACK]                                                                   (0x06)
2023-09-13T04:45:12.821Z SERIAL « 0x0107013b9b95957f26                                                 (9 bytes)
2023-09-13T04:45:12.823Z SERIAL » [ACK]                                                                   (0x06)
2023-09-13T04:45:12.826Z DRIVER « [RES] [GetBackgroundRSSI]
                                    channel 0: -101 dBm
                                    channel 1: -107 dBm
                                    channel 2: -107 dBm
2023-09-13T04:45:12.834Z DRIVER   all queues idle
2023-09-13T04:45:38.198Z DRIVER   all queues busy
2023-09-13T04:45:38.204Z SERIAL » 0x011000a9007200310298402500000000807a                              (18 bytes)
2023-09-13T04:45:38.205Z DRIVER » [Node 049] [REQ] [SendDataBridge]
                                  │ source node id:   114
                                  │ transmit options: 0x25
                                  │ callback id:      128
                                  └─[SecurityCCNonceGet]
2023-09-13T04:45:38.212Z SERIAL « [ACK]                                                                   (0x06)
2023-09-13T04:45:38.214Z SERIAL « 0x010401a90152                                                       (6 bytes)
2023-09-13T04:45:38.216Z SERIAL » [ACK]                                                                   (0x06)
2023-09-13T04:45:38.218Z DRIVER « [RES] [SendDataBridge]
                                    was sent: true
2023-09-13T04:45:38.229Z SERIAL « 0x011d00a98000000100cf7f7f7f7f00000300000000030100007f7f7f7f7f7b    (31 bytes)
2023-09-13T04:45:38.230Z SERIAL » [ACK]                                                                   (0x06)
2023-09-13T04:45:38.233Z DRIVER « [REQ] [SendDataBridge]
                                    callback id:            128
                                    transmit status:        OK, took 10 ms
                                    routing attempts:       1
                                    protocol & route speed: Z-Wave, 100 kbit/s
                                    routing scheme:         LWR
                                    ACK RSSI:               -49 dBm
                                    ACK channel no.:        0
                                    TX channel no.:         0
2023-09-13T04:45:38.243Z SERIAL « 0x011800a800007200310a9880ed3f748bc3fd2fc300cf007f7f2e              (26 bytes)
2023-09-13T04:45:38.245Z SERIAL » [ACK]                                                                   (0x06)
2023-09-13T04:45:38.247Z DRIVER « [Node 049] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -49 dBm
                                  └─[SecurityCCNonceReport]
                                      nonce: 0xed3f748bc3fd2fc3
2023-09-13T04:45:38.250Z SERIAL » 0x012900a9007200311b98811df43e3615b42d51b264d264483efc11ed2102e7ec2 (43 bytes)
                                  a907b8a250000000081d3
2023-09-13T04:45:38.252Z DRIVER » [Node 049] [REQ] [SendDataBridge]
                                  │ source node id:   114
                                  │ transmit options: 0x25
                                  │ callback id:      129
                                  └─[SecurityCCCommandEncapsulation]
                                    │ nonce id: 237
                                    └─[MultiChannelCCCommandEncapsulation]
                                      │ source:      0
                                      │ destination: 2
                                      └─[BinarySwitchCCSet]
                                          target value: true
2023-09-13T04:45:38.259Z SERIAL « [ACK]                                                                   (0x06)
2023-09-13T04:45:38.260Z SERIAL « 0x010401a90152                                                       (6 bytes)
2023-09-13T04:45:38.261Z SERIAL » [ACK]                                                                   (0x06)
2023-09-13T04:45:38.261Z DRIVER « [RES] [SendDataBridge]
                                    was sent: true
2023-09-13T04:45:38.277Z SERIAL « 0x011d00a98100000100cf7f7f7f7f00000300000000030100007f7f7f7f7f7a    (31 bytes)
2023-09-13T04:45:38.278Z SERIAL » [ACK]                                                                   (0x06)
2023-09-13T04:45:38.278Z DRIVER « [REQ] [SendDataBridge]
                                    callback id:            129
                                    transmit status:        OK, took 10 ms
                                    routing attempts:       1
                                    protocol & route speed: Z-Wave, 100 kbit/s
                                    routing scheme:         LWR
                                    ACK RSSI:               -49 dBm
                                    ACK channel no.:        0
                                    TX channel no.:         0
2023-09-13T04:45:38.280Z CNTRLR   [Node 049] [+] [Binary Switch] targetValue: true                  [Endpoint 2]
2023-09-13T04:45:38.282Z CNTRLR   [Node 049] [~] [Binary Switch] currentValue: false => true        [Endpoint 2]
2023-09-13T04:45:38.286Z DRIVER   all queues idle
2023-09-13T04:45:39.289Z DRIVER   all queues busy
2023-09-13T04:45:39.292Z SERIAL » 0x011000a90072003102984025000000008278                              (18 bytes)
2023-09-13T04:45:39.294Z DRIVER » [Node 049] [REQ] [SendDataBridge]
                                  │ source node id:   114
                                  │ transmit options: 0x25
                                  │ callback id:      130
                                  └─[SecurityCCNonceGet]
2023-09-13T04:45:39.300Z SERIAL « [ACK]                                                                   (0x06)
2023-09-13T04:45:39.302Z SERIAL « 0x010401a90152                                                       (6 bytes)
2023-09-13T04:45:39.304Z SERIAL » [ACK]                                                                   (0x06)
2023-09-13T04:45:39.307Z DRIVER « [RES] [SendDataBridge]
                                    was sent: true
2023-09-13T04:45:39.316Z SERIAL « 0x011d00a98200000100cf7f7f7f7f00000300000000030100007f7f7f7f7f79    (31 bytes)
2023-09-13T04:45:39.318Z SERIAL » [ACK]                                                                   (0x06)
2023-09-13T04:45:39.320Z DRIVER « [REQ] [SendDataBridge]
                                    callback id:            130
                                    transmit status:        OK, took 10 ms
                                    routing attempts:       1
                                    protocol & route speed: Z-Wave, 100 kbit/s
                                    routing scheme:         LWR
                                    ACK RSSI:               -49 dBm
                                    ACK channel no.:        0
                                    TX channel no.:         0
2023-09-13T04:45:40.357Z CNTRLR   [Node 049] Timed out while waiting for a response from the node (ZW0201)
2023-09-13T04:45:40.360Z DRIVER   all queues idle
2023-09-13T04:45:43.098Z SERIAL « 0x011800a800007200310a98805892f50ca41e966400cf007f7faa              (26 bytes)
2023-09-13T04:45:43.101Z SERIAL » [ACK]                                                                   (0x06)
2023-09-13T04:45:43.104Z DRIVER « [Node 049] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -49 dBm
                                  └─[SecurityCCNonceReport]
                                      nonce: 0x5892f50ca41e9664
2023-09-13T04:45:43.630Z DRIVER   all queues busy
2023-09-13T04:45:43.633Z SERIAL » 0x011000a900720038027204250000000083de                              (18 bytes)
2023-09-13T04:45:43.635Z DRIVER » [Node 056] [REQ] [SendDataBridge]
                                  │ source node id:   114
                                  │ transmit options: 0x25
                                  │ callback id:      131
                                  └─[ManufacturerSpecificCCGet]
2023-09-13T04:45:43.641Z SERIAL « [ACK]                                                                   (0x06)
2023-09-13T04:45:43.643Z SERIAL « 0x010401a90152                                                       (6 bytes)
2023-09-13T04:45:43.645Z SERIAL » [ACK]                                                                   (0x06)
2023-09-13T04:45:43.648Z DRIVER « [RES] [SendDataBridge]
                                    was sent: true
2023-09-13T04:45:43.702Z SERIAL « 0x011d00a98300000502ae7f7f7f7f00000326640000030100007f7f7f7f7f5d    (31 bytes)
2023-09-13T04:45:43.704Z SERIAL » [ACK]                                                                   (0x06)
2023-09-13T04:45:43.707Z DRIVER « [REQ] [SendDataBridge]
                                    callback id:            131
                                    transmit status:        OK, took 50 ms
                                    repeater node IDs:      38, 100
                                    routing attempts:       1
                                    protocol & route speed: Z-Wave, 100 kbit/s
                                    routing scheme:         LWR
                                    ACK RSSI:               -82 dBm
                                    ACK RSSI on repeaters:  N/A, N/A
                                    ACK channel no.:        0
                                    TX channel no.:         0
2023-09-13T04:45:43.772Z SERIAL « 0x011600a80000720038087205010f0102300000ae007f7fe7                  (24 bytes)
2023-09-13T04:45:43.774Z SERIAL » [ACK]                                                                   (0x06)
2023-09-13T04:45:43.777Z CNTRLR   [Node 056] [~] [Manufacturer Specific] manufacturerId: 271 => 271 [Endpoint 0]
2023-09-13T04:45:43.783Z CNTRLR   [Node 056] [~] [Manufacturer Specific] productType: 258 => 258    [Endpoint 0]
2023-09-13T04:45:43.786Z CNTRLR   [Node 056] [~] [Manufacturer Specific] productId: 12288 => 12288  [Endpoint 0]
2023-09-13T04:45:43.789Z DRIVER « [Node 056] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -82 dBm
                                  └─[ManufacturerSpecificCCReport]
                                      manufacturer id: 0x010f
                                      product type:    0x0102
                                      product id:      0x3000
2023-09-13T04:45:43.801Z SERIAL » 0x011000a90072003802861125000000008438                              (18 bytes)
2023-09-13T04:45:43.802Z DRIVER » [Node 056] [REQ] [SendDataBridge]
                                  │ source node id:   114
                                  │ transmit options: 0x25
                                  │ callback id:      132
                                  └─[VersionCCGet]
2023-09-13T04:45:43.810Z SERIAL « [ACK]                                                                   (0x06)
2023-09-13T04:45:43.812Z SERIAL « 0x010401a90152                                                       (6 bytes)
2023-09-13T04:45:43.812Z SERIAL » [ACK]                                                                   (0x06)
2023-09-13T04:45:43.814Z DRIVER « [RES] [SendDataBridge]
                                    was sent: true
2023-09-13T04:45:43.907Z SERIAL « 0x011d00a98400000902ad7f7f7f7f00000326640000030100007f7f7f7f7f55    (31 bytes)
2023-09-13T04:45:43.908Z SERIAL » [ACK]                                                                   (0x06)
2023-09-13T04:45:43.910Z DRIVER « [REQ] [SendDataBridge]
                                    callback id:            132
                                    transmit status:        OK, took 90 ms
                                    repeater node IDs:      38, 100
                                    routing attempts:       1
                                    protocol & route speed: Z-Wave, 100 kbit/s
                                    routing scheme:         LWR
                                    ACK RSSI:               -83 dBm
                                    ACK RSSI on repeaters:  N/A, N/A
                                    ACK channel no.:        0
                                    TX channel no.:         0
2023-09-13T04:45:43.982Z SERIAL « 0x011900a800007200380b861203041803050201030500ae007f7f29            (27 bytes)
2023-09-13T04:45:43.985Z SERIAL » [ACK]                                                                   (0x06)
2023-09-13T04:45:43.987Z CNTRLR   [Node 056] [~] [Version] libraryType: 3 => 3                      [Endpoint 0]
2023-09-13T04:45:43.991Z CNTRLR   [Node 056] [~] [Version] protocolVersion: "4.24" => "4.24"        [Endpoint 0]
2023-09-13T04:45:43.995Z CNTRLR   [Node 056] [~] [Version] firmwareVersions: 3.5,3.5 => 3.5,3.5     [Endpoint 0]
2023-09-13T04:45:43.998Z CNTRLR   [Node 056] [~] [Version] hardwareVersion: 2 => 2                  [Endpoint 0]
2023-09-13T04:45:44.001Z DRIVER « [Node 056] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -82 dBm
                                  └─[VersionCCReport]
                                      library type:      Enhanced Slave
                                      protocol version:  4.24
                                      firmware versions: 3.5, 3.5
                                      hardware version:  2
2023-09-13T04:45:44.039Z DRIVER   all queues idle
2023-09-13T04:45:48.679Z DRIVER   all queues busy
2023-09-13T04:45:48.683Z SERIAL » 0x011000a9007200310298402500000000857f                              (18 bytes)
2023-09-13T04:45:48.685Z DRIVER » [Node 049] [REQ] [SendDataBridge]
                                  │ source node id:   114
                                  │ transmit options: 0x25
                                  │ callback id:      133
                                  └─[SecurityCCNonceGet]
2023-09-13T04:45:48.691Z SERIAL « [ACK]                                                                   (0x06)
2023-09-13T04:45:48.694Z SERIAL « 0x010401a90152                                                       (6 bytes)
2023-09-13T04:45:48.696Z SERIAL » [ACK]                                                                   (0x06)
2023-09-13T04:45:48.698Z DRIVER « [RES] [SendDataBridge]
                                    was sent: true
2023-09-13T04:45:48.708Z SERIAL « 0x011d00a98500000100ce7f7f7f7f00000300000000030100007f7f7f7f7f7f    (31 bytes)
2023-09-13T04:45:48.709Z SERIAL » [ACK]                                                                   (0x06)
2023-09-13T04:45:48.710Z DRIVER « [REQ] [SendDataBridge]
                                    callback id:            133
                                    transmit status:        OK, took 10 ms
                                    routing attempts:       1
                                    protocol & route speed: Z-Wave, 100 kbit/s
                                    routing scheme:         LWR
                                    ACK RSSI:               -50 dBm
                                    ACK channel no.:        0
                                    TX channel no.:         0
2023-09-13T04:45:48.716Z SERIAL « 0x011800a800007200310a988005f2f70aa571b1b100d0007f7f10              (26 bytes)
2023-09-13T04:45:48.717Z SERIAL » [ACK]                                                                   (0x06)
2023-09-13T04:45:48.719Z DRIVER « [Node 049] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -48 dBm
                                  └─[SecurityCCNonceReport]
                                      nonce: 0x05f2f70aa571b1b1
2023-09-13T04:45:48.721Z SERIAL » 0x012900a9007200311b9881b3f9d0ce502f22778c9fb7ba23da287d059e2e859fb (43 bytes)
                                  104729c250000000086a5
2023-09-13T04:45:48.722Z DRIVER » [Node 049] [REQ] [SendDataBridge]
                                  │ source node id:   114
                                  │ transmit options: 0x25
                                  │ callback id:      134
                                  └─[SecurityCCCommandEncapsulation]
                                    │ nonce id: 5
                                    └─[MultiChannelCCCommandEncapsulation]
                                      │ source:      0
                                      │ destination: 2
                                      └─[BinarySwitchCCSet]
                                          target value: false
2023-09-13T04:45:48.730Z SERIAL « [ACK]                                                                   (0x06)
2023-09-13T04:45:48.731Z SERIAL « 0x010401a90152                                                       (6 bytes)
2023-09-13T04:45:48.731Z SERIAL » [ACK]                                                                   (0x06)
2023-09-13T04:45:48.732Z DRIVER « [RES] [SendDataBridge]
                                    was sent: true
2023-09-13T04:45:48.748Z SERIAL « 0x011d00a98600000100ce7f7f7f7f00000300000000030100007f7f7f7f7f7c    (31 bytes)
2023-09-13T04:45:48.748Z SERIAL » [ACK]                                                                   (0x06)
2023-09-13T04:45:48.749Z DRIVER « [REQ] [SendDataBridge]
                                    callback id:            134
                                    transmit status:        OK, took 10 ms
                                    routing attempts:       1
                                    protocol & route speed: Z-Wave, 100 kbit/s
                                    routing scheme:         LWR
                                    ACK RSSI:               -50 dBm
                                    ACK channel no.:        0
                                    TX channel no.:         0
2023-09-13T04:45:48.751Z CNTRLR   [Node 049] [~] [Binary Switch] currentValue: true => false        [Endpoint 2]
2023-09-13T04:45:48.753Z DRIVER   all queues idle
2023-09-13T04:45:49.757Z DRIVER   all queues busy
2023-09-13T04:45:49.763Z SERIAL » 0x011000a9007200310298402500000000877d                              (18 bytes)
2023-09-13T04:45:49.764Z DRIVER » [Node 049] [REQ] [SendDataBridge]
                                  │ source node id:   114
                                  │ transmit options: 0x25
                                  │ callback id:      135
                                  └─[SecurityCCNonceGet]
2023-09-13T04:45:49.778Z SERIAL « [ACK]                                                                   (0x06)
2023-09-13T04:45:49.780Z SERIAL « 0x010401a90152                                                       (6 bytes)
2023-09-13T04:45:49.782Z SERIAL » [ACK]                                                                   (0x06)
2023-09-13T04:45:49.784Z DRIVER « [RES] [SendDataBridge]
                                    was sent: true
2023-09-13T04:45:49.837Z SERIAL « 0x011d00a98700000600cf7f7f7f7f00000300000000030200007f7f7f7f7f78    (31 bytes)
2023-09-13T04:45:49.838Z SERIAL » [ACK]                                                                   (0x06)
2023-09-13T04:45:49.840Z DRIVER « [REQ] [SendDataBridge]
                                    callback id:            135
                                    transmit status:        OK, took 60 ms
                                    routing attempts:       2
                                    protocol & route speed: Z-Wave, 100 kbit/s
                                    routing scheme:         LWR
                                    ACK RSSI:               -49 dBm
                                    ACK channel no.:        0
                                    TX channel no.:         0
2023-09-13T04:45:50.927Z CNTRLR   [Node 049] Timed out while waiting for a response from the node (ZW0201)
2023-09-13T04:45:50.930Z DRIVER   all queues idle
2023-09-13T04:45:53.718Z SERIAL « 0x011800a800007200310a9880dd9ff2fd6bd4d8d100cf007f7f2a              (26 bytes)
2023-09-13T04:45:53.721Z SERIAL » [ACK]                                                                   (0x06)
2023-09-13T04:45:53.725Z DRIVER « [Node 049] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -49 dBm
                                  └─[SecurityCCNonceReport]
                                      nonce: 0xdd9ff2fd6bd4d8d1
2023-09-13T04:45:55.932Z DRIVER   all queues busy
2023-09-13T04:45:55.936Z SERIAL » 0x0103003bc7                                                         (5 bytes)
2023-09-13T04:45:55.937Z DRIVER » [REQ] [GetBackgroundRSSI]
2023-09-13T04:45:55.942Z SERIAL « [ACK]                                                                   (0x06)
2023-09-13T04:45:55.944Z SERIAL « 0x0107013b9b96967f26                                                 (9 bytes)
2023-09-13T04:45:55.946Z SERIAL » [ACK]                                                                   (0x06)
2023-09-13T04:45:55.949Z DRIVER « [RES] [GetBackgroundRSSI]
                                    channel 0: -101 dBm
                                    channel 1: -106 dBm
                                    channel 2: -106 dBm
2023-09-13T04:45:55.955Z DRIVER   all queues idle
2023-09-13T04:46:25.932Z DRIVER   all queues busy
2023-09-13T04:46:25.937Z SERIAL » 0x0103003bc7                                                         (5 bytes)
2023-09-13T04:46:25.938Z DRIVER » [REQ] [GetBackgroundRSSI]
2023-09-13T04:46:25.943Z SERIAL « [ACK]                                                                   (0x06)
2023-09-13T04:46:25.945Z SERIAL « 0x0107013b9a94957f26                                                 (9 bytes)
2023-09-13T04:46:25.947Z SERIAL » [ACK]                                                                   (0x06)
2023-09-13T04:46:25.949Z DRIVER « [RES] [GetBackgroundRSSI]
                                    channel 0: -102 dBm
                                    channel 1: -108 dBm
                                    channel 2: -107 dBm
2023-09-13T04:46:25.953Z DRIVER   all queues idle

Would really appreciate any insight and advise.
Thanks

2

I originally moved to the Zooz stick due to my Z-wave network randomly becoming unresponsive. In researching the issue I mentioned above, I came across this issue Zwave · Issue #99736 · home-assistant/core · GitHub which is exactly what I was experiencing. As it seems that issue is now reolved, I’ve since restored the backup to my Aeotec controller and everything is working correctly again.

3

This may be the problem:

By default zwave devices send updates to the LifeLine which is Node 1; since your controller is no longer node 1 the controller is not going to receive it, Go into zwave ui for one of the switches and look at the default association. Try to edit this to add the new controller ID or replace the old controller id with the new one.

1 Like
4

Hi, thanks so much for taking the time to respond. That’s a very interesting point and while i’m not new to Z-wave, i’ll admit I’m definitely not across the deeper, more technical side of it’s operation. I had seen posts where other users had migrated controllers using the same method and the controller was no longer node 1, who initially had issues with devices not updating status, but a re-interview solved it.

Unfortunately, the only method I had found which allows changing the node number is to create a bunch of virtual nodes (up to 232) so that adding the controller back again would force it to node 1. The 500 series controller I had did not allow for that function, however I’ve just received an 800 series, so will try again by migrating the 500 to 700, then the 700 to 800 which should leave me with the 800 series on node 1. The speed and range of the 700 series controller was noticeably better, so I’m eager to switch controllers, but not at the cost of function and reliability.

Will update again once i’ve made the change again.

5

Every Z-Wave Plus device has a lifeline association. This is how devices know what node id to report information to. This is why your devices are not reporting.

In the Z-WaveJSUI Control Panel you can edit the associations for your devices. All you would need to do is delete the entry for node id 1 and add a new entry for the new node #.

Depending on how many devices you have you may want to use the Simplicity Studio Z-Wave PC Controller Software. In the software you can add and remove associations from multiple devices at once instead of one at a time like in Z-WaveJSUI.

6

Thanks, this makes perfect sense. It was actually your video I was following - and thanks for a great tutorial by the way - but as I mentioned, the 500 series controller I had did not allow the creation of a virtual node. I have since performed the shift again and have the new 800 series controller as node 1, however ZwaveJSUI is saying that that “auto-discovered functionality has changed since last interview; re-interview to update” with an orange re-interview button. Unfortunately pressing this does nothing and the controller just says starting re-interview then stopping straight away. My devices are also showing as unavailable.

I should note that i’ve updated the USB serial port, done a heal and re-interview of the nodes

7

A subsequent re-interview of all nodes now has them back online, but the controller still has the message about the auto-discovered functionality being changed. Not sure if this is an issue or not.