December 20, 20241 yr 3 hours ago, BastiKA84 said: the IPv4 address the VM gets: 192.168.122.154 - normally my Range ist 19.168.178.xxx You won't be able to access an IP on a different subnet - as you've noticed. It's possible with some changes to router settings on something like pfSense, but in general, that's the reason you can't access Home Assistant. You need to make sure it's on an interface that gets IP addresses from your normal DHCP (your router). So a network bridged to a real LAN port on the machine like I mentioned, or a host port like you mentioned above.
December 20, 20241 yr Thanks for this ED. I have set it all up and works perfectly except…..if I manually set a static ip in HA it does not update in the config so if I click on webui from the docker list it goes to the incorrect IP. I would also like to expand the vdisk to make sure I don’t run out of room. Will doing this cause any issues? So yeah 2 things. Static IP Ecpand vdisk
December 28, 20241 yr I have the problem that I cannot open my HA via the WebUI. In addition, the HA app protocol is giving me incorrect IP addresses. In bridge mode, the VM should be accessible at 192.168.122.115 and in host mode at 172.30.232.1. However, my IP address for Unraid is 192.168.212.5 and my home LAN runs in the address range 192.168.212.xxx Ich habe das Problem das ich mein HA nicht über die WebUI öffnen kann. Dazu kommt das mir das Protokoll der HA App auch falsche IP Adressen ausgibt. Im Bridge Mode soll die VM unter 192.168.122.115 und im Host Mode unter 172.30.232.1 erreichbar sein. Meine IP Adresse von Unraid ist aber 192.168.212.5 bzw. mein Home LAN läuft im Adressbereich 192.168.212.xxx
December 28, 20241 yr 9 hours ago, Curiosity said: the VM should be accessible at 192.168.122.115 ..., my IP address for Unraid is 192.168.212.5 and my home LAN runs in the address range 192.168.212.xxx How are you going to access anything on 192.168.122.* from 192.168.212.* ? In bridge mode, you should get a 192.168.212.* address (if your mask is /24)
December 28, 20241 yr I don't have access to the network 192.168.122.xx. I only see the IP address in the app's protocol with which IP the vm is recognized by the app
December 29, 20241 yr What IP is displayed in your VM row for HA on the Unraid VM page? My LAN uses the range 10.8.8.0/23 (which includes 10.8.8.0 through to 10.8.9.254), and an IP is reserved by my DHCP server as 10.8.8.230 by matching the VM MAC Address If your VM is set up with a bridged interface (like my example below) then you must receive an IP on your 192.168.212.* range. This will be done by the DHCP server on your router. You will need to create a static assignment in your DHCP for the MAC address listed in the VM config if you want to set it to your own IP. You can also set this in Home Assistant (see more below) In Home Assistant, Settings -> System -> Network - you can manually specify IP/Mask etc. or set to Automatic (default) Edited December 29, 20241 yr by Espressomatic
January 3, 20251 yr How do we update Home Assistant itself ? Just use it's update mechanism within the VM (in Home Assistant) ? Edited January 3, 20251 yr by RacerX10
January 8, 20251 yr Using the default settings with priv. Keep getting an extraction failure. Tried restarting and redownloading the image.
January 20, 20251 yr Getting the following error when starting after installation. Error Message HomeAssistantinabox: 20-01-2025 14:13 Home Assistant VM setup failed. There was an error during the VM definition process. Log Warning: mail(): Could not execute mail delivery program '/usr/sbin/sendmail -t -i' in /usr/local/emhttp/webGui/scripts/notify on line 87 Version check passed. Continuing... Host path for '/domains' is /mnt/user/domains Highest Q35 machine type available is pc-q35-9.1 The default VM network type is br0 Icon already there skipping..... Home Assistant directories are already present...continuing. There is already a vdisk image here...skipping. As this is an OVMF VM, I need to create an NVRAM file. Creating now .... Formatting '/etc/libvirt/qemu/nvram/1ce857a5-af20-49e0-935f-372f81767d68_VARS-pure-efi.fd', fmt=raw size=65536 All required files are present. Attempting to define the VM... Failed to define the VM. There was an error during the VM definition process. Warning: mail(): Could not execute mail delivery program '/usr/sbin/sendmail -t -i' in /usr/local/emhttp/webGui/scripts/notify on line 87 Any thoughts sorry if I've been thick.
February 2, 20251 yr @SpaceInvaderOne thank you very much for this great app. Worked for me out of the box. 👍🏼 I've got two questions/sugestions: What is the best way to work with the VM Backup Plugin? Is there a way to extend the docker to monitor further VMs? Thanks in advance!
February 11, 20251 yr No matter what I do the WebUI will not load. I followed the instructions in the video verbatim. The IP it gives me is 192.168.122.11 My unRAID IP is 192.168.1.88
February 12, 20251 yr On 1/8/2025 at 11:24 AM, karleksbarn said: Using the default settings with priv. Keep getting an extraction failure. Tried restarting and redownloading the image. I'm getting this same error message. What needs to be done to resolve this?
February 15, 20251 yr Hi everyone, I got this installed and working but I'm having trouble passing through my Sonoff Zigbee radio and my Z-wave radio. Only "TTYS0" device is showing but I get an error "Failed to connect" when trying to start it. I'm sure maybe I'm doing something wrong like not passing it through or something...
March 18, 20251 yr Now running Unraid 7.0.0 and Home Assistant will not install. Getting this on the log: It appears others have experienced this, haven't seen a solution. Any ideas?
March 21, 20251 yr IMO, this is all much more complicated than it needs to be (when it doesn't work). You can easily install HA in a few short steps like described here: https://smarthome.yoavmor.com/home-assistant/setting-up-home-assistant-on-unraid/
March 28, 20251 yr tried to install but got a VM setup failed. There was an error during the VM definition process. and wouldn't work
March 29, 20251 yr On 10/27/2024 at 5:28 AM, Jorgo said: I can't seem to get this running, Error: text error warn system array login % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 341M 100 341M 0 0 31.3M 0 0:00:10 0:00:10 --:--:-- 28.2M /config/vdisk1.qcow2.xz: 341.4 MiB / 866.9 MiB = 0.394, 35 MiB/s, 0:24 error: Failed to define domain from /config/tmp.xml error: internal error: Failed to start QEMU binary /usr/local/sbin/qemu for probing: Start/autostart is disabled in VM settings. sleep: invalid time interval '' Try 'sleep --help' for more information. Version check passed. Continuing... Host path for '/domains' is /mnt/user/domains Highest Q35 machine type available is pc-q35-9.1 The default VM network type is vhost0 Icon already there skipping..... mkdir: created directory '/domains/Home Assistant' I have created the Home Assistant directories. Found .qcow2.xz file: https://github.com/home-assistant/operating-system/releases/download/13.2/haos_ova-13.2.qcow2.xz downloading the Home Assistant vdisk from the official source extracting the vdisk to /config/vdisk1.qcow2.xz (removing the .xz)... Moving the extracted vdisk to /domains/Home Assistant/vdisk1.img... vdisk downloaded and moved to /domains/Home Assistant/vdisk1.img. As this is an OVMF VM, I need to create an NVRAM file. Creating now .... Formatting '/etc/libvirt/qemu/nvram/0bde0555-8a11-4213-8f16-c10b571d3c36_VARS-pure-efi.fd', fmt=raw size=65536 All required files are present. Attempting to define the VM... Failed to define the VM. There was an error during the VM definition process. Any ideas? On 12/5/2024 at 1:59 AM, pb21 said: i have troubles installing the app. everytime single time this error occurs: On 1/8/2025 at 2:24 PM, karleksbarn said: Using the default settings with priv. Keep getting an extraction failure. Tried restarting and redownloading the image. On 1/20/2025 at 10:20 AM, Steve Hyland said: Getting the following error when starting after installation. Error Message HomeAssistantinabox: 20-01-2025 14:13 Home Assistant VM setup failed. There was an error during the VM definition process. Log Warning: mail(): Could not execute mail delivery program '/usr/sbin/sendmail -t -i' in /usr/local/emhttp/webGui/scripts/notify on line 87 Version check passed. Continuing... Host path for '/domains' is /mnt/user/domains Highest Q35 machine type available is pc-q35-9.1 The default VM network type is br0 Icon already there skipping..... Home Assistant directories are already present...continuing. There is already a vdisk image here...skipping. As this is an OVMF VM, I need to create an NVRAM file. Creating now .... Formatting '/etc/libvirt/qemu/nvram/1ce857a5-af20-49e0-935f-372f81767d68_VARS-pure-efi.fd', fmt=raw size=65536 All required files are present. Attempting to define the VM... Failed to define the VM. There was an error during the VM definition process. Warning: mail(): Could not execute mail delivery program '/usr/sbin/sendmail -t -i' in /usr/local/emhttp/webGui/scripts/notify on line 87 Any thoughts sorry if I've been thick. On 2/12/2025 at 11:56 AM, APD189 said: I'm getting this same error message. What needs to be done to resolve this? On 3/18/2025 at 4:54 PM, JLKunka said: Now running Unraid 7.0.0 and Home Assistant will not install. Getting this on the log: It appears others have experienced this, haven't seen a solution. Any ideas? On 10/27/2024 at 4:31 PM, Jorgo said: I found the problem, I had set the generel VM settings to not autostart VM. After I changed that value, everything initiated itself correctly. Thanks for you work, @SpaceInvaderOne! I was just able to resolve the same issue all of yall are dealing with. Here were my steps which expand on the advice from @Jorgo: First head to VM Manager and set 'Diable Autostart' to Yes. Remember to hit apply. Stop the HomeAssistant_inabox docker container If you still have a HomeAssistant OS vm hanging, delete it and the vdisk if it asks Go back to the docker tab and remove the container and image if it asks Use a terminal like midnight commander or whatever you find easiest to delete the HomeAssistant_inabox appdata folder Then go to the unraid apps tab > click previous > select HomeAssistant_inabox > delete (which removes the template) shout out @SpaceInvaderOne who shared this part of the solution in the app repo's issues! I've chosen not to link there at this time so as to encourage the next few steps also be taken. Now feel free to reinstall the container I also suggest editing the HomeAssistant_inabox docker container's VM Images Location to a sub-directory of '/mnt/user/domains/' such as '/mnt/user/domains/HAOS/' (no spaces in folder name) so that way the application install doesn't attach itself to any previously downloaded .qcow2.xz files. HomeAssistant_inabox has a tendancy to look far and wide for an image to use (see reference below) Head back over to VM Manager > Diable Autostart/Start option for VMs > set that to 'No' > remember to hit apply restart the HomeAssistant_inabox docker and it should rebuild the VM. Be patient while the webui needs to get started after re-initializing. Good Luck! Really hoping I didn't miss any steps I took lol Edited March 30, 20251 yr by trevor4n
March 31, 20251 yr On 3/29/2025 at 6:58 PM, trevor4n said: I was just able to resolve the same issue all of yall are dealing with. Here were my steps which expand on the advice from @Jorgo: First head to VM Manager and set 'Diable Autostart' to Yes. Remember to hit apply. Stop the HomeAssistant_inabox docker container If you still have a HomeAssistant OS vm hanging, delete it and the vdisk if it asks Go back to the docker tab and remove the container and image if it asks Use a terminal like midnight commander or whatever you find easiest to delete the HomeAssistant_inabox appdata folder Then go to the unraid apps tab > click previous > select HomeAssistant_inabox > delete (which removes the template) shout out @SpaceInvaderOne who shared this part of the solution in the app repo's issues! I've chosen not to link there at this time so as to encourage the next few steps also be taken. Now feel free to reinstall the container I also suggest editing the HomeAssistant_inabox docker container's VM Images Location to a sub-directory of '/mnt/user/domains/' such as '/mnt/user/domains/HAOS/' (no spaces in folder name) so that way the application install doesn't attach itself to any previously downloaded .qcow2.xz files. HomeAssistant_inabox has a tendancy to look far and wide for an image to use (see reference below) Head back over to VM Manager > Diable Autostart/Start option for VMs > set that to 'No' > remember to hit apply restart the HomeAssistant_inabox docker and it should rebuild the VM. Be patient while the webui needs to get started after re-initializing. Good Luck! Really hoping I didn't miss any steps I took lol Attempted this fix but still not getting webUI, I could be doing something wrong. I do not see an Autostart option under VM manager. I am toggling it under VMs (though it seemed to be off by default). Honestly not sure how to make this work. If anyone is willing to help I am more than willing to compensate for your time.
April 7, 20251 yr Some additional questions: 1. How do I setup HA on unraid so that it communicates with my VLAN for IoT 2. Purchased a ZBT-1 usb stick, how do I get it installed by HA_inabox?
April 8, 20251 yr I get Ed does great work for the unraid community but what I don't understand is why not just use the HA docker container and not mess with VMs at all. Edited April 8, 20251 yr by MowMdown
April 8, 20251 yr 20 minutes ago, MowMdown said: why not just use the HA docker container and not mess with VMs at all. Running HA OS is much more useful than running HA in docker. Supervisor, ability to install add-ons, HACS, etc. In summary, HA in docker is a neutered solution that I don't recommend anyone ever use. I've long suggested they stop supporting it, honestly.
April 8, 20251 yr 41 minutes ago, Espressomatic said: Running HA OS is much more useful than running HA in docker. Supervisor, ability to install add-ons, HACS, etc. In summary, HA in docker is a neutered solution that I don't recommend anyone ever use. I've long suggested they stop supporting it, honestly. I think you're living in the past man. Every add-on to HA you need is just a docker container you can spin up right on unraid which will then be able to run independently in the event HA is non-responsive like when there's an Unraid update that breaks VMs like I see above. HACS is just a dockermod you add courtesy of LSIO, or you can just install it manually through the appdata. Oh and if you need to access any of the underlying config YAML files, fully accessbile via HA's appdata without having to mess with stuff inside a VM. Oh and backups, being able to take snapshots AND backups of HA is a godsend when you fudge something. Can't really do that with VMs as easily. Oh and no VM XML template BS to figure out. I guarantee you I can spin up all of these services below faster than you can install and get HA in a VM running. Passing through a USB device is stupid easy. Edited April 8, 20251 yr by MowMdown
April 8, 20251 yr 2 hours ago, MowMdown said: Every add-on to HA you need is just a docker container you can spin up right on unraid Container yes, with Unraid-specific templates available for everything, no - and certainly not with the the seamless zero configuration of rolling out many add-ons within HAOS. The folks having trouble in here setting up HA with this easy-to-use docker launchpad will be in a world of hurt trying to get support. HA on external docker engine on top of another distro is just a juggling act for zero gain. How fast you can spin up HA docker for the first time is irrelevant. Once it's up, it's up. Backups are integrated into HAOS and support external targets. VM backups are trivial with Unraid 7.x. I've never been wanting for more backup options, nor to roll my own. You can take/steal my HA physical system and restoring from a backup isn't much of a bother - temporarily onto any other server or even onto new hardware installed from scratch. If you want to advocate HA in a docker, that's fine somewhere else, everyone's entitled to run it how they wish. This isn't the thread for that. 3 hours ago, MowMdown said: but what I don't understand This exactly. You've admitted to not understanding, so given that fact, why do you think it's a good idea to make the suggestion in the first place? I've been with HA for about 8 years, and to this day have yet to see anyone, anywhere, offer a single universal and concrete suggestion as to why HA on a separate docker host is better than running HAOS (bare metal or VM). Plenty of negatives however, especially for anyone who might already have issues installing a pre-packaged VM image. Edited April 8, 20251 yr by Espressomatic
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.