Importing HomeAssistant Backup into Umbrel > Machine > HomeAssistant

[pellebinke89]

Backup HomeAssistant inlezen in Umbrel > Machine> HomeAssistant

Afgelopen week Umbrel geïnstalleerd met HomeAssistant Operating System HAOS via Machines aldaar. Op een Acer 8GB RAM en 128 SSD en 1TB HDD. Van HomeAssistant, welke nog draait in een Virtual Machine op een Dell Wyse met Proxmox versie 8, een backup gemaakt en die backup meteen aangevinkt bij het Inlezen van een backup in HA onder Umbrel. Voor de start werden de 4 of 5 vinkjes allemaal geaccepteerd, dus klikken op inlezen, of zoiets. Het proces ging van start en op het scherm verscheen de melding dat het wel 45 minuten kan duren.

Na 4 of 5 uur heb ik de pc waar Umbrel op draait maar uitgezet, andere manieren om het proces te stoppen zag ik niet zo snel. PC weer starten met Umbrel, maar nu is HA niet meer te bereiken met umbrel.local:40000 of IPadres:40000.

Iemand enig idee wat ik nu kan doen?

Ik heb wel een idee: De nieuwste versie van Proxmox erop zetten en daarin HA laten draaien

_________

English

Importing HomeAssistant Backup into Umbrel > Machine > HomeAssistant.

Last week, I installed Umbrel with the HomeAssistant Operating System HAOS via Machines there. On an Acer 8GB RAM, 128GB SSD, and 1TB HDD. I created a backup of HomeAssistant, which is still running in a Virtual Machine on a Dell Wyse with Proxmox version 8, and immediately selected that backup when importing a backup into HA under Umbrel. Before starting, all 4 or 5 checkboxes were accepted, so I clicked on “import,” or something similar. The process started, and a message appeared on the screen stating that it could take up to 45 minutes.

After 4 or 5 hours, I just turned off the PC running Umbrel; I didn’t see any other ways to stop the process quickly. I restarted the PC with Umbrel, but now HA is no longer accessible via umbrel.local:40000 or IPadres:40000.

Does anyone have any idea what I can do now?

I do have an idea: Install the latest version of Proxmox and run HA in it

On Umbrel

On the Dell Wyse:

The backup file.

will follow

Proxmox 8.1.4 on the Dell Wyse

will follow

[pellebinke89]

[aidencole]

hey, this might be the port issue again. switching to port 80 fixed the fresh install, but restoring your backup may have switched HA back to 8123.

Try changing the machine port back to 8123 in the VM’s port forwarding settings. Keep the Umbrel port at 40000, then try http://umbrel.local:40000 again.

If that doesn’t work, can you share a screenshot of the VM’s console in Machines and the browser error? I’d leave the Dell install and backup untouched for now.

[pellebinke89]

The port is still on 80

The console of Machines:

When I type in the adressbar: http://192.168.178.118:4000/

Exceptions of the HTTPS modes.

[aidencole]

ah, that console screenshot helps! Home Assistant shows its address ending in :8123 now. The 80 in your first screenshot is where Umbrel forwards connections, so those two need to match.

In that port forwarding screen, change 80 under “Machinepoort” to 8123, leave “Umbrel-poort” at 40000, and click “Bewaren”. Then open:
http://192.168.178.118:40000

Your IP-address screenshot has :4000, so watch out for the missing zero too.

If it still won’t open, click inside the black Home Assistant console, type core logs at the ha > prompt and press Enter. Share a screenshot of the last lines so we can see whether HA is having trouble starting.

[pellebinke89]

Yes, I changed Machineport to :8123 and then I could Login.

But on the dashboard I could read the HAOS image I used im Umbrel is not ment to use in a virtual machine.

Some integrations do not work correct: Shelly and UPnP/IGD

What I am going to do (I think)

• Delete the used HAO image
• Install the image, ment to use for the KVM virtualisation
• Pay close attention to the Machineport!
• Import a new backup

Do I forget something?

[aidencole]

nice, glad you’re back in! yep, the KVM image is the right one. I was too quick to say to leave the image alone earlier just because it booted.

I’d download a fresh backup to your computer first, along with its encryption key if it’s encrypted. Then use the KVM .qcow2.xz image linked here:

Linux

If you have room, keep the current VM stopped rather than deleting it until the replacement works. Use a different Umbrel port, like 40001, for the new VM while keeping the old one. Check the machine port before and after restoring, since it may change from 80 to 8123 again. Once you’re testing the restored setup, stop HA on the Dell too so you don’t have two copies running the same automations.

One catch: the Shelly and UPnP errors may be a separate networking issue. Umbrel puts VMs on a separate network, which can affect device discovery and updates. The correct image should address that warning, but may not fix those integrations. If they’re still failing afterward, share the error details from inside each integration and the Shelly models you’re using.

[pellebinke89]

Thanks again.
I am removing the current version of HAOS in Umbrel > Machines on the Acer after all, because it is a test machine. The ultimate goal is a properly functioning HAOS on the Dell server and synchronization software for our files. That is currently Syncthing.
I will get started today or tomorrow to install the new HAOS under Umbrel.

[pellebinke89]

Nederlands/Dutch, English below:

Vandaag geprobeerd om haos_ova-18.3.qcow2.xz of het Schijfkopiebestand haos_ova-18.3.qcow2 geïnstalleerd te krijgen als Machine in Umbrel. Steeds kreeg ik de melding: “Machine Image niet geldig”. Morgen maar verder kijken, ben nu te moe.

English:

Today I tried to install haos_ova-18.3.qcow2.xz or the disk image file haos_ova-18.3.qcow2 as a Machine in Umbrella. I kept getting the message: “Machine image invalid”. I’ll look into it again tomorrow, I’m too tired right now.

[aidencole]

sorry, this one’s on me. The KVM image is right for Home Assistant, but Umbrel’s custom-image importer only accepts .img and .iso files. I missed that when I suggested the .qcow2 download.

The fix is to convert it to a raw .img, not just rename it. I tested the conversion with that exact HAOS image and confirmed Umbrel accepts the result.

Put the extracted haos_ova-18.3.qcow2 file directly in Files > Home on Umbrel. Then open Settings > Advanced settings > Terminal > umbrelOS and paste:

cd ~/umbrel/home &&
test ! -e haos_ova-18.3.img &&
qemu-img convert -p -f qcow2 -O raw haos_ova-18.3.qcow2 haos_ova-18.3.img

Wait for it to reach 100%, then select the new haos_ova-18.3.img in Machines. Keep AMD64 and UEFI selected, and give it at least 32 GB of disk space. Your original download stays untouched.

[pellebinke89]

Dutch

Even uitleggen, voor mijn begrip:
Met
cd ~/umbrel/home
ga ik in de terminal naar de directory waar het bestand staat.

Deze opdracht begrijp ik niet:
test ! -e haos_ova-18.3.img
Wat doet dat?

Met de laatste opdracht:
qemu-img convert -p -f qcow2 -O raw haos_ova-18.3.qcow2 haos_ova-18.3.img

wordt het “qcow2” bestand omgezet naar een .img bestand.

Nadat ik qemu-utils op mijn LinuxMint pc geïnstalleerd had heb ik de laatste opdracht uitgevoerd in de terminal in de directory waar het haos_ova-18.3.qcow2 bestand staat.
En daar staat nu ook een .img bestand. Overigens is dat wel 34,4GB groot! Klopt dat

English

Let me explain, for my understanding:
With
cd ~/umbrel/home
, I navigate to the directory where the file is located in the terminal.

I don’t understand the command:
test ! -e haos_ova-18.3.img.
What does that do?

With the last command:
qemu-img convert -p -f qcow2 -O raw haos_ova-18.3.qcow2 haos_ova-18.3.img,

the “qcow2” file is converted into an .img file.

After I installed qemu-utils on my LinuxMint PC, I executed the last command in the terminal in the directory where the haos_ova-18.3.qcow2 file is located.
And there is now a .img file there as well. By the way, that is 34.4GB in size! Is that correct?

EDIT a few hours later:

Th file size of 34.4GB borders me. So I looked at this site Convert ova or vmdx to qcow2 using qemu-img · GitHub

and I tried in my LinuxMint PC this command: qemu-img convert -O qcow2 haos_ova-18.3.qcow2 haos_ova-18.3.img

and now haos_ova-18.3.img has the same size as the origin: 970,3MB. Perhaps this is better?

[pellebinke89]

Maar in plaats van me eerst op de opdrachten te richten had ik je natuurlijk eerst moeten bedanken. Waar zou Umbrel zijn zonder jou? Top man!

But instead of focusing on the assignments first, I should have thanked you first, of course. Where would Umbrel be without you? You’re the best!

[aidencole]

thanks, that’s really kind of you! glad to help.

You’ve understood the commands correctly. test ! -e haos_ova-18.3.img just checks that the output file doesn’t already exist. The && means the conversion only runs if that check passes, so it won’t overwrite an earlier image.

And yes, 34.4 GB is expected! That’s the virtual disk’s 32 GiB capacity, displayed in decimal GB. The raw image is a “sparse” file: empty space doesn’t necessarily take up actual storage. My converted copy shows 34.4 GB too, but only uses about 965 MB on disk. Copying or uploading it can expand that, which is why I suggested converting directly on Umbrel.

The second command unfortunately creates another QCOW2 file, just named .img. -O qcow2 sets the actual format; the filename doesn’t change it. So don’t import that smaller file.

You can keep both and create the correct one with a different name on Mint:

qemu-img convert -p -f qcow2 -O raw haos_ova-18.3.qcow2 haos_ova-18.3-raw.img

Then use haos_ova-18.3-raw.img in Machines. Or, to avoid transferring the large raw file, upload the original .qcow2 to Umbrel and run the conversion there.

[pellebinke89]

Oké, I understand. I will upload the original .qcow2 to Umbrel and run the conversion there.

[pellebinke89]

Thanks again! @aidencole

Yes, HAOS is installed. I uploaded the original .qcow2 to Umbrel. Gave the commands:

cd ~/umbrel/home &&
test ! -e haos_ova-18.3.img &&
qemu-img convert -p -f qcow2 -O raw haos_ova-18.3.qcow2 haos_ova-18.3.img

and waited til it was on 100%. Went to Machines > HAOS > Settings and set the Portfowarding to 10.203.0.2:80

In the adressbar of the browser: http://192.168.178.118:40000/

and see, here I am.

Tomorrow I will import the backup.

[pellebinke89]

@filtermann01 And if you look here:

Importing HomeAssistant Backup into Umbrel > Machine > HomeAssistant

Thanks again! @aidencole Yes, HAOS is installed. I uploaded the original .qcow2 to Umbrel. Gave the commands: cd ~/umbrel/home && test ! -e haos_ova-18.3.img && qemu-img convert -p -f qcow2 -O raw haos_ova-18.3.qcow2 haos_ova-18.3.img and waited til it was on 100%. Went to Machines > HAOS > Settings and set the Portfowarding to 10.203.0.2:80 [HAOSReady] In the adressbar of the browser: http://192.168.178.118:40000/ and see, here I am. [OnboardingHAOS] Tomorrow I will import the back…