Z-Wave JS UI and Rind KeyPad v2

[DoughyKitty]

Add-on: Z-Wave JS UI

Add-on Version: 1.14.0
System: Home Assistant OS 10.3 (amd64/qemuz86-64)
Home Assistant Core: 2023.7.1
Home Assistant Supervisor: 2023.07.1

Whenever JS UI interviews the Ring Keypad V2, it will pin at 50% add-on cpu usage and keep constantly restarting the add-on.

The normal Z-Wave JS appears to be able to interview the node fine, but it is only JS UI that has issues.

Oddly enough, I added the Keypad to via the JS UI QR Code, which functioned correctly.

2023-07-13T22:29:15.912Z CNTRLR » [Node 021] querying parameter #14 information...
2023-07-13T22:29:15.964Z CNTRLR « [Node 021] received information for parameter #14:
value format: UnsignedInteger
value size: 1 bytes
min value: 0
max value: 100
default value: 20
is read-only: false
is advanced (UI): true
has bulk support: true
alters capabilities: false
2023-07-13T22:29:15.966Z CNTRLR » [Node 021] querying parameter #15 information...
2023-07-13T22:29:16.015Z CNTRLR « [Node 021] received information for parameter #15:
value format: UnsignedInteger
value size: 1 bytes
min value: 0
max value: 1
default value: 1
is read-only: false
is advanced (UI): true
has bulk support: true
alters capabilities: false
2023-07-13T22:29:16.016Z CNTRLR » [Node 021] querying parameter #16 information...
2023-07-13T22:29:16.069Z CNTRLR « [Node 021] received information for parameter #16:
value format: UnsignedInteger
value size: 1 bytes
min value: 0
max value: 255
default value: 50
is read-only: false
is advanced (UI): true
has bulk support: true
alters capabilities: false
2023-07-13T22:29:16.070Z CNTRLR » [Node 021] querying parameter #17 information...
2023-07-13T22:29:16.121Z CNTRLR « [Node 021] received information for parameter #17:
value format: UnsignedInteger
value size: 1 bytes
min value: 0
max value: 100
default value: 30
is read-only: false
is advanced (UI): true
has bulk support: true
alters capabilities: false`

[DoughyKitty]

Interesting. If I put it in the microwave, it will finish interviewing all the other nodes.. But decide the keypad is dead.

After Z-Wave JS UI finishes loading and labeling it as dead, I can then take it out of the microwave and it will function fine.

[robertsLando]

Please make a driver log, loglevel debug and attach it here as a file (drag & drop into the text field).

Also instead of the addon version please give me the zwave-js-ui version. You can find it by clicking on top bar info icon

[miniminne]

docker_log_zwave.log

Above is my generic Log file in debug mode, but attached below is my driver log (or as much as it could record before crashing and restarting). Node 5, Param 23 is what it seems to be getting stuck on.
zwavejs_2023-07-14.log

zwave-js-ui: 8.19.0
zwave-js: 11.0.0

I will say the current version of ZWaveJS (official add-on) for HA doesn't have this issue. They seem to be using 10.22.3.

[robertsLando]

CC @AlCalzone

[AlCalzone]

Another duplicate of zwave-js/node-zwave-js#6012

[AlCalzone]

This will be fixed in driver version 11.5.1

[robertsLando]

Fixed in 8.21.1