ZwaveJS2MQTT inclusion assigns same node id twice

Setting up a new network with a new HUSBZB-1; using ZwaveJS2MQTT on an RPi. Had some difficulty with a few nodes that were too far away to complete inclusion, which left some holes in the nodes assignments. Tried to add another node, and the inclusion process assigned a node that was already in use. Perhaps it was trying to use one of the missing numbers and got the wrong number? Next node number should have been 80, but it picked 43 instead. Not sure if this is a HUSBZB problem, or ZwaveJS, or …?

Here’s the log from the ZWaveJS integration:

2022-02-22 18:23:22.344 INFO ZWAVE: Calling api startInclusion with args: [
  0,
  { forceSecurity: false, name: 'Jans Mini', location: 'Portable' },
  [length]: 2
]
2022-02-22 18:23:22.419 INFO ZWAVE: Controller status: Secure inclusion started
2022-02-22 18:23:22.425 INFO ZWAVE: Success zwave api call startInclusion true
2022-02-22 18:23:24.729 INFO ZWAVE: Controller status: Inclusion stopped
2022-02-22 18:23:25.437 ERROR ZWAVE: Error while adding node 43 node has been added twice
Error: node has been added twice
    at ZwaveClient._addNode (/opt/server/lib/ZwaveClient.js:2316:63)
    at ZwaveClient._onNodeAdded (/opt/server/lib/ZwaveClient.js:1762:25)
    at ZWaveController.emit (node:events:532:35)
    at ZWaveController.emit (node:domain:475:12)
    at ZWaveController.handleAddNodeStatusReport (/opt/node_modules/zwave-js/src/lib/controller/Controller.ts:2425:10)
    at Driver.handleRequest (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:3148:22)
    at Driver.handleUnsolicitedMessage (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:2756:5)
2022-02-22 18:23:25.443 INFO ZWAVE: Node 43: added with security None
1 Like