Top man!! You have no idea how long I waited for another version of tutorial to come to CZcams. With all the other tutorials, I kept getting secure boot error no matter what I did. Thank you so much.
Thank you! I was struggling to install using outdated videos that were using older versions that used different commands, just like you noted! Whew, what I relief! I was able to import my VM from another Hypervisor using your video :)
I tried Home Assistant a year or two ago. It DEFINITELY does more than I need for my small handful of smart bulbs that I have. But there are some channels out there like Smart Home Solver and a few others that have incredible detailed walkthroughs on how to get in the weeds and make HA do a ton of cool stuff. Excellent tutorial. You can also spin up Home Assistant in a Docker container, which is how I was running it at the time.
@@testbox3201 able to install all the addons that were available. I had Node Red, Mosquitto MQQT, and the Home Assistant config backup addons installed. As well as the integrations for all my devices.
Excellent and thorough walk through. You covered important points like Discard and SSD emulation, other vids did not cover. Mine was lvm-thin. A Proxmox forum user suggested I leave it thin, I was going to blow it out and load zfs. Said my machine might not handle. Why, I dont know. HA opened up, I used IP:8123, I already have a Nabu Casa Green device running. Thank you! This may also work for Ubuntu and Mint install. I'll find out.😅 I'll follow up with unknown high memory usage of 82%. Did reboot vm. No change. Hmmm. Updated to HA Beta, mem better at 49%.
Hi great tutorial I had been struggling to get the home assistant software to be transferred. This method worked first time. Thank for taking the time create such a great channel
I love this. This topic was next on my list to play with on a MicroServer Gen8 after I try to get Intel Quick Sync to work through Proxmox > TrueNAS > Jelyfin to allow hardware transcode without installing an extra GPU.
That topics is on my list too, except without TrueNAS involved. Proxmox -> Jellyfin (in LXC) w/ storage mounted from Proxmox's ZFS pool should be easier.
Looking at it more in depth, it seems like the microserver gen8 doesn't enable the iGPU at all, so it wouldn't be usable in either OS. Mine doesn't show the igpu and there's no render node in /dev/dri for it either.
I'm using an E3-1265LV2 which shows Quick Sync in Intel's info sheet. When I looked a couple weeks ago, I didn't see many low wattage FCLGA1155 CPUs that have it. I don't remember seeing or hearing which CPU you said was in yours. You probably said it or showed it, I just don't remember.
I have the same CPU, which does show Quick Sync in Intel's sheet, but using quick sync requires the iGPU to be enabled by the BIOS. The Microserver disables it so the only graphic device is the iLO graphics, so the iGPU doesn't show up as a PCIe device, the intel graphics driver isn't loaded in the kernel, and quick sync can't be used.
Thanks for this great tutorial. It really helped me get up and running. I'm trying to pass through a Dell Optiplex PCI device which is a network and bluetooth adapter, I have added the raw device in Proxmox on the home assistant VM, device is called 0000:02:00.0, but this device is not appearing in the Hardware section of my Home Assistant front end. I have tried turning off memory balooning on the VM as I understand this is not compatible with pass through. Could you give me any pointers of what to try next please?
Great tutorial, I did this whole procedure already last month. It would have me saved so much time if I have waited for your video :D But unfortunately I want to migrate the VM regularly between the nodes in my cluster (different reasons), but the USB-device is of course not available on the other node. So my idea was to use some USB-over-IP stuff... do you think you can make some follow-up on this topic? The hardest thing would be to get this tool into the already packaged homeassistant-vm, because they don´t have direct root access there. maybe i have to go back with homeassistant to a docker-compose setup for my goals?
I personally run ZWaveJS UI and Zigbee2MQTT on a Raspberry Pi so the VM has no hardware dependencies (so it can migrate) and I can put the radios in a better location in the house. I'm also considering adding a second Z2M network since I have a lot of Aqara devices which are stupid and don't work through relay nodes. Overall my Zwave network has way less headache. I'll probably make a video on installing Zigbee / Zwave on an x86 thin client at some point. I have them all working nicely through systemd services and everything. If your Proxmox hosts aren't identical, you'll need to not use the cpu=host option and pick the CPU architecture that's the least common denominator. If you're mixing Intel and AMD then live migration won't really work reliably.
@@apalrdsadventures Interesting approach, I will definitely take a look on this Zigbee2MQTT thing... The cpu type was not the problem with my installation, but more with the whole importing disk and not knowing in how to attach the disk and making it bootable. If you know the procedure already then its easy, but even the lack of information to double-click on the disk to mount it via scsi was not easy to find out. Indeed my both nodes have AMD and Intel CPUs. The live migration with running VMs works flawlessly, since I´m not setting the cpu options I guess :)
You could try cpu=kvm64 + AES (advanced options lets you add some specific flags) and that would probably get you at least some performance back if you use HTTPS for anything. I found I couldn't get a good common denominator CPU with my setup, but part of the problem is my cluster runs AMD mobile chips which don't have the same instruction sets as their Opteron counterparts (sorta like mixing Atom based CPUs, they don't follow the same instruction set compatibility as their Core / Xeon counterparts). Also a surprising amount of the performance improvement aside from AES is memcpy, gnu libc will use any of the vector extensions up through AVX512 just to do mem copy faster. I started making a video on this topic, but it might end up being a super clickbait short (9000% performance improvement in oddly specific workloads with one easy trick*), but the performance improvement of generally data-centric tasks is real.
Thanks for your tutorials. I got a question to homeassistant in a HA environment. Do you know any solution, to give cluster access to one USB device, like z-wave stick?
Basically not directly, since the VM could move to any node at any time. My solution is to run Z-wave and Zigbee on separate small nodes which are dedicated to only running ZwaveJS and Zigbee2MQTT respectively. They can be a Raspberry Pi or small thin client. If the node goes down, HA itself is still running, and just that particular radio is down. This also means the small nodes can have tiny USB power banks as a UPS and be located in the ideal part of the house for signal strength. Some Zigbee sticks also support serial over Ethernet, and they would work fine this way as well.
@@apalrdsadventures thank you for your quick answer, I'll think about your solution. May be I can run two instances of homeassistant, one z-wave and one zigbee, they exchange everything via MQTT. Please give us more high quality tutorials.
That's really not necessary. Zigbee and Z-wave aren't part of HA itself, they are both addons, so you can run the controller software separately. For Zigbee, Zigbee2MQTT is already going over MQTT to Home Assistant (if it runs locally or remotely), and Z-wave is going to use websockets, so again it can run remotely.
I tried HA several times and I cannot get used to it, I find it a clunky piece of software. Instead I only run node-red, which can do exactly the same and then some.
I've used Node-Red for around 4 years now and switched entirely the other way, since HA deals with state storage a lot better and also has a nice GUI to build interface screens with
@@apalrdsadventures I agree that HA is an actual state machine, unlike NR. The workflow in NR clicks more in my brain. The workflow in HA doesnt work for me; click here, click there. I build GUI's myself. Perhaps things have changed by now, maybe I should retry it (only for the state, I would still keep the logic in NR I think).
I end up using template sensors or helpers ('input_boolean', etc) a lot in the process to aggregate / make decisions on things, and the automations just have to apply changes to devices.
I still use Node-RED and Home Assistant and think they both have their place. But the user experience of HA is getting better and better month by month. Nabu Casa has certainly recognised that the UX was a barrier to entry for many people. The need for a PI, dedicated PC or setting up a VM is still a barrier for the non-techy.
You are in the middle and started explaining things that beginners do not know, and you did not explain how to add LG TVs to this application. would you PLEASE help us in how to add LG webOS TV on home assistant from beging and also if lg tv dosen't has LG connect app what we have to? do we have to do any edite in configuration.ymal ? thanks
Thanks for a great tutorial. I really appreciate that you take the time and explain what the different options are and why you choose them!
Glad it was helpful!
Top man!! You have no idea how long I waited for another version of tutorial to come to CZcams. With all the other tutorials, I kept getting secure boot error no matter what I did. Thank you so much.
Thank you! I was struggling to install using outdated videos that were using older versions that used different commands, just like you noted! Whew, what I relief! I was able to import my VM from another Hypervisor using your video :)
Thank you for your clear an concise tutorials
Glad you like it!
I tried Home Assistant a year or two ago. It DEFINITELY does more than I need for my small handful of smart bulbs that I have. But there are some channels out there like Smart Home Solver and a few others that have incredible detailed walkthroughs on how to get in the weeds and make HA do a ton of cool stuff. Excellent tutorial. You can also spin up Home Assistant in a Docker container, which is how I was running it at the time.
In docker then without add-ons I guess
@@testbox3201 able to install all the addons that were available. I had Node Red, Mosquitto MQQT, and the Home Assistant config backup addons installed. As well as the integrations for all my devices.
Thank you for posting this. And, I appreciate the level of detail.
Tried a few of these nstall videos for HA and none worked.... until this one. easy to follow, easy to understand. many thanks!
Excellent and thorough walk through. You covered important points like Discard and SSD emulation, other vids did not cover. Mine was lvm-thin. A Proxmox forum user suggested I leave it thin, I was going to blow it out and load zfs. Said my machine might not handle. Why, I dont know. HA opened up, I used IP:8123, I already have a Nabu Casa Green device running. Thank you! This may also work for Ubuntu and Mint install. I'll find out.😅 I'll follow up with unknown high memory usage of 82%. Did reboot vm. No change. Hmmm. Updated to HA Beta, mem better at 49%.
Hi great tutorial I had been struggling to get the home assistant software to be transferred. This method worked first time. Thank for taking the time create such a great channel
Great video - loving all your content!
Glad you enjoy it!
Your tutorial helped me a lot with my first VM, thanks su much
These are good videos sir
Thank you!
Thanks for making this great guide! Just as an update in Proxmox 8 its qm diskimport *no space* between the two words to import this disk!
I love this. This topic was next on my list to play with on a MicroServer Gen8 after I try to get Intel Quick Sync to work through Proxmox > TrueNAS > Jelyfin to allow hardware transcode without installing an extra GPU.
That topics is on my list too, except without TrueNAS involved. Proxmox -> Jellyfin (in LXC) w/ storage mounted from Proxmox's ZFS pool should be easier.
I'm actually considering dropping Proxmox completely for the Microserver Gen8 and just using TrueNAS SCALE as the host.
Looking at it more in depth, it seems like the microserver gen8 doesn't enable the iGPU at all, so it wouldn't be usable in either OS. Mine doesn't show the igpu and there's no render node in /dev/dri for it either.
I'm using an E3-1265LV2 which shows Quick Sync in Intel's info sheet. When I looked a couple weeks ago, I didn't see many low wattage FCLGA1155 CPUs that have it. I don't remember seeing or hearing which CPU you said was in yours. You probably said it or showed it, I just don't remember.
I have the same CPU, which does show Quick Sync in Intel's sheet, but using quick sync requires the iGPU to be enabled by the BIOS. The Microserver disables it so the only graphic device is the iLO graphics, so the iGPU doesn't show up as a PCIe device, the intel graphics driver isn't loaded in the kernel, and quick sync can't be used.
Hi. Great video. Can you explain how to install the "Home Assistant Supervised version" in a Proxmox VM?
I'm curious why HA needs it's own VM? Couldnt' it be run under a container?
Great Video!. Did you know how to integrated max thermostat in home assistant over NanoCUL ?
Thanks for this great tutorial. It really helped me get up and running. I'm trying to pass through a Dell Optiplex PCI device which is a network and bluetooth adapter, I have added the raw device in Proxmox on the home assistant VM, device is called 0000:02:00.0, but this device is not appearing in the Hardware section of my Home Assistant front end. I have tried turning off memory balooning on the VM as I understand this is not compatible with pass through. Could you give me any pointers of what to try next please?
A lot of network and bluetooth adapters actually use PCI for Wifi and USB for Bluetooth, so that's probably why it isn't showing up
Thanks so much. This solved my issue. It was an unnamed device which could be found under usb devices. All sorted. 😊
i cannot get an IP address when HA starts up. Tried everything i can think of.
Great tutorial, I did this whole procedure already last month. It would have me saved so much time if I have waited for your video :D But unfortunately I want to migrate the VM regularly between the nodes in my cluster (different reasons), but the USB-device is of course not available on the other node. So my idea was to use some USB-over-IP stuff... do you think you can make some follow-up on this topic? The hardest thing would be to get this tool into the already packaged homeassistant-vm, because they don´t have direct root access there. maybe i have to go back with homeassistant to a docker-compose setup for my goals?
I personally run ZWaveJS UI and Zigbee2MQTT on a Raspberry Pi so the VM has no hardware dependencies (so it can migrate) and I can put the radios in a better location in the house. I'm also considering adding a second Z2M network since I have a lot of Aqara devices which are stupid and don't work through relay nodes. Overall my Zwave network has way less headache.
I'll probably make a video on installing Zigbee / Zwave on an x86 thin client at some point. I have them all working nicely through systemd services and everything.
If your Proxmox hosts aren't identical, you'll need to not use the cpu=host option and pick the CPU architecture that's the least common denominator. If you're mixing Intel and AMD then live migration won't really work reliably.
@@apalrdsadventures Interesting approach, I will definitely take a look on this Zigbee2MQTT thing...
The cpu type was not the problem with my installation, but more with the whole importing disk and not knowing in how to attach the disk and making it bootable. If you know the procedure already then its easy, but even the lack of information to double-click on the disk to mount it via scsi was not easy to find out.
Indeed my both nodes have AMD and Intel CPUs. The live migration with running VMs works flawlessly, since I´m not setting the cpu options I guess :)
You could try cpu=kvm64 + AES (advanced options lets you add some specific flags) and that would probably get you at least some performance back if you use HTTPS for anything. I found I couldn't get a good common denominator CPU with my setup, but part of the problem is my cluster runs AMD mobile chips which don't have the same instruction sets as their Opteron counterparts (sorta like mixing Atom based CPUs, they don't follow the same instruction set compatibility as their Core / Xeon counterparts).
Also a surprising amount of the performance improvement aside from AES is memcpy, gnu libc will use any of the vector extensions up through AVX512 just to do mem copy faster.
I started making a video on this topic, but it might end up being a super clickbait short (9000% performance improvement in oddly specific workloads with one easy trick*), but the performance improvement of generally data-centric tasks is real.
Hello Ihave problem with dongle sonoff zigbee not reading on proxmox error 71
Nice tutorial but why do you type the whole name of the file instead of just pressing Tab key to autocomplete it?
A decade of working with cmd.exe and batch scripts (cringes)
Thanks for your tutorials. I got a question to homeassistant in a HA environment. Do you know any solution, to give cluster access to one USB device, like z-wave stick?
Basically not directly, since the VM could move to any node at any time.
My solution is to run Z-wave and Zigbee on separate small nodes which are dedicated to only running ZwaveJS and Zigbee2MQTT respectively. They can be a Raspberry Pi or small thin client. If the node goes down, HA itself is still running, and just that particular radio is down. This also means the small nodes can have tiny USB power banks as a UPS and be located in the ideal part of the house for signal strength.
Some Zigbee sticks also support serial over Ethernet, and they would work fine this way as well.
@@apalrdsadventures thank you for your quick answer, I'll think about your solution. May be I can run two instances of homeassistant, one z-wave and one zigbee, they exchange everything via MQTT. Please give us more high quality tutorials.
That's really not necessary. Zigbee and Z-wave aren't part of HA itself, they are both addons, so you can run the controller software separately. For Zigbee, Zigbee2MQTT is already going over MQTT to Home Assistant (if it runs locally or remotely), and Z-wave is going to use websockets, so again it can run remotely.
I tried HA several times and I cannot get used to it, I find it a clunky piece of software. Instead I only run node-red, which can do exactly the same and then some.
I've used Node-Red for around 4 years now and switched entirely the other way, since HA deals with state storage a lot better and also has a nice GUI to build interface screens with
@@apalrdsadventures I agree that HA is an actual state machine, unlike NR. The workflow in NR clicks more in my brain. The workflow in HA doesnt work for me; click here, click there. I build GUI's myself. Perhaps things have changed by now, maybe I should retry it (only for the state, I would still keep the logic in NR I think).
I end up using template sensors or helpers ('input_boolean', etc) a lot in the process to aggregate / make decisions on things, and the automations just have to apply changes to devices.
I still use Node-RED and Home Assistant and think they both have their place. But the user experience of HA is getting better and better month by month. Nabu Casa has certainly recognised that the UX was a barrier to entry for many people. The need for a PI, dedicated PC or setting up a VM is still a barrier for the non-techy.
You are in the middle and started explaining things that beginners do not know, and you did not explain how to add LG TVs to this application. would you PLEASE help us in how to add LG webOS TV on home assistant from beging and also if lg tv dosen't has LG connect app what we have to? do we have to do any edite in configuration.ymal ? thanks
I have no idea why you think I'd own an LG webOS TV based on this video
@@apalrdsadventuresSaw this a few weeks ago but I keep comingback because this is somehow too funny to me. Great vid by the way!
Zigbee2MQTT ftw..
I use Z2M myself, but on a separate Pi elsewhere in the house. The basement isn't a great place for radios.