Hi, I am new to Home Assistant. In the past I played a bit with Z-Wave on an old Pi2 using the RaZberry HAT. Now I thought to get everything up and running on a Pi4, but I can't get the HAT detected. A number of instructions on the forum talks about disabling the Bluetooth and enabling the UART in /boot/config.txt, but the HAOS does not have this. What is the correct way of getting things up and running? Where is an instruction for this?
I tried to add a /boot/config.txt via the terminal with the suggested settings:
dtoverlay=gpio-pwm-0,pin=18,func=2
and restarted the system, but got no device /dev/ttyAMA0 Will look into the YAML options...
Option 1 (The easiest way):
Shut down your Pi 4, pull out the SD card/SSD, and plug it into your PC. You will see a small readable partition named hassos-boot. Open the config.txt file there with a text editor, scroll to the bottom, and add these lines:
dtoverlay=disable-bt
enable_uart=1
Save it, put it back in the Pi, and boot it up.
Option 2 (Via SSH Advanced Terminal):
If you don't want to pull the card, install the Advanced SSH & Web Terminal add-on (make sure to turn OFF "Protection Mode" in the add-on settings so you get root privileges). Open the terminal and type:
vi /mnt/boot/config.txt
Add the two lines above at the bottom of the file, save, and reboot.
After doing this, setup your Z-Wave JS integration and use /dev/ttyAMA0 as your serial device path. That should get your RaZberry HAT talking! Let us know how it goes.
Thanks for this! I'll give it a try.
OK. I did some digging around... In trying option 1, I couldn't find the partition. There was only hassos-data and hassos-layer (or overlay). My kernel did not have squashfs, so after enabling it, I did see a squashfs with an image. I did not unpack it or try to add something to it. There were a total of 8 partitions that I saw with fdisk.
With option 2 I have not been able to get the terminal running yet. I'll look into sharing keys etc. (EDIT: found the log of the Advanced SSH) or using the terminal as I have the Pi on my desk and can access the unit directly as explained in: Unfiltered root access?
Opening the console via kb and monitor did the trick! ttyAMA0 and ACM0 are live!