Hey all, I just wasted the better part of my Sunday fighting with the Zigbee module for the Argon ONE V5 M.2 Case. The case itself has been great, so I thought I would add their Zigbee module as physical integration is much nicer than another external USB device. Unfortunately use of the module in HAOS requires some config changes.
I run HAOS on an M.2 drive with this case. Because (under HAOS) I couldn’t run the Argon install script provided for the Zigbee module install, I created a Raspberry Pi OS microSD to boot from. The Raspberry Pi imager makes it easy to install the Lite verison, enable SSH, and run it headless so you don’t have to bother with a monitor, keyboard, and mouse.
I did not have to disconnect the M.2 drive containing HAOS, as the pi will boot from the SD card if present. Once running rpi OS, I was able to run the Argon install script. Note the changes it makes are persistent (firmware?) and will carry over when booting HAOS. But that wasn’t the end of my troubles. Claude helped me through the rest, as shown here:
Problem: HAOS on RPi 5 in an Argon ONE V5 case couldn’t see the Zigbee daughtercard module.
Root Cause: The Argon ONE V5’s internal USB hub runs on the Pi’s dwc2 USB controller (Bus 001), which is not enabled by default in HAOS.
Fix: Add these two lines under [all] in the boot partition’s config.txt on the NVMe drive:
dtoverlay=dwc2,dr_mode=host
usb_max_current_enable=1
Since the boot partition is on NVMe and HAOS locks down filesystem access, the edit had to be made by booting a separate OS from an SD card and mounting the NVMe boot partition from there.