whiskerz007 / proxmox_hassos_install

New Proxmox VM with Home Assistant

This script will create a new Proxmox VM with the latest version of Home Assistant. To create a new VM, run the following in a SSH session or the console from Proxmox interface

bash -c "$(wget -qLO - https://github.com/whiskerz007/proxmox_hassos_install/raw/master/install.sh)"

After script completes, click on the new VM (the script will tell you the ID), click on the Hardware tab for the VM and change the Memory and Processors settings to what you desire. The Hard Disk can be expanded by clicking on it, then click on the Resize disk button above (Note: additional steps must be taken for storage to take effect in the VM after the first boot). The network MAC address can be changed by selecting Network Device and clicking Edit above. Once all changes have been made, click Start above.

Root Prompt

To get to the root prompt

• Open the console after the VM has been started
• When the messages slow down press the Enter key a couple of times until you see the following

Welcome to Home Assistant
homeassistant login:

• Login using root, no password is requested
• When you see the hassio > prompt, type login
• You should now see a # prompt.

Add a serial port

By adding a serial port, you are able to use a different interface to interact with the VM. When you click on the down arrow next to Console you will be able to use xterm.js which enables you to Right-Click and get access to Copy and Paste functions. If the serial port was already added by the install script, no further actions are required to enable the functionality.

• Click on the VM in the list of containers at the left side panel
• Click Hardware tab located beside the list of containers
• Click Add located beside Summary tab, then click Serial Port
• Serial Port should be set to 0 in the input box, then click Add
• Start the VM, if it isn't already
• At the root prompt type sed -i 's/$/ console=ttyS0/' /mnt/boot/cmdline.txt
• A Shutdown and Start is required for the changes to take effect

Show Current IP Address

To get the current IP address assigned to the VM from the Proxmox interface

• Click on the VM in the list of containers at the left side panel
• Click Summary tab located beside the list of containers
• Click More near IPs in the top left section
• You can find the assigned IP addresses on the line with the name similar to enp0s18

To get the current IP address assigned to the VM from the command line

• At the root prompt type nmcli -g ip4.address d sh $(nmcli -g device c)
• The response will be the IP address with subnet mask or nothing

Note: If DHCP is configured and nothing is shown, check DHCP server and VM network settings

Configure Network for Static IP Address

To set a static IP address, use the following as an example

• At the root prompt type nmcli c mod $(nmcli -g uuid c) ipv4.method manual ipv4.addresses "192.168.20.170/24" ipv4.gateway "192.168.20.1" ipv4.dns "8.8.8.8,8.8.4.4"
• At the root prompt type nmcli c up $(nmcli -g uuid c)

Configure Network for DHCP

To remove all static IP addresses and enable DHCP

• At the root prompt type nmcli c mod $(nmcli -g uuid c) ipv4.method auto ipv4.addresses "" ipv4.gateway "" ipv4.dns ""
• At the root prompt type nmcli c up $(nmcli -g uuid c)

Default Interface Name

To get the default interface name

• At the root prompt type nmcli -g device c
• The response with be the interface name

Change Hostname

To change the HassOS VM hostname

• At the root prompt type hostnamectl set-hostname your-new-hostname
• You can verify the change by logging out with exit, the last line printed will be your-new-hostname login:

Resize Disk

To resize the disk after the first boot

• At the root prompt type df -h /dev/sda8 and note the Size
• Shutdown the VM
• Resize the disk to the desired size
• At the root prompt type sgdisk -e /dev/sda
• At the root prompt type reboot
• Verify resize was successful by typing df -h /dev/sda8 at the root prompt

proxmox_hassos_install's Issues

USB port can not be mapped from 'proxmox' to 'hass.io'...

On proxmox I have set-up 'USB' device... And it has 'usb0'.

However in 'hass.io' I do not see this port (ls -l /dev | more):

However under 'hassi.io' menu; 'hardware' I see only ports like 'ttySx':

Any additional settings are needed to see the USB device in 'hass.io' ???

running script error no local-lvm

---

•   Creating new VM        *
  

---

storage 'local-lvm' does not exists

CPU is constant high using discovery on proxmox and hassos

After using the script and changing the ip to static ip as instructed, hassio started fine (awesome job). But CPU is running high (constant 80-90) even now after one hour. I am running this on a 32 Gig memory, I3 256G ssd. My hassio install on a debian vm runs at 1-3% cpu. Efter testing some stuff i removed the discovery component and the CPU issue was gone! Anyone seeing this?

Script does nothing

latest proxmox server, copy/pasted script and thing happens, immediatly finishes and left at prompt.

Stuck on Reboot at HASSOS Boot Menu

Whiskerz007 I followed your setup of Proxmox on a NUC from DrZZz videos to the letter and all went great. I did the same thing for loading HASSIO on to Proxmox using your script and it beautifully added the container and all was good. I had to make a hardware change to add a USB but when I restarted the container it loads then shows a "HASSOS Boot Menu" which it just sits there. I tried autoboot and nothing. I chose option 2 and it reboots but goes right back to that menu again. Any idea on this? I deleted the container four times now and rebuilt HA from backups but each time I reboot the container in Proxmox it kills Hassio.

Apple home app cannot be connected

Hello, everything works fine, but the Home App from Apple cannot be integrated, is there a workaraound?

Firewall is not configured on proxmox and HassOS gets its IP through DHCP
I like to share logs or useful stuff, But I don't know what is useful for this error analysis.

greeting

Internet connection needed on Proxmox server

I have no Internet on the Proxmox host.
Therefore, I need to download the Hass.iso file and transfer via local ssh network to the Proxmox host.
Please advise which Hass file needs to be downloaded.

Monitoring disk and system resources

I can see in some of the other issues that people can see their disk usage. I am getting an error when I tried using the system_monitor component and I thought (based on a bit of googlefu) that it might be due to the "containerized" nature of the proxmon install. How can I monitor in the front end the disk and memory usage of proxmox hassio. I see there is a way in the command line to enlarge your disk in the readme so I will review that.

Very high memory usage.

On a fresh install the vm is using a large amount of the memory. If I increase the memory it can use it will use it up as well.

Can I use dual network segments?

The device wo n’t work as long as I have dual network cards installed
Is there a new way?

Terminal access also seconding the question of lxc use instead of vm

First thanks a bunch! for this. I was just wondering if I should have access to xterm. I thought it was mentioned on DR ZZ's video but I could not get access once your virtual machine started. I needed to set the ip address and I couldnt copy and paste to novnc or spice so I typed it out and got it wrong once or twice lol.

Before giving up I tried to install hass.io on docker nested in an ubuntu 18.04 container. I had several containers in docker running nicely. Portainer, home assistant, and watch tower all ran fine in docker that way but I could not install hass.io . The install method Alternative: install on generic Linux server only created a hypervisor and not fully functional hass.io. Wondered if you knew why? or would consider making a container running a similiar setup as the overhead for lxc containers is better than a virtual machine.

If you do get back to reading this than big thanks for the proxmox virtual machine

Multiple instances

Do you know how to make it so you can deploy this as many times as needed to one proxmox environment? I want to be able to have a development environment that I work with, so that I'm not messing around with the one running the house, but be able to commit my code and then pull from production for any code I want brought over.

Guest has not initialized the display (yet)

I get this message
Left it for an hour!!!

Worked about 3 weeks ago, not working now

Option to re-install for wipe and do a clean install on an existing VM with Hassos

To allow redoing the complete reinstall without deleting the VM.

No disk space left

First of all, this script runs great! I have been able to get it up running and runs perfect. My question is I have run out of space. I got an error saying such when trying to upgrade. I was wondering how the script defines how much memory to use? Or if there is a way to define it? I tried resizing disk but my guess is I need to increase the partition as well but as a noob haven't been able to figure out how to do it. Any help or insight is greatly appreciated.

USB detect - D1 Mini

Thanks so much for all your work.

When I plug an FTDI adapter into the USB port, Proxmox identifies it and allows me to assign the device and assign it to my Hassos VM. It doesn't do this for the D1 mini. To allow my standalone Windows PC to identify the D1 mini I had to install CH340G drivers. Is there a way to add these drivers to Proxmox?

Audio not working on Intel NUC

I have troubles with the Audio within HomeAssistant. I am using the Spotify connect add-on to play music on some speakers.

The problem is that the supervisor does not recognize any audio hardware. I have tried almost all of the Proxmox settings but nothing seems to work.
I'm not 100% sure if it's a problem with my NUC / Proxmox or this repo. So has anyone got audio working?

Bluetooth

Hi,

Thank you for a great script.

I have managed to get this up and running and migrated my hass.io to it and everything is working, except for bluetooth.

Any idea about how to activate Bluetooth? I have checked that it is activated in the bios on the NUYC.

Guest has not initialized the display yet

After running the script and the VM gets created, when I turn on the VM the console never shows anything except: Guest has not initialized the display yet. The CPU runs at 100 percent (I've given it over 40 minuets) Running Proxmox Virtual Environment 6.0-11

Certificate error

Hi Whiskerz007

I don't know if you're still taking questions on this but can you tell me why I get a certificate error whenever I open Proxmox in my browser?

I can of course click through the warnings but I'd rather it didn't happen.

Thanks...

Also possible for LXC?

Hi,
Thank you for your work.
Do you think this can also be used for LXC instead of a VM?

Best regards,

E: You don't have enough free space in /var/cache/apt/archives/

something wrong going on while running the install script ....

Hi all. Congrats on the great work!
I've tried to install this on proxmox and got this error:

root@proxmox:# TMP=mktemp -d;pushd $TMP > /dev/null;wget -qO - https://raw.githubusercontent.com/whiskerz007/proxmox_hassos_install/master/install.sh | bash;popd > /dev/null;rm -rf $TMP;unset TMP
Traceback (most recent call last):
File "", line 4, in
KeyError: 'ids'
root@proxmox:#

What am I doing wrong ? Please advise.
Thanks in advance.

Using alternate iso/image acordingly the hardware used for proxmox (e.g. Intel NUC)

Instead of only installing the VDI image on Proxmox, would be interesting to auto detect the Intel NUC hardware and provide instead the proper image for this one kind of.

This might solve the issues about missing drivers for that specific platform in case of direct passthrough on specific hardware components, as the bluetooth, wifi modules, etc.

'ids' error - simple workaround

Thanks Whiskerz, you're a star.

The problem reported by script ('ids') occurs when there are no existing VMs in place. An easy workaround to make the script work without alteration is to create a dummy VM with no resources so the script doesn't encounter a null value.

Homekit not working

I can not pair my Apple Home Kit.

1. Have Static IP
2. Port is open 51827
3. Delayed start not working

unable to parse directory...

just tried installing on a fresh new proxmox, just updated (it's installed via its repository on top of a debian stretch install, as i don't want any lvm and only local fs, and i've a working windows 10 vm with id 100 already working...), and there's plenty of space available:

root@pve:~# TMP=`mktemp -d`;pushd $TMP > /dev/null;wget -qO - https://raw.githubusercontent.com/whiskerz007/proxmox_hassos_install/master/install.sh | bash -s local;popd > /dev/null;rm -rf $TMP;unset TMP



 ********************************
 *  Getting latest HassOS Info  *
 ********************************




 ********************************
 *      Downloading HassOS      *
 ********************************




 ********************************
 *      Extracting HassOS       *
 ********************************




 ********************************
 *       Creating new VM        *
 ********************************

unable to parse directory volume name 'vm-101-disk-1'


root@pve:~# df -h
File system     Dim. Usati Dispon. Uso% Montato su
udev            3,9G     0    3,9G   0% /dev
tmpfs           793M  8,7M    785M   2% /run
/dev/sda1       212G   23G    179G  12% /
tmpfs           3,9G   43M    3,9G   2% /dev/shm
tmpfs           5,0M     0    5,0M   0% /run/lock
tmpfs           3,9G     0    3,9G   0% /sys/fs/cgroup
/dev/sdb1       916G   14G    856G   2% /1TB
/dev/fuse        30M   16K     30M   1% /etc/pve
tmpfs           793M     0    793M   0% /run/user/0


root@pve:~# pvesm status -content images
Name         Type     Status           Total            Used       Available        %
local         dir     active       221559680        23368884       186866484   10.55%

Hassio does not start

Hello,
Thank you for a great script, helps a lot!

I had hassio working well for a couple of weeks on an Intel NUC, but after a power loss Hassio does not restart again!
Unfortunately I had not baxkup to be able to restore ;)
Is there any way to bring Hassio to life?
Is there any way to access the Hassio files to copy them?

change the keyboard layout ?

Is it possible to change the keyboard layout for HassOS ?
It's set to qwerty, and the usual commands are not present to change the layout.

Error during VM boot: Failed to start QEMU Guest Agent

System:
NUC P7JYH with new Proxmox 6.1-1 install.

Problem:
After script has created hassosova-3.10 VM and the VM is started the following QEMU error message appears on the console:

After the VM was created, in Options QEMU Guest Agent was disabled.
I then enabled QEMU Guest Agent:

And rebooted the VM. The error message is not shown during boot when option QEMU Guest Agent is enabled:

I tried this several times and even re-installed the VM and above behavior is consistent.

• The README contains no information about whether the QEMU Guest Agent must be enabled for the VM or not.

• Does QEMU Guest Agent need to be enabled and why?

How to update HassOS

Thanks for this excellent guide. Installing hass.io has never been so easy 👍

I have a question on how to update HassOS. Version 2.9 is installed and now version 2.10 is available.
When I press the update button in the Hassio - System tab I get the following errors.

19-02-23 22:00:48 INFO (MainThread) [hassio.hassos] Fetch OTA update from https://github.com/home-assistant/hassos/releases/download/2.10/hassos_ova-2.10.raucb
19-02-23 22:05:49 WARNING (MainThread) [hassio.hassos] Can't fetch versions from https://github.com/home-assistant/hassos/releases/download/2.10/hassos_ova-2.10.raucb: 
19-02-23 22:05:49 ERROR (MainThread) [asyncio] SSL error errno:1 reason: KRB5_S_INIT
protocol: <uvloop.loop.SSLProtocol object at 0x7fe5f93209b0>
transport: <TCPTransport closed=False reading=False 0x55a0f3759538>
Traceback (most recent call last):
  File "uvloop/sslproto.pyx", line 504, in uvloop.loop.SSLProtocol.data_received
  File "uvloop/sslproto.pyx", line 204, in uvloop.loop._SSLPipe.feed_ssldata
  File "uvloop/sslproto.pyx", line 189, in uvloop.loop._SSLPipe.feed_ssldata
  File "/usr/local/lib/python3.7/ssl.py", line 767, in unwrap
    return self._sslobj.shutdown()
ssl.SSLError: [SSL: KRB5_S_INIT] application data after close notify (_ssl.c:2605)

And in the Host System tile (Hass.io - System tab) it shows Error: 502: Bad Gateway just below the hardware button.

Hassio update problem

Since update 100.3 it won't update any further (to 102.2).

19-11-28 21:12:45 WARNING (MainThread) [hassio.homeassistant] Don't wait anymore of Home Assistant startup! 19-11-28 21:12:45 CRITICAL (MainThread) [hassio.homeassistant] HomeAssistant update fails -> rollback! 19-11-28 21:12:45 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.100.3 19-11-28 21:12:45 INFO (SyncWorker_16) [hassio.docker.interface] Update image homeassistant/qemux86-64-homeassistant:0.102.2 to homeassistant/qemux86-64-homeassistant:0.100.3 19-11-28 21:12:45 INFO (SyncWorker_16) [hassio.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.100.3. 19-11-28 21:12:47 INFO (SyncWorker_16) [hassio.docker.interface] Stop homeassistant application 19-11-28 21:12:52 INFO (SyncWorker_16) [hassio.docker.interface] Clean homeassistant application 19-11-28 21:12:52 INFO (SyncWorker_17) [hassio.docker.homeassistant] Start homeassistant homeassistant/qemux86-64-homeassistant with version 0.100.3 19-11-28 21:13:02 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance 19-11-28 21:13:02 INFO (MainThread) [hassio.homeassistant] Successful run Home Assistant 0.100.3 19-11-28 21:13:02 INFO (SyncWorker_8) [hassio.docker.interface] Cleanup images: ['homeassistant/qemux86-64-homeassistant:0.102.2']

Not sure if problem with qemu image or hassio itself.

Possible to have a BIOS image instead of UEFI?

The UEFI image installed by this script does not initialize a display on my Proxmox server. BIOS works fine on all my other VMs.

Is it possible to get a BIOS version of the script?

Not an issue - a feature request - dual home

What's here already is fantastic and works perfectly for me. So this isn't an issue, it's a feature request:

Is it possible to bind proxmox to both ethernet and WIFI NICs?

My reason for wanting to do this is as a manky workaround allowing me to get mdns (unroutable) coverage across two subnets for esphome putting my 50+ ESP devices on an 'IOT' subnet and everything else on another.

I hoped to be able to do this by just assigning the WIFI nic to the existing Proxmox instance but haven't found a way to do this.

hassos installer hangs

The script doesnt appear to be working on 6.1-3

Not sure if its script or hassos related.

Static IP address

How do you assign static ip address to the VM.

I copied VM MAC address to my DHCP server, assigning ip address to MAC address, then restarted the VM but VM's ip address is not what is assigned by DHCP

resize disk

hi, just run your script, changed ram to 2gb and hd resized via proxmox web gui to 16gb (from original 6gb)... how to enlarge internal filesystem, now? i see /dev/sda8 of 5.3gb... thanks

Hassio Samba Addon

I love what you've done to make this easy for us. Thank you.

I am trying to add Samba Addon- It can't find the eth0 interface, or any of the other variants I tried (net0, net1). What is the correct setting and method to use Samba addon?

Secondly, how can I rename the host as my production samba shares "Hassio" and I would like the dev to share " Hasiso-dev" or similar.

Thank you !

Command not showing any result

Hi,
In Shell copied the command
After 3 sec it returns to prompt without installing anything.
I have a "dummy" VM installed.
I'm stucked.
What could go wrong?

Thank you

VM Console hangs during boot (just before Login prompt should appear)

System:
NUC P7JYH with new Proxmox 6.1-1 install.
CPU: Pentium Silver J5005 quad-core, memory: 16GB.
(There is sufficient CPU, memory and disk space in the host for the VM to start.)

Problem:
After the script has created the hassosova-3.10 VM and the VM is started and the console is opened, then everything appears to start normal but then the console hangs (and nothing further happens).

This is the point where it hangs. This is where the Login prompt should appear next, but it does not. It just hangs and still hangs after many hours.

I have tried this several times and also have re-installed the VM several times but the behavior is very consistent.

Strange enough hassio itself does start and I am able to access it via the hassio web ui.
But something goes wrong during the boot process. I don't know what and why and what the results of the hanging console/boot process are.

(Enabling or disabling the QEMU Guest Agent as described in #46 makes no difference.)

• I have installed the SSH & Web Terminal add-on (with protection off to get full access to the system) and opened the Web Terminal in hope to find any useful information in boot.log but there are no logfiles at all in /var/log.

• Any ideas for how to fix or how to debug this are welcome.

No CLI after logging in with root and executing login command.

Proxmox version: 6.1-7
Hass OS Downloaded: 3.12

What happened: After booting for the first time, the homeassistant login appears. When I type in "root", it sends me to the "ha >" prompt. Typing in "login" sends me right back to the homeassistant login.

What's expected to happen: Root access to the VM's CLI.

Troubleshooting steps: Tried the script again, no dice.

Is it possible to update it with HASSOS 3.8?

As per subject, thanks

download specific version rather than latest

Hi, is there an easy way to download a specific version using your script rather than the latest, reason i ask is to try out a development build, as it has Bluetooth supposedly working (version 4.2)
Ta

ERROR: 255@27: 'local-lvm' is not a valid storage ID.

Hello, looks like a great install process, however I received the error:
ERROR: 255@27: 'local-lvm' is not a valid storage ID.
root@proxmox:~# wget -qO - https://raw.githubusercontent.com/whiskerz007/proxmox_hassos_install/master/install.sh | bash -s local-lvm ERROR: 255@27: 'local-lvm' is not a valid storage ID.
My Proxmox Virtual Environment 4.4-1/eb2d6f1e (hypervisor) has 9 VMs at the moment, however I don't think that's an issue to creating another VM?

Also, I was considering installing onto a Container rather than Virtual Machine to reduce resources. Not sure if there's a script where I can adjust that, or if Hass will allow install to a container (I will research this a bit further).

2 host runing hassos with usb pass?

hi
i have a cluster with 2 host.
i install your hass in the first host.
i have 3 usb dongle atteched to the vm

how can i make migration to the secound host?

Update (103) is not installing...

Trying to install newest update - but some problem...

19-12-16 18:24:17 INFO (SyncWorker_0) [hassio.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.103.0. 19-12-16 18:24:33 ERROR (SyncWorker_0) [hassio.docker.interface] Can't install homeassistant/qemux86-64-homeassistant:0.103.0 -> 404 Client Error: Not Found ("no such image: homeassistant/qemux86-64-homeassistant:0.103.0: No such image: homeassistant/qemux86-64-homeassistant:0.103.0"). 19-12-16 18:24:33 WARNING (MainThread) [hassio.homeassistant] Update Home Assistant image fails

Not working on Proxmox 6

There seems to be an issue using this script on Proxmox 6.0
Fails to boot UEFI

Script Stalls

After clicking "Start" the script runs for a while then it stalls with no error message. It stops at:
[ ok ] Started Docker Application Container Engine.

I've tried to restarting a few times but it continually stalls at this point.

Read-only file system error when changing hostname.

ProxMox 6.0-4
I was able to change the IP address, but when I try and change the hostname I get the error.
Thanks,
Rob

Does not work on VE 5.4-3

When running the command in Proxmox Shell or in a SSH session
Nothing happens at all, no errors no nothing
Running a fresh Proxmox 5.4-3 install on a BareMetal Dell machine

wget -qO - https://raw.githubusercontent.com/whiskerz007/proxmox_hassos_install/master/install.sh | bash -s local-lvm