Move Home Assistant to Proxmox: A complete step-by-step guide

[@ResinChemTech]

Note: Changes to both Proxmox and Home Assistant versions resulted in changes to the scripts used for the post install and the Home Assistant VM creation, rendering the links/scripts shown here obsolete. Please see the following for the latest scripts and execution info: community-scripts.github.io/ProxmoxVE/scripts

[@Ariana-sb4ix]

This tutorial was just what I needed. Proxmox is so intimidating, but this made it easy. Thank you for such great detail!!

[@ResinChemTech]

Glad you found it helpful. Unfortunately, videos like this can become a bit dated over time as new versions of software are released. I think Proxmox is now up to 8.3.x. And new software versions can also change things like the install scripts, etc. But hopefully the general process still works even with new versions. I've been very happy with Proxmox after a poor experience with Virtual Box when trying to move off of my original Raspberry Pi. I've yet to experience a single failure or issue with Home Assistant on Proxmox. And if I do, I have the added bonus of the full VM backups if need to move to a different machine because of a hardware failure. Thanks for watching.... and thanks for the comment!

[@Ariana-sb4ix]

⁠ for what it’s worth, I just used this video with Proxmox 8.3 and was able to follow everything. I had to adjust the script to work with 8.3 but a google search led me to a Reddit post that showed how to do that. Overall it is really the exact same process. I am moving over from hosting HA on my QNAP NAS, which has not been a good experience. Slowness and crashes all around. I am really looking forward to seeing how it does on the miniPC. Already it is way faster to restart!!!

[@kloakovalimonada]

You're a great instructor. The little hints and tips ("...that means you have two instances of HA running but as they have different IPs, it's fine") are very valuable and almost always omitted in guides. Clarity is #1 important and your video is super clear.

[@ResinChemTech]

Wow... thanks for the kind words! I do try to explain the "why" and just not the "what" in my videos. This tends to make them a bit longer than other videos of the same type, but I hope that it allows folks to take my ideas and understand how to adapt them for their own projects. Thanks for watching... and thanks again for taking time to leave a comment!

[@bobdurk5180]

Definately a great tutorial; I think I will need to watch it through again a few times before I attempt it.

[@ResinChemTech]

Do note that, as someone else mentioned here, a few things have changed since I made the original video. But the steps should still pretty much be the same. The other important thing is that to assure you upgrade your existing Home Assistant to the latest production release before you move it to Proxmox, as the installation on Proxmox will install the latest version and trying to migrate an older version to the most current one could cause issues in some situations. Thanks for the comment!

[@klowirzi]

@@ResinChemTech I got the notification that the script used for "Configuring and Updating Proxmox VE". I get the message, that "This version of Proxmox Virtual Environment is not supported. Requires Proxmox Virtual Environment Version 8.0 or later." while running Proxmox Virtual Environment 8.3.0. Any solution to that? Thanks for the tutorial by the way ;)

[@ResinChemTech]

Unfortunately, version changes to Proxmox and Home Assistant also required changes to the scripts. I didn't develop these scripts, but you can find _current_ versions on the author's site: community-scripts.github.io/ProxmoxVE/scripts For example, you can find the latest post-update script under the Proxmox branch (Proxmox VE Post Install) and the Home Assistant installation script under the Home Assistant branch. Running the scripts as posted there should work. If not, then you'd likely need to get in touch with the author or post an issue/comment in the repo. I'll try to update the video description and blog article with this info as well.

[@MonoxideC]

This was such an amazing help! Huge thanks!

[@ResinChemTech]

You are most welcome! Thanks for the comment!

[@richmaliz]

This was a great tutorial! Got my Home Assistant up and running on proxmox in less that an hour. Keep up the great content.

[@ResinChemTech]

Fantastic! Glad my video helped out a bit. I've been very happy with the performance and stability of Home Assistant on Proxmox and love the ability to create both snapshots and full VM backups in addition to the normal Home Assistant config backups. Thanks for taking the time to post a comment and let me know that it worked out for you!

[@angusmccloud3369]

had been putting off this job for so long, followed your vid and it couldn't have been easier. thank you so much. now to get frigate going!

[@ResinChemTech]

Congrats! I've been very happy with Home Assistant running on Proxmox and the process really is easier than most might believe. Good luck with your Frigate project. Thanks for taking time to leave a comment. It is appreciated!

[@ssoat1136]

Massive help this guide

[@ResinChemTech]

Thank you so much! I greatly appreciate the support and I'm glad you found the video helpful. Don't hesitate to reach back out if you run into any questions and I'll be glad to try to help.

[@apreotea]

Thanks for this video, helped me migrate from RPi to a nice little compact i5 box with minimum of headaches. Cheers!

[@ResinChemTech]

You are welcome! Glad you found the video helpful. And I think you will be very happy running under Proxmox with the i5 over the RPi. Thanks for the comment!

[@apreotea]

@@ResinChemTech I'm considering adding Frigate with a Coral USB accelerator next... I think you threw me down a rabbit hole 🤣

[@troyd-motorsport9933]

Great video! Very detailed and easy to follow for a noobie at proxmox. Thanks!

[@ResinChemTech]

You are welcome! Glad you found it helpful. Thanks for the comment.

[@ZerozPk]

This was easily the best step by step video for proxmox and HA I found. I'm super super new to servers, VMs, and HA so I found it confusing and really needed a step by step guide. Thank you so much for the clear instructions.

[@ResinChemTech]

You are welcome... and thanks for the kind words. While my videos are generally longer than most, I do try to assure that I cover all the steps that someone with little to no experience can follow to successfully complete a project, while trying to also including the "why" as well as the "how". I'm glad you found my video to be helpful... and hopefully not too confusing! Thanks for watching... and taking the time to post a comment.

[@Nickolas63000]

Hello, my nuc will be shipped tomorrow and is going to replace my rpi3 so your guide is just perfect to me , way easy to understand many thanks for this ! Fingers crossed for tomorrow's installation but with your video I'm really confident to succeed in doing this. Again Merci beaucoup !!!

[@ResinChemTech]

I've been very happy with my Home Assistant running under Proxmox on a NUC/Mini PC. It is fast, stable and I get the added benefit of the VM backups. Good luck... and let me know how it goes!

[@ElishaiPoran]

Well done for creating the video on a very important and useful topic without a doubt! Thank you very much and I subscribed to your channel for fun!

[@ResinChemTech]

Thanks for the comment... and subscribing. Welcome to the channel!

[@andymok7945]

Good info. I started with HA on a pi, with slow reboots and damaged SD cards. Then ran HA on Proxmox for several years. Now have it on HA blue hardware. Reason, it was a pain having the down time during the reboots when Proxmox has certain update. I have all the add-ons running in LXC on a small system running Proxmox and is working out great. It was easy to transfer HA from my first Proxmox machine to a new Proxmox with more resources. Just create a new backup of the VM and then restore it to the new machine. Having node-red, mqtt up while HA is rebooting is also nice.

[@ResinChemTech]

Thanks for the feedback. My ultimate goal here is to use my three separate Proxmox servers to setup replication and high availability. So, when I need to run any kind of updates on Proxmox, I just replicate Home Assistant to another server and then I can update the original machine with no downtime. And of course if the server goes down, Home Assistant will spin back up on one of the other two servers automatically. I am running a few other things on one of the other servers now... like PiHole and the Unifi controller. But I want to experiment with some other stuff down the road. Thanks for watching and taking time to share your Proxmox journey!

[@andymok7945]

@@ResinChemTech I saw over a year ago that someone else made a video on hosting HA on a cluster of 3 proxmox systems. It was a neat setup. for having high availability HA. I pondered it and decided that it was not for be and the way I do things. Each to their own. I know that Quindor from Intermitent-tech is doing a series of videos in using proxmox as well. It would be nice to have high availability for MQTT, node-red, ESPHome, zigbee2mqtt as an easy setup, but I am not holding my breath. I am struggling with getting influxdb2 working with storing the database files on a network share. Anyway, enjoy the journey and have fun learning new things.

[@ResinChemTech]

Yeah.. it was Quindor's video that inspired me to pick up a 3rd server (I was already running 2 Proxmox servers). For me, it really is more about learning... and just seeing if I can... than it is about true 100% uptime for Home Assistant. That being said, my wife has become accustomed to many of the automations and conveniences. With the failover, if Home Assistant goes down for some reason while I happen to be out of town or away, it will come back up on a second server and keep running until I can get home to address the original issue, making for a better WAF... which is always a good thing! But honestly... I'm just doing it to see if I can, and to learn a little bit more about Proxmox along the way (I learned a bunch already just doing this first video... despite the fact I had been running Proxmox for 3 years).

[@DaveA-sb7ue]

Another great video and tutorial. Followed this step by step and I am now running my HA on proxmox. Great suggestions you just don't see in other videos. The part about copying the Mac address was such a great idea and worked perfectly. Thanks!

[@ResinChemTech]

Thanks! It really is a pretty easy process, although it may not seem like it at first! Congrats on the successful move. I think you'll be happy with the end results and reliability... especially if you migrated from something like the Raspberry Pi.

[@JMX246]

This is great - thanks for posting - will be doing it when my Nuc arrives - appreciate the written version too (sometimes easier to follow)

[@ResinChemTech]

You are welcome! I try to create a written guide for most of my projects, especially those that have wiring diagrams or code. To me, it is easier than trying to go back through the video, find the appropriate diagram or code block and then freezing the video. Good luck your migration. Let me know how it goes or if you run into any problems or questions.

[@echodun]

Moved from Win 11 VM/VirtualBox to Proxmox by following this video and I was up and running in less than an hour. BalenaEtcher killed my USB card until I got it back running and tteckster's page looks a little different now, but I figured it out. Also, ran the backup using the method here to my Windows 11 server computer that HA was originally installed. In the last steps (after copying the MAC address and putting my old HA offline), I inserted the Sonoff USB into the NUC (GMKtec G3) and it did require a reboot of the new Proxmox HA install, but worked after that.

[@ResinChemTech]

Glad it worked out for you! Yeah... the scripts always have to be updated due to both newer versions of Proxmox and later releases of Home Assistant, so it's always likely that older videos may not be 100% accurate after a time. I don't have a USB dongle (my Zigbee hub is standalone), but I appreciate you letting me know that just moving the USB dongle worked out without issue. Thanks again for watching.. and the comment.

[@rodneysmith1750]

Great video, and timely in my particular case! Thank you for everything, all your beneficial and informative videos, and the personalized help you have offered in the past, you have opened a whole new hobby for me with Home Assistant. I am anxious to see where you go next...

[@ResinChemTech]

Wow! Thanks. I'm glad you found the information helpful... and I'm always glad to help out whenever and however I can. Thanks for watching... and thanks so much for the kind words!

[@sashastal]

Thanks for the tutorial! Might be useful for somebody: 24:20 It doesn't work for me if I restore from "welcome page", its processing endlessly; I tried several times. But if I sign up to new VM, upload full backup file to it (Settings -> System -> Backups: Upload backup) and restore from that backup, it goes smoothly and quite fast 🤗. Everything works on new machine as expected. (I'm performing migration from RPI 4 to ProxMox (on Firebat ak2Plus), backup file weights ~120MB, influxDB, grafana and some integrations. )

[@SavagrH3]

I just migrated from an Unraid VM and this video was very helpful. I tried migrating a while ago and had issues with the MQTT broker. Using the same IP address as the old installation and copying the MAC address from my Unraid VM made the transition seamless. Thanks!

[@ResinChemTech]

It was the same for me... although I moved from Virtual Box. But by having the MQTT add-on as my broker, keeping the same IP address was a requirement due to the number of devices that relied on MQTT. Thanks for watching and I'm glad my video helped out a bit.

[@shb117]

Thank you - this worked for migrating my HAOS 12.4 on an older Dell Wyse PC to my newer PC running Proxmox 8. The only extra thing I had to do, to get my Sonoff Zigbee dongle to work was allow the VM to see the USB port.

[@ResinChemTech]

Glad it worked out for you! My Zigbee hub is standalone, so I didn't have to do anything with a USB dongle. But like you, many have reported that you just need to pass the USB port thru to the VM for it to work. Thanks for the comment and letting me know that it worked out for you!

[@ssoat1136]

Brilliant tutorial for moving old HAS from raspberry pi to new proxmox VM. The tip to clone the mac address from the original instance was an absolute timesaver.

[@ResinChemTech]

Thanks! For me, I had way too many devices that relied on the Home Assistant/MQTT IP address. Changing IPs wasn't an option. Of course, I could have reassigned the IP address via the router, but just cloning the MAC address was the quickest and easiest option for me.

[@ajueket]

Thank you for this. It was super helpful!!!

[@ResinChemTech]

You are welcome! I'm glad that you found it helpful.

[@MaultierKojote]

Fantastic video. I will move soon to a new flat an was wondering on how to replace my rpi with something beefier and more reliable. Thanks to you now I know :)

[@ResinChemTech]

I've been very happy with Home Assistant running on Proxmox. And the setup/migration process is much easier today than it was when I migrated a few years ago. Glad you found the video helpful. Thanks for taking the time to leave a comment!

[@trashpse6094]

Nice work, thanks! Could you also give me a hint on you dashboard? Whicht ha-bib did you use to build this clear structure with this nice cards, and temperature graphs?

[@ResinChemTech]

There really isn't anything fancy or advanced about my dashboards. I use my own custom theme, primarily based on some changes I made to the built-in default theme. I then just dropped in a background image, which I found online and is loosely based on a Homekit background. Pretty much everything else, including the temperature graphs are pretty much "stock" Home Assistant. I do use two custom HACS components... the custom-button card and the custom-text divider. But otherwise, there aren't any other add-ons or fancy YAML used to create the dashboards I show. Thanks for watching... and thanks for the comment.

[@Epikaiigh]

Thanks for the guide! I followed it successfully to move my HAOS into Proxmox this afternoon!

[@ResinChemTech]

You are welcome... and congrats! If you migrated from the Pi, I think you'll be much happier running under Proxmox. Not only for the speed, but for the ability to do snapshots and full VM backups. Thanks for taking time to post a comment and to let me know that my video helped!

[@ThomasOberhoff]

Great video thank you 😊

[@ResinChemTech]

Glad you liked it. Thanks for the comment and kind words.

[@hoctrimededebutry8655]

Hello from France !! thanks for this great video 🙂I'm getting to try to migrate my HA on PI4 to a mini PC HP G800. Thanks a lot !!

[@ResinChemTech]

You are very welcome! The process really is pretty straightforward and simple these days. Where most folks run into issues is if they try to migrate Home Assistant from the Pi before it has been fully upgraded. You should always assure you are on the latest version of Home Assistant and everything is working correctly on the PI before taking your backup and attempting to migrate. Good luck... and let me know if you have any questions or problems!

[@natearrigoni]

Edited: I had to do the VM again, something was off with the RAM I set, and it wouldn't let me change it. Ghost in the machine, I guess. There were a few changes in one of the scripts but going with defaults for those has worked so far. Nice work, I'll check out some of your other stuff!

[@ResinChemTech]

Unfortunately, with technology and especially software, a video can be out of date almost as soon as it is published. Home Assistant has a new release every month and Proxmox is now at version 8 and the video is nearly a year and a half old. So invariably things are going to change and it is simply not feasible to keep all the old videos, blog articles and Github repos up to date. Sorry if you found my video out of date, but hopefully even though some particulars may be slightly different, the process and overall teps are generally the same.

[@natearrigoni]

@@ResinChemTech No, it was fine. Everything updates so fast, which is good, and your pace is great. Proxmox is new to me, so new this was the 1st time I messed with it. I just left the unknowns default, and it was fine on the 2nd go. Still not sure what happened on that 1st try but I won't lose sleep over it. Other issue, which I realized quickly, is this Latte Panda MU has no Bluetooth for my sensors, lol. I totally overlooked that. I have a dongle on the way I think will work and I can set it up under USM in Proxmox. But might need a recommendation for one if this isn't compatible. Thanks again for this video!

[@GregOnSummit]

Just what i needed ... thank you. Now to figure out my zigbee and coral devices.

[@ResinChemTech]

You are welcome! I've been very happy with Proxmox and it has been very stable. If you haven't looked at it yet, I have a companion written guide to the video that might be helpful when you do decide to actually migrate: resinchemtech.blogspot.com/2023/03/home-assistant-proxmox.html I do talk a bit in the article about USB devices, but since I don't use any (my Zigbee hub is standalone), I didn't have a good way to show/demo the process of moving it. But in most cases, it is a pretty simple process. Let me know if you run into any questions or problems along the way when you decide to make the move.

[@tomgle]

Very well done video. It looks like that took some work. Thank You. I bought a Beelink Mini PC last Fall with a 5095 that has the performance more or less of an I5. Power is low ranging from 4 watts to 11 watts on my Watt Meter. When you mentioned the virtualization setting of Intel VT, I had to boot the Beelink into Bios to take a look. The Beelink Bios has Intel VMX and it was on by default. I Googled VMX and it's equivalent to VT. Your video is the incentive I need to get my HA moved off a Pi 4 and onto the Beelink.

[@ResinChemTech]

Glad it might help you out. I first tried to move from the Pi onto VirtualBox running on Windows... that didn't go well! But I've been very happy running on Proxmox... it has been very stable, takes very little maintenance.. and the VM backups are a huge plus, along with the ability to do those snapshots right before something like a Home Assistant upgrade. I'm sure you won't have any issues, but just let me know if you run into questions.

[@Sciencefriend]

Thank you for your nice instructions! How do I find out the MAC address of the old system when it runs on a Raspberry Pi? Thank you!

[@ResinChemTech]

The easiest way it probably to just go to your router, find the IP address of your Home Assistant install and you should be able to get the MAC address from there. it's also possible to get it from the command line of Home Assistant, but looking it up on your router is probably the quickest and easiest solution.

[@mmoci81]

Very useful and clearly explained video, thank you! One question though, where can I find doc for Zigbee USB dongle migration?

[@ResinChemTech]

Since I don't use a dongle, I really can't tell you. But a simple Google search turned up this article which you might find helpful: smarthomescene.com/guides/how-to-passthrough-usb-devices-to-home-assistant-in-proxmox/

[@aalmarshad]

I have proxmox running more than 4 months. I thought it’s complicated to migrate from raspberry pi to prx. Thanks 🙏

[@ResinChemTech]

Not too long ago (and when I actually migrated) it was much more complicated. But now between the updated and excellent script to create the Home Assistant instance and the full backups of the Home Assistant configuration, the migration is much easier and quicker. Before, you had to run a lot of Linux commands from the command line. Now, it's just a couple of copy/paste statements and you are up and running. Thanks for watching and taking the time to comment.

[@dreamkiss]

Fabolous video, thanks

[@ResinChemTech]

You are very welcome. Hopefully you found it helpful.

[@fredjaspers4364]

Thank you for your great video and clear guidance. I am migrating from a Pi to a Intel NUC. Using a Conbee II usb stick as controller. The full backup tar file import went without any problem. I wonder if I can just plug the Conbee stick into the NUC and HA will pick up the integration based on the Full backup data?

[@ResinChemTech]

As I think I mentioned in the video, I don't use any USB dongles as my Zigbee hub is standalone and not attached to the HA server. But from what understand from comments made by others, you just need to set the USB port to pass-thru for the Home Assistant VM. It should be picked up and work at that point. You could probably just do a search for something like "home assistant proxmox zigbee dongle" and find exact information on how to set it up.

[@hoctrimededebutry8655]

I'e just done the migration 🙂It is a success !! thanks a lot. Just one step to do : install my USB Conbee dongle on my new machine. I suppose that i could find useful video/tutorial on it on the web. Thanks again for your help !!

[@ResinChemTech]

Great! Congrats. I think you'll find running Home Assistant on Proxmox is outstanding.. especially the ability to create those quick snapshots as an extra precaution before an upgrade. As I mentioned in the video, I don't use any USB dongles, but my understanding is that you just need to go to the hardware setting for the HA VM and select USB passthrough for the dongle. But you are right, there should be ample information available elsewhere to help you out with that. Thanks for the comment... and letting me know you have it successfully working!

[@hoctrimededebutry8655]

@@ResinChemTech My USB Zigbee dongle works perfectly. In fact it was very easy to add it via the hardware menu. The next step is to by a bluetooth dongle (the HP 800G2 doesn't have a BT chip inside...) in order to communicate with my temperature sensors.

[@dave1383]

Great video! I haven't done it yet, have liked and subscribed! Looking forward to watching that fallover video. My HA is still small and on HA Green actually. My Proxmox box I picked up on eBay, new, for $100, HP Z1 G5 workstation, i7-8700, 32gb RAM, couple new Crucial 1tb SSDs, couple 1tb HDDs not enterprise, should suffice. I'll follow up when I get there.😅

[@ResinChemTech]

Yeah.... I need to get to that failover video at some point. But Home Assistant on Proxmox has been so reliable, I just haven't had the motivation to move it up on my list of projects. That machine you picked up will be more (much more) than enough for Home Assistant and a handful of other VMs as well. Definitely follow up once you make the move... and thanks for the sub. I greatly appreciate it!

[@dave1383]

Being a fair newb, I'm uncertain while playing around. The HA script creates a VM/CT has a blue dot behind the VM name now, did load, if I didn't do something wrong. 😅 HA restore also seems hesitant to do a full backup and spins for hours. 67mb tar file. Will continue to poke around at it.

[@dave1383]

Somehow, I got there, not exactly the same path. Creating a new HA instance in Proxmox wasn't restoring 🤷, I removed and retried several times. Since I already had another raw HA instance in Proxmox, my primary is HA Green, I fiddled and read how to's until blue in the face, eventually figured out how to copy my backup file to that instance, restarted that HA instance, used Google backup to restore. Whatever I did, it worked. Still, kudos for the video and being so thorough. I'm new at Proxmox.😂

[@ResinChemTech]

Glad you got it working! Despite the initial difficulty, I think you'll be happy with HA on Proxmox.

[@TheUnofficialMaker]

great guide, installed and running on Beelink, Only problem having is Node Red won't start. Any ideas?

[@ResinChemTech]

Unfortunately, I'm not a NodeRed user... I write all my automations the old manual YAML way! I'm assuming you are using the NodeRed add-on for Home Assistant? You might just assure that all parts of Home Assistant and the NodeRed add-on are up-to-date with the latest versions. I think the latest update of NodeRed included an update that also required a minimum core version of Home Assistant. But again, I don't use NodeRed and don't have it installed. Sorry I can't be more help. Maybe someone else here, or maybe on Discord or the HA forums, have an idea or can help out. I sure haven't heard of any issues with NodeRed running under Home Assistant on Proxmox.

[@teamgaesgarminbyorbea6002]

Thanks a lot, I will follow your instructions. One question, I have HAOS in a MiniPC and I want to migrate it to another MiniPC with Proxmox keeping ther MAA Address as you explained. But in case to use the old minipc installing windows 11, the mac address willnot be the same that the HAOS , correct?, and I could use both minipc without any problem?

[@ResinChemTech]

You will need to change the MAC address on the original PC since it will be in use by the new Proxmox/HA instance. This can be done in the network settings of new Windows machine, but you have to obviously boot up the machine first. This will initially result in duplicate MAC addresses on your network... which is a no-no. So what you will likely have to do is temporarily shut down Home Assistant on the Proxmox machine, boot up the new Windows machine and change its MAC address so that it is not the same as the Home Assistant instance, then you can restart Home Assistant. However you opt to do it, you just have to assure you don't have two devices with the same MAC address trying to join your network at the same time. Alternatively, you could use a new MAC address on the Proxmox/HA install and use your router to move the current IP address from the old MAC to the new MAC. This will result in just a slightly longer downtime for Home Assistant up front, but will save you that time when you try to bring up the new Windows install on the old machine as you won't have to shut down Home Assistant and change the MAC address on the Windows machine. Either method will work as long as each machine has a unique MAC address. I hope that explanation makes sense and helps you out a bit with your planning.

[@teamgaesgarminbyorbea6002]

@@ResinChemTech thanks a lot

[@OrlandoPaco]

Thank you.

[@ResinChemTech]

You are most welcome! Thanks for the comment.

[@liveartrainbow]

Thank you for sharing

[@ResinChemTech]

You are welcome! While this video won't be for everyone... and maybe not for most today... I think that people that have used Home Assistant for a while generally start looking at options to move off the Raspberry Pi. This is just one of those options for when that time comes.

[@mizar65cs]

I'm actuall yrunning HA on a Homeassistant Yellow with integrated Zigbee transceiver. How can I migrate it to ProxMox? Can I add a ZigBee dongle to the proxmox setup? I think I have to pair again all ZigBee sensors ...

[@ResinChemTech]

The process to moving to Proxmox is the same, regardless of what platform you are coming from (Raspberry Pi, HA Yellow, etc.). The only thing that the old platform is used for is to create a backup of your current system. Yes, you can attach a Zigbee dongle to the Proxmox install using the USB passthrough option within the VM. If you change Zigbee coordinators then yes, I believe you have to 'unpair' your Zigbee devices from the old coordinator first. However, if you are using ZHA, there is a 'migrate radio' option that will move all your devices from one coordinator to another. I'm not sure if Zigbee2MQTT has a similar feature or not.

[@davidhill8151]

Great video! You mentioned in a different comment that your zigbee hub is standalone. This is very interesting! Do you have a video on how you set this up? Like probably most people, I have a zigbee usb plugged into my current HA box, using zigbee2mqtt. I would love to see what you're doing with zigbee - how you have it set up, how you interface with your HA install, how you handle backups, what advantages it holds over the "classic" setup, etc. Thanks! That said, it may be "too late" for me. I have about 40 zigbee devices, and one thing that seems to be lacking from the community (maybe because it's not easy or possible), are videos on how to move zigbee installations, how to back them up, how to restore, etc. Even swapping zigbee dongles (to upgrade to a more capable zigbee stick) seems super complicated, without having to re-join all of your devices, rebuild your network and update all your related automations.

[@ResinChemTech]

I'm using s Sonoff ZBBridge flashed with Tasmota. I set it up nearly 3 years ago, so I'd have to review my notes to even remember how I did it. I followed a video by Travis over at DigiblurDIY when I initially set it up. At the time, I did it so I could locate the hub centrally on the main floor of the house instead of tethering it to the HA machine, which is on the top floor in a corner room. I'm using ZHA instead of Z2MQTT and have added a few routers (mostly Zigbee plugs) over time to extend the mesh, but I currently only have around 20 devices. I remember seeing something a while back about a new feature in HA that allowed you to move all your devices to a new ZHA hub (I think it involved cloning the radio address on the new hub... much like I cloned the MAC address here) that used a backup/restore process for your devices (and therefore the name of all the entities are maintained, I believe, so automations don't have to be updated). I don't know if there is a similar option for Z2MQTT or not, but I do have an option in my ZHA integration to "migrate radio". I don't know if any of that is really helpful to you, but in my case I basically just setup the hub and forgot about it. "It just works..."! I've not had any issues with joining devices to it, so I've done very little with the hub itself since the initial install outside of applying a couple of Tasmota upgrades.

[@davidhill8151]

@@ResinChemTech appreciate the reply. I'll take a look at that solution. Yeah, I've seen some recent video titles with something to do with ZHA improvements in backuo/restoring or migrating. I feel like there's work to be done on the z2mqtt side. Thanks again.

[@TheDiabeticWay]

I seem to be having issues with HA booting up, if there any thing you can surgest please? so far your video as been very helpful until now where mine is nott booting up Home assistant the same as your. I have tried to restart it and it still does the same. Thanks Hope you can help me out further

[@ResinChemTech]

I'm happy to try to help, but I might need a little more information. Does HA fail to boot up right after the Proxmox installation scripts or after you restore your backup from your current HA install? When you look at the summary information for the HA VM in Proxmox, does the VM appear to be running and does it show the IP address for the new install? Be sure this is the same IP address you are entering in a browser. There are numerous things that could be happening here, but without more information, it is hard for me to provide any meaningful recommendations.

[@TheDiabeticWay]

@@ResinChemTech thank you! Im just doing it all again from a fresh installation so will let you know when Its done the updates! I think it was running ok right away and then messed up after trying to add the Home Assistance but I cannot be fully 100% on that. And why to help me learn and understand Im installing it again! love you videos too and find them very well put together! If there is any where I can go for it easier to help please just let me know! It locked up on loading up Home Assistant for the first time the section where you first get the address to go to your Home Assistant in the URL on your video! On my second attempt I'm getting a error apt-get update after a reboot! Video Time: 16:33

[@TheDiabeticWay]

boots up ok first time!@@ResinChemTech

[@TheDiabeticWay]

? @ResinChemTech should i disable "pve-enterprise" repository? my version is 8.1.3 so its a little different than yours!

[@ResinChemTech]

Yes... the enterprise repository is for the "paid" version of Proxmox. Unless you want to pay a subscription, you want the free 'community' version, so you should disable the enterprise repository. The scripts should handle that and also update your install to pull from the community repository for updates.

[@davidfarrell1062]

If the old home assistant in on a physical box and you use the MAC on the new VM version will that cause an issue if you use the old hardware for something else and the hardware connects with the same MAC even though it has a different IP without changing it in the windows or linux OS.

[@ResinChemTech]

Correct... and I mention that. If you clone the MAC address and opt to repurpose the old device (like a Pi), you then need to modify the original device's MAC address. Alternatively, you could update the MAC address on the VM and assign the new MAC address to the original IP when you decide to reuse the old hardware.... or as I cover, simply reassign the IP address to the new MAC address of the VM when you first create it. My method was primarily meant for minimal downtime of Home Assistant for the migration (and to make it easy to migrate back if something goes wrong). But there are other ways, such as moving the reserved/static IP address in the router that also works... with just a bit longer downtime and a little more work if you need to migrate back.

[@davidfarrell1062]

@@ResinChemTech Perfect. So I only need to migrate the MAC if I want the router to give the same IP. If I do a manual assignment in the router for the new HA mac and the old HA IP that would do aswell ?

[@ResinChemTech]

Exactly right! This is only necessary if you need or want to keep the same IP address for the migrated Home Assistant. In my case, that was critical since HA is also my MQTT broker and I have a ton of devices that would have to be updated if the IP address changed. But you can use the technique of reassigning the IP address to the new VM MAC address as well. Cloning the MAC or reassigning the IP address to a new MAC in your router results in the same net effect... Home Assistant keeps the same IP address. I just used the cloned MAC method because it means Home Assistant is only down for a few seconds and it can be a little easier for beginners or those that really aren't comfortable messing around with their router settings (or have an ISP router where they may be locked out). As long as you don't have two devices with either the same MAC address or static IP address on the network at the same, you can use any technique you like to move or reassign the IP address from the old install to the new.

[@ferrymeijlink7441]

If i clone the macaddress from my PI, can i use that pi in the future for something else? would be a waste of a PI if i never can use that because the macaddress is allreaydy in use on my LAN

[@ResinChemTech]

You can either change the MAC address on the PI (just Google how to do it) or you can change the MAC address on the Proxmox/HA VM and reassign the original Home Assistant IP address to the new MAC address. Either way works... but you are correct that you cannot have two identical MAC addresses. So if you want to later use the Pi, you can change the MAC address on the Pi or on the Home Assistant VM. I recommend initially leaving them the same so that you have a fallback position in case something doesn't go quite right with the new Proxmox instance.... that way you can just power down one and power the other one back up... no router changes required and the IP address remains the same. But you can use a new MAC address for Proxmox and reassign the IP address at the router if you don't want to duplicate the Pi MAC address.

[@ferrymeijlink7441]

I use static ip addresses for fixed devices, and dhcp for mobile devices. can i just powerdown the PI and change the proxmox HA instance to thePI addres then? there is no way to release a mac adres from a static ipadres as i can remember in my router

[@ResinChemTech]

Well, it would be unusual for a router to allow fixed addresses to be assigned but then not released.. But irregardless, if you clone the MAC address from the Pi to the Proxmox VM (as I showed in the video), then yes... you would power down the Pi and start up the Home Assistant VM and it should get the same IP address from the router if the MAC address is the same. Then if you want to re-use the Pi for something else once you assure everything is working with the new Home Assistant, you can just give the Pi a new MAC address... and it will get a new IP address from your router when it joins the network. Also note that the Pi had TWO MAC addresses... one for wireless and one for wired. If you were using wired before, you can use wireless (or vice versa) without changing any MAC addresses.

[@ferrymeijlink7441]

yes that make sense, got te cloning done it works thank you for your clear explaination and also thank you for the mqtt tutorial.

[@ashmakes21]

Hi, i am getting this problem. When i put the script (any script) it just goes to the next line in the shell rather than executing it, do you have any idea why this is happening. thank you.

[@ResinChemTech]

Not sure what the issue could be. It almost sounds like you are in an editor of some sort instead of at the command line. You should see a prompt similar to 'root@proxmox: ~#'. The name may be different depending on what you named your instance, but it should be a command prompt. If you aren't seeing this, then you are either not logged in or aren't at the command line. You could try a different terminal program/type and see if that makes any difference. Hope that helps... but if nothing is happening after pasting a command/script and hitting the key, you aren't at the actual command line for the Proxmox server.

[@ashmakes21]

@@ResinChemTech hi thanks for answering, it definitely says bash and root and everything but I do get asked to log in when I refresh and I do?

[@ResinChemTech]

Bash? How are you getting to the shell? Are you selecting the Proxmox node in the left column, then in the middle section, selecting Shell (which is under Search, Summary and Notes)? If you are prompted to login, then you should log in as root and use the password you specified when you initially set up Proxmox. Once logged in from the screen, you should be able to run scripts.

[@ashmakes21]

@@ResinChemTech yep that's exactly right

[@Arcadier]

I did exactly that what you did, and uploaded my backup from my 1st homeassistant. it say it can take up to 45 minutes to import that, and then it got stuck. after hours and hours nothing happens anymore. No idea what I'm doing wrong. I really need help to get my HA moved to my proxmox. who can help me out ?

[@ResinChemTech]

Silly question, but did you try refreshing the browser? The restore screen where you load the backup really doesn't give any indication that something is happening (or that it finished). Try refreshing the browser or opening another tab and going to the IP address of your new HA installation (with :8123 of course).

[@Tsura88]

Not sure if this is mentioned but I have currently a USB Zonoff Zigbee Dongle that integrates all my zigbee devices.....The question is can I bind this USB device to the Proxmox Virtual machine? Something that gets auto bound every time the virtual machine is restarted. currently Every time I reboot I have to manually attach USB dongle via software (VMware Workstation Pro).

[@ResinChemTech]

I do briefly mention it, but since my Zigbee hub is standalone and not attached to the Proxmox machine, I don't cover the process. But from what I've read and seen from others, you can simply pass-through the USB port via Proxmox to the Home Assistant VM and it works fine... including after restarts of both Home Assistant and the VM/server. Here's a good guide on how to pass the Zigbee hub through to Home Assistant on Proxmox: smarthomescene.com/guides/how-to-passthrough-usb-devices-to-home-assistant-in-proxmox/ but again, I haven't tested it.

[@tomashermansson6898]

The restore dosnt finish... I am running HA 10.1 and moving from rpi4 to proxmox. isnt restore supported anymore on new platform?

[@ResinChemTech]

Did you full upgrade Home Assistant (core, OS, etc.) and then take a backup before attempting to migrate? When you install Home Assistant on Proxmox (assuming you used the script), it is installing the most recent version. If your back up was from an older version, there could possibly be restore issues. But I restored Home Assistant probably at least a dozen times in the process of making this video and never had any issues. So... yes, it should still be supported.

[@idomaghic]

Fwiw, at least on HAOS 11, there's now a "spinning circle" to indicate that the restore process is "running", however, I'm using quotes here as it turned out this indicator kept going long after the restore had actually finished (which I figured out by checking the HAOS logs in the terminal via proxmox). I was additionally confused since it seemed like the server was memory constrained at 8GB and therefore thought it was taking a longer time. In the end, the restore process finished in about 15min for a backup file of about 600MB on an intel i5 4670k with no other load on the server (while I waited 45mins with the spinning indicator).

[@victorlowe]

the command in your guide to run the script to create the Home Assistant VM is broken edit- after looking at your github, I removed "-v5" from the file name and it worked just fine after that

[@ResinChemTech]

Yeah... this video is over 1 year old now and unfortunately links and other sources change from time to time and it is nearly impossible for me to keep track and update all the links that I provide in my numerous videos and guides. I believe I have updatedthe particular guide to the latest link for installing the Home Assistant VM, but you should always check the source for the latest versions. In this case, all the latest supporting scripts can be found at: tteck.github.io/Proxmox/

[@Dunner1988x]

I upgraded my current HAOS to 10.5 and created a backup file. Can confirm 10.5 is the version I selected in proxmox as well. When using the backup file to restore my new HAOS (created as per the instructions in the video), it appears to be taking a long time. Still going 10 hours later. Is this normal? I dedicated 2 cores and 8gb of ram to the home assistant VM and its been using 90% of the memory and 4% CPU this whole time. The backup file is 616MB.

[@ResinChemTech]

The restore should not be taking that long in a normal situation. I think mine took somewhere between 5-10 minutes. While you say that your OS is the same version (10.5), is the core version the same between the back up and new install (e.g. 2023.9.x)? My backup files are generally around 100MB, but I run a recorder purge and DB repack once a week. It appears that something has hung on your restore process as even with a much bigger backup file size, it still shouldn't take more than a few minutes to restore from backup. Again, I'd make sure that the core versions are the same and try the restore process again. Let me know if you are still having problems after than.

[@Dunner1988x]

@@ResinChemTech thanks for the response! I did ensure that both the core and the OS version were updated to current before creating the backup file. I would assume the bash code that was used in your tutorial would provide the same current core version? Is there a way to double check on the new install what core version I have? The prompts only indicated the OS version (10.5). I currently have core version 2023.9.1 included in the backup file. For additional context, I am trying to migrate over to proxmox from virtualbox. Proxmox is installed on a 256gb NVMe ssd within a lenovo thinkcentre m710q. 16gb ram, i5-7500T 2.7ghz. connected via ethernet. The Disk IO is showing activity but only like ~15 kb/min. I appreciate your help!

[@ResinChemTech]

Silly question, but have you tried refreshing/relaunching the browser? If that doesn't make any difference, at this point you might try restarting the VM. If it hasn't restored the backup by now, odds are it is not going to... so a restart isn't going to hurt. If the restart once again displays the onboarding, you can try restoring the backup again. Worst case, you may have to blow away the VM and create it again. I'm not sure what might have gone wrong... as I probably did the install/restore 6 or 7 times in the process of recording the video and never had an issue. The script that creates the Home Assistant VM should be installing the latest production release of core (currently 2023.9.1 I think). You machine and what you've allocated to the VM should be more than enough for Home Assistant, so that shouldn't be an issue. As well as the fact that you are coming from Virtual Box... a full HA backup should be the same regardless of the source system... as far as I know.

[@Dunner1988x]

@@ResinChemTech thanks again for your responses - I appreciate you taking the time to try and help me out! I did try closing my browser, restarting both my computer with the web browser proxmox open, as well as the proxmox server computer, but no luck. I also deleted and reinstalled HA 3-4 times on proxmox and re-downloaded a new backup file, but that didn't appear to do the trick either. I'm going to try posting on the HA forums to see if anyone might have an answer there. In the meantime, I'm just going to let the restore process run again, as it does appear to be inching along based on the Disk IO activity in proxmox. I'm not super skilled when it comes to this stuff, but I assume the Disk IO (write) summary tells me how much of the backup file I've downloaded? If so, I'm at about 150-200MB written, with ~400MB to go, which translate to about 7 more days to restore with the current avg write speed of 40kb/min, lol. Who knows though, maybe the 40KB/min is temporary, based on the HA addons that are being unpacked at this point in time.

[@ResinChemTech]

Sorry you are having the issues. I honestly don't know what could be causing the restore to take so long. But please let me know if you get it resolved or if you locate the cause. I'd be curious to know what exactly is going on.

[@AceBoy2099]

I just tried this with 8.0.4 (proxmox) and 11.something (HAOS) and it kept rejecting the tar file saing it wasnt a tar file.

[@Demios101]

You manage to solve this issue yet?

[@AceBoy2099]

@@Demios101 nope, built from new. I don't have much on my HA anyway.

[@christianfilouler]

perfect, thx

[@ResinChemTech]

You are welcome. I'm glad you found it helpful. Home Assistant on Proxmox has been rock solid for me and the best platform I've run it on.

[@Linux-s8l]

the link to bashscript in youre discription does not match