Installing Home Assistant OS using Proxmox 8

[tteck (𝙩𝙩𝙚𝙘𝙠𝙨𝙩𝙚𝙧)]

N5105

Installing Home Assistant OS using Proxmox 7 - #786 by tteck

Installing Home Assistant OS using Proxmox 7 - #790 by tteck

[Schneider (Antonio Schneider)]

Hello @tteck! Just to let you know that changing the Kernel to v6 solved all of my problems!

Doing a simple apt get for the Kernel, as shown on your post, did not worked, I had to use your Kernel script to changed it to V6, working great now. Even the “memory leak” is now fixed!

Thanks again and have a great day!

[boheme61]

I Just wiped my old MSI GE60, installed latest ProxMox via same “old” script at the top here, and installed HA aswell … so far so good, not much time spend …
Then i close the lid (after dedicated this laptop to ProxMox) , and proxmox goes into sleep, and with that ha
… or atleast both become unavalable
Anyone know howto fix this , i doubt i have features in Bios for controlling the lid, and can’t find anything in Proxmox

[tteck (𝙩𝙩𝙚𝙘𝙠𝙨𝙩𝙚𝙧)]

Here’s the fix you’re looking for:

nano /etc/systemd/logind.conf

[Login]
#NAutoVTs=6
#ReserveVT=6
#KillUserProcesses=no
#KillOnlyUsers=
#KillExcludeUsers=root
#InhibitDelayMaxSec=5
#HandlePowerKey=poweroff
#HandleSuspendKey=suspend
#HandleHibernateKey=hibernate
HandleLidSwitch=ignore
#HandleLidSwitchExternalPower=suspend
HandleLidSwitchDocked=ignore
#PowerKeyIgnoreInhibited=no
#SuspendKeyIgnoreInhibited=no
#HibernateKeyIgnoreInhibited=no
#LidSwitchIgnoreInhibited=yes
#HoldoffTimeoutSec=30s
#IdleAction=ignore
#IdleActionSec=30min
#RuntimeDirectorySize=10%
#RemoveIPC=yes
#InhibitorsMax=8192
#SessionsMax=8192

Save and exit the editor with “Ctrl+O”, “Enter” and “Ctrl+X”

systemctl restart systemd-logind.service

[tteck (𝙩𝙩𝙚𝙘𝙠𝙨𝙩𝙚𝙧)]

To receive better assistance, consider creating a new topic instead of continuing to post off-topic comments in this thread. This thread should remain focused on installing Home Assistant OS using Proxmox 7.

[boheme61]

@tteck

Here’s the fix you’re looking for:

nano /etc/systemd/logind.conf

Thx , fwiw, further config can be found in other topics:

Running HA in Proxmox: Performance Configuration Tips & Tricks [2023]

IO Thread checkbox in disk settings for HA VM… according to site linked below it assigns a thread to IO so it increases performance for the VM as it no longer has to wait on other operations. I kept seeing high IO_Wait in Glances on my HA instance so I wonder whether this will help… Quoting site linked above: IO thread By default, Proxmox uses io=native for all disk images unless the IO thread option is specifically checked for the disk image. The IO thread option allows each disk image to…

PSA How to configure Proxmox for lower power usage

Hello all, I want to share something I recently discovered while running Home Assistant in a Proxmox 6.4-12. You can tune a Proxmox installation to consume less power with a simple command. In a default Proxmox configuration the OS is tuned to “performance”. In my case it means the CPU is running 100% all the time. It’s possible to configure a different profile so the CPU is “sleeping” more. And a more idle CPU means less power usage. These CPU states are called CPU governor states. The amou…

[ctreu (Christian)]

Hi,

I am a bit lost at the moment and would appreciate any help
Just moved my homeassitant from a raspi 3 to a NUC using Proxmox 7.3.4 and your install script (which is pretty awesome btw.).
Everything works fine, but after 4-5 hours I am not able to switch on/off my shellys or set the climate temperature and so on. Strange thing is that the status of the shellys is still updated and displayed correctly in hassio. Also all of my zigbeedevices and nodered flows etc. are working smoothly…

After rebooting the whole VM everything works fine for another 4-5 hours. In the first hours I am able to review the supervisor logs, after the “crash” I am not able to open the logs anymore. My guess would be that there seems to be a problem with the supervisor but I have no clue what to do. In the VM I can see that the allocated 4GB RAM are constantly fully taken.

When I move back to the old raspi 3b+, everything works fine with no problems…

Thanks for any hints and support

Here are my specs:

Proxmox 7.3.4 with only Homeassistant running in a VM
NUC-Kit NUC6CAYH, 4 x Intel(R) Celeron(R) CPU J3455 @ 1.50GHz, 8GB DDR3 RAM, 512SSD
Kernel: Linux 6.1.2-1

From the Homeassistant logs:

Proxmox specs:

[tteck (𝙩𝙩𝙚𝙘𝙠𝙨𝙩𝙚𝙧)]

Try increasing RAM

EDIT: is this OS 9.5?

[ctreu (Christian)]

wow, you’re fast.
I’ll give it a try with the RAM

Yes its 9.5 and Supervisor 2023.01.1

[ctreu (Christian)]

Increasing the RAM wasn’t the solution
Still encountering the same Problems…

[boheme61]

@ctreu

When I move back to the old raspi 3b+, everything works fine with no problems…

And You get “request timeouts” + Bad gateway , when your on the “new” Proxmox … Sounds like you haven’t “transferred” your network-settings correct

[ctreu (Christian)]

I would agree if it wouldn’t work perfectly for 4-5 hours before it runs into some kind of network errors. Or am I wrong with this?

[boheme61]

Most likely your logs + events are building up , until it hangs and crashes , so monitor your homeassistant.log and homeassistant_db

[ctreu (Christian)]

I think I will rebuild the DB and give that one a Chance

[teeeeee]

This is a great guide, worked perfectly for me, so thank you for taking the time to make it.

One question: this script seems to allocate 32 GB of disk space for the virtual machine - is there any way to reduce it? I would like something more like 16 GB.

On line 320 of the script there is a number of 32 GB hardcoded:

I tried to run a version of the script with this number manually edited to “16G”, but the VM that resulted was still 32GB. Thanks!

[Arh]

If I remember near the start when running the script it asks if you want standard settings (or something like that), say no and it may let you change them in there, it lets you change memory size i know as I did.

By the way 32gb is the recommended size. so may not be wise changing it although my setup does not get anywhere near 32gb.

[tteck (𝙩𝙩𝙚𝙘𝙠𝙨𝙩𝙚𝙧)]

The minimum disk size for the .qcow2 disk image provided by the Home Assistant team is set to 32GB and cannot be altered during the virtual machine creation process.

[nayd]

@tteck Just wanted to say thanks for creating these useful scripts, I’ve tried setting up things manually and couldn’t get anything to boot. Found your scripts, and voilà everything just worked out of the box!

Thank you!

[Bourner]

Hi @tteck i don’t know if my problem is related to your script (i dont think so) but i hope you can help me with my problem.

I have proxmox 7.3-4 installed with kernel 5.19.17-edge on an Intel Celeron N5105. I am fully happy with this and installation with your scripts is great and easy.
Only thing i struggle with is to expose my bluetooth from host (from mainboard no extra dongle) to HA OS VM. I have no trouble to expose other dongles (deconz zigbee stick) with works perfect.
But as soon as i expose my bluetooth device and reboot HA goes very slowly and
buttons/switches/lights take up to 10 seconds to change state.

Do you have any idea what i can try? Or is exposing built in bluetooth to a VM a bad idea?

EDIT: my proxmox syslogs go crazy with usb or bluetooth issues.

Feb 04 10:55:40 pve kernel: usb 1-8: new full-speed USB device number 106 using xhci_hcd
Feb 04 10:55:40 pve kernel: usb 1-8: device descriptor read/64, error -71
Feb 04 10:55:41 pve kernel: usb 1-8: device descriptor read/64, error -71
Feb 04 10:55:41 pve kernel: usb 1-8: new full-speed USB device number 107 using xhci_hcd
Feb 04 10:55:41 pve kernel: usb 1-8: device descriptor read/64, error -71
Feb 04 10:55:41 pve kernel: usb 1-8: device descriptor read/64, error -71
Feb 04 10:55:41 pve kernel: usb usb1-port8: attempt power cycle
Feb 04 10:55:42 pve kernel: usb 1-8: new full-speed USB device number 108 using xhci_hcd
Feb 04 10:55:42 pve kernel: usb 1-8: Device not responding to setup address.
Feb 04 10:55:42 pve kernel: usb 1-8: Device not responding to setup address.
Feb 04 10:55:42 pve kernel: usb 1-8: device not accepting address 108, error -71
Feb 04 10:55:43 pve kernel: usb 1-8: new full-speed USB device number 109 using xhci_hcd
Feb 04 10:55:43 pve kernel: usb 1-8: New USB device found, idVendor=8087, idProduct=0a2a, bcdDevice= 0.01
Feb 04 10:55:43 pve kernel: usb 1-8: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 04 10:55:43 pve systemd[1]: Reached target Bluetooth.
Feb 04 10:55:43 pve systemd[17465]: Reached target Bluetooth.
Feb 04 10:55:44 pve kernel: Bluetooth: hci0: urb 00000000f769f221 failed to resubmit (2)
Feb 04 10:55:44 pve kernel: usb 1-8: USB disconnect, device number 109
Feb 04 10:55:45 pve kernel: Bluetooth: hci0: command 0x0c03 tx timeout
Feb 04 10:55:48 pve systemd[1]: systemd-rfkill.service: Succeeded.
Feb 04 10:55:53 pve QEMU[14309]: kvm: libusb_kernel_driver_active: -4 [NO_DEVICE]
Feb 04 10:55:53 pve QEMU[14309]: kvm: libusb_kernel_driver_active: -4 [NO_DEVICE]
Feb 04 10:55:53 pve QEMU[14309]: kvm: libusb_kernel_driver_active: -4 [NO_DEVICE]
Feb 04 10:55:53 pve QEMU[14309]: kvm: libusb_kernel_driver_active: -4 [NO_DEVICE]
Feb 04 10:55:53 pve QEMU[14309]: kvm: libusb_kernel_driver_active: -4 [NO_DEVICE]
Feb 04 10:55:53 pve kernel: Bluetooth: hci0: sending initial HCI reset failed (-110)
Feb 04 10:55:53 pve QEMU[14309]: kvm: libusb_kernel_driver_active: -4 [NO_DEVICE]
Feb 04 10:55:53 pve QEMU[14309]: kvm: libusb_kernel_driver_active: -4 [NO_DEVICE]
Feb 04 10:55:53 pve QEMU[14309]: kvm: libusb_kernel_driver_active: -4 [NO_DEVICE]
Feb 04 10:55:53 pve QEMU[14309]: kvm: libusb_kernel_driver_active: -4 [NO_DEVICE]
Feb 04 10:55:53 pve QEMU[14309]: kvm: libusb_kernel_driver_active: -4 [NO_DEVICE]
Feb 04 10:55:53 pve QEMU[14309]: kvm: libusb_kernel_driver_active: -4 [NO_DEVICE]
Feb 04 10:55:53 pve QEMU[14309]: kvm: libusb_kernel_driver_active: -4 [NO_DEVICE]
Feb 04 10:55:53 pve QEMU[14309]: kvm: libusb_kernel_driver_active: -4 [NO_DEVICE]
Feb 04 10:55:53 pve QEMU[14309]: kvm: libusb_kernel_driver_active: -4 [NO_DEVICE]
Feb 04 10:55:53 pve QEMU[14309]: kvm: libusb_kernel_driver_active: -4 [NO_DEVICE]
Feb 04 10:55:53 pve systemd[17465]: Stopped target Bluetooth.
Feb 04 10:55:53 pve systemd[1]: Starting Load/Save RF Kill Switch Status...
Feb 04 10:55:53 pve systemd[1]: Stopped target Bluetooth.
Feb 04 10:55:53 pve systemd[1]: Started Load/Save RF Kill Switch Status.
Feb 04 10:55:53 pve pvestatd[927]: status update time (7.810 seconds)
Feb 04 10:55:53 pve kernel: usb 1-8: new full-speed USB device number 110 using xhci_hcd
Feb 04 10:55:53 pve kernel: usb 1-8: device descriptor read/64, error -71
Feb 04 10:55:53 pve kernel: usb 1-8: device descriptor read/64, error -71
Feb 04 10:55:54 pve kernel: usb 1-8: new full-speed USB device number 111 using xhci_hcd
Feb 04 10:55:54 pve kernel: usb 1-8: device descriptor read/64, error -71
Feb 04 10:55:54 pve kernel: usb 1-8: device descriptor read/64, error -71
Feb 04 10:55:54 pve kernel: usb usb1-port8: attempt power cycle
Feb 04 10:55:55 pve kernel: usb 1-8: new full-speed USB device number 112 using xhci_hcd
Feb 04 10:55:55 pve kernel: usb 1-8: Device not responding to setup address.
Feb 04 10:55:55 pve kernel: usb 1-8: Device not responding to setup address.
Feb 04 10:55:55 pve kernel: usb 1-8: device not accepting address 112, error -71

[tteck (𝙩𝙩𝙚𝙘𝙠𝙨𝙩𝙚𝙧)]

@Bourner

i don’t know if my problem is related to your script

I don’t see any connection between the script and Bluetooth, it merely automates the creation of a Virtual Machine and nothing else.