Enabling Long Range protocol in the SmartStart entry is being allowed for nodes that don't support LR #3735
Closed
3 tasks done
Labels
bug
Something isn't working
Checklist
Deploy method
Docker
Z-Wave JS UI version
9.13.1.b613753
ZwaveJS version
12.9.1
Describe the bug
When editing a provisioning entry for a normal node, I am allowed to change the protocol from Z-Wave to Z-Wave Long Range (ZWLR). At least with this device, it causes the inclusion to fail and it will repeat this continuously. There is no indication in the UI that this is happening, so it just appears like the node never joins. It's only visible with driver logs.
To Reproduce
Expected behavior
I would expect that a device that does not claim to support ZWLR should not be allowed to be configured with ZWLR protocol. E.g. the menu option should not be visible for these nodes.
And/or the driver should provide some feedback that a node is joining with the wrong protocol?
But, I don't know if there are LR devices that are missing the supported protocol information. Should some kind of force override be allowed in that case? What if a vendor adds LR support in a firmware update (per DrZwave you can OTA devices in the field to add ZWLR)? Are they required to generate a new QR code for you? The existing QR code would be missing the protocol info.
Additional context
I ran driver code to decode the QR code:
The output is:
So you can see there is no
supportedProtocols
field that lists Long Range as available, it's simply omitted. I would presume this means LR is not supported, otherwise it would indicate so.I added the QR code, and you can see the same in the debug logs, no support for LR:
But then edit the entry and am allowed to change it:
The logs confirm the change was made, now protocol is LR.
Now I power on the node and can see it attempts to join, but the driver ignores it. This particular device will continue this non-stop.
I go back and edit the provisioning entry to switch back the protocol to ZW, and it includes successfully.
Attached is a fully log of the above activities.
zwave.log
The text was updated successfully, but these errors were encountered: