I have been trying to use the helper script. However I get stuck at ~30% download state. I have tried it multiple times. What am I doing wrong?
Here is what I see.
Creating a HAOS VM using the above default settings
✓ Using local-lvm for Storage Location.
✓ Virtual Machine ID is 105.
✓ https://github.com/home-assistant/operating-system/releases/download/11.5/haos_ova-11.5.qcow2.xz
haos_ova-11.5.qcow2.xz 31%[===========> ] 121.59M --.-KB/s eta 32s
looks like some other issue, as I see the same situation even when I use wget command on shell
It’s ok here. (US)
✓ https://github.com/home-assistant/operating-system/releases/download/11.5/haos_ova-11.5.qcow2.xz
✓ Downloaded haos_ova-11.5.qcow2.xz
I can download it on other computer in the same network, however unable to download it on Proxmox shell
Could be a DNS issue
Just another thought, space available on Proxmox?
It worked for me the other day
here is the space situation.
root@pve:~# df -h
Filesystem Size Used Avail Use% Mounted on
udev 7.7G 0 7.7G 0% /dev
tmpfs 1.6G 1.7M 1.6G 1% /run
/dev/mapper/pve-root 39G 7.0G 30G 20% /
tmpfs 7.7G 40M 7.7G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
efivarfs 192K 86K 102K 46% /sys/firmware/efi/efivars
/dev/nvme0n1p2 1022M 12M 1011M 2% /boot/efi
/dev/fuse 128M 20K 128M 1% /etc/pve
tmpfs 1.6G 0 1.6G 0% /run/user/0
managed to download another big 3gig iso via wget just now, without any issues. Somehow the issue seem to be isolated to haos qcow2 file
Just as a comparison as to what I have:
Attrributes:
And I directed the script install to go onto Store01 and this is the VM that was created
Just so you have something to compare with
Hi all! Not sure where to post this, but maybe it could be related with any configuration of proxmox.
I have followed the guide and all is working OK.
Now I want to shutdown the host if I detect an outage so I am testing, performing a node shutdown. It seems that proxmox firstly shutdown the HA VM and later the host, but sometimes (and not always) I see this warning on the log:
WARNING (Recorder) [homeassistant.components.recorder.util] The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly
So, is there any way to cleanly shutdown the host from HA?
Thanks!
I can’t think of a better place to ask this.
I am running proxmox and the VM of HAOS as per the script here. I now want to install zigbee2mqtt.
Am I better to install the HAOS addon on top of the HAOS VM, or install the Zigbee2MQTT LXC via @tteck’s other script. Also whether the alpine version or the debian version of the LXC are recommended, and if it has a downside.
Advice and reasons for it would be of assistance.
Two specific questions:
To Update Zigbee2MQTT, run the command below (or type update) in the LXC Console .
The ability to run an update is not mentioned in respect of the Alpine LXC. Does update work in the same way in the Alpine LXC as the Debian LXC?
I prefer deploying each of my services in separate LXC containers, with each service backed up individually. This way, if there’s a mishap, I can restore that specific service without affecting the others.
By having Home Assistant, Node-Red, MQTT, and Zigbee2MQTT in separate containers, you can create automations thoughtfully within Node-Red to ensure that critical processes continue even if Home Assistant goes down.
I prefer the Debian distribution of Z2M. Available updates will not be shown in HAOS, but are available instantly when released by Koenkk.
Alpine Z2M is a package (update via apk update && apk upgrade), not maintained by Koenkk.
Spent a bunch of time reading through all of this, and various other guides etc.
So firstly, thank you to @kanga_who and @tteck, and all those that actively contribute here.
Then comes the question… I have seen since PVE 8.1 in some posts that you can leave secure boot enabled (LINK) in the BIOS, others (like in @kanga_who 's ) suggest disabling it (LINK)
Anyone able to explain the reasoning either way (enable &/ disable)? If there aren’t downsides to “disable secure boot” then it seems to the best way to go given the amount of times I’ve seen it as a prerequisite of installing PVE.
It’s typically advisable to disable Secure Boot in the BIOS before installing Proxmox, particularly if you expect to utilize hardware or drivers that lack recognition by your system for Secure Boot keys.
Hi all, I’m new to proxmox and i set it up with the intention of home assistant being my first VM. ive followed several separate tutorials that all point to tteck’s install script.
Ive been running the Home Assistant OS VM script from tteck in the proxmox terminal and it returns complete, however when I log into the web UI it’ll go through the initialization process until hitting this block of code that just errors and loops
homeassistant:2024.3.1: 500 Server Error for http+docker://localhost/v1.43/images/create?tag=2024.3.1&fromImage=ghcr.io%2Fhome-assistant%2Fqemux86-64-homeassistant&platform=linux%2Famd64: Internal Server Error (“Get “https://ghcr.io/v2/”: context deadline exceeded”)
[supervisor.homeassistant.core] Error on Home Assistant installation. Retrying in 30sec
it looped for about 6 times before stalling completely, am i missing a prerequisite before install ?
Thanks! Turn off secure boot it is then.
Hi Timothy, welcome to the forum!
I cannot help you with that error but I tried the script right now and it works fine.
You could try another script for a VM to see if that goes well.
Thanks @Nick4, that’s helpful because it might be my outbound connection that’s the issue. ill run some more tests, hopefully it was just a transient server error.
DNS issue?
Welcome to the forum. Not to tell you different. But, I have been using Proxmox with HA for a few years. I didn’t opt for the docker install but used an actual VM to install the HA OS directly to my Proxmox instance/VM. I prefer the complete/full HA OS install and works perfectly. I tried the docker install and it takes a lot of setup and work. If you are using Promox it’s simple to create a VM and configure the full HA OS instance. They have an OVA. I actually like docker but you have to know the networking and DNS issues if you plan to go there. I thought I posted my install a few years ago. Good luck and hope you can figure it out.
