JVorbeck
January 16, 2025, 9:03pm
1
I purchased a Zooz Zen17 800LR relay to use with my Home Assistant. I have a Z-Wave JS UI hub using a Zooz ZST39 800LR controller. My HA is v2025.1.2. The hub running Z-Wave JS UI for this controller is zwave-js-ui: 9.29.0.b8373a3 ; zwave-js: 14.3.7 and server 1.40.2.
The Zen17 was running FW 2.00. It will include, operate normally, and exclude normally utilizing the standard Z-Wave JS UI manual inclusion process. I need this device to operate in LR protocol mode due to the intended distance. I cannot get the device to include successfully using the SmartStart process. I have tried the device reset procedure and I have performed a hard reset on my controller. I have scanned the barcode using the HA app on my android to begin SmartStart, pasted in the QR code text manually into the JS UI provisioning page and manually typed in the DSK code on the provisioning page.
All I can get to occur is for the SmartStart inclusion process to begin upon powering up the Zen17, a new device to appear in the control panel page containing a device ID > 256 and the rest of the values are question marks. After perhaps a minute the process stops and that device disappears from the list.
I will typically have to delete the provisioning entry and reset the device to get it to reattempt smartstart inclusion again where it always fails. I included the device in regular mode again and pushed Zooz’s latest device firmware 1.20 to the unit to assist with troubleshooting. This however had no positive effect on the issue.
To note, I have a Zooz ZSE41 800LR window sensor that will perform a smartstart inclusion successfully to this hub and controller and operates as expected in LR mode. So it is something about this Zen17 device that’s causing trouble. I captured a debug log of the entire process and I will include it here.
I contacted Zooz technical support but since it includes successfully in Z-Wave mode they will provide no further support and recommended that I come here for assistance. If anyone here would be interested in looking at the debug log and offering a suggestion I would be most appreciative!
JVorbeck
January 16, 2025, 9:04pm
2
2025-01-16T01:57:17.225Z CNTRLR Enabling Smart Start listening mode...
2025-01-16T01:57:17.236Z DRIVER one or more queues busy
2025-01-16T01:57:17.247Z SERIAL » 0x0105004a4900f9 (7 bytes)
2025-01-16T01:57:17.250Z DRIVER » [REQ] [AddNodeToNetwork]
action: Enable Smart Start listening mode
2025-01-16T01:57:17.267Z SERIAL « [ACK] (0x06)
2025-01-16T01:57:17.276Z CNTRLR Smart Start listening mode enabled
2025-01-16T01:57:17.283Z DRIVER all queues idle
2025-01-16T01:57:36.428Z DRIVER one or more queues busy
2025-01-16T01:57:36.440Z SERIAL » 0x0103003bc7 (5 bytes)
2025-01-16T01:57:36.442Z DRIVER » [REQ] [GetBackgroundRSSI]
2025-01-16T01:57:36.451Z SERIAL « [ACK] (0x06)
2025-01-16T01:57:36.456Z SERIAL « 0x0107013b9e9696a4f8 (9 bytes)
2025-01-16T01:57:36.460Z SERIAL » [ACK] (0x06)
2025-01-16T01:57:36.468Z DRIVER « [RES] [GetBackgroundRSSI]
channel 0: -98 dBm
channel 1: -106 dBm
channel 2: -106 dBm
channel 3: -92 dBm
2025-01-16T01:57:36.476Z DRIVER all queues idle
2025-01-16T01:58:06.428Z DRIVER one or more queues busy
2025-01-16T01:58:06.441Z SERIAL » 0x0103003bc7 (5 bytes)
2025-01-16T01:58:06.443Z DRIVER » [REQ] [GetBackgroundRSSI]
2025-01-16T01:58:06.452Z SERIAL « [ACK] (0x06)
2025-01-16T01:58:06.458Z SERIAL « 0x0107013b9f989880dd (9 bytes)
2025-01-16T01:58:06.462Z SERIAL » [ACK] (0x06)
2025-01-16T01:58:06.471Z DRIVER « [RES] [GetBackgroundRSSI]
channel 0: -97 dBm
channel 1: -104 dBm
channel 2: -104 dBm
channel 3: -128 dBm
2025-01-16T01:58:06.480Z DRIVER all queues idle
2025-01-16T01:58:36.430Z DRIVER one or more queues busy
2025-01-16T01:58:36.442Z SERIAL » 0x0103003bc7 (5 bytes)
2025-01-16T01:58:36.444Z DRIVER » [REQ] [GetBackgroundRSSI]
2025-01-16T01:58:36.452Z SERIAL « [ACK] (0x06)
2025-01-16T01:58:36.458Z SERIAL « 0x0107013b9d9b9b80df (9 bytes)
2025-01-16T01:58:36.462Z SERIAL » [ACK] (0x06)
2025-01-16T01:58:36.470Z DRIVER « [RES] [GetBackgroundRSSI]
channel 0: -99 dBm
channel 1: -101 dBm
channel 2: -101 dBm
channel 3: -128 dBm
2025-01-16T01:58:36.485Z DRIVER all queues idle
2025-01-16T01:58:42.124Z SERIAL « 0x011f004987000018cfdd71d6100310005e9f55258e5985866c736072877a5a703 (33 bytes)
f
2025-01-16T01:58:42.131Z SERIAL » [ACK] (0x06)
2025-01-16T01:58:42.138Z DRIVER « [REQ] [ApplicationUpdateRequest]
type: SmartStart_LongRange_HomeId_Received
remote node ID: 0
NWI home ID: 0xcfdd71d6
basic device class: End Node
generic device class: 16
specific device class: 0
supported CCs:
· Z-Wave Plus Info
· Security 2
· Transport Service
· Binary Switch
· Multi Channel Association
· Association Group Information
· Association
· Version
· Supervision
· Powerlevel
· Multi Channel
· Manufacturer Specific
· Indicator
· Firmware Update Meta Data
· Device Reset Locally
· Configuration
2025-01-16T01:58:42.143Z CNTRLR Received Smart Start inclusion request (Z-Wave Long Range)
2025-01-16T01:58:42.146Z CNTRLR NWI Home ID found in provisioning list, including node...
2025-01-16T01:58:42.149Z CNTRLR Including SmartStart node with DSK 48539-08529-26251-22278-36829-29142-38394-2
5132 using Z-Wave Long Range
2025-01-16T01:58:42.155Z DRIVER one or more queues busy
2025-01-16T01:58:42.164Z SERIAL » 0x010d004ae803cfdd71d615fa622d46 (15 bytes)
2025-01-16T01:58:42.168Z DRIVER » [REQ] [AddNodeToNetwork]
action: Add Smart Start node
NWI Home ID: 0xcfdd71d6
high power: true
network wide: true
protocol: Z-Wave Long Range
callback id: 3
2025-01-16T01:58:42.179Z SERIAL « [ACK] (0x06)
2025-01-16T01:58:42.192Z SERIAL « 0x0108004a0301000000bf (10 bytes)
2025-01-16T01:58:42.194Z SERIAL » [ACK] (0x06)
2025-01-16T01:58:42.202Z DRIVER « [REQ] [AddNodeToNetwork]
status: Ready
callback id: 3
2025-01-16T01:58:42.205Z DRIVER handling request AddNodeToNetwork (74)
2025-01-16T01:58:42.206Z DRIVER 1 handler registered!
2025-01-16T01:58:42.208Z DRIVER invoking handler #0
2025-01-16T01:58:42.209Z CNTRLR handling add node request (status = Ready)
2025-01-16T01:58:42.211Z DRIVER all queues idle
2025-01-16T01:58:46.131Z SERIAL « 0x0108004a0302000000bc (10 bytes)
2025-01-16T01:58:46.135Z SERIAL » [ACK] (0x06)
2025-01-16T01:58:46.140Z DRIVER « [REQ] [AddNodeToNetwork]
status: NodeFound
callback id: 3
2025-01-16T01:58:46.142Z DRIVER handling request AddNodeToNetwork (74)
2025-01-16T01:58:46.143Z DRIVER 1 handler registered!
2025-01-16T01:58:46.144Z DRIVER invoking handler #0
2025-01-16T01:58:46.145Z CNTRLR handling add node request (status = NodeFound)
2025-01-16T01:58:46.495Z SERIAL « 0x011b004a03030104130310005e9f55258e5985866c736072877a5a7014 (29 bytes)
2025-01-16T01:58:46.499Z SERIAL » [ACK] (0x06)
2025-01-16T01:58:46.504Z DRIVER « [REQ] [AddNodeToNetwork]
status: AddingSlave
callback id: 3
2025-01-16T01:58:46.506Z DRIVER handling request AddNodeToNetwork (74)
2025-01-16T01:58:46.507Z DRIVER 1 handler registered!
2025-01-16T01:58:46.508Z DRIVER invoking handler #0
2025-01-16T01:58:46.508Z CNTRLR handling add node request (status = AddingSlave)
2025-01-16T01:58:46.525Z DRIVER the message was handled
2025-01-16T01:58:46.536Z SERIAL « 0x011b004a03050104130310005e9f55258e5985866c736072877a5a7012 (29 bytes)
2025-01-16T01:58:46.539Z SERIAL » [ACK] (0x06)
2025-01-16T01:58:46.542Z DRIVER « [REQ] [AddNodeToNetwork]
status: ProtocolDone
callback id: 3
2025-01-16T01:58:46.544Z DRIVER handling request AddNodeToNetwork (74)
2025-01-16T01:58:46.545Z DRIVER 1 handler registered!
2025-01-16T01:58:46.546Z DRIVER invoking handler #0
2025-01-16T01:58:46.547Z CNTRLR handling add node request (status = ProtocolDone)
2025-01-16T01:58:46.549Z CNTRLR finishing inclusion process...
2025-01-16T01:58:46.554Z DRIVER one or more queues busy
2025-01-16T01:58:46.561Z SERIAL » 0x0105004ac50471 (7 bytes)
2025-01-16T01:58:46.564Z DRIVER » [REQ] [AddNodeToNetwork]
action: Stop
high power: true
network wide: true
callback id: 4
2025-01-16T01:58:46.574Z SERIAL « [ACK] (0x06)
2025-01-16T01:58:46.580Z SERIAL « 0x0108004a0406010400ba (10 bytes)
2025-01-16T01:58:46.583Z SERIAL » [ACK] (0x06)
2025-01-16T01:58:46.587Z DRIVER « [REQ] [AddNodeToNetwork]
status: Done
callback id: 4
2025-01-16T01:58:46.606Z SERIAL » 0x0105004ac50075 (7 bytes)
2025-01-16T01:58:46.609Z DRIVER » [REQ] [AddNodeToNetwork]
action: Stop
high power: true
network wide: true
callback id: 0
2025-01-16T01:58:46.617Z SERIAL « [ACK] (0x06)
2025-01-16T01:58:46.624Z CNTRLR The inclusion process was stopped
2025-01-16T01:58:46.635Z CNTRLR finished adding node 260:
basic device class: End Node
generic device class: Binary Switch
specific device class: Unused
supported CCs:
· Z-Wave Plus Info (0x5e)
· Security 2 (0x9f)
· Transport Service (0x55)
· Binary Switch (0x25)
· Multi Channel Association (0x8e)
· Association Group Information (0x59)
· Association (0x85)
· Version (0x86)
· Supervision (0x6c)
· Powerlevel (0x73)
· Multi Channel (0x60)
· Manufacturer Specific (0x72)
· Indicator (0x87)
· Firmware Update Meta Data (0x7a)
· Device Reset Locally (0x5a)
· Configuration (0x70)
controlled CCs:
2025-01-16T01:58:46.651Z SERIAL » 0x011000a900010104029f04250000000005fb (18 bytes)
2025-01-16T01:58:46.653Z DRIVER » [Node 260] [REQ] [SendDataBridge]
│ source node id: 1
│ transmit options: 0x25
│ callback id: 5
└─[Security2CCKEXGet]
2025-01-16T01:58:46.669Z SERIAL « [ACK] (0x06)
2025-01-16T01:58:46.674Z SERIAL « 0x010401a90152 (6 bytes)
2025-01-16T01:58:46.677Z SERIAL » [ACK] (0x06)
2025-01-16T01:58:46.681Z DRIVER « [RES] [SendDataBridge]
was sent: true
2025-01-16T01:58:46.743Z SERIAL « 0x011d00a905010008007f7f7f7f7f00030600000000040300000ea37f7f7fe8 (31 bytes)
2025-01-16T01:58:46.747Z SERIAL » [ACK] (0x06)
2025-01-16T01:58:46.754Z DRIVER « [REQ] [SendDataBridge]
callback id: 5
transmit status: NoAck, took 80 ms
routing attempts: 3
protocol & route speed: Z-Wave Long Range, 100 kbit/s
routing scheme: Resort to Direct
TX channel no.: 3
TX power: 14 dBm
measured noise floor: -93 dBm
2025-01-16T01:58:46.766Z SERIAL » 0x011000a900010104029f04250000000005fb (18 bytes)
2025-01-16T01:58:46.769Z DRIVER » [Node 260] [REQ] [SendDataBridge]
│ source node id: 1
│ transmit options: 0x25
│ callback id: 5
└─[Security2CCKEXGet]
2025-01-16T01:58:46.775Z SERIAL « [ACK] (0x06)
2025-01-16T01:58:46.782Z SERIAL « 0x010401a90152 (6 bytes)
2025-01-16T01:58:46.785Z SERIAL » [ACK] (0x06)
2025-01-16T01:58:46.790Z DRIVER « [RES] [SendDataBridge]
was sent: true
2025-01-16T01:58:46.879Z SERIAL « 0x011d00a90501000a007f7f7f7f7f00030600000000040300000ea37f7f7fea (31 bytes)
2025-01-16T01:58:46.882Z SERIAL » [ACK] (0x06)
2025-01-16T01:58:46.886Z DRIVER « [REQ] [SendDataBridge]
callback id: 5
transmit status: NoAck, took 100 ms
routing attempts: 3
protocol & route speed: Z-Wave Long Range, 100 kbit/s
routing scheme: Resort to Direct
TX channel no.: 3
TX power: 14 dBm
measured noise floor: -93 dBm
2025-01-16T01:58:46.896Z SERIAL » 0x011000a900010104029f04250000000005fb (18 bytes)
2025-01-16T01:58:46.898Z DRIVER » [Node 260] [REQ] [SendDataBridge]
│ source node id: 1
│ transmit options: 0x25
│ callback id: 5
└─[Security2CCKEXGet]
2025-01-16T01:58:46.905Z SERIAL « [ACK] (0x06)
2025-01-16T01:58:46.911Z SERIAL « 0x010401a90152 (6 bytes)
2025-01-16T01:58:46.914Z SERIAL » [ACK] (0x06)
2025-01-16T01:58:46.917Z DRIVER « [RES] [SendDataBridge]
was sent: true
2025-01-16T01:58:47.029Z SERIAL « 0x011d00a90501000c007f7f7f7f7f00030600000000040300000ea37f7f7fec (31 bytes)
2025-01-16T01:58:47.032Z SERIAL » [ACK] (0x06)
2025-01-16T01:58:47.035Z DRIVER « [REQ] [SendDataBridge]
callback id: 5
transmit status: NoAck, took 120 ms
routing attempts: 3
protocol & route speed: Z-Wave Long Range, 100 kbit/s
routing scheme: Resort to Direct
TX channel no.: 3
TX power: 14 dBm
measured noise floor: -93 dBm
2025-01-16T01:58:47.045Z CNTRLR [Node 260] The node did not respond after 3 attempts, it is presumed dead
2025-01-16T01:58:47.049Z CNTRLR [Node 260] Security S2 bootstrapping failed, the node was not granted any S2 s
ecurity class: The node did not acknowledge the command (ZW0204)
2025-01-16T01:58:47.052Z CNTRLR [Node 260] SmartStart inclusion failed. Checking if the node needs to be remov
ed.
2025-01-16T01:58:47.053Z CNTRLR » [Node 260] pinging the node...
2025-01-16T01:58:47.065Z SERIAL » 0x010f00a90001010401002500000000067f (17 bytes)
2025-01-16T01:58:47.067Z DRIVER » [Node 260] [REQ] [SendDataBridge]
│ source node id: 1
│ transmit options: 0x25
│ callback id: 6
└─[NoOperationCC]
2025-01-16T01:58:47.074Z SERIAL « [ACK] (0x06)
2025-01-16T01:58:47.079Z SERIAL « 0x010401a90152 (6 bytes)
2025-01-16T01:58:47.082Z SERIAL » [ACK] (0x06)
2025-01-16T01:58:47.085Z DRIVER « [RES] [SendDataBridge]
was sent: true
2025-01-16T01:58:47.167Z SERIAL « 0x011d00a906010009007f7f7f7f7f00030600000000040300000ea27f7f7feb (31 bytes)
2025-01-16T01:58:47.170Z SERIAL » [ACK] (0x06)
2025-01-16T01:58:47.173Z DRIVER « [REQ] [SendDataBridge]
callback id: 6
transmit status: NoAck, took 90 ms
routing attempts: 3
protocol & route speed: Z-Wave Long Range, 100 kbit/s
routing scheme: Resort to Direct
TX channel no.: 3
TX power: 14 dBm
measured noise floor: -94 dBm
2025-01-16T01:58:47.183Z CNTRLR [Node 260] The node did not respond after 1 attempts, it is presumed dead
2025-01-16T01:58:47.187Z CNTRLR [Node 260] ping failed: The node did not acknowledge the command (ZW0204)
2025-01-16T01:58:47.197Z SERIAL » 0x010600610104079a (8 bytes)
2025-01-16T01:58:47.199Z DRIVER » [REQ] [RemoveFailedNode]
payload: 0x010407
2025-01-16T01:58:47.206Z SERIAL « [ACK] (0x06)
2025-01-16T01:58:47.211Z SERIAL « 0x01040161009b (6 bytes)
2025-01-16T01:58:47.213Z SERIAL » [ACK] (0x06)
2025-01-16T01:58:47.218Z DRIVER « [RES] [RemoveFailedNode]
2025-01-16T01:58:47.284Z SERIAL « 0x0105006107019d (7 bytes)
2025-01-16T01:58:47.288Z SERIAL » [ACK] (0x06)
2025-01-16T01:58:47.293Z DRIVER « [REQ] [RemoveFailedNode]
2025-01-16T01:58:47.328Z CNTRLR [Node 260] was removed
2025-01-16T01:58:47.336Z CNTRLR Enabling Smart Start listening mode...
2025-01-16T01:58:47.341Z DRIVER the message was handled
2025-01-16T01:58:47.348Z SERIAL » 0x0105004a4900f9 (7 bytes)
2025-01-16T01:58:47.350Z DRIVER » [REQ] [AddNodeToNetwork]
action: Enable Smart Start listening mode
2025-01-16T01:58:47.371Z SERIAL « [ACK] (0x06)
2025-01-16T01:58:47.378Z CNTRLR Smart Start listening mode enabled
2025-01-16T01:58:47.384Z DRIVER all queues idle
2025-01-16 01:58:47.397 INFO Z-WAVE-SERVER: Client disconnected
2025-01-16 01:58:47.401 DEBUG Z-WAVE-SERVER: Code 1000:
2025-01-16 01:58:47.427 DEBUG Z-WAVE-SERVER: New client
2025-01-16T01:59:06.433Z DRIVER one or more queues busy
2025-01-16T01:59:06.452Z SERIAL » 0x0103003bc7 (5 bytes)
2025-01-16T01:59:06.455Z DRIVER » [REQ] [GetBackgroundRSSI]
2025-01-16T01:59:06.466Z SERIAL « [ACK] (0x06)
2025-01-16T01:59:06.471Z SERIAL « 0x0107013b9d9797a2fd (9 bytes)
2025-01-16T01:59:06.476Z SERIAL » [ACK]
JVorbeck
January 17, 2025, 5:47pm
3
I resolved this by moving the Zen17 right next to the controller. It was astonishingly close previously, within about 25 feet. I don’t have very high expectations with the range of this device in use.
Do you have a USB extension cable connected to the controller?
https://zwave-js.github.io/node-zwave-js/#/troubleshooting/first-steps
Right before the smartstart request you have a strange value for background RSSI reported on the LR channel (channel 3):
2025-01-16T01:58:36.470Z DRIVER « [RES] [GetBackgroundRSSI]
channel 0: -99 dBm
channel 1: -101 dBm
channel 2: -101 dBm
channel 3: -128 dBm