Trouble connecting a Scenemaster ZRC-90 to Zwave-js-ui

Configuration Z-Wave
,
1

Env:
RPi running zwave-js-ui inside a docker, using MQTT to integrate with HA.
I have a Z-Stick Gen5+ zwave controller using an USB Extention cord.
(also a zigbee stick is active separately on this RPi).

A sunricher remote does integrate and report into HA with all buttons.
A ZRC-90 remotec scene controller is recognized a s A device without an ID.
Device ID
undefined-undefined-undefined (0xXXXX-0xXXXX-0xXXXX)

When i insert the 0x5254.0x0001.0x8510 device id into the XXXX.values.jsonl then it shows up with the right name …
a reinterview of the device clears all but the battery level (92%) , and battery low indicator (false) .

Where does it fail. How to investigate / solve this conundrum. The other topics i found don’t seem to work that well
adding an USB extension cord doesn’t make a difference (it once did for zigbee).
And most involve migrating from previous ZWave interfaces to ZWave-JS-UI.

Debug output: from pressing W (wake for 30 seconds) button ( up to completion of re-interview device). 
2022-11-04T11:55:28.640Z SERIAL « 0x010b000404020380035cc100eb                                        (13 bytes)
2022-11-04T11:55:28.647Z SERIAL » [ACK]                                                                   (0x06)
2022-11-04T11:55:28.653Z CNTRLR   [Node 002] [~] [Battery] level: 92 => 92                          [Endpoint 0]
2022-11-04T11:55:28.707Z CNTRLR   [Node 002] [~] [Battery] isLow: false => false                    [Endpoint 0]
2022-11-04T11:55:28.738Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
                                  │ type: broadcast
                                  └─[BatteryCCReport]
                                      level:  92
                                      is low: false
2022-11-04T11:55:40.828Z SERIAL « 0x010a00040002028407c400b6                                          (12 bytes)
2022-11-04T11:55:40.835Z SERIAL » [ACK]                                                                   (0x06)
2022-11-04T11:55:40.841Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
                                  └─[WakeUpCCWakeUpNotification]
2022-11-04T11:55:40.847Z CNTRLR « [Node 002] received wakeup notification
2022-11-04T11:55:41.818Z SERIAL « 0x010a00040002028407c400b6                                          (12 bytes)
2022-11-04T11:55:41.826Z SERIAL » [ACK]                                                                   (0x06)
2022-11-04T11:55:41.833Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
                                  └─[WakeUpCCWakeUpNotification]
2022-11-04T11:55:41.840Z CNTRLR « [Node 002] received wakeup notification
2022-11-04T11:55:42.829Z SERIAL « 0x010a00040002028407c400b6                                          (12 bytes)
2022-11-04T11:55:42.833Z SERIAL » [ACK]                                                                   (0x06)
2022-11-04T11:55:42.837Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
                                  └─[WakeUpCCWakeUpNotification]
2022-11-04T11:55:42.840Z CNTRLR « [Node 002] received wakeup notification
2022-11-04T11:55:43.831Z SERIAL « 0x010a00040002028407c400b6                                          (12 bytes)
2022-11-04T11:55:43.838Z SERIAL » [ACK]                                                                   (0x06)
2022-11-04T11:55:43.844Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
                                  └─[WakeUpCCWakeUpNotification]
2022-11-04T11:55:43.850Z CNTRLR « [Node 002] received wakeup notification
2022-11-04T11:55:44.276Z CNTRLR   [Node 002] [+] [Node Naming and Location] name: "scenemaster"
2022-11-04T11:55:44.305Z CNTRLR   [Node 002] [+] [Node Naming and Location] location: "kamer"
2022-11-04T11:55:44.336Z CNTRLR   [Node 002] Beginning interview - last completed stage: None
2022-11-04T11:55:44.337Z CNTRLR   [Node 002] new node, doing a full interview...
2022-11-04T11:55:44.355Z CNTRLR » [Node 002] querying protocol info...
2022-11-04T11:55:44.377Z SERIAL » 0x0104004102b8                                                       (6 bytes)
2022-11-04T11:55:44.378Z DRIVER » [REQ] [GetNodeProtocolInfo]
                                    payload: 0x02
2022-11-04T11:55:44.393Z SERIAL « [ACK]                                                                   (0x06)
2022-11-04T11:55:44.398Z SERIAL « 0x01090141131601010106b4                                            (11 bytes)
2022-11-04T11:55:44.402Z SERIAL » [ACK]                                                                   (0x06)
2022-11-04T11:55:44.406Z DRIVER « [RES] [GetNodeProtocolInfo]
                                    payload: 0x131601010106
2022-11-04T11:55:44.422Z CNTRLR « [Node 002] received response for protocol info:
                                  basic device class:    Controller
                                  generic device class:  Remote Controller
                                  specific device class: Simple Remote Control
                                  node type:             Controller
                                  is always listening:   false
                                  is frequent listening: false
                                  can route messages:    false
                                  supports security:     false
                                  supports beaming:      true
                                  maximum data rate:     100000 kbps
                                  protocol version:      3
2022-11-04T11:55:44.458Z CNTRLR   [Node 002] The node is now asleep.
2022-11-04T11:55:44.505Z CNTRLR   [Node 002] Interview stage completed: ProtocolInfo
2022-11-04T11:55:44.506Z CNTRLR » [Node 002] querying node info...
2022-11-04T11:55:44.832Z SERIAL « 0x010a00040002028407c100b3                                          (12 bytes)
2022-11-04T11:55:44.837Z SERIAL » [ACK]                                                                   (0x06)
2022-11-04T11:55:44.841Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
                                  └─[WakeUpCCWakeUpNotification]
2022-11-04T11:55:44.846Z CNTRLR « [Node 002] received wakeup notification
2022-11-04T11:55:44.873Z CNTRLR   [Node 002] The node is now awake.
2022-11-04T11:55:44.902Z SERIAL » 0x010400600299                                                       (6 bytes)
2022-11-04T11:55:44.904Z DRIVER » [Node 002] [REQ] [RequestNodeInfo]
                                    payload: 0x02
2022-11-04T11:55:44.916Z SERIAL « [ACK]                                                                   (0x06)
2022-11-04T11:55:44.920Z SERIAL « 0x01040160019b                                                       (6 bytes)
2022-11-04T11:55:44.924Z SERIAL » [ACK]                                                                   (0x06)
2022-11-04T11:55:44.928Z DRIVER « [RES] [RequestNodeInfo]
                                    payload: 0x01
2022-11-04T11:55:44.949Z SERIAL « 0x010900498402030101063c                                            (11 bytes)
2022-11-04T11:55:44.951Z SERIAL » [ACK]                                                                   (0x06)
2022-11-04T11:55:44.953Z DRIVER « [Node 002] [REQ] [ApplicationUpdateRequest]
                                    payload: 0x0203010106
2022-11-04T11:55:44.965Z CNTRLR « [Node 002] node info received
                                  supported CCs:
2022-11-04T11:55:44.996Z CNTRLR   [Node 002] Interview stage completed: NodeInfo
2022-11-04T11:55:44.999Z CNTRLR   [Node 002] Interviewing Wake Up...
2022-11-04T11:55:45.000Z CNTRLR » [Node 002] retrieving wakeup interval from the device...
2022-11-04T11:55:45.027Z SERIAL » 0x0109001302028405250342                                            (11 bytes)
2022-11-04T11:55:45.028Z DRIVER » [Node 002] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      3
                                  └─[WakeUpCCIntervalGet]
2022-11-04T11:55:45.040Z SERIAL « [ACK]                                                                   (0x06)
2022-11-04T11:55:45.043Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-11-04T11:55:45.044Z SERIAL » [ACK]                                                                   (0x06)
2022-11-04T11:55:45.046Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-11-04T11:55:45.056Z SERIAL « 0x011800130300000200c47f7f7f7f000003000000000301000030              (26 bytes)
2022-11-04T11:55:45.058Z SERIAL » [ACK]                                                                   (0x06)
2022-11-04T11:55:45.060Z DRIVER « [REQ] [SendData]
                                    callback id:            3
                                    transmit status:        OK, took 20 ms
                                    routing attempts:       1
                                    protocol & route speed: Z-Wave, 100 kbit/s
                                    ACK RSSI:               -60 dBm
                                    ACK channel no.:        0
                                    TX channel no.:         0
2022-11-04T11:55:45.080Z SERIAL « 0x010e0004000206840600000001c400b6                                  (16 bytes)
2022-11-04T11:55:45.082Z SERIAL » [ACK]                                                                   (0x06)
2022-11-04T11:55:45.090Z CNTRLR   [Node 002] [Wake Up] wakeUpInterval: metadata updated             [Endpoint 0]
2022-11-04T11:55:45.111Z CNTRLR   [Node 002] [+] [Wake Up] wakeUpInterval: 0                        [Endpoint 0]
2022-11-04T11:55:45.125Z CNTRLR   [Node 002] [Wake Up] controllerNodeId: metadata updated           [Endpoint 0]
2022-11-04T11:55:45.146Z CNTRLR   [Node 002] [+] [Wake Up] controllerNodeId: 1                      [Endpoint 0]
2022-11-04T11:55:45.161Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
                                  └─[WakeUpCCIntervalReport]
                                      wake-up interval:   0 seconds
                                      controller node id: 1
2022-11-04T11:55:45.168Z CNTRLR « [Node 002] received wakeup configuration:
                                  wakeup interval: 0 seconds
                                  controller node: 1
2022-11-04T11:55:45.170Z CNTRLR   [Node 002] [+] [Wake Up] interviewComplete: true       [Endpoint 0] [internal]
2022-11-04T11:55:45.201Z CNTRLR   [Node 002] Interview stage completed: CommandClasses
2022-11-04T11:55:45.225Z CNTRLR   [Node 002] Interview stage completed: OverwriteConfig
2022-11-04T11:55:45.258Z CNTRLR   [Node 002] Interview completed
2022-11-04T11:55:45.300Z CNTRLR   [Node 002] The node is ready to be used
2022-11-04T11:55:48.106Z SERIAL « 0x010a00040002028407c300b1                                          (12 bytes)
2022-11-04T11:55:48.112Z SERIAL » [ACK]                                                                   (0x06)
2022-11-04T11:55:48.117Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
                                  └─[WakeUpCCWakeUpNotification]
2022-11-04T11:55:48.123Z CNTRLR « [Node 002] received wakeup notification
2022-11-04T11:55:49.107Z SERIAL « 0x010a00040002028407c100b3                                          (12 bytes)
2022-11-04T11:55:49.114Z SERIAL » [ACK]                                                                   (0x06)
2022-11-04T11:55:49.119Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
                                  └─[WakeUpCCWakeUpNotification]
2022-11-04T11:55:49.124Z CNTRLR « [Node 002] received wakeup notification
2022-11-04T11:55:50.117Z SERIAL « 0x010a00040002028407c100b3                                          (12 bytes)
2022-11-04T11:55:50.123Z SERIAL » [ACK]                                                                   (0x06)
2022-11-04T11:55:50.129Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
                                  └─[WakeUpCCWakeUpNotification]
2022-11-04T11:55:50.139Z CNTRLR « [Node 002] received wakeup notification
2022-11-04T11:55:51.119Z SERIAL « 0x010a00040002028407c100b3                                          (12 bytes)
2022-11-04T11:55:51.125Z SERIAL » [ACK]                                                                   (0x06)
2022-11-04T11:55:51.130Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
                                  └─[WakeUpCCWakeUpNotification]
2022-11-04T11:55:51.136Z CNTRLR « [Node 002] received wakeup notification
2022-11-04T11:55:52.121Z SERIAL « 0x010a00040002028407c100b3                                          (12 bytes)
2022-11-04T11:55:52.129Z SERIAL » [ACK]                                                                   (0x06)
2022-11-04T11:55:52.135Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
                                  └─[WakeUpCCWakeUpNotification]
2022-11-04T11:55:52.140Z CNTRLR « [Node 002] received wakeup notification
2022-11-04T11:55:53.112Z SERIAL « 0x010a00040002028407bb00c9                                          (12 bytes)
2022-11-04T11:55:53.118Z SERIAL » [ACK]                                                                   (0x06)
2022-11-04T11:55:53.123Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
                                  └─[WakeUpCCWakeUpNotification]
2022-11-04T11:55:53.128Z CNTRLR « [Node 002] received wakeup notification
2022-11-04T11:55:54.112Z SERIAL « 0x010a00040002028407bc00ce                                          (12 bytes)
2022-11-04T11:55:54.119Z SERIAL » [ACK]                                                                   (0x06)
2022-11-04T11:55:54.124Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
                                  └─[WakeUpCCWakeUpNotification]
2022-11-04T11:55:54.129Z CNTRLR « [Node 002] received wakeup notification
2022-11-04T11:55:55.124Z SERIAL « 0x010a00040002028407b900cb                                          (12 bytes)
2022-11-04T11:55:55.130Z SERIAL » [ACK]                                                                   (0x06)
2022-11-04T11:55:55.135Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
                                  └─[WakeUpCCWakeUpNotification]
2022-11-04T11:55:55.140Z CNTRLR « [Node 002] received wakeup notification
2022-11-04T11:55:56.125Z SERIAL « 0x010a00040002028407bb00c9                                          (12 bytes)
2022-11-04T11:55:56.131Z SERIAL » [ACK]                                                                   (0x06)
2022-11-04T11:55:56.136Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
                                  └─[WakeUpCCWakeUpNotification]
2022-11-04T11:55:56.141Z CNTRLR « [Node 002] received wakeup notification
2022-11-04T11:55:59.242Z SERIAL « 0x010b000404020380035cca00e0                                        (13 bytes)
2022-11-04T11:55:59.250Z SERIAL » [ACK]                                                                   (0x06)
2022-11-04T11:55:59.257Z CNTRLR   [Node 002] [Battery] level: metadata updated                      [Endpoint 0]
2022-11-04T11:55:59.291Z CNTRLR   [Node 002] [+] [Battery] level: 92                                [Endpoint 0]
2022-11-04T11:55:59.334Z CNTRLR   [Node 002] [Battery] isLow: metadata updated                      [Endpoint 0]
2022-11-04T11:55:59.355Z CNTRLR   [Node 002] [+] [Battery] isLow: false                             [Endpoint 0]
2022-11-04T11:55:59.374Z CNTRLR   [Node 002] [Battery] chargingStatus: metadata updated             [Endpoint 0]
2022-11-04T11:55:59.388Z CNTRLR   [Node 002] [Battery] rechargeable: metadata updated               [Endpoint 0]
2022-11-04T11:55:59.406Z CNTRLR   [Node 002] [Battery] backup: metadata updated                     [Endpoint 0]
2022-11-04T11:55:59.450Z CNTRLR   [Node 002] [Battery] overheating: metadata updated                [Endpoint 0]
2022-11-04T11:55:59.482Z CNTRLR   [Node 002] [Battery] lowFluid: metadata updated                   [Endpoint 0]
2022-11-04T11:55:59.515Z CNTRLR   [Node 002] [Battery] rechargeOrReplace: metadata updated          [Endpoint 0]
2022-11-04T11:55:59.534Z CNTRLR   [Node 002] [Battery] disconnected: metadata updated               [Endpoint 0]
2022-11-04T11:55:59.564Z CNTRLR   [Node 002] [Battery] lowTemperatureStatus: metadata updated       [Endpoint 0]
2022-11-04T11:55:59.585Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
                                  │ type: broadcast
                                  └─[BatteryCCReport]
                                      level:  92
                                      is low: false

Link: Link to device

2

Hi, I am running 2 of these, and had a similar problem, I solved it in the end, by opening the battery cover and hit the button with W above it, it will start flashing, then try a re-interview.

3

Thanks, Without pressing te W button everything just times out. As the ZRC-90 device doesn’t wake up.
Note that the device reports as an unknown… So something is seen.

Added a debug trace in the top post.
(this W button was therefore not a solution).

4

Also created a bug report: ZRC-90 not recognized on (re-)interview · Issue #5192 · zwave-js/node-zwave-js · GitHub

5

ZRC-90 works perfectly fine with HA with Zwave-JS-UI (formerly ZWJS2MQTT). I’ve added it, removed it and added it again multiple times on both Aeotec 500 stick and Zooz 700 sticks.

Sounds like you need to remove the device and include it again. If I’m recalling correctly, it’s the L button (and only the L button) that needs to be pressed ONCE to put the remote into inclusion mode.

6

It was probably the reset sequence that actually failed.
The manual says press R at least 10 seconds… then what happens is: (times timed with a timer).
After almost 5 seconds the blue led Lights up, after about 8 seconds blue light goes off and after 10 seconds it flashes… before the 3 R presses can be done.
And this gives consistently non-functional results.

I decided to Press R and release when the blue light stops, and then press R 3 times. That responds with a solid blue flash of a few seconds… Then it seems properly reset.

Either the reset procedure is inaccurate / inconsistent with documentation, or the device has slightly shorter times than documented.

After this reset the device reports normally

7

I am trying to link a ZRC-90 to Home Assistant using Zwave-js-ui and have the same problem with the Manufactured/Product/Product code, that actually is 0xXXXX. That file that you mention, the XXXX.values.json, where is?

8

That was for debugging purposes. I installed the zwave-js-ui on a separate RaspberryPi not on home assistant (there it is within a separate docker).

Then it is trivial. Editing the JSON file is NOT the solution though.

The reset sequency is different from what the manual says it is.
See the solution mentioned above.