That is ample for anything HA related, plus Plex and an NVR/CCTV. This is mine currently with everything running as noted above. (My wife is currently watching Columbo on Plex a well 
)
haha nice 
Question, I just ran the whizkers script, took like 2 mins. Can I configure the Z-Wave USB stick later? Just run the install and let it go? 1. It’s late here and I’m heading to bed. 2. I need to power down the pi and well then my lights don’t work. 3. I need to run to the basement lol
1 Like
Yep. Just shutdown the system, plug in the Z-wave stick, then start up. It should show in the list after the reboot.
The great thing about i7 over an i5 is hyperthreading. That means ProxMox will see it as 8vCPUs so plenty of power for what it seems like you want to do.
ProxMox has USB passthrough. Just set that up in your VM. I use a Conbee II and a ZwaveMe USB stick and I pass both through with zero issues. You can either passthrough the device or actually pass through the entire USB port. I do port passthrough as those two devices are only used by HA, but both methods work flawlessly. If you do it later, you just stop the VM (shutdown the OS in Home Assistant) and passthrough the USB to the VM when needed.
As a note, I started on a Raspberry Pi 3 and migrated to the VM using a HA snapshot and it needed nothing to be reconfigured to detect the passed through USB devices. It just worked. DeConz using the HA add-on and Zwave setup via integration not yaml.
Oops. That was meant to be for @swiftvic
Thanks for the guide, I got it running!
A thing to mention: I needed to run apt update before apt-get install sudo
2 Likes
Is it possible to install MQTT following your other guides on the same VM as HA, or do I need to create a separate one for that?
Script works great… I need to copy my backup over but the base OS seems really stripped down. No apt for installing sshd. Am I missing something?
1 Like
I would install a Debian or Ubuntu VM to run any software, not on the Proxmox OS.
1 Like
If not available, you can install SSH with this.
apt install openssh-server openssh-client -y
Yeah, I went the route of firing up a Debian VM then installing on that. The bummer is I can’t pull the configs off the old VM since that was installed using the script from the Proxmox CLI.
/bin/ash: foo: not found is a common result when doing things on the underlying OS.
What are you trying to run that is giving you that?
I open a console to the HA VM then login to the underlying OS. Any command like apt, find, etc. gives me the not found response.
1 Like
@kanga_who I’m following the instructions to install on my NUC. I’ve made it to Section 2.2. When I type
apt-get install sudo
I get this:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package sudo
Not sure what to do next…
Edited to add: I found the post above by @Hs82H and that worked. Could I suggest that you add that to the initial post? Thanks!
Thank you very much for the detailed guide - I now have Home Assistant running on my 4th gen i5 NUC which has 8GB of memory and a 80GB mSata SSD drive. I gave the HA VM 4GB of memory, 2 cores and 32GB of disk space. It seems to be running at a little over 50% memory usage - I’m a bit surprised that it is using that much memory, as folks in this thread seemed to think 2GB was enough for HA.
I have one question - I have the systemmonitor sensors set up from my previous Supervised install on Ubuntu. They are showing data, but are these giving me accurate information given that HA is running in a VM? They don’t correspond to what I see in Proxmox - they are showing about 4% CPU use and 22% memory use.
platform: systemmonitor
resources:
- type: disk_use_percent
arg: /
- type: memory_use_percent
- type: processor_use
- type: last_boot
Memory use reported by Proxmox is the basic output of the “free” command. It includes kernel filesystem cache and buffers, both of which can be released very quickly at any time.
It’s not a good indication of process or even truly a Linux VM’s real RAM use. Even a VM with a tmpfs filesystem if you have a distro that uses that, will affect that number.
You’ll have to get into the VM and use the various switch options for “free” or tools like vmstat, top, htop, or others to get a real understanding of RAM use in any Linux.
Hello,
I am having issues of the condition: time part of my automations not working. Trying to trouble shoot.
The host which runs Proxmox is on Europe/Berlin. The container running hass.io is in the correct timezone (Europe/Berlin). Same is the UI.
The VM (which runs the hassio container) which I set up the script mentioned in the initial post is still on UTC.
Host (localtime)
VM (UTC)
Container (localtime)
On VM:
$ timedatectl
Local time: Tue 2020-06-15 07:59:09 UTC
Universal time: Tue 2020-06-15 07:59:09 UTC
RTC time: Tue 2020-06-15 07:59:10
Time zone: Etc/UTC (UTC, +0000)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
I am trying to change that in the VM with
$ timedatectl set-timzone Europe/Berlin
Failed to set time zone: Failed to set time zone: Read-only file system
This changes the localtime until next reboot of the host or the VM. Not perfect.
How can I change the timezone of the VM inside Proxmox persisting a reboot?
I checked. Changing to localtime on the VM solved my initial problem of the time conditions not firing.
Best regards.
Ralf
1 Like
Does anyone know how to set a static IP for the VM in the Proxmox GUI? (please no answers about static leases etc ect).
I can do it on the OS but I’m sure I should be able to do it at the VM level as you can with ESXi.
Apart from the above query, this guide is awesome. I had an old laptop, put some more memory in it and it is running Proxmox with a HomeAssistantOS install - just so easy. Old laptop = battery = UPS! Only drawing 14W so a definite alternative to a Pi.
Easily installed a Let’s Encrypt SSL cert so I don’t get the silly SSL warning.
Only additional thing I had to do was to stop the laptop suspending when I closed the lid - edit /etc/systemd/logind.confas root and…
[Login]
HandleLidSwitch=ignore
HandleLidSwitchDocked=ignore
restart the service or reboot your machine
systemctl restart systemd-logind.service
Job done. Thanks @kanga_who.
1 Like
I would set it up on your switch or router to the VM’s mac address.
I’ve been running my HA on Proxmox for the last 6 months or so and that it was I do with any VM/CT that i need to remain static. Then if you need to spin another copy you have the option of selecting Unique to create a new MAC (and subsequent new IP) or just reuse the original.