Home Assistant on Rock pi 4

There is no config.txt, only haos-config.txt. But currently there is nothing to configure there.
What you want to do?

I am trying to set up Raspbee 2 HAT unit [RaspBee II Overview].

This requires putting in two lines of code in /boot/config.txt to disable bluetooth on the GPIO to make way for the Raspbee 2.

enable_uart=1
dtoverlay=disable-bt

I have seen the haos-config.txt file and tried to put the code thereā€¦doesnt seem to work. Are these the same config files or is haos-config something else?

Hello, didnt see there were two answers here.

I flashed your image for Rock 4 SE onto a SD card - and then inserted it in the SD slot of the Rock 4.
Home Assistant works perfectly.

Then as I described earlier, I am supposed to edit /boot/config.txt in relation to a configuration of Raspbee 2 Zigbee controllerā€¦but I can not find this file on the SD card with your Home Assistant.

These instructions are for a Raspberry Pi specifically and canā€™t be applied like that to another board. Do you know whether the Raspbee 2 is compatible with Rock Pi?
I could try to provide you with similar devicetree overlays but it seems like the module requires additional kernel drivers and other software which will be hard to get into the image. Is the Raspbee 2 supported by HAOS?

Raspbee 2 is supported by HAOS, doesnt seem to require much tinkering to work with a normal Pi.

Rock Pi is not on the official Raspbee 2, but I got an email from Raspbee support that with the correct configuration it should work, but they cannot dig into it. They sent me this link for innstall guide / configuration:

I picked up this qoute from another message board regarding Home Assistant + Rock Pi:

ā€œProbably you know Rock Pi 4 doesnā€™t work out-of-box with HATs talk on RX/TX, actually neither Raspberry Pi 3. They have different problem but all have the same symptoms, RX/TX are occupied by other functions, on Raspberry Pi 3 itā€™s the Bluetooth, on Rock Pi 4 itā€™s the FIQ debugger.ā€

Was wondering if the Rock Pi needs an overlay to ā€œunoccupyā€ the RX/TXā€¦but not the same as a normal Piā€¦FIQ debugger???

Reply aboveā€¦:slight_smile:

I think they are referring to pin 8 and 10 which are by default mapped as serial2 and used as the main serial output. It should be possible to create an overlay which undoes that and makes the pins available for the Raspbee.
Maybe it is even enough to modify the kernel commandline (cmdline.txt) and remove both of these arguments:

earlycon=uart8250,mmio32,0xff1a0000 console=ttyS2,115200n8

Then, the kernel would not occupy the serial port anymore and that may be enough. But that is hard for me to verify without the hardware.

Ok, I will try that.

I couldnt wait and bought the USB version of Raspbee ā†’ Conbee. That one works without trouble.
After reading some threads about zigbee controllers on pi, many people recommended using the USB version with an extionsion chord to get som distance from the Pi to minimize radio interference. So maybe this was all for nothing anyway :slight_smile:

But for curiosity I will try your proposal. Thank you for the HA port and for the help.

What are your plans for the HA-ROCK port, do you intend to update it alongside HA updates?

Yeah, connecting it via USB sounds much more convenient.

But for curiosity I will try your proposal. Thank you for the HA port and for the help.

Cool, I am also curious to know if this works.

What are your plans for the HA-ROCK port, do you intend to update it alongside HA updates?

Yes I plan stay up to date with new HAOS versions. As soon as it is more mature and has a decent user base, I would definitely like to merge it into upstream but I am not sure what the HAOS folks think about that and what their requirements for upstreaming are.

I just got a Rock 4C+ as well and tried the SD-card only way (there is no SSD capability on the 4C+).

I managed to boot just fine. Even restoring a full backup from a VM-version of HA which I ran before getting the ROCK worked perfectly. Below however are three issues bugging me:

  1. WIFI not working
    Under System->Network there is no WIFI option. On Github WIFI is listed as being supported.
    (I am well aware that using LAN is superior, yet I would like this to work)

I ran dmesg in VSCode terminal and found the following suspicious entries:

[ 6.991541] brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.radxa,rock-4c-plus.bin failed with error -2
[ 9.867500] ieee80211 phy0: brcmf_bus_started: failed: -110
[ 9.873962] ieee80211 phy0: brcmf_attach: dongle is not responding: err=-110

Could it be that some kernel parameter is required to disable power-saving?

  1. No CPU-Temp
    Apparently the CPU-temperature cannot be read out. The sensor is not created in system monitor. There is also no thermal_zone* under /sys/class/thermal. Any way to fix this?

  2. The LEDs cannot (easily) be disabled.
    Please see this thread: Disable LEDs on Rock Pi - #2 by Elarion245
    It would be very nice to add some flags to /boot/haos-config.txt which enable/disable the various LEDs (just as is possible for Raspberry via the config.txt)

WIFI not working

There is already another issue on GitHub by a user who noticed that Wifi doesnā€™t work on the latest release. I will try to look into that as soon as possible. The log line you posted is already helpful. You could try if the 20230204 release works for you, although there is no specific image for the 4C.

No CPU-Temp

I never looked into that. Does raspian or another distro support reading the temperature? If yes we could probably borrow that code.

The LEDs cannot (easily) be disabled.

It should be quite straightforward to create a device tree overlay which disables the heartbeat if this what you want. I am planning to include overlays in the next release.

In general, it would probably be better if you post these as separate issues/feature requests on GitHub so that we can keep track :slight_smile:

1 Like

Thank you for coming back on this.

I am currently not anywhere near my Rock, so tests will need to be delayed by a couple of days.

I will open individual topics at Github. For the time being I can say the following.

For the Led:
An overlay would be great. For the time being I solved it via a great add-on (see led thread)

On the CPU Temp:
I have not tested it myself, but I remember reading that the native ubuntu server OS supports reading the cpu and gpu temps. I am running passive cooling, so some way of accessing them would be great!

Wifi:
Will test the older version.

Hate to resurrect an old thread, but it seems to be the ONLY pertinent thread.

FYI, I downloaded the latest image (1706592026 from the above github link) for Rock4SE and burned it with Balena Etcher to a 64M emmc card and booted from the emmc with no issues, except that wifi is still not enabled.

The HA tutorial indicates that to boot from an emmc card, one has to update the firmware first. Apparently that isnā€™t necessary for the current Rock images.

UPDATE: I was able to get the Radxa4SE to connect to wifi after setting the wifi paramaters, including password, in the homeassistant settings on my desktop computer.