Migrating Home Assistant to an Argon ONE V5

Many months ago, Argon Forty sent me an Argon One V5 NVMe case for Raspberry Pi 5, along with the Argon Industria OLED display, and Argon Industria Zigbee Module. I wanted to migrate my existing Home Assistant installation from an Argon NEO 5 NVMe case into the larger ONE V5. The migration would replace my external Nortek USB Zigbee dongle with an internal module and provide a larger passive cooling surface, reducing how often the fan needs to run. The Process My Home Assistant system runs on a 4GB Raspberry Pi 5 and boots directly from a 250GB WD Blue NVMe drive. It does not use an SD card. After shutting down Home Assistant and disconnecting the power, I moved the Raspberry Pi 5 and NVMe drive from the NEO 5 into the ONE V5. I installed the Argon Industria Zigbee module, connected the PCIe ribbon cable between the Pi and NVMe daughterboard, and attached the OLED display to its header. The system booted successfully on the first attempt, and Home Assistant resumed running from its new enclosure. I then configured the fan monitoring, OLED display, and Zigbee module. Temperature Controlled Fan Both the ONE V5 and NEO 5 connect to the Raspberry Pi 5’s standard fan header, so the Pi automatically adjusts the fan speed according to temperature. I installed the ArgonOneV5Linear Add-on, which exposes the current fan speed as an entity in Home Assistant. You can customise the temperature thresholds and fan speeds in /boot/config.txt. The README for the OLED Add-on includes several example configurations. Enabling the Display Ben Wolstencroft’s Home Assistant Add-on made the OLED straightforward to configure. I added its repository to the Home Assistant App Store and installed the Add-on. The display immediately began cycling through resource usage, temperature, fan speed, the IP address, and other system information. The user interface lets you select the temperature units and choose which screens to display. Editing the YAML configuration provides additional options, including the interval between screens. I configured the display to show CPU usage, storage, RAM, temperature, fan speed, and the IP address. It changes screens every five seconds. Enabling the Argon Industria Zigbee Module Home Assistant did not detect the Argon Industria Zigbee module after the first boot. I found the solution in a Home Assistant Community forum post. The ONE V5 connects its internal USB hub through the dwc2 controller, but Home Assistant OS does not enable that controller by default. To enable the controller, I added these two lines to the [all] section of /boot/config.txt: dtoverlay=dwc2,dr_mode=host usb_max_current_enable=1 Editing the Boot Volume Home Assistant OS does not expose the boot volume through its normal file-system tools when the Pi boots from NVMe. I therefore shut down the Pi, removed the NVMe drive, placed it in a USB enclosure, and connected it to my Mac. 1. Identify the drive: diskutil list external physical /dev/disk4 (external, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *250.1 GB disk4 1: EFI hassos-boot 67.1 MB disk4s1 2: Linux Filesystem 25.2 MB disk4s2 3: Linux Filesystem 268.4 MB disk4s3 4: Linux Filesystem 25.2 MB disk4s4 5: Linux Filesystem 268.4 MB disk4s5 6: Linux Filesystem 8.4 MB disk4s6 7: Linux Filesystem 100.7 MB disk4s7 8: Linux Filesystem 249.3 GB disk4s8 2. Confirm the identifier of the hassos-boot partition. On my system, it appeared as /dev/disk4s1. Replace /dev/disk4s1 with the identifier shown on your Mac. Check the identifier carefully before continuing. Using the wrong one could cause you to modify another drive. 3. Create a mount point and mount the partition: sudo mkdir -p /Volumes/hassos-boot sudo mount_msdos -o rw /dev/disk4s1 /Volumes/hassos-boot 4. Add the two configuration lines to /Volumes/hassos-boot/config.txt in the [all] section. 5. Save the changes and unmount the volume: sync sudo umount /Volumes/hassos-boot 6. Eject the NVMe drive in Finder, reinstall it in the Argon ONE V5, and power the Pi back on. After Home Assistant booted, I opened Settings → System → Hardware → System Hardware. Home Assistant now listed the CP2102N interface as ttyUSB0. Migrating Zigbee Network I expected this to be the most difficult part of the migration, but Home Assistant made it surprisingly easy. I opened Settings → Devices & Services → Zigbee Home Automation → Add Hub and added the new Argon module. Home Assistant then offered to migrate my existing Zigbee network. I temporarily reconnected the Nortek USB module, after which Home Assistant transferred the network and all its devices to the new coordinator. The Zigbee visualisation identified the new coordinator as a “Texas Instruments CC2652”. It showed every device connected either directly to the coordinator or through one of my existing Zigbee routers. Conclusion The migration proved much easier than I expected. Home Assistant transferred the complete Zigbee network without requiring me to pair every device again, and the ONE V5 now houses the Pi, NVMe storage, Zigbee coordinator, and status display in a single enclosure. My RFX433 receiver is now the only external USB radio connected to the Raspberry Pi. Perhaps that should be my next migration project. Product Links Raspberry Pi 5 (Amazon) (Pimoroni) (ThePiHut) Raspberry Pi 5 PSU (Amazon) (Pimoroni) (ThePiHut) Argon ONE V5 Case with single M.2 NVMe support (Amazon) (Pimoroni) (ThePiHut) (Argon40) Argon ONE V5 Industria OLED Display Module (ThePiHut) (Argon40) Argon Industria Zigbee Module (Amazon) (ThePiHut) Sabrent USB NVMe enclosure (Amazon) Amazon and AliExpress links are affiliate links that help support the site. Where possible, I’ve used regional links that should take you to the product in your local Amazon store. I’ve included links to other suppliers for convenience. The post Migrating Home Assistant to an Argon ONE V5 appeared first on Martin Rowan.