Razberry (Zwave) Board is not recognized after HassOS 4.8

Configuration Z-Wave
1

Hello everyone,
after the update from HassOS 3.13 to 4.8 my Razberry Boad does not work/is not recognized anymore!
I have reproduced it, i.e. I have installed an old backup and updated all of them, except the update HassOS 4.8!
OZW Log ->
14:31:54.224 Always, OpenZwave Version 1.4.3469 Starting Up
14:32:13.081 Info, Setting Up Provided Network Key for Secure Communications
14:32:13.081 Warning, Failed - Network Key Not Set
14:32:13.081 Info, Opening controller /dev/ttyAMA0
14:32:13.081 Info, Trying to open serial port /dev/ttyAMA0 (attempt 1)
14:32:13.082 Info, mgr, Added driver for controller /dev/ttyAMA0
14:32:13.082 Info, Serial port /dev/ttyAMA0 opened (attempt 1)
14:32:13.082 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
14:32:13.082 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
14:32:13.082 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
14:32:13.083 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
14:32:13.083 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
14:32:13.083 Detail,
14:32:13.083 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
14:32:13.083 Detail, contrlr, Notification: DriverFailed

Any tips are very helpfull

2

I have the same problem.

I reverted to 3.13 but it still don’t work. I don’t know what to do right now. They say the 4.9 should fix the issue, but apparently it does not.

3

I also have the same problem. I have reinstalled the whole package from a fresh download but no success… How do I install an older version so I can get this up and running again?

4

Hello, Magnus,
I was lucky enough to have a one-to-one copy of an SD card. (part of my backup strategy)
From this version I have done the updates (except for HassOS 4.8!)
But what also worked was the downgrade from 4.8 back to 3.13!

5

Now - more than half a year later - it doesn’t seem to work either, right?

I installed Home Assistant OS 5.9 and ‘Notification: DriverFailed’ …

Anyone successful here?

6

I think you have to disable BlueTooth on the Pi4 to use the Razberry board
Check:

7

Thanks Rick!

I did - unfortunately for no success!

8

Not sure about that. Setting BT to miniUART should allow foth BT and GPIO at the same time:
/boot/config.txt:

dtoverlay=miniuart-bt
force_turbo=1

The 1st line switches BT to the miniUART and the 2nd line is needed with miniUART BT to set the VPU core clock to a fixed frequency, this is required based on https://www.raspberrypi.org/documentation/configuration/uart.md / UARTs and Device Tree -section, 3rd chapter.

1 Like
9

I’ve switched force_turbo=1 with core_freq=250 as there were some BT related errors visible in system log. After the switch I have not yet seen any BT errors.
Now I have Home Assistant with RazBerry2 Z-Wave hat and BlueTooth working simultaneously.