Installing Home Assistant OS using Proxmox 7

Open 2 SSH sessions. In one, tail the homeassistant log and in the second journalctl -f.

Your snapshot size is 0.1 MB. Thatā€™s 100KB. Way too small for a correct snapshot. The snapshot itself is the problemā€¦
Redo it. Retransfer it. You can also open it on your PC (it is a compressed tar file) to check whether the content looks ok.
GV

The snapshot was that small because it was a test. I did a fresh install of proxmox and home assistant. I just installed one addon made the snapshot and then removed the addon. Then I tried to restore the snapshot (with one addon) to an empty home assistant.

Iā€™m not sure it this is what you ment but this is what I have done:

1 open ssh to promox as root ang gave command journalctl -f see log below

[email protected]ve:~# journalctl -f
ā€“ Logs begin at Sun 2020-08-23 09:21:21 CEST. ā€“
Aug 23 10:07:29 pve systemd[1770]: Listening on GnuPG cryptographic agent (ssh-a gent emulation).
Aug 23 10:07:29 pve systemd[1770]: Reached target Paths.
Aug 23 10:07:29 pve systemd[1770]: Listening on GnuPG network certificate manage ment daemon.
Aug 23 10:07:29 pve systemd[1770]: Listening on GnuPG cryptographic agent and pa ssphrase cache (restricted).
Aug 23 10:07:29 pve systemd[1770]: Reached target Sockets.
Aug 23 10:07:29 pve systemd[1770]: Reached target Basic System.
Aug 23 10:07:29 pve systemd[1770]: Reached target Default.
Aug 23 10:07:29 pve systemd[1770]: Startup finished in 59ms.
Aug 23 10:07:29 pve systemd[1]: Started User Manager for UID 0.
Aug 23 10:07:29 pve systemd[1]: Started Session 5 of user root.
Aug 23 10:08:00 pve systemd[1]: Starting Proxmox VE replication runnerā€¦
Aug 23 10:08:01 pve systemd[1]: pvesr.service: Succeeded.
Aug 23 10:08:01 pve systemd[1]: Started Proxmox VE replication runner.
Aug 23 10:09:00 pve systemd[1]: Starting Proxmox VE replication runnerā€¦
Aug 23 10:09:01 pve systemd[1]: pvesr.service: Succeeded.
Aug 23 10:09:01 pve systemd[1]: Started Proxmox VE replication runner.
Aug 23 10:10:00 pve systemd[1]: Starting Proxmox VE replication runnerā€¦
Aug 23 10:10:01 pve systemd[1]: pvesr.service: Succeeded.
Aug 23 10:10:01 pve systemd[1]: Started Proxmox VE replication runner.
Aug 23 10:11:00 pve systemd[1]: Starting Proxmox VE replication runnerā€¦
Aug 23 10:11:01 pve systemd[1]: pvesr.service: Succeeded.
Aug 23 10:11:01 pve systemd[1]: Started Proxmox VE replication runner.
Aug 23 10:12:00 pve systemd[1]: Starting Proxmox VE replication runnerā€¦
Aug 23 10:12:01 pve systemd[1]: pvesr.service: Succeeded.
Aug 23 10:12:01 pve systemd[1]: Started Proxmox VE replication runner.
Aug 23 10:13:00 pve systemd[1]: Starting Proxmox VE replication runnerā€¦
Aug 23 10:13:01 pve systemd[1]: pvesr.service: Succeeded.
Aug 23 10:13:01 pve systemd[1]: Started Proxmox VE replication runner.
Aug 23 10:14:00 pve systemd[1]: Starting Proxmox VE replication runnerā€¦
Aug 23 10:14:01 pve systemd[1]: pvesr.service: Succeeded.
Aug 23 10:14:01 pve systemd[1]: Started Proxmox VE replication runner.
Aug 23 10:15:00 pve systemd[1]: Starting Proxmox VE replication runnerā€¦
Aug 23 10:15:01 pve systemd[1]: pvesr.service: Succeeded.
Aug 23 10:15:01 pve systemd[1]: Started Proxmox VE replication runner.
Aug 23 10:16:00 pve systemd[1]: Starting Proxmox VE replication runnerā€¦
Aug 23 10:16:01 pve systemd[1]: pvesr.service: Succeeded.
Aug 23 10:16:01 pve systemd[1]: Started Proxmox VE replication runner.
Aug 23 10:17:00 pve systemd[1]: Starting Proxmox VE replication runnerā€¦
Aug 23 10:17:01 pve systemd[1]: pvesr.service: Succeeded.
Aug 23 10:17:01 pve systemd[1]: Started Proxmox VE replication runner.
Aug 23 10:17:01 pve CRON[3131]: pam_unix(cron:session): session opened for user root by (uid=0)
Aug 23 10:17:01 pve CRON[3132]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Aug 23 10:17:01 pve CRON[3131]: pam_unix(cron:session): session closed for user root
Aug 23 10:18:00 pve systemd[1]: Starting Proxmox VE replication runnerā€¦
Aug 23 10:18:01 pve systemd[1]: pvesr.service: Succeeded.
Aug 23 10:18:01 pve systemd[1]: Started Proxmox VE replication runner.
Aug 23 10:19:00 pve systemd[1]: Starting Proxmox VE replication runnerā€¦
Aug 23 10:19:01 pve systemd[1]: pvesr.service: Succeeded.
Aug 23 10:19:01 pve systemd[1]: Started Proxmox VE replication runner.
Aug 23 10:20:00 pve systemd[1]: Starting Proxmox VE replication runnerā€¦
Aug 23 10:20:01 pve systemd[1]: pvesr.service: Succeeded.
Aug 23 10:20:01 pve systemd[1]: Started Proxmox VE replication runner.
Aug 23 10:20:56 pve pvedaemon[18974]: [email protected] successful auth for user ā€˜[email protected]ā€™
Aug 23 10:21:00 pve systemd[1]: Starting Proxmox VE replication runnerā€¦
Aug 23 10:21:01 pve systemd[1]: pvesr.service: Succeeded.
Aug 23 10:21:01 pve systemd[1]: Started Proxmox VE replication runner.
Aug 23 10:21:23 pve smartd[634]: Device: /dev/sda [SAT], SMART Prefailure Attribute: 194 Temperature_Celsius changed from 66 to 68
Aug 23 10:22:00 pve systemd[1]: Starting Proxmox VE replication runnerā€¦
Aug 23 10:22:01 pve systemd[1]: pvesr.service: Succeeded.
Aug 23 10:22:01 pve systemd[1]: Started Proxmox VE replication runner.
Aug 23 10:22:44 pve pveproxy[18995]: worker exit
Aug 23 10:22:44 pve pveproxy[1024]: worker 18995 finished
Aug 23 10:22:44 pve pveproxy[1024]: starting 1 worker(s)
Aug 23 10:22:44 pve pveproxy[1024]: worker 3926 started
Aug 23 10:23:00 pve systemd[1]: Starting Proxmox VE replication runnerā€¦
Aug 23 10:23:01 pve systemd[1]: pvesr.service: Succeeded.
Aug 23 10:23:01 pve systemd[1]: Started Proxmox VE replication runner.
Aug 23 10:24:00 pve systemd[1]: Starting Proxmox VE replication runnerā€¦
Aug 23 10:24:01 pve systemd[1]: pvesr.service: Succeeded.
Aug 23 10:24:01 pve systemd[1]: Started Proxmox VE replication runner.

2 installed SSH addon in home assistant and gave command tail -f /config/home-assistant.log

Only entry is

Received message for unregistered webhook b70c0e96878fe3a06cb455cd09bf3ef539a8d8*********** from 192.168.1.*****

The restore command was given around 10:13.

I think it has something to do with chrome.

I restored the snapshot with the ssh terminal and that went fine. I also tied it with firefox and that also went fine.

1 Like

Successfull install in a Beelink U55 server ( 2GB memory and 1 CPU Core for now)

1 Like

I would suggest you add this part for people who want a static IP address: https://tech.borpin.co.uk/2018/10/18/using-nmcli-to-set-a-static-ipv4-address-in-hass-io/

Glad it was of use - how this is still an issue 2 years later. However, I think I saw a Tweet the other day that implied there was shortly (in dev) going to be a native way to do this via the UI.

[edit]

I just installed proxmox on a NUC and used Whiskerz script to install HA. All went well.
I did the samba config from Kanga-Who.
I can connect with winscp to the ip address of the proxmox machine. But when I try to connect to the IP address of the HA VM I got ā€œconnection refusedā€.
All I want is accessing the HA files to make some changes (Automations, configuration.yamlā€¦)
Any ideas?

Hello,

I have installed successfully Home Assistant using Proxmox following the guide of post #1 ( and setting the USB in USB port in proxmox to use the Aeotec Gen5 Zwave Dongle ZW090 )

The addon Mosquitto Broker and OpenZwave ahec been installed and configured .

The issue is that the Aeotec Zwave Dongle ZW090 is not showing in the Openzwave UI ( no zwave device added yet ) , as per the attahced screenshot :

However at the botton in the OZW log , the usb port of the Zwave dongle seems to work correctly .

Any idea ?

Thank you

EDIT FOR THE SOLUTION : The Aeotec USB Dongle is correctly detected in the HA VM , after modification of the USB device configuration in Proxmox from USB USB PORT to USB USB Vendor/Device ID + Choose device 0658:0200 ( The ZW090 USB dongle) as per the lsusb command :

Bus 0002 Device 0003 : ID 0658:0200

=> This is the Aeotec ZW090 USB Dongle

Then the ZW090 equipment is displayed in the OZW panel

Did you install the ssh addon? I have a HA running in Proxmox as well and it works for meā€¦

1 Like

As David mentioned, you will need to install SSH to each VM you wish to connect too. Each VM is treated as itā€™s own entity, or PC if you like, so each one needs itā€™s own SSH config.

Use the built-in HA SSH add-on to enable SSH to the HA VM.

You can just use the PVE web console.

Solved , Post #109 updated with the solution

Yes, installed the SSH from Homeassistant but still get ā€˜refusedā€™.

Access the configuration.yaml file with proxmox web console? How?

Interestingā€¦

Add-on store on an RPi Supervised installā€¦

Add-on Store on a PVE Hassio install.

My bad, I was thinking of my supervised install. You can use the Samba Add-on.

I donā€™t have that issue on my end with a PVE install. All 21 add-ons from your first screenshot are listed for me. Any errors in your Supervisor log?

Doh! :man_facepalming:Hadnā€™t enabled ā€˜Advanced Modeā€™

1 Like