Raspi4 & Razberry 2 board - is it incompatible with Hassio?

Configuration
1

I have added dtoverlay=pi3-disable-bt to the end of my /mnt/boot/config.txt file, and the zwave integration seems to install successfully in the UI by using the

USB path = /dev/ttyAMA0

per my hardware listing, however when I try to start the zwave network, I continue to get the following error in my OZW_Log.txt:

2020-04-14 20:48:24.890 Always, OpenZwave Version 1.4.3469 Starting Up
2020-04-14 20:49:09.311 Info, Setting Up Provided Network Key for Secure Communications
2020-04-14 20:49:09.312 Info, mgr, Added driver for controller /dev/ttyAMA0
2020-04-14 20:49:09.312 Info, Opening controller /dev/ttyAMA0
2020-04-14 20:49:09.315 Info, Trying to open serial port /dev/ttyAMA0 (attempt 1)
2020-04-14 20:49:09.315 Info, Serial port /dev/ttyAMA0 opened (attempt 1)
2020-04-14 20:49:09.316 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-04-14 20:49:09.316 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2020-04-14 20:49:09.316 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2020-04-14 20:49:09.316 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2020-04-14 20:49:09.318 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2020-04-14 20:49:09.318 Detail,
2020-04-14 20:49:09.318 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-04-14 20:49:09.318 Detail, contrlr, Notification: DriverFailed

I’ve tried dtoverlay=pi3-miniuart-bt as well as replacing pi3 with pi4. no change.
Any suggestions?

2

Sorry, I failed to mention I’ve tried on HA version 108.2, 108.3. and now 108.4.

3

I just got the Razberry first version Razberrry versions up and running since a week now without issues on a rpi4.
This is the last section of my /boot/config.txt:

[pi4]
# Enable DRM VC4 V3D drive`Preformatted text`r on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3dmax_framebuffers=2

[all]
gpu_mem=16
dtoverlay=disable-bt
enable_uart=1

Some tips:
The ModemManager must be disabled and stopped when using Z-Wave or Zigbee (https://www.home-assistant.io/docs/z-wave/installation/#home-assistant).

# Check the status of the ModemManager
$ sudo systemctl status ModemManager
or 
$ sudo systemctl |grep Modem

# Disable and stop the ModemManager
$ sudo systemctl disable ModemManager
$ sudo systemctl stop ModemManager

# Purge the ModemManager (optional)
$ sudo apt-get purge modemmanager
4

Thanks for the help!
I added these two lines out of your config:
dtoverlay=disable-bt
enable_uart=1
and it’s working now for the first time!

I tried to turn off ModemManager, but there was no ModemManager in my systemctl.
systemctl |grep Modem yielded null, systemctl |grep Manager yielded several NetworkManager items.

I also upgraded to Hassos 3.13, but I think it was those two lines that fixed it!

Thanks again, wwortel!