Can someone advice me if a Razberry 2 board should work on a Raspberry Pi 5? Currently it’s not working and after a couple of hours of troubleshooting I think it’s never going to work. Can’t really find any documentation if the combination of the two is supported. Thank you for your help.
Thank you for the information. Already tried this and still having the same issue. This is the logfile being generated while starting. I’ve tried to use both /dev/ttyAMA10 and /dev/ttyS0 ports. Both are failing with the same error.
[09:39:28] INFO: No s0_legacy_key is set, generating one...
[09:39:28] INFO: No 'network_key' detected, setting it to 's0_legacy_key' for backwards compatibility
[09:39:28] INFO: No s2_access_control_key is set, generating one...
[09:39:29] INFO: No s2_authenticated_key is set, generating one...
[09:39:29] INFO: No s2_unauthenticated_key is set, generating one...
[09:39:30] INFO: No lr_s2_access_control_key is set, generating one...
[09:39:30] INFO: No lr_s2_authenticated_key is set, generating one...
[09:39:31] INFO: Flushing config to disk due to creation of new key(s)...
[09:39:32] INFO: Soft-reset set to automatic
[09:39:32] INFO: Virtual Machine not detected, enabling soft-reset
cont-init: info: /etc/cont-init.d/config.sh exited 0
cont-init: info: running /etc/cont-init.d/structure.sh
cont-init: info: /etc/cont-init.d/structure.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun zwave_js (no readiness notification)
s6-rc: info: service legacy-services successfully started
[09:39:33] INFO: Successfully send discovery information to Home Assistant.
2024-08-18T07:39:34.043Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗
╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝
███╔╝ █████╗ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ ██║ ███████╗
███╔╝ ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ██ ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║
╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝
2024-08-18T07:39:34.046Z DRIVER version 12.11.2
2024-08-18T07:39:34.046Z DRIVER
Logging to file:
/config/zwave_2024-08-18.log
2024-08-18T07:39:35.420Z CONFIG version 12.11.1
2024-08-18T07:39:39.020Z CNTRLR querying Serial API capabilities...
2024-08-18T07:39:40.183Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2024-08-18T07:39:41.290Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2024-08-18T07:39:43.398Z DRIVER Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK
from the controller (ZW0200)
at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Drive
r.ts:5450:23)
at ZWaveController.queryCapabilities (/usr/src/node_modules/zwave-js/src/l
ib/controller/Controller.ts:1007:37)
at Driver.initializeControllerAndNodes (/usr/src/node_modules/zwave-js/src
/lib/driver/Driver.ts:1475:46)
at Immediate.<anonymous> (/usr/src/node_modules/zwave-js/src/lib/driver/Dr
iver.ts:1276:16)
Error in driver ZWaveError: Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK from the controller (ZW0200)
at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:5450:23)
at ZWaveController.queryCapabilities (/usr/src/node_modules/zwave-js/src/lib/controller/Controller.ts:1007:37)
at Driver.initializeControllerAndNodes (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1475:46)
at Immediate.<anonymous> (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1276:16) (ZW0100)
at Immediate.<anonymous> (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1296:6) {
code: 100,
context: undefined,
transactionSource: undefined
}
Shutting down
[07:39:43] WARNING: Halt add-on
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped