Hi all-
Pi4
Aeotec Z-Stick Gen5 Z-Wave using a USB Hub to get around the USB problems this stick was having.
Not sure Core and Supervisor versions, I stopped updating them in Feb or March when the release notes mentioned that OZW support was being removed
Everything was working fine until I woke up to my z-wave integration not functioning properly, all devices in an ‘unavailable’ state. I performed a reboot to no luck. After initial troubleshooting to make sure the USB stick was plugged in, ensuring device path was correct, etc; I figured that now would be a great time to migrate to Z Wave JS. In hindsight, attempting a migration when the base config was not functioning was a blunder.
Ultimately, I decided to rollback to a fully operating backup. Again, another blunder was not putting core and supervisor info in the backup file name. I used the latest image, restored the backup and I’m in the same spot. OZW does not seem to be functioning. And in this broken state, I cannot seem to migrate to Z Wave JS. The other option is that the stick has failed, but I am not sure how to test that.
Presently, running core 2021.12.3 and supervisor 2022.04.0.
I have removed OZW. Rebooted, and installed the Z Wave JS supervisor and integration (again). None of the z wave devices are being pulled in. The supervisor error I get it:
Unable to start driver ZWaveError: The security key for class S0_Legacy must be a buffer with length 16! (ZW0108)
at checkOptions (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:285:11)
at new Driver (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:449:3)
at /usr/src/node_modules/@zwave-js/server/dist/bin/server.js:96:11
at Object.<anonymous> (/usr/src/node_modules/@zwave-js/server/dist/bin/server.js:134:3)
at Module._compile (internal/modules/cjs/loader.js:1085:14)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
at Module.load (internal/modules/cjs/loader.js:950:32)
at Function.Module._load (internal/modules/cjs/loader.js:790:12)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:75:12)
at internal/main/run_main_module.js:17:47 {
code: 108,
context: undefined,
transactionSource: undefined
Puting the supervisor server in Debug mode allows the integration to connect to the server, but does not pull over any devices and I receive errors on the server:
New client
Unexpected error TypeError: driver.controller.getProvisioningEntries is not a function
at Function.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/controller/message_handler.js:50:51)
at Object.controller (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:37:103)
at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:95:99)
at WebSocket.<anonymous> (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:48:45)
at WebSocket.emit (events.js:400:28)
at WebSocket.emit (domain.js:475:12)
at Receiver.receiverOnMessage (/usr/src/node_modules/ws/lib/websocket.js:1137:20)
at Receiver.emit (events.js:400:28)
at Receiver.emit (domain.js:475:12)
at Receiver.dataMessage (/usr/src/node_modules/ws/lib/receiver.js:528:14)
Deleting the legacy code, and letting it be auto configured allows the supervisor server to work without error, but breaks the Z Wave JS integration piece. Deleting, rebooting and attempting new install of the integration provides a ‘abort’ and failed to connect.
What should my next troubleshooting steps be?