Migrating My Residence Assistant from Python Digital Setting to Residence Assistant Working System in Proxmox

The Migration Plan

Earlier than diving in, I created an in depth migration plan:

• Snapshot the present Residence Assistant Proxmox VM
• Obtain Residence Assistant backups
• Be sure I’ve copies of Z-wave safety keys
• Word USB passthrough gadgets for my Z-Wave/Zigbee controller and Bluetooth adapter
• Be sure I do know my credentials for Nabu Casa and Residence Assistant
• Shut down the present Residence Assistant VM
• Run the neighborhood HAOS Proxmox set up script in superior mode to customise disk dimension, identify, and ID
• Assign USB passthrough gadgets for Z-Wave/Zigbee and Bluetooth gadgets to new VM
• Restore Residence Assistant backup from Nabu Casa
• Set up Z-Wave JS and change to Z-Wave JS UI
• Add the Samba add-on for file entry
• Check and get every thing working!

All the things went easily at first. Utilizing my new Proxmox host, the neighborhood HAOS Proxmox script created the brand new VM in minutes. I restored my backup from Nabu Casa and restarted… solely besides into secure mode.

Hiccup #1: Secure Mode and the Lacking Listing

Secure mode turned out to be brought on by a nasty allowlist_external_dirs path. My previous Ubuntu setup used a listing for writing month-to-month vitality readings that didn’t exist in HAOS. I’d written about that setup in an earlier submit on monitoring house energy utilization and price with Residence Assistant.

Up to now, I’d simply edit configuration recordsdata through SSH, however HAOS doesn’t work that means. As an alternative, I put in the File Editor add-on, up to date the listing path in configuration.yaml, and rebooted. Easy repair, even when I did miss the previous command line flexibility.

Backups Work Amazingly Effectively

Top-of-the-line components of this migration was seeing how Residence Assistant backups embrace every thing—customized parts, integrations, and even my RF management script that I wrote about in Utilizing a Sonoff RF Bridge to Broaden Your Good Residence. The set up asks you if you wish to restore a backup, and you are able to do it from a neighborhood backup or from Nabu Casa. After restoring, all of that labored instantly with no points, besides…

Hiccup #2: Alarm.com Integration

My customized Alarm.com integration from HACS didn’t reauthenticate after the restore, and wouldn’t settle for my username and password, although I knew they have been appropriate. The repair was simple: I reinstalled the mixing and reauthenticated, and it labored instantly.

Rebuilding the Z-Wave Community

Subsequent, I centered on getting Z-Wave working once more. I adopted Residence Assistant’s Z-Wave JS setup information, switching to Z-Wave JS UI—the identical interface I used beforehand through Ubuntu Snap. I desire Z-Wave JS UI as a result of it offers higher visibility into machine statuses and communication points.

The migration principally went positive, however with about 50 Z-Wave gadgets, it took time for every thing to reconnect. Lots of the battery-powered gadgets wanted to be woken up manually. Fortunately, I had my safety keys useful, and finally, each machine got here again on-line.

Zigbee, then again, labored nearly immediately with none configuration modifications. Good and simple. However then, I solely have a handful of Zigbee gadgets

Hiccup #3: Presence Detection and the Disabled Entity

After the Z-Wave rebuild, I observed that presence detection wasn’t working. I exploit the nmap integration to detect smartphones on my community. For some motive, the nmap entity tied to my telephone was disabled, although the others weren’t. Re-enabling it mounted the problem instantly.

Hiccup #4: Telegram Bot Notifications

My Telegram Bot integration additionally failed to attach after migration, however reinstalling the mixing mounted it. I wrote about my Telegram setup in Utilizing a Telegram Bot for Residence Assistant Notifications, and fortunately, the reconfiguration was easy.

Customized Irrigation Controller, Cron Job, Shell Command, and MQTT Setup

Certainly one of my extra custom-made setups is my Residence Assistant irrigation controller, which makes use of a shell command triggered by cron and MQTT. Since HAOS doesn’t provide you with direct cron entry, I moved that shell script and cron job to my Proxmox VM that runs all my Docker containers.

Now, getting the shell command to work in HAOS was a chore. My shell script makes use of instructions not accessible within the HAOS Docker container. Because the script is already hosted on the Proxmox VM that runs my Docker containers, I made a decision to arrange my shell command to ssh into that VM and run the script. To do that that you must:

• Create an SSH key on the goal VM and replica that to the /config folder of your HAOS set up (so it survives upgrades)
• You’ll additionally wish to create a known_hosts in your config listing so it doesn’t get overridden
• Then you may SSH into your VM and execute a script with no password.
• Replace your Residence Assistant shell command to make use of an SSH command that particularly makes use of the important thing within the config folder and the known_hosts file

That’s the overview. This neighborhood information walks by the particular instructions.

That very same VM already hosts my MQTT dealer utilizing Docker and Eclipse Mosquitto, which I described in MQTT and Residence Assistant Utilizing Docker and Eclipse Mosquitto. I nonetheless use that dealer as an alternative of the one now constructed into Residence Assistant, just because it’s steady, acquainted, and already built-in with my community automations.

Ultimate Ideas

In spite of everything that, issues stabilized shortly. I examined a number of automations and integrations, and every thing gave the impression to be functioning usually. Even the cell app continued working, possible as a result of I reused the identical hostname and IP deal with from the previous set up.

I put in the Samba add-on and arrange a share on my Linux desktop for simple entry to configuration recordsdata—simple and dependable.

Then, only for a remaining take a look at, I attempted upgrading Residence Assistant from the UI. It labored completely. The OS up to date, too, so I not have to fret about sustaining the underlying system. Even restarts from the Residence Assistant UI now work, which they by no means did in my previous Python venv set up.

I’d nonetheless add SSH entry later, however for now, every thing is operating easily. From begin to end, the complete migration took just some hours, with most of that point spent rebuilding the Z-Wave community.

The true take a look at can be if anybody in my household notices something. I doubt they are going to—and that’s precisely the way it must be.

Key Takeaways

• Residence Assistant is formally deprecating Core and Supervised installs—migrate to the Residence Assistant Working System (HAOS) for long-term help.
• The Proxmox set up script makes spinning up an HAOS VM easy and quick.
• Restoring backups preserves most customized parts, integrations, and automations.
• Be ready for minor fixes: path modifications, disabled entities, or reauthentication points.
• HAOS simplifies life—upgrades and restarts from the UI simply work.