Be Smart, Go Local.

How To Install Home Assistant on Proxmox 8: The Easy Way

UPDATED for Proxmox 8.2: Complete guide for easily installing Home Assistant Operating System on Proxmox VE 8, using a custom automated script.

You can now easily upgrade from Proxmox 7 to 8 without loosing data, keeping all your VMs and containers intact. Follow the upgrade guide.

So, you’ve been using Home Assistant for a while now and decided to move from the Raspberry Pi to something more powerful. You picked up a cheap used Intel NUC Mini PC or maybe a refurbished Dell Optiplex and you want to deploy it as your main Home Assistant server.

Proxmox 8 Home Assistant Easiest Setup Featured Image

That’s all great, only you find out your NUC is really overpowered and would like to have the option to run something else in parallel to your Home Assistant instance. You’ve come across Promox a few times within the community, but thought that it might be too complicated for you to setup and maintain.

Well, developer tteck created a bunch of helper scripts for deploying various different VMs and LXCs within Promox with simple one-line commands, streamlining the setup process significantly. We can use it to spin up a Home Assistant OS VM in Proxmox and, if needed, customize the dedicated resources the VM will use.

We can use these helper scripts to also setup a Zigbee2MQTT LXC and separate it from Home Assistant, so it’s always up and running in case of Home Assistant failure. Proper USB passthrough is also important for your Zigbee/Z-Wave dongles or other peripherals you might want the VM to access.

If you already have Proxmox up and running, jump to Installing Home Assistant on Proxmox section and continue from there.

What’s Proxmox?

Proxmox VE is a complete, open-source server management platform for enterprise virtualization. It tightly integrates the KVM hypervisor and Linux Containers (LXC), software-defined storage and networking functionality, on a single platform. With the integrated web-based user interface you can manage VMs and containers, high availability for clusters, or the integrated disaster recovery tools with ease.

Proxmox VE 8 Install Guide Home Assistant
Source: proxmox.com

Like I mentioned, for a smart home use case, we can utilize Proxmox and it’s capabilities do deploy different VMs and LXCs for Home Assistant, Zigbee2MQTT, ESPHome, MQTT Broker or maybe Plex Servers and similar. This will allow you to really utilize the mini PC you just bought.

Create a Proxmox Bootable USB Drive

Before installing Proxmox on your new Mini PC, first, you need to create a bootable USB Drive with the latest version of Proxmox. You can do this by flashing the ISO file either with Balena Etcher or Rufus.

  1. Download Balena Etcher and install it
  2. Download the latest Proxmox VE ISO Installer and save it
  3. Insert the USB drive in your PC
  4. Open Balena Etcher and click Flash from file
Proxmox Home Assistant Balena Etcher
Balena Etcher: Select file
  1. Select the Proxmox ISO file you just downloaded
  2. Click Select target and choose your USB Drive
  3. Click Flash and wait for the process to finish
Proxmox Home Assistant Balena Etcher Choose Target
Balena Etcher: Select drive
  1. Depending on the speed of your USB Drive, the process should take ~2-5minutes
  2. You will get a Flash Completed! confirmation
Proxmox Home Assistant Balena Etcher Flash Complete
Balena Etcher: Flash completed
  1. Close Balena Etcher
  2. Safely remove hardware (USB)
  3. You are ready to install Proxmox on your Mini PC

Install Proxmox on your Mini PC

With Proxmox 8.1, it is no longer needed to disable SecureBoot, a mechanism which the boot sequence verifies digital signatures of the system. However, some users in community forums have reported SecureBoot still causing problems, so it’s best to disable it. With your USB ready, follow this procedure:

  1. Plug in the USB Drive you just created in your Mini PC
  2. Plug in an Ethernet cable for internet
  3. Power it on, and navigate to BIOS (Usually by pressing DEL or F10 key during boot)
    • Depending on your setup, BIOS might look differently
    • Make sure Secure Boot is disabled
    • Make sure Legacy Boot is enabled
    • Make sure Virtualization Technology is enabled
Proxmox Home Assistant Legacy Boot
BIOS Legacy boot
Proxmox Home Assistant Legacy Virtualization Technology
BIOS Virtualization technology
  1. Save your BIOS settings and reboot
  2. Enter your Boot Order Menu (Usually F8 key)
  3. Select your USB Drive and hit enter
  4. You will be presented with the Proxmox Welcome Screen
  5. Select Install Proxmox VE (Graphical)
Proxmox 8 Home Assistant OS Install: Welcome Screen
Proxmox: Welcome Screen
  1. Accept the License Agreement and hit Next
  2. Select the Hard Drive you want to install Proxmox to and hit Next
  3. Select your Country, Time zone and Keyboard layout
    • Make sure select the correct information, as Proxmox is heavily reliant on the time zone to synchronize everything
Proxmox 8 Home Assistant OS Install: Location and time zone
Proxmox: Location and Time Zone Selection
  1. Set a password and e-mail and click Next
    • Password needs to be at least 8 characters, containing letters and numbers
    • You will use this password for the initial Proxmox login
    • E-mail is used for alert notifications (backup failures etc.)
Proxmox 8 Home Assistant OS Install: Email and password
Proxmox: Password and Email
  1. Setup your Network configuration and click Next
    • Set Hostname (pve.proxmox or pve.smarthomescene)
    • IP Address, Gateway and DNS Settings should automatically populate if you have the Mini PC plugged to your home network
Proxmox 8 Home Assistant OS Install: Network configuration
Proxmox: Network Configuration
  1. Wait for the process to finish
  2. Installation successful should appear on the screen
  3. Click Reboot
  4. Access your Promox server from the IP_Address:8006 you gave it
Proxmox 8 Home Assistant OS Install: Finished
Proxmox: Installation Successful

Update Proxmox Packages

Once Proxmox is up and running, you can continue to install the Home Assistant OS VM package. Before deploying the VM, it’s best to check for package updates. Follow this guide:

  1. Open your Proxmox instance by navigating to IP_Address:8006 from your main PC
  2. You will get a warning message Your connection is not private
  3. Click Advanced and click Proceed to IP_Address
  4. On the Promox VE Login enter your credentials:
    • Username: root
    • Password: password you set during installation
Installing HAOS on Proxmox 8: Login Screen
Proxmox: Login Screen
  1. You will get a message saying you do not have a valid subscription
    • This message is showing up because you don’t have a valid enterprise license. We can use a script to remove it
  2. On the left side of the screen, select your VM and click Updates
  3. Click Refresh and click Upgrade
Installing HAOS on Proxmox 8: Upgrade Packages Screen
Proxmox: Check for Updates
  1. A dialog window will popup, going through the available package updates
  2. You may get another license warning, just ignore it
  3. If you get a confirmation dialog, type in “y” and hit enter
  4. If you get a dialog asking the Keyboard encoding select UTF-8 and English
  5. You will get a your system is up to date message
Installing HAOS on Proxmox 8: Upgrade Packages Finished
Proxmox: Updated Packages
  1. Close the window and you are done
  2. If you click Refresh again, the package list should disappear since you already updated them
  3. Done

(Optional) Proxmox Post Install Script

This step is optional, but I highly suggest you run this script too as it will clean up your Proxmox Virtual Environment, get rid of the Enterprise message that keeps pestering you, add or correct repositories and update Proxmox VE.

Proxmox Post Install CleanUp Script
Proxmox: Post Install Clean-up Script
  1. To run this script, select your node on the left and click Shell again:
  2. Copy the following code in the Shell and hit enter
bash -c "$(wget -qLO - https://github.com/tteck/Proxmox/raw/main/misc/post-pve-install.sh)"

You will get a couple of confirmation prompts

  1. Answer “y” to all of them and finally confirm to reboot Proxmox
  2. Done
Installing HAOS on Proxmox 8: Post Install Script
Proxmox: Clean-up Script Finished

Install Home Assistant OS on Promox

To Install Home Assistant OS, we are going to use a script by tteck which will automate the process significantly. This script is tweakable, so there is no need to deploy the VM manually. Running this script will:

  • Find, download and extract the official KVM (qcow2) Home Assistant OS image
  • Define user settings, import and attach disk, set boot order and start the VM automatically
  • Install the VM with Default Settings: 4GB RAM, 32GB Storage and 2vCPU cores
  • Settings can be tweaked during installation
Proxmox Home Assistant Install Script
Home Assistant OS: Install Script
  1. Click your VM on the left and select Shell
  2. Copy the following command to run the script and hit enter:
bash -c "$(wget -qLO - https://github.com/tteck/Proxmox/raw/main/vm/haos-vm.sh)"
Installing HAOS on Proxmox 8: Script command
Proxmox: Running HA OS Install Script
  1. The wizard will ask you to confirm that you want to create a Home Assistant OS VM
  2. Select Yes and click confirm
Installing HAOS on Proxmox 8: Create new HAOS VM
Proxmox: Script confirmation
  1. On the next screen, choose either Default settings or Advanced
    • Default settings are fine for a Home Assistant OS install, but you can assign more RAM and Storage if you need to
  2. If you choose Advanced Settings, you will be prompted to choose:
    • Home Assistant OS Version (Stable, Beta)
    • Hostname (cannot contain underscore ‘_’)
    • VM Machine ID
    • Machine type
    • Allocated CPU Cores
    • Allocated RAM Memory
  3. Select the final Yes to confirm
  4. Wait for the script to download, extract and install the latest KVM image of HA OS
  5. Once you get a Completed Successfully message, HA is installed
Installing HAOS on Proxmox 8: HAOS Script comlpeted
Proxmox: HA OS Script Completed

To check the IP address your router assigned to your Home Assistant VM instance, click your node on the left and select your newly created Home Assistant VM. The IP address will be displayed in the middle, use it to access Home Assistant in your web browser e.g. 192.168.xxx.xxx:8123.

Finished, you just installed Home Assistant OS on Proxmox!

Installing HAOS on Proxmox 8: Home Assistant Welcome Screen
Home Assistant OS: Welcome Screen

(Optional) USB Passthrough to Home Assistant VM

If you use a Zigbee or a Z-Wave dongle, there is one additional step you must do in order to allow the Home Assistant VM to read your attached USB device.

  1. Plug in your USB Device (Zigbee dongle) to your Mini PC
  2. Select your Home Assistant VM on the left
  3. Select Hardware from the Menu
  4. Click Add at the top bar
  5. Select USB Device
Installing HAOS on Proxmox 8: Home Assistant USB Passthrough
Proxmox: USB Passthrough
  1. Select Use USB Vendor/Device ID from the menu
  2. Select your USB Device (Zigbee/Z-Wave Dongle)
  3. Click Add
Proxmox: USB Passthrough by device id
  1. At the top corner, press the small arrow next to Shutdown
  2. Choose Reboot and confirm to restart the VM

If you navigate to Home Assistant, you USB dongle will be auto-discovered and you can continue to setup your integrations. If you are having issues, read more of how to properly Passthrough USB Devices To Home Assistant.

(Optional) Set CPU scaling governor

The CPU scaling governor controls how fast the CPU works depending on what it’s doing, aiming to save power or boost performance. By changing the speed of the CPU, the computer can use less energy when it’s not working hard. To set the CPU governor, open the Proxmox Shell and run the script bellow:

bash -c "$(wget -qLO - https://github.com/tteck/Proxmox/raw/main/misc/scaling-governor.sh)"

The script will show you what the current scaling governor is, and depending on your hardware and how concerned you are about saving energy, you can set it to powersave:

Proxmox CPU Scaling Governer Home Assistant OS
Proxmox: CPU Scaling Governor

Make sure to also setup a cronjob on the next screen, so the CPU scaling governor configuration is persistent across reboots. Select yes, followed by ok and reboot Proxmox.

(Optional) Set a static IP Address

It’s highly recommended to set a static address for Home Assistant OS in router’s DHCP settings. This will allow the VM to be able always reachable to the same IP address, preventing access issues in the future. If you don’t know how, google your router model + static IP address. You can also do this in Home Assistant too:

  1. Open your Home Assistant instance
  2. Navigate to Settings > System > Network
  3. Click IPv4 and select Static
Home Assistant Proxmox Static IP address
Home Assistant: Set a static IP Address
  1. Set the IP, Gateway and DNS
  2. Click Save

Summary

Deploying Home Assistant on a Proxmox Virtual Environment using these scripts is a breeze. Developer tteck made it a seamless process that even the non-technical can follow. He has a bunch of scripts on his repository, which allow you to further customize your Home Assistant installation in a VE. For example:

  • Install Zigbee2MQTT as a separate LXC
  • Install MQTT Mosquitto Broker as separate LXC
  • Install ESPHome as a separate LXC
  • Install MariaDB as a separate LXC
  • Install InfluxDB as a separate LXC
  • Deploy AdGuard or Pi-Hole for system-wide ad blocking
  • Deploy Tailscale for easy remote access

The advantage of deploying these Home Assistant add-ons separately is they will be independent of Home Assistant and it’s current state (installing, rebooting, breaking changes etc). You can connect them together and setup HA to read data from each one, operating as it should.

If you are looking to replace that old Raspberry Pi, this is the way to go, especially if you are not familiar with virtual machines and Linux environments. Consider buying him a coffee for creating these awesome scripts.

74 thoughts on “How To Install Home Assistant on Proxmox 8: The Easy Way”

  1. Going forward, versioning will no longer be utilized in order to avoid breaking web-links in blogs and YouTube videos (for the final time). So, as a result, the name of the shell script has been updated from `haos-vm-v5.sh` to `haos-vm.sh` .

    Reply
  2. Databases can be very sensitive to sudden power loss. This is less of an issue on bare metal, but is a big concern in virtual environments. The hypervisor may do caching/buffering that the DB is not expecting and can result in irrecoverable DB corruption. I would strongly urge Proxmox users to set the disk cache option on the HAOS VM to “writethrough” to greatly lessen the chance of lost writes that cause corruption.

    Reply
  3. I would also suggest adding an optional step to opt-in to the latest 6.x kernel that Promox offers. This can really help with hardware compatibility/drivers, particularly on newer Intel platforms.

    Reply
  4. The script produces an error on Proxmox 7.4-3:
    Using Default Settings
    Using HAOS Version: 9.5
    Using Virtual Machine ID:
    Using Machine Type: i440fx
    Using Disk Cache: Default
    Using Hostname: haos9.5
    Using CPU Model: Default
    Allocated Cores: 2
    Allocated RAM: 4096
    Using Bridge: vmbr0
    Using MAC Address: 02:63:F2:9B:5E:DE
    Using VLAN: Default
    Using Interface MTU Size: Default
    Start VM when completed: yes
    Creating a HAOS VM using the above default settings
    – Validating Storage…bash: line 362: pvesm: command not found
    numfmt: invalid number: ‘\033[01;31m362\033[m:’

    [ERROR] in line 355: exit code 2: while executing command FREE=$(echo $line | numfmt –field 4-6 –from-unit=K –to=iec –format %.2f | awk ‘{printf( “%9sB”, $6)}’)

    Reply
  5. Thanks for this guide and thanks to the Dev for the scripts.
    Can I ask I’m wanting to do this mainly for
    HassOS,
    ZigBee2Mqtt & Node red.
    But there’s about another 4 on that list I would like also and each ones shows default ram and CPU cores,
    so say I want 8 small VMs that say they need 1gb ram each and 1-2 CPU cores would that mean I need a system with 8gb Ram and 8-16 CPU cores 😲
    Or are you not meant to add them together like that.

    Reply
    • No, no need. All containers share the kernel and resources of the PC, so you can get away with less.

      It largely depends on what you intend to run though

      Reply
  6. The final script did not work. I put it in (3x – copied twice and then typed a third) – system just went to the next line. No evidence anything happened. Ideas??

    Reply
  7. Awesome stuff. Thank you.
    What a great tutorial and script. Saved me sooo much time on my rebuild compared to my first implementation.
    The only thing I’m having an issue with is the USB device config.
    I’ve config’d the proxmox vm as you did for USB vendor/Device ID and rebooted.
    HAS does auto discover the Conbee II and I can see it in integrations but when I try to configure it I get an error “Failed to probe the usb device” then it disappears from the integrations page until I reboot and it’s auto discovered again. I tried a few different ways, incl usb as a passthrough port but same error.

    Any advice ?
    Thanks
    Gav
    HAS 2023.4.4
    Proxmox 7.3-6

    Reply
    • Hello,

      Did the Conbee worked before? Seems like a firmware issues, have you tried flashing it with the latest firmware?
      I had similar problems with a Sonoff ZBDongle-E which I fixed by flashing the latest firm.

      Let me know.

      Reply
      • It did work previously but it was a few yrs ago when I set it up.
        Other research found there were problems with the conbee after a firmware update.
        I did flash a few different firmware versions but no joy so I’ve now bought a SkyConnect and it’s chugging along nicely.

        Reply
  8. I have the same issue, the command does nothing. I tried to copy/paste and tried to type it… Any idea why it is not executing? I’m running it as a root user.

    Reply
    • Are you sure you are pasting it correctly? If a letter or two is missing, it won’t do anything.
      Use Shift + Insert to paste the script, I am saying it again: It is correct.

      Reply
      • I had the same issue. I followed the http link to the script and did a copy of the code. Then I opened the console command and navigated to the location of where the script was supposed to reside and nano created the .sh script with a paste. I then had to make it executable and manually ran the script from the cli. It worked and was a bit of a fudge. I’m not sure why me and others can’t run the script from the wget code.

        Reply
  9. “UPDATE 29.03.2023: A pro tip for setting the disk cache option on HAOS to writethrough greatly lowers the chance of a corrupted database on Proxmox. Thanks Derek!”

    How? LOL

    Reply
  10. Got it!
    HAOS
    – Hardware
    – Hard Disk (double click to open option window)
    – Cache dropdown
    – Write through

    Reply
  11. Hello. First I want to say I appreciate the work you have done. I have just completed proxmox with the intent of learning virtualization and especially home assistant, and many other things. I started researching installing HA and found your guide which seems to make it easy.

    However, I like others I have experienced the issue where using the command does nothing. There were no available updates on my fresh install (not sure if that’s weird or convenient)

    At first I was like ‘well, lets make sure I can reach the outside world’ so I used traceroute (after getting irate that shell wouldn’t recognize tracert until I remembered I was using linux) and that was successful. I rebeooted the machine (step 1, just in case, right).

    I copied and pasted the link several times, copied it to notepad to make sure there are no extra spaces at the beginning or end, and typed it carefully several times and am still experiencing the issue others have had where the command does nothing.

    I’m sure your script does work in 99 percent of the cases and don’t expect you to cater to me (especially because you are doing this out of the kindness of your heart and to help people) but it does seem to be more than an isolated issue. Do you have any suggestions to any configuration issues that may be causing a few of us to experience difficulties?

    Either way, thank you for your contributions, I am excited to start the fun!

    Reply
    • Okay, this is such a well-written comment that I would to thank you for providing your feedback.

      The shell command has been working without issues for me, BUT there might really be something going on since so many people reported it. I will dig deeper and post a video tommorow of EXACTLY the steps I take to install the VM using the script.

      Cheers

      Reply
      • Thank you! In reading through your instructions to set up HA I skipped the ProxMox install as I already had it installed. I went back and read and the only difference in my install is I used a fake FQDN as that’s what the install suggested. I don’t know if that will affect this situation, but wanted to give you any info I have.

        Reply
      • If I understand the problem, I ran in to the same. When I copied the script and pasted it into the Proxmox Shell, then hit “Enter”, nothing happened. Tried several times with same result; it just returns immediately to the command line. I then typed in the script manually and hit Enter and it ran just fine. I later ran into the same problem with copying and pasting scripts into the Shell where nothing happened. But, if I manually type in the script it runs fine. Not sure what the problem is, but it is repeatable and I have not yet resolved the problem with pasted-in scripts.

        Reply
  12. Your traceroute worked? I’m not sure if that’s what you said. (Forget how to traceroute in Linux.)
    It wasn’t working for me either. I ran it several times and thought it was to work silently. LOL.
    After a few hours I came back to check and no change. Then I decided to ping something. I found out that internet wasn’t working. Fixed that and ran the script again.
    IT WAS A THING OF BEAUTY!

    Thanks!!!
    You have NO IDEA how much pain you saved me!

    Reply
    • My Traceroute did work (On linux its traceroute, on Windows its Tracert). My trace route did work and I still am having the same issue, but I can’t help but wonder if I’m having some sort of connection issue to the outside because I do get an error trying to find the Debian repositories, but it’s weird that I can ping, trace route and still get nothing.

      Reply
    • I mucked up DNS and got these symptoms, i.e. script wouldn’t work, but it wouldn’t without DNS would it! All worked well for me – thanks.

      Reply
  13. I’ve racked my brain all day at work, and then I had an epiphany and I solved my issue (and I think everyone elses issue) with the script not working. I still had the 127.0.0.1 which was the default example for the DNS- I only ever pinged and traced the DNS, but never tried a domain. I switched my DNS to the google 8.8.8.8 and sure enough, the script worked.

    Not bad for a car salesman who just dabbles in computers for fun, right?

    Reply
  14. Awesome, just upgraded from Virtualbox running on a windows 10 PC with a script to auto start that was having issues after an internet outage requiring the host to be rebooted to regain access. TY TY!

    Reply
  15. great guide!

    maybe you can add on step 23 Hostname cannot consist _

    script will fail, got the info from the home assistant forum

    Reply
  16. Question,
    Is there a reason why the HA is build as a VM and not as a container?
    Just wondering, since I had the option to go through Docker on an Ubuntu OS, but I read Proxmox can also handle both.
    I’m using now Proxmox on an HP elite desk 8GRam and i5 7Gen.
    Thanks for a reply.

    Reply
  17. Count me as a successfully deployed Proxmox+HA+Zigbee in a Lenovo M93p

    So easy and straight forward. Thank you so much!

    Reply
  18. I installed Proxmox using this method on a NUC which was running Windows 11. Is there any way of reversing the Proxmox installation so that I go back to Windows 11 and all the apps that were previously running?

    Reply
  19. Hi,
    Thank you for your extensive guide. I’ve got it up and running but I’m struggling to reach certain port from an addons. In my case I would like port 81 to be accessible in order to acces the Nginx Proxy Manager UI, is this something that I need to configure on the VM in Proxmox?

    Thank you

    Reply
  20. Thank you for this tool. It worked for me the first time, however I decided to “blow up” my HA setup and start over – and now having issues.

    I successfully removed/deleted my original VM containing HA.

    Running the script again – getting some of the same issues listed above – cutting and pasting the script command the first time results in nothing happening. Typing it didn’t help either.

    I simply get a next line with a “>” displayed.

    If I past it AGAIN, then it will run – seems to run successfully. I can see it create a new VM which appears under the PVE for a few seconds …. then it disappears and I get this error:

    bash: -c: option requires an argument
    [ERROR] in line 431: exit code 2: while executing command bash -c

    Any suggestions here?

    Reply
    • See the other comments bellow, you need to check your DNS settings.
      The second error is most likely because you are not pasting the command correctly. Use CTRL + SHIFT + V

      Reply
    • I screwed up my copy paste and got this behavior. I got it to go making sure the command had the trailing quote and tossed semicolon on for good measure.

      Reply
  21. Hi, I’m getting an error after install.
    Using google DNS and its working. Did cntr shift v to paste

    Any ideas?

    Using HAOS Version: 11.0
    Using Virtual Machine ID: 101
    Using Machine Type: i440fx
    Using Disk Cache: Write Through
    Using Hostname: haos11.0
    Using CPU Model: Host
    Allocated Cores: 2
    Allocated RAM: 4096
    Using Bridge: vmbr0
    Using MAC Address: 02:AD:74:67:39:03
    Using VLAN: Default
    Using Interface MTU Size: Default
    Start VM when completed: yes
    Creating a HAOS VM using the above default settings
    ✓ Using local-lvm for Storage Location.
    ✓ Virtual Machine ID is 101.
    https://github.com/home-assistant/operating-system/releases/download/11.0/haos_ova-11.0.qcow2.xz
    ✓ Downloaded haos_ova-11.0.qcow2.xz
    ✓ Extracted KVM Disk Image
    ✓ Created HAOS VM (haos11.0)
    ✓ Started Home Assistant OS VM
    ✓ Completed Successfully!

    bash: -c: option requires an argument

    [ERROR] in line 442: exit code 2: while executing command bash -c

    Reply
    • You are either pasting wrong or pasting at the wrong space.
      In any case, update Proxmox packages.
      Reboot the host.
      Paste the command.

      Let me know how it goes

      Reply
  22. Hello from France !

    Many thanks for this very effective tutorial. A very nice job.
    I followed it by directly installing version 8 of Promox on a NUC N95 / 8GB DDR5 3200MHz / 256GB nvme SSD for €135. Faster and cheaper than a Raspberry Pi 4 (which I love) with power supply + sdd + case

    Congratulations
    Fred

    Reply
  23. Simplified things. Is it possible to get the scripts. I do like to review the scripts to verify security and malicious activity possibilities.

    Reply
  24. Hi,
    I succesfully installed PVE and HA as you suggested. I read your article on Zigbee, MQTT. If I understand it correctly PVE has to be in a container, not a VM. Can the VM be converted to a LXC container? If not how do you create the HA container? Thanks for your help.
    Steve

    Reply
    • Hello Stephen,
      PVE stands for Proxmox Virtual Environment and it’s just that – an Debian-based virtual environment that you use a base and install applications (containers) or virtual machines (operating system) on to it.
      You cannot convert a VM to an LXC, you would have to reinstall it.
      Please tell me, ultimately, what are you trying to achieve?

      Reply
  25. First time proxmox and HA user so excuse my ignorance. I’ve followed the guide no problem and have HA running. I read there is different types of HA installs, (full install, hass.io, supervised etc) which one is this or what do these terms mean? I was searching for the Myenergi integration but it doesn’t show up and supposedly it may not be available depending on the type of install. If i want to manually add an integration how can I get to the folder directorys in my HA instance on proxmox? It’s probably staring me in the face but I can’t find it anywhere. All help greatly appreciated.

    Reply
    • Are you pasting it correctly in the Shell?
      Use right click or Ctrl+Shift+V
      bash -c "$(wget -qLO - https://github.com/tteck/Proxmox/raw/main/vm/haos-vm.sh)"

      Reply

Leave a Comment