How to operate a Razberry 2 module (GPIO) with Home Assistant?

I recycled an old Raspberry Pi 3D with a Razberry 2 module (supporting Z-Wave modules) to install Home Assistant. Unfortunately, there’s no way to make it work.

Basically, it conflicts with the Raspberry Pi’s Bluetooth.

So, I’m going to detail all the steps I’ve gone through to help you solve this problem. I’ll try to be quick and concise so I don’t waste your time.

Razberry 2 Update:

This step is not mandatory, but since I did it, I figured I’d include it. My module is a few years old, so it was time to update it. There is a firmware update procedure with ZMESerialUpdater, but not being sure which firmware version to use, I took a different route.

To do this, I installed Raspberry OS on an SD card and booted it to my Raspberry Pi. So far, nothing crazy. Then I installed Z-Way, the Z-Wave OS that allows you to drive the Razberry. The goal is to use it to update the firmware.

So once I was connected via SSH to my Rpi, I ran the following command:

wget -qO - | sudo bash

Once it was installed and the Z-Way service is launched, just go to this URL: Below the login form, you should then see the IP address of your Raspberry. Click on it, and you will be taken to the Z-Way interface.

Then, go to the “Management” menu (accessible at the top right)…

and you will then be able to update the firmware.

So that’s a good thing done.

Switching Home Assistant to Debug Mode:

Now I’m assuming you’ve deployed Home Assistant OS on your Raspberry Pi. The goal here is to have SSH access to HAOS (Home Assistant OS).

So the first step is to go to the Home Assistant App Store and install “Advanced SSH & Web Terminal.” Launch it in unprotected mode.

We’re going to need it for the rest of the operation. Except that this web terminal will not give access to the entire HAOS system… We don’t have access to the boot configuration, for example.

So we’re going to set HAOS to switch it to debug mode to have SSH access that gives full system access.

To do this, you need a simple USB stick formatted as FAT32, EXT4, or NTFS. Rename this key to “CONFIG” in uppercase. This is important because that’s what makes it detect by HAOS.

On top of that, we’re going to put a public SSH key. On Windows, you can download an SSH client such as PuTTY and use the included PuTTYgen utility to generate the key pair.

Alternatively, on Linux, macOS (and Windows), if OpenSSH is installed, you can generate a key pair with the following command:

ssh-keygen -t rsa -b 4096

Give it a name, enter a password, and you’re done. You will have a pair of keys like id_haos (it’s the private key; you don’t touch it) and (it’s the public key that you will copy to the USB key). Rename this public key on the USB drive: authorized_keys. You can also copy and paste this:

cat /Users/manu/.ssh/ > /Volumes/BT/authorized_keys

Then, insert this USB drive into your Raspberry Pi. Then you have two choices. Either you reboot the Raspberry, and when it loads, HAOS will integrate your key. Or you go back to the Home Assistant web interface, and in Advanced SSH & Web Terminal, you enter the following command:

ha os import

This will import the key. Next, open a terminal on your computer and initiate an SSH connection like this, using port 22222 and specifying the path to your private key with the -i parameter:

ssh root@homeassistant.local -p 22222 -i /Users/manu/.ssh/id_haos

And there you have it; you are connected via SSH to your HAOS without any restrictions.

Fixed issue with conflict between Z-Wave and Bluetooth:

Now we’ll be able to fix the problem related to Z-Wave/Bluetooth. Still in SSH, you will edit the following file with vi:

vi /mnt/boot/config.txt

Vi, you know… You have to press “i” to edit the content. And when you’re done, you press “Esc” to exit edit mode and you press “:wq” to save and exit the editor.

So we’re going to edit the file and uncomment the dtoverlay line and add the force_turbo line to it like this:


As soon as that’s done, you save, quit Vi, and reboot the Raspberry Pi:


There you go. Then you go back to the Home Assistant interface, and you can set up your Z-Wave network as it should be.


Mohamed SAKHRI
Mohamed SAKHRI

I'm the creator and editor-in-chief of Tech To Geek. Through this little blog, I share with you my passion for technology. I specialize in various operating systems such as Windows, Linux, macOS, and Android, focusing on providing practical and valuable guides.

Articles: 1378

Newsletter Updates

Enter your email address below and subscribe to our newsletter

Leave a Reply

Your email address will not be published. Required fields are marked *