[SOLVED] Zwave JS Error - New Device Inclusion (addon 0.61) - fixed in 0.62

Hello HA Community.

Has any come across the following errors when adding a Zwave device? I’ve got a new Aeotec Smart Switch 6. I have already got a couple of these switches, they were added to the network a while back and operate without issue.

System / Sequence of Events.

  1. Rpi 4, full rebuild / new SD card (Evo) about 1.5 months ago
  2. System 100%, all 17 Zwave Devices functioning.
  3. Order a new Smart Switch
  4. Add to network via Zwave JS Add Device
  5. Press the button on the smart switch to add to network…
  6. Below Error occurred.
  7. Attempt another inclusion - “spinning wheel”, no text appeared when adding new device (just the info that displays on the pop-up when adding a new device)
  8. Rebooted Via HA interface → System → Reboot?
  9. 10 min later no interface
  10. Hard reboot - nothing, unable to ping controller. Seems dead.

After rebooting with this error (via the interface, rebooting HOST), my RPI failed to start… still have not got it back up and running…

Any suggestions on the error code? I’m at the stage I need to re-flash the SD card and restore a backup, but not keen to add this device again if it bricks the system.

2022-06-20T09:18:14.559Z CNTRLR   Starting inclusion process with strategy Default...
2022-06-20T09:18:14.592Z CNTRLR   The controller is now ready to add nodes
2022-06-20T09:18:32.659Z CNTRLR   handling add node request (status = NodeFound)
2022-06-20T09:18:32.936Z CNTRLR   handling add node request (status = AddingSlave)
2022-06-20T09:18:47.896Z CNTRLR   handling add node request (status = ProtocolDone)
2022-06-20T09:18:47.898Z CNTRLR   finishing inclusion process...
2022-06-20T09:18:48.042Z CNTRLR   The inclusion process was stopped
(node:181) UnhandledPromiseRejectionWarning: ZWaveError: Node 26 was not found! (ZW0209)
    at /usr/src/node_modules/zwave-js/src/lib/controller/Controller.ts:295:10
    at Map.<anonymous> (/usr/src/node_modules/@zwave-js/shared/src/ThrowingMap.ts:17:5)
    at Driver.getValueDB (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:737:38)
    at getValue (/usr/src/node_modules/zwave-js/src/lib/node/utils.ts:31:14)
    at Object.endpointCountIsDynamic (/usr/src/node_modules/zwave-js/src/lib/node/utils.ts:48:9)
    at ZWaveNode.get endpointCountIsDynamic [as endpointCountIsDynamic] (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:1034:20)
    at dumpNode (/usr/src/node_modules/@zwave-js/server/dist/lib/state.js:137:38)
    at /usr/src/node_modules/@zwave-js/server/dist/lib/forward.js:34:44
    at Array.forEach (<anonymous>)
    at ZWaveController.<anonymous> (/usr/src/node_modules/@zwave-js/server/dist/lib/forward.js:31:44)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:181) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 6)
(node:181) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Oddly, after loading the SD Card to a Ubuntu VM, grabbing a backup, (It’s been a few weeks since a recent external backup from the SD card… murphy’s law), I set the RPI back up and powered on as one last test before reformatting, system came back up!

The Node had been added however was “unknown”, no entities… and pinging the node from the interface woke it up. The device was then interviewed and added to HA…

Very odd… I’m happy everything is working and the device is not faulty. If anyone else experiences the zwave inclusion error above, it will probably appear as an unknow node, just ping it and it should re-interview.

2022-06-20T12:00:32.642Z CNTRLR   [Node 026] Interviewing Meter...
2022-06-20T12:00:32.643Z CNTRLR » [Node 026] querying meter support...
2022-06-20T12:00:33.001Z CNTRLR « [Node 026] parameter #254 has value: 65535
2022-06-20T12:00:33.008Z CNTRLR   [Node 026] Interviewing Meter...
2022-06-20T12:00:33.008Z CNTRLR » [Node 026] querying meter support...
2022-06-20T12:00:34.300Z CNTRLR   [Node 026] Timed out while waiting for a response from the node (ZW0201)
2022-06-20T12:00:34.301Z CNTRLR   [Node 026] Querying meter support timed out, skipping interview...
2022-06-20T12:00:34.309Z CNTRLR   [Node 026] Interviewing Clock...
2022-06-20T12:00:34.310Z CNTRLR » [Node 026] requesting current clock setting...
2022-06-20T12:00:38.908Z CNTRLR   [Node 026] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2022-06-20T12:00:43.637Z CNTRLR   [Node 026] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2022-06-20T12:00:44.232Z CNTRLR « [Node 026] received meter support:
                                  type:                 Electric
                                  supported scales:     
                                  · kWh
                                  · W
                                  · V
                                  · A
                                  supported rate types: 
                                  supports reset:       true
2022-06-20T12:00:44.234Z CNTRLR » [Node 026] querying meter value (type = Electric, scale = kWh)...
2022-06-20T12:00:44.387Z CNTRLR « [Node 026] received current clock setting: 03:07
2022-06-20T12:00:44.395Z CNTRLR   [Node 026] Interview stage completed: CommandClasses
2022-06-20T12:00:44.397Z CNTRLR   [Node 026] Interview stage completed: OverwriteConfig
2022-06-20T12:00:44.399Z CNTRLR   [Node 026] Interview completed
2022-06-20T12:00:44.400Z CNTRLR   [Node 026] The node is ready to be used
2022-06-20T12:00:45.193Z CNTRLR » [Node 026] querying meter value (type = Electric, scale = W)...
2022-06-20T12:00:45.808Z CNTRLR » [Node 026] querying meter value (type = Electric, scale = V)...
2022-06-20T12:00:46.671Z CNTRLR » [Node 026] querying meter value (type = Electric, scale = A)...
2022-06-20T12:00:46.800Z CNTRLR   [Node 026] Interview stage completed: CommandClasses
2022-06-20T12:00:46.802Z CNTRLR   [Node 026] Interview stage completed: OverwriteConfig
2022-06-20T12:00:46.803Z CNTRLR   [Node 026] Interview completed

Hi,

Just discovered this issue last night. There’s a more permanent fix coming in the driver later but I will push a temporary fix to the add on soon. Sorry for the inconvenience.

1 Like

The new addon has been released

do you mind updating the topic to “[SOLVED] Zwave JS Error - New Device Inclusion (addon 0.61) - fixed in 0.62”? trying to prevent duplicate topics. Thanks!

1 Like