Ignore SmartStart inclusion requests when S2 keys are not configured #6644
-
Checklist
Describe the issueIf S2 keys are not configured and a user includes a node with SmartStart, the S2 bootstrapping fails (presumably, but I didn't see the logs). This problem was reported by a user in HA Discord who reported the "infinite" inclusion using SmartStart, and the problem was solved by adding S2 keys, which were previously not set. According to one of the spec docs [1], on S2 bootstrapping failure:
Kind of a weird phrasing, but it sounds like the device can either try forever, or try for a minimum of 2 times and then give up. It seems this device (ZEN04) tries forever. So I guess it doesn't it doesn't make much sense to attempt an inclusion without S2 keys as SmartStart requires S2. I did not find anything in the spec docs that alludes to this use case. [1] Section "4.5.4.3.4 Unsuccessful SmartStart inclusion" in Z-Wave and Z-Wave Long Range Network Layer Specification 2.0. Software versionsNo response Device informationNo response Checklist
Upload LogfileNone provided by user. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
👋 Hey @kpine! Thanks for opening an issue! It doesn't look like you provided a logfile though. While not strictly necessary for every issue, having a driver log on loglevel debug is required to diagnose most issues. Please consider uploading a logfile that captures your problem. As a reminder, here's how to create one: |
Beta Was this translation helpful? Give feedback.
-
Escalated to an issue #6771 |
Beta Was this translation helpful? Give feedback.
Escalated to an issue #6771