You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a node is removed, an error like the following may occur:
2024-07-14 17:54:47.153 INFO Z-WAVE: Calling api startExclusion with args: [ [length]: 0 ]
2024-07-14 17:54:47.164 INFO Z-WAVE: Controller status: Exclusion started
2024-07-14 17:54:47.164 INFO Z-WAVE: Success zwave api call startExclusion true
2024-07-14 17:55:02.677 INFO Z-WAVE: Controller status: Exclusion stopped
2024-07-14 17:55:02.684 INFO Z-WAVE: [Node 029] Removed, reason: 0
2024-07-14 17:55:02.685 ERROR APP: Unhandled Rejection, reason: TypeError: Cannot read properties of undefined (reading 'remove')
TypeError: Cannot read properties of undefined (reading 'remove')
at ZwavejsProm.onNodeRemoved (/var/lib/zwave/node_modules/@kvaster/zwavejs-prom/index.js:90:25)
at ZwaveClient.emit (node:events:514:28)
at ZwaveClient._removeNode (/var/lib/zwave/node_modules/zwave-js-ui/server/lib/ZwaveClient.js:3768:18)
at ZwaveClient._onNodeRemoved (/var/lib/zwave/node_modules/zwave-js-ui/server/lib/ZwaveClient.js:3132:14)
at ZWaveController.emit (node:events:526:35)
at ZWaveController.handleRemoveNodeStatusReport (/var/lib/zwave/node_modules/zwave-js/src/lib/controller/Controller.ts:4375:10)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at Driver.handleRequest (/var/lib/zwave/node_modules/zwave-js/src/lib/driver/Driver.ts:4772:22)
at Driver.handleUnsolicitedMessage (/var/lib/zwave/node_modules/zwave-js/src/lib/driver/Driver.ts:4211:5)
For me, this seems to happen 100% of the time after removing a node.
This causes the driver to become confused, thinking that exclusion mode is still active when it is not. A restart is required to fix it.
The text was updated successfully, but these errors were encountered:
When a node is removed, an error like the following may occur:
For me, this seems to happen 100% of the time after removing a node.
This causes the driver to become confused, thinking that exclusion mode is still active when it is not. A restart is required to fix it.
The text was updated successfully, but these errors were encountered: