Hello, I have successfully installed HA on Proxmox following the instructions here.
An issue I have noticed, which promoted me to fully re-install the proxmox instance, is that after I do an upgrade, my home assistant instance reboots itself about half an hour after it comes back up.
When I look for a reason, after the random reboot recovers and HA is running again, is that USB devices do not seem to passed through - for example Zigbee, Z-Wave and Bluetooth fail to initialize. In order to recover the situation I have to go to the proxmox box and hard re-boot the thing using the power switch.
I have also tried to reboot the VM within Proxmox but that too fails:
I have passed through the USB devices (bluetooth, zigbee and z-wave). I was hoping a complete re-install would resolve this issue but alas it has returned.
Has anyone else encountered this issue or has any advice to share?
Iβve not seen that however Iβd be surprised if that cased a HA reboot rather than just extra (error) logging. Possibly a bad connection doing it rather than incompatibility or lack of detection.
That said, I have had some issues after a restore getting the BlueTooth dongle to read properly, but I changed the hardware passthrough a few times and eventually the errors stopped and never returned.
Itβs slightly different to your linked instructions, but hereβs how mine are now mapped - USB port rather than relying on proxmox to detect the device:
When I did mine, this was the guide I used and have had no issues.
Although In ours I gave it more disk, 6Gb RAM and 4 cores to use.
Thinking about it, the only time Iβve seen HA force a reboot was when I had an automation that caught itself in a loop and as a result it eventually consumed all the RAM and then HA rebooted itself.
Perhaps try a fresh HA install and leave it vanilla for a while to see if HA still reboots with nothing set up?
The 2 times I had issues that caused HA to reboot back when I was a noob
Hey thanks for that. I am not sure that the USB detection is causing the re-boot TBO. Just that it happens when those USB relyant integrations fail to load.
Yes, I am passing through via the vendor / device ID. Think Iβll give your suggestion of mapping them via ports a try.
Thanks for your suggestion and advice. Itβs appreciated.
Hey an update on this issue i was having, I had to remove the EFI disk and re-add one with Pre-Enroll keys unchecked, and the vm boots normal with q35 set.
The scripts mentioned here will no longer provide support for Proxmox VE 7 starting from July 2024 (scripts will not execute on PVE7). Subsequent Proxmox VE - Support Lifecycle
Great guide.
I used it to install Proxmox and then HA.
I noticed that add ons are not there.
I thought the script installed HAOS which has add ons.
What am missing here?.
how many times !!! Do not do this sort of thing with only 3hrs sleep.
Apologies, my old HA setup had Add-ons on the sidebar and I wrongly assumed that this was just missing.
I exactly have the same problem. I use i5 NUC. Could you find out? It only does with HA on ProxMox 8. Previously I had ProxMox 7 and did not have this problem. I started everything from scratch clean install Proxmox 8 and clean install HA with other containers. I have 2 cores and 8 GB RAM for HA. I exactly have the same problem. However I did not install with @tteck script I will delete the HA and redo with the script if you couldnβt solve it.
The scripts mentioned here will no longer provide support for Proxmox VE 7 starting from July 2024 (scripts will not execute on PVE7). Subsequent