@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! 
2 Likes
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
I donโt see any connection between the script and Bluetooth, it merely automates the creation of a Virtual Machine and nothing else.
Yes you are right. It has nothing to do with your script. But do you still have an idea whats going on here?
i think this is an proxmox/bluetooth/celeron N5105 issue. Maybe also has something do to with the linux kernel? If not its also ok for me.
If I understand correctly, thatโs a PCIe device, not USB.
As far as I recall, the use of an external Bluetooth adapter is necessary to utilize the Bluetooth integration in Home Assistant.
Edit: I habitually remove the PCIe WiFi/Bluetooth card from the machine running Proxmox to reduce 2.4GHz interference.
In installed HAOS on Proxmox
using
bash -c "$(wget -qLO - https://github.com/tteck/Proxmox/raw/main/vm/haos-vm-v5.sh)"
Itโs been been โPreparing Home Assistant (this can take up to 20 minutes)โ since last evening. the Homa Assistant observer is happy (Supervisor: Connected, Supporte: Suported, Healthy: Healthy"
โha core logsโ just shows 3 lines : โStar DNS broadcast, Publish http://โฆ:8123 to _home-assitant._tcpโ and โStart webserver on http://0.0.0.0:8213โ. The latter is accessible (and indicates itโs preparing HA).
On startup, the start job times on on getting the Kernel Time Synchronized:
(Now I restarted but th VM does not get its IP from the DHCP server - not convinced that is related because it had an IP before reboot).
Once more, this doesnโt have any connection to the installation script.
https://community.home-assistant.io/search?q=getting%20the%20Kernel%20Time%20Synchronized
At first Iโd like to say thank you @tteck for this awesome script. It made it possible for me to test out the HA installation on my PVE7 host pretty easily.
Now one question to all the users that run HA virtualized inside PVE7. How stable is the whole thing? Any problems with updates, addons etc.? At the moment Iโm running it on a dedicated HA Blue which runs the HA very very stable. But Iโd like to reduce my hardware park. So Iโm interested in how stable the whole thing runs over time in such a VM.
Iโm looking forward reading some feedback.
The stability of your Proxmox setup depends on the hardware you choose. Itโs worth noting that newer Intel Celeron CPUs have been reported to have compatibility issues.
1 Like
Hello @denisha,
I had to consider alternatives to HA Blue once my unit got bricked. I had to find a solution fast. I used an Oracle Virtualbox at first but it presented problems and ran for days not weeks without a restart.
Next, I set up a separate box with Proxoxโs PVE7 and used the @tteck script to get going. I repurposed an older x86 machine of 2000 vintage. So far everything has been working very verry well for weeks without having to reboot the underlying PVE7 environment. Itโs quick, resource stable and I use a dozen add-ons with it without issue. Highly recommended!
1 Like
Thank you very much @tteck and @pg.sylvestre.
My proxmox env is pretty stable and running since about a year. (i5-8500, ECC RAM, server SSDs including power loss protection etc.)
It is nice to hear that it only depends on the proxmox stability and no other virtualisation related problems specific to HA seem to occur.
1 Like
I installed my setup on an HP T630 with 16gb ram and 256gb ssd. over Christmas. Went from a 4gb RPi4. I used the script here. I installed HA alongside, pihole, plex and OMV. (with 3 usb ssdโs for storage) The system has not been rebooted since it was installed and HA appears to be rock solid. Certainly never noticed any issues. Ha is only ever restarted for an update.
1 Like
I am a bit lost. First time installed Proxmox and sruggling already getting HA installed.
Using the link above, norhing happens and I as there is no error message, I do not know on what to do now:
root@pve:~# bash -c โ$(wget -qLO - https://github.com/tteck/Proxmox/raw/main/vm/haos-vm-v5.sh)โ
root@pve:~#
Pressing enter after cpying the script, but now action at all.
Using a lenovo ThinkCentra M700 with i3-6100T, 8GB Ram and 256GB SSD
tx in advance
Internet connectivity is required. You can quickly verify if you have an Internet connection by running the following command in the Proxmox shell:
if ping -c 1 -W 1 1.1.1.1 &> /dev/null; then echo "Internet Connected"; else echo "Internet NOT Connected"; fi
This command will check if you can ping the IP address 1.1.1.1 , which is a public DNS resolver. If you see the message โInternet Connectedโ after running the command, then you have an active Internet connection. If you see โInternet NOT Connectedโ, then thereโs an issue with your network settings.
Having the same issue as Opoeler. Dug into the code a bit, and it looks like it may be having trouble getting the version numbers (aka the $BRANCH variable). Still trying to get it to work for me.
UPDATE: My DNS was set to use my old ISPโs info, not my newer one. So, just a gateway/DNS resolution error. Strange since all my other VM services are able to communicate to the internet and such.
@tteck @kanga_who Hi, just wanted to say a big thank you for these scripts and guide! I had no experience with Proxmox before now, and this made the process of migrating from my old Celeron nuc to an i5 Dell 3060 much quicker 
2 Likes
can we make disk bigger ? i can make it grow from proxmox , but looks like i cannot expand it inside vm wihout ssh (hassos vm)
If you increase the disk size of the virtual machine in Proxmox, Home Assistant will be able to utilize the additional storage capacity.
EDIT:
Normal Storage as shown in HAOS:
Increase by 32GB in Proxmox:
Result:
REBOOT VM
Increased Storage as shown in HAOS:
1 Like
Just wanted to say a big THANK YOU @tteck for your scripts - though I wish I had seen the Homebridge one before I made myself jump through hoops (and watch a German YouTube when I donโt speak German!) getting THAT setup. All the best!
2 Likes