Closed adubkov closed 11 months ago
robertsLando
commented
1 year ago @adubkov you should wait some minutes, also Smart start doens't require any user interaction after you scan the QR code, it adds the node it's own (just ensure that the provisioning entry in the table has active flag set to true)
robertsLando
commented
1 year ago cc @AlCalzone
AlCalzone
commented
1 year ago After that I activated "inclusion" mode
That's not how SmartStart works. Like @robertsLando said, it requires no user interaction except setting up the provisioning entry. If you're pushing the button anyways, you can just enable the inclusion in Z-Wave JS first, then push the button to do a normal inclusion.
Or just wait for SmartStart to do its thing. If a factory reset doesn't work, you can try removing the battery for a second.
adubkov
commented
1 year ago I tried removing battery for some time and it did not help. Zooz support suggested do the exclusion first. Not sure what they meant because sensor is not actually registered in controller and had factory reset on both.
SmartStart works well with hard wired sensors, but I have no luck with battery powered sensors so far. Is there any specific steps to wake up battery powered devices to register them with SmartStart? @AlCalzone
(please ignore wired one that is not included, i just did not power it up yet)
AlCalzone
commented
1 year ago Zooz support suggested do the exclusion first.
Sometimes devices seem to be included in a factory network or something. Not sure if factory reset should have removed this link, but if you just start excluding devices in Z-Wave JS UI and push the button on your sensor, you can exclude it from any network, not just the current one.
FWIW, I tried with a brand new ZSE41 myself. Turned it on, added the provisioning entry and a few seconds later the inclusion started. Excluded it again, re-enabled the provisioning entry, nothing happened. After I removed and re-inserted the battery, it immediately included.
adubkov
commented
1 year ago @AlCalzone I was trying to do same steps. It seems that exclusion did in-fact exclude it, but then following inclusion failing:
2023-03-16T20:30:48.033Z CNTRLR Leaving Smart Start listening mode...
2023-03-16T20:30:48.056Z SERIAL » 0x0105004ac50075 (7 bytes)
2023-03-16T20:30:48.058Z DRIVER » [REQ] [AddNodeToNetwork]
action: Stop
high power: true
network wide: true
callback id: 0
2023-03-16T20:30:48.066Z SERIAL « [ACK] (0x06)
2023-03-16T20:30:48.077Z CNTRLR Left Smart Start listening mode
2023-03-16T20:30:48.078Z CNTRLR starting exclusion process...
2023-03-16T20:30:48.096Z SERIAL » 0x0105004bc10a7a (7 bytes)
2023-03-16T20:30:48.097Z DRIVER » [REQ] [RemoveNodeFromNetwork]
payload: 0xc10a
2023-03-16T20:30:48.104Z SERIAL « [ACK] (0x06)
2023-03-16T20:30:48.107Z SERIAL « 0x0107004b0a010000b8 (9 bytes)
2023-03-16T20:30:48.109Z SERIAL » [ACK] (0x06)
2023-03-16T20:30:48.111Z DRIVER « [REQ] [RemoveNodeFromNetwork]
payload: 0x0a010000
2023-03-16T20:30:48.123Z CNTRLR The controller is now ready to remove nodes
2023-03-16T20:30:52.177Z SERIAL « 0x0107004b0a020000bb (9 bytes)
2023-03-16T20:30:52.181Z SERIAL » [ACK] (0x06)
2023-03-16T20:30:52.185Z DRIVER « [REQ] [RemoveNodeFromNetwork]
payload: 0x0a020000
2023-03-16T20:30:52.190Z DRIVER handling request RemoveNodeFromNetwork (75)
2023-03-16T20:30:52.191Z DRIVER 1 handler registered!
2023-03-16T20:30:52.192Z DRIVER invoking handler #0
2023-03-16T20:30:52.192Z CNTRLR handling remove node request (status = NodeFound)
2023-03-16T20:30:53.387Z SERIAL « 0x011c004b0a030515040701000000000000000000000000000000000000b3 (30 bytes)
2023-03-16T20:30:53.395Z SERIAL » [ACK] (0x06)
2023-03-16T20:30:53.399Z DRIVER « [REQ] [RemoveNodeFromNetwork]
payload: 0x0a030515040701000000000000000000000000000000000000
2023-03-16T20:30:53.402Z DRIVER handling request RemoveNodeFromNetwork (75)
2023-03-16T20:30:53.403Z DRIVER 1 handler registered!
2023-03-16T20:30:53.404Z DRIVER invoking handler #0
2023-03-16T20:30:53.404Z CNTRLR handling remove node request (status = RemovingSlave)
2023-03-16T20:30:53.405Z DRIVER the message was handled
2023-03-16T20:30:53.407Z SERIAL « 0x011c004b0a060515040701000000000000000000000000000000000000b6 (30 bytes)
2023-03-16T20:30:53.411Z SERIAL » [ACK] (0x06)
2023-03-16T20:30:53.414Z DRIVER « [REQ] [RemoveNodeFromNetwork]
payload: 0x0a060515040701000000000000000000000000000000000000
2023-03-16T20:30:53.418Z DRIVER handling request RemoveNodeFromNetwork (75)
2023-03-16T20:30:53.418Z DRIVER 1 handler registered!
2023-03-16T20:30:53.419Z DRIVER invoking handler #0
2023-03-16T20:30:53.419Z CNTRLR handling remove node request (status = Done)
2023-03-16T20:30:53.443Z SERIAL » 0x0105004bc50074 (7 bytes)
2023-03-16T20:30:53.445Z DRIVER » [REQ] [RemoveNodeFromNetwork]
payload: 0xc500
2023-03-16T20:30:53.448Z SERIAL « [ACK] (0x06)
2023-03-16T20:30:53.464Z CNTRLR the exclusion process was stopped
2023-03-16T20:30:53.466Z CNTRLR Enabling Smart Start listening mode...
2023-03-16T20:30:53.477Z DRIVER the message was handled
2023-03-16T20:30:53.490Z SERIAL » 0x0105004a4900f9 (7 bytes)
2023-03-16T20:30:53.492Z DRIVER » [REQ] [AddNodeToNetwork]
action: Enable Smart Start listening mode
2023-03-16T20:30:53.499Z SERIAL « [ACK] (0x06)
2023-03-16T20:30:53.512Z CNTRLR Smart Start listening mode enabled
2023-03-16T20:31:25.660Z SERIAL « 0x0120004985001add37b3d2120407015e858e595586725a73809f71873070846c7 (34 bytes)
a2d
2023-03-16T20:31:25.664Z SERIAL » [ACK] (0x06)
2023-03-16T20:31:25.668Z DRIVER « [REQ] [ApplicationUpdateRequest]
type: SmartStart_HomeId_Received
remote node ID: 0
NWI home ID: 0xdd37b3d2
basic device class: 4
generic device class: 7
specific device class: 1
supported CCs:
· Z-Wave Plus Info
· Association
· Multi Channel Association
· Association Group Information
· Transport Service
· Version
· Manufacturer Specific
· Device Reset Locally
· Powerlevel
· Battery
· Security 2
· Notification
· Indicator
· Binary Sensor
· Configuration
· Wake Up
· Supervision
· Firmware Update Meta Data
2023-03-16T20:31:25.676Z CNTRLR Received Smart Start inclusion request
2023-03-16T20:31:25.677Z CNTRLR NWI Home ID found in provisioning list, including node...
2023-03-16T20:31:25.678Z CNTRLR Including SmartStart node with DSK XXX-XXX-XXX-XXX-XXX-XXX-XXX-0
6530
2023-03-16T20:31:25.697Z SERIAL » 0x010d004ac80bdd37b3d23962198331 (15 bytes)
2023-03-16T20:31:25.699Z DRIVER » [REQ] [AddNodeToNetwork]
action: Add Smart Start node
NWI Home ID: 0xdd37b3d2
high power: true
network wide: true
callback id: 11
2023-03-16T20:31:25.704Z SERIAL « [ACK] (0x06)
2023-03-16T20:31:25.716Z SERIAL « 0x0107004a0b010000b8 (9 bytes)
2023-03-16T20:31:25.717Z SERIAL » [ACK] (0x06)
2023-03-16T20:31:25.726Z DRIVER « [REQ] [AddNodeToNetwork]
status: Ready
callback id: 11
2023-03-16T20:31:25.731Z DRIVER handling request AddNodeToNetwork (74)
2023-03-16T20:31:25.732Z DRIVER 1 handler registered!
2023-03-16T20:31:25.732Z DRIVER invoking handler #0
2023-03-16T20:31:25.734Z CNTRLR handling add node request (status = Ready)
2023-03-16T20:31:29.761Z SERIAL « 0x0107004a0b020000bb (9 bytes)
2023-03-16T20:31:29.764Z SERIAL » [ACK] (0x06)
2023-03-16T20:31:29.768Z DRIVER « [REQ] [AddNodeToNetwork]
status: NodeFound
callback id: 11
2023-03-16T20:31:29.773Z DRIVER handling request AddNodeToNetwork (74)
2023-03-16T20:31:29.774Z DRIVER 1 handler registered!
2023-03-16T20:31:29.774Z DRIVER invoking handler #0
2023-03-16T20:31:29.775Z CNTRLR handling add node request (status = NodeFound)
2023-03-16T20:31:31.687Z SERIAL « 0x0107004a0b070500bb (9 bytes)
2023-03-16T20:31:31.690Z SERIAL » [ACK] (0x06)
2023-03-16T20:31:31.695Z DRIVER « [REQ] [AddNodeToNetwork]
status: Failed
callback id: 11
2023-03-16T20:31:31.701Z DRIVER handling request AddNodeToNetwork (74)
2023-03-16T20:31:31.702Z DRIVER 1 handler registered!
2023-03-16T20:31:31.703Z DRIVER invoking handler #0
2023-03-16T20:31:31.704Z CNTRLR handling add node request (status = Failed)
2023-03-16T20:31:31.704Z CNTRLR Adding the node failed
2023-03-16T20:31:31.706Z CNTRLR stopping inclusion process...
2023-03-16T20:31:31.722Z SERIAL » 0x0105004ac50c79 (7 bytes)
2023-03-16T20:31:31.724Z DRIVER » [REQ] [AddNodeToNetwork]
action: Stop
high power: true
network wide: true
callback id: 12
2023-03-16T20:31:31.733Z SERIAL « [ACK] (0x06)
2023-03-16T20:31:31.738Z SERIAL « 0x0107004a0c060500bd (9 bytes)
2023-03-16T20:31:31.739Z SERIAL » [ACK] (0x06)
2023-03-16T20:31:31.740Z DRIVER « [REQ] [AddNodeToNetwork]
status: Done
callback id: 12
2023-03-16T20:31:31.753Z CNTRLR The inclusion process was stopped
2023-03-16T20:31:31.755Z CNTRLR Enabling Smart Start listening mode...
2023-03-16T20:31:31.762Z DRIVER the message was handled
2023-03-16T20:31:31.768Z SERIAL » 0x0105004a4900f9 (7 bytes)
2023-03-16T20:31:31.769Z DRIVER » [REQ] [AddNodeToNetwork]
action: Enable Smart Start listening mode
2023-03-16T20:31:31.775Z SERIAL « [ACK] (0x06)
2023-03-16T20:31:31.782Z CNTRLR Smart Start listening mode enabledAlso I have seen this error, when run exclusion, inclusion first time:
2023-03-16T20:37:56.091Z DRIVER handling request AddNodeToNetwork (74)
2023-03-16T20:37:56.092Z DRIVER 1 handler registered!
2023-03-16T20:37:56.092Z DRIVER invoking handler #0
2023-03-16T20:37:56.093Z CNTRLR handling add node request (status = Ready)
2023-03-16T20:37:56.195Z SERIAL « 0x012600a814ff001ddd35fced0127539c0107015e858e595586725a73809f71873 (40 bytes)
070846c7a00e6c9
2023-03-16T20:37:56.200Z DRIVER Dropping message because it could not be deserialized: The command class unkno
wn (0xdd) is not implemented (ZW0303)
webmogul1
commented
1 year ago Are you clicking the Z-Wave button 3 times as quickly as possible? ( LED indicator will start flashing).
webmogul1
commented
1 year ago Just saw that:
VER. 1.40 (released as OTA 10/2022) Firmware: 1.40
Data packets changed to 5-byte to help address inclusion, range, or security inclusion issues.
adubkov
commented
1 year ago @webmogul1 Yes, I was clicking button 3 times and tried everything else. At this time I'm unable to include it with S2. Support offered me start RMA process, but I did not have time for that and it seems that sensors itself work, just some issue with inclusion.
AlCalzone
commented
1 year ago status = Failed
is an unspecified communication error between the stick and the device during the inclusion process. I'm not sure what can cause it, but often power cycling the device and/or the stick can help with that.
kaechele
commented
1 year ago I will just say that both the ZSE41 and ZSE42 have been extremely problematic to include for me as well in the past. I think the 1.40 firmware fixed it for me. But obviously you'll need to include it first to update the firmware OTA.
Some of the sensors needed manual inclusion, some came online through SmartStart by themselves.
I would suggest including without security first (I found this more likely to not fail), update the firmware and then exclude and re-include (SmartStart should work now) with Security enabled.
adubkov
commented
1 year ago @kaechele Thanks. This partially solved the problem. I was able to include 2 of 3 sensors with no security and update them. After that 1 was able to include itself with SmartStart, 1 still don't and 1 could not even include without security, even after factory reset.
github-actions[bot]
commented
11 months ago This issue is stale because it has been open 90 days with no activity. Remove the stale label or comment or this will be closed in 5 days. To ignore this issue entirely you can add the no-stale label
github-actions[bot]
commented
11 months ago This issue is now closed due to inactivity, you can of course reopen or reference this issue if you see fit.
I have used QR code and I'm seeing the node in Provisioning Entities list now. After that I activated "inclusion" mode on the sensor and ...
... nothing happened. I have tried it multiple times. I have also tried do factory reset on both sensor and controller and starting all over again. Nothing seem to help.
Both sensor and controller in the same room 15 feet away with no obstruction in between them.
Battery seem to be ok, although it is not new.
zwave-js-ui: 8.10.1.e5d6c21 zwave-js: 10.11.1 home id: 3711302893 home hex: 0xdd35fced