April 8, 20251 yr 1 hour ago, Espressomatic said: 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. That's why the docker hub exists. You click this --> HA Add-ons are literally docker containers installed inside HAOS. There is nothing you can't install yourself from unraid or dockerhub if an unraid template doesn't already exist. It's as seamless as putting your dockers all to the same docker network so they can commuincate by their docker names: To connect to my z-wave service you just replace the word "localhost" with "zwavejs" or whatever you named your zwave docker. 1 hour ago, Espressomatic said: 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? Your assumption is incorrect, I know why people are using this "HA In a box". It's because they didn't know better and that a much more simplified method exists. There isn't anything you can't do with the docker install that HAOS does. You see, if you scroll through this entire post/thread, people dealing with VM issues simply do not exist for a docker install. 1 hour ago, Espressomatic said: 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). The sole fact that if for whatever reason HAOS goes down, bugs out, or breaks because of an update or a misconfiguration, not having your entire smart home ecosystem rendered inoperable is not a compelling enough argument why running your "HA Add-ons" outside of HAOS is not a "single universal and concrete" advantage to you... Then I don't what more to tell you. You simply cannot do this with HAOS and Supervisor. Sure HAOS can update in the background but if it goes wrong, the entire thing is toast. Been there, done that, got the T-shirt. Another massive benefit is that you have more granular control over your add-ons, they're not dependent on a specific HAOS version to function. I ran HAOS for a little while before switching to docker install. The fact that either an HAOS update or a add-on update caused friction drove me insane. Now I don't have those kinds of issues. I can update either one all day long and they still work, both in tandem and independently. You do you. Edited April 8, 20251 yr by MowMdown Spelling
April 15, 20251 yr Hi, I'm trying to install HaCasa and am stumped. Following their guide here: https://damianeickhoff.github.io/HaCasa/getting-started/download And for the life of me I cannot find "the root of your HA configuration (this is where your configuration.yaml lives" as they say in the guide. I feel like this should be really obvious, what am I missing? thanks
April 16, 20251 yr Don't even consider installing something like HaCasa if you're not already familiar with the ins and outs of Home Assistant and where all the files live in HAOS. Wait for it to someday be available as a HACS installation (plus manual configuration) - there's no technical limitation preventing that from happening right now (or last year). Edited April 16, 20251 yr by Espressomatic
May 7, 20251 yr Hello, At first glance, it appears that HA is running. I'm now trying to redirect my HAinAbox to the outside world via NPM. I can get to the site that far. However, the internal redirection to the VM host—that is, the IP x.x.x.6—cannot be opened. So how is this supposed to work?
May 14, 20251 yr Hi everyone, I'm encountering an issue when trying to install the PredBat add-on in Home Assistant. The installation seems to fail with a "No such file or directory" error. Here's the relevant part of the log: 2025-05-14 05:44:27.826 INFO (SyncWorker_4) [supervisor.docker.manager] Export image 6adb4f0d/amd64-addon-predbat done 2025-05-14 05:44:48.673 ERROR (MainThread) [supervisor.addons.addon] Can't write tarfile <securetar._InnerSecureTarFile object at 0x7fb97f552cf0>: Error adding /data/addons/data/6adb4f0d_predbat to tarfile: [Errno 2] No such file or directory: '/data/addons/data/6adb4f0d_predbat' (FileNotFoundError) 2025-05-14 05:44:48.673 ERROR (MainThread) [supervisor.backups.backup] Can't create backup for 6adb4f0d_predbat 2025-05-14 05:44:48.674 WARNING (MainThread) [supervisor.backups.backup] Can't save Add-on 6adb4f0d_predbat: Can't create backup for 6adb4f0d_predbat 2025-05-14 05:44:48.676 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on cc2581ab_predai 2025-05-14 05:45:44.251 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token 2025-05-14 05:49:55.211 INFO (SyncWorker_5) [supervisor.docker.manager] Export image cc2581ab/amd64-addon-predai to /data/tmp/tmpjvc0xr2l/image.tar 2025-05-14 05:53:56.510 ERROR (SyncWorker_5) [supervisor.docker.manager] Can't write tar file /data/tmp/tmpjvc0xr2l/image.tar: [Errno 28] No space left on device 2025-05-14 05:53:56.735 ERROR (MainThread) [supervisor.backups.backup] Can't create backup for cc2581ab_predai 2025-05-14 05:53:56.735 WARNING (MainThread) [supervisor.backups.backup] Can't save Add-on cc2581ab_predai: Can't create backup for cc2581ab_predai 2025-05-14 05:53:56.735 INFO (MainThread) [supervisor.backups.manager] Backup 0ebec207 starting stage folders 2025-05-14 05:53:56.737 INFO (SyncWorker_2) [supervisor.backups.backup] Backing up folder ssl 2025-05-14 05:53:56.819 INFO (SyncWorker_2) [supervisor.backups.backup] Backup folder ssl done 2025-05-14 05:53:56.820 INFO (MainThread) [supervisor.backups.manager] Backup 0ebec207 starting stage finishing_file 2025-05-14 05:53:56.858 INFO (MainThread) [supervisor.backups.manager] Creating partial backup with slug 0ebec207 completed 2025-05-14 06:05:39.542 INFO (MainThread) [supervisor.host.info] Updating local host information 2025-05-14 06:05:39.989 INFO (MainThread) [supervisor.host.services] Updating service information 2025-05-14 06:05:39.992 INFO (MainThread) [supervisor.host.network] Updating local network information 2025-05-14 06:05:40.061 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information 2025-05-14 06:05:40.247 INFO (MainThread) [supervisor.host.manager] Host information reload completed 2025-05-14 06:15:50.030 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token 2025-05-14 06:21:57.971 ERROR (SyncWorker_1) [supervisor.utils.json] Can't write /data/addons/data/6adb4f0d_predbat/options.json: [Errno 2] No such file or directory: '/data/addons/data/6adb4f0d_predbat/tmpwjbzf7vs' 2025-05-14 06:21:57.971 ERROR (MainThread) [supervisor.addons.addon] Add-on 6adb4f0d_predbat can't write options [supervisor.addons.addon] Add-on 6adb4f0d_predbat can't write options This looks like it's happening during the installation process, as it's trying to write the options.json file for PredBat. Has anyone else experienced this when installing an add-on? Any ideas on what could be preventing the creation of these directories or the writing of this file? Thanks for any help!
May 16, 20251 yr On 5/14/2025 at 6:37 AM, Johan71 said: Hi everyone, I'm encountering an issue when trying to install the PredBat add-on in Home Assistant. The installation seems to fail with a "No such file or directory" error. Here's the relevant part of the log: 2025-05-14 05:44:27.826 INFO (SyncWorker_4) [supervisor.docker.manager] Export image 6adb4f0d/amd64-addon-predbat done 2025-05-14 05:44:48.673 ERROR (MainThread) [supervisor.addons.addon] Can't write tarfile <securetar._InnerSecureTarFile object at 0x7fb97f552cf0>: Error adding /data/addons/data/6adb4f0d_predbat to tarfile: [Errno 2] No such file or directory: '/data/addons/data/6adb4f0d_predbat' (FileNotFoundError) 2025-05-14 05:44:48.673 ERROR (MainThread) [supervisor.backups.backup] Can't create backup for 6adb4f0d_predbat 2025-05-14 05:44:48.674 WARNING (MainThread) [supervisor.backups.backup] Can't save Add-on 6adb4f0d_predbat: Can't create backup for 6adb4f0d_predbat 2025-05-14 05:44:48.676 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on cc2581ab_predai 2025-05-14 05:45:44.251 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token 2025-05-14 05:49:55.211 INFO (SyncWorker_5) [supervisor.docker.manager] Export image cc2581ab/amd64-addon-predai to /data/tmp/tmpjvc0xr2l/image.tar 2025-05-14 05:53:56.510 ERROR (SyncWorker_5) [supervisor.docker.manager] Can't write tar file /data/tmp/tmpjvc0xr2l/image.tar: [Errno 28] No space left on device 2025-05-14 05:53:56.735 ERROR (MainThread) [supervisor.backups.backup] Can't create backup for cc2581ab_predai 2025-05-14 05:53:56.735 WARNING (MainThread) [supervisor.backups.backup] Can't save Add-on cc2581ab_predai: Can't create backup for cc2581ab_predai 2025-05-14 05:53:56.735 INFO (MainThread) [supervisor.backups.manager] Backup 0ebec207 starting stage folders 2025-05-14 05:53:56.737 INFO (SyncWorker_2) [supervisor.backups.backup] Backing up folder ssl 2025-05-14 05:53:56.819 INFO (SyncWorker_2) [supervisor.backups.backup] Backup folder ssl done 2025-05-14 05:53:56.820 INFO (MainThread) [supervisor.backups.manager] Backup 0ebec207 starting stage finishing_file 2025-05-14 05:53:56.858 INFO (MainThread) [supervisor.backups.manager] Creating partial backup with slug 0ebec207 completed 2025-05-14 06:05:39.542 INFO (MainThread) [supervisor.host.info] Updating local host information 2025-05-14 06:05:39.989 INFO (MainThread) [supervisor.host.services] Updating service information 2025-05-14 06:05:39.992 INFO (MainThread) [supervisor.host.network] Updating local network information 2025-05-14 06:05:40.061 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information 2025-05-14 06:05:40.247 INFO (MainThread) [supervisor.host.manager] Host information reload completed 2025-05-14 06:15:50.030 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token 2025-05-14 06:21:57.971 ERROR (SyncWorker_1) [supervisor.utils.json] Can't write /data/addons/data/6adb4f0d_predbat/options.json: [Errno 2] No such file or directory: '/data/addons/data/6adb4f0d_predbat/tmpwjbzf7vs' 2025-05-14 06:21:57.971 ERROR (MainThread) [supervisor.addons.addon] Add-on 6adb4f0d_predbat can't write options [supervisor.addons.addon] Add-on 6adb4f0d_predbat can't write options This looks like it's happening during the installation process, as it's trying to write the options.json file for PredBat. Has anyone else experienced this when installing an add-on? Any ideas on what could be preventing the creation of these directories or the writing of this file? Thanks for any help! No one?
May 18, 20251 yr On 5/16/2025 at 11:07 AM, Johan71 said: No one? IMO, add-on and integration issues need searching in the official Home Assistant community forum, where most HA discussion happens. I've never heard of this add-on, but installation issues are usually add-on specific and not HA-specific. Likely a change in a recent HA update that removed some deprecated code and the add-on hasn't been updated. One of a number of threads about this add-on and installation errors. This one started in 2024. https://community.home-assistant.io/t/predbat-add-on-error/770835
May 30, 20251 yr 15 hours ago, Uncommon said:How can i increase the memory in the VM without breaking it?Stop VM, edit, change memory allocation, apply, start VM.
July 6, 2025Jul 6 Whenever I reboot the unraid server itself, I have to reconfigure the USB devices for my home assistant VM:After a reboot, these are all unchecked. Not an issue when only rebooting the VM.Is there anyway to prevent this setting from being cleared?
July 12, 2025Jul 12 After you have created your VM & setup everything is the docker still required or can this be removed?
July 14, 2025Jul 14 Edit: I fixed it with the following help: https://community.home-assistant.io/t/help-os-16-killed-my-home-assistant-yellow/909365/13If you have access to the ha cli (ha>) try os info to check the slots and then boot from the other slot with ha os boot otherBest regards,TobiasHi together,I hope you can help.I have updated via the iOS App my Home Assistant from Operating Version 15 to 16.Now the VM Log shows always the following and the HA instance is not reachable anymore.2025-07-14 08:04:09.705+0000: Domain id=8 is tainted: high-privileges2025-07-14 08:04:20.246+0000: Domain id=8 is tainted: custom-ga-commandThe Domain ID counts up, when restarting the VM and DockerTroubleshooting so far:Unraid is updated to v7.1.4The Docker is up to dateI tried already to change the Machine for the VM from Q35-9.1 to Q35-9.2I disabled the virtual GPU and set it to NoneI removed the Passthrough of the Zigbee DongleRebooted Unraid, VM and the Docker multiple timesI have the feeling it is because of the HA Operating Version. Because with 15 everything was running.A downgrade from the CLI of HA is not possible because I get the Info that Supervisor is not connected to the internet. But the VM has the Docker Network as IP Address and the Docker has the correct IP of my HA Instance.Has someone else the same issue or can help me what that error means? If I should provide some files or any additional information, let me know.Thank you advance for your help.Tobias Edited July 14, 2025Jul 14 by t0bit0bsen Found the solution on the HA Community Page and wanted to share this information with the Unraid Community.
July 25, 2025Jul 25 Hey there, I've run into the following issue when trying to set up the container. Log states: Version check passed. Continuing...Host path for '/domains' is /mnt/user/domainsHighest Q35 machine type available is pc-q35-9.2The default VM network type is bond0Icon already there skipping.....VM 'Home Assistant' is already defined. Skipping VM creation steps...current status of VM 'Home Assistant': shut offVM 'Home Assistant' is not running.RESTART is set to 'Yes'. Attempting to start the VM...Attempting to start VM 'Home Assistant' (Attempt 1/5)...Failed to start VM 'Home Assistant'. Retrying in 60 seconds...Attempting to start VM 'Home Assistant' (Attempt 2/5)...error: Failed to start domain Home Assistanterror: Unable to add bridge bond0 port vnet8: Operation not supportedFailed to start VM 'Home Assistant'. Retrying in 60 seconds...Attempting to start VM 'Home Assistant' (Attempt 3/5)...error: Failed to start domain Home Assistanterror: Unable to add bridge bond0 port vnet9: Operation not supportedFailed to start VM 'Home Assistant'. Retrying in 60 seconds...Attempting to start VM 'Home Assistant' (Attempt 4/5)...error: Failed to start domain Home Assistanterror: Unable to add bridge bond0 port vnet10: Operation not supportedFailed to start VM 'Home Assistant'. Retrying in 60 seconds...Attempting to start VM 'Home Assistant' (Attempt 5/5)...error: Failed to start domain Home Assistanterror: Unable to add bridge bond0 port vnet11: Operation not supportedAny ideas?
July 26, 2025Jul 26 On 4/8/2025 at 9:45 PM, Espressomatic said: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 have't notice this thread, so reading through.I start HA in Raspberry then direct migrate to VM for 1 (or 2 yrs). But after trying docker then never return back ( since Sep 2023 ), it use much less resources and restart almost on the fly.The main problem are you can't migrate from VM to docker, so you need start in fresh. Next is its worst backup functionality ( should overcome in current version ) ..... but backup docker appdata actually much simple then that. ( My HA appdata ~164MB )Below are current backup functionality , I just simple trying ,but never use. Edited July 26, 2025Jul 26 by Vr2Io
October 3, 2025Oct 3 What is the best practice for letting all your IoT devices to connect to the VM?My UnRaid server is on my "normal" network, but all of the devices I want HA to talk to are on the IoT VLAN.Should I give the VM a IP address on the IoT VLAN? (I tried and i get the "Requires guest agent installed" error on the IP address column under the VM's.... For some reason the Docker shows the assigned IoT VLAN IP address. I just can't get the IP attached to the VM.OR do I punch a hole in between the vlans, so the UnRraid VM can talk to the IoT network....Seems like a bad idea.Also, how do I add edit the file structure within the VM? I am trying to install an integration, but those instructions want me to upload a folder to a directory. I am kinda lost on how to make this happen within the VM.Thanks for the help. Edited October 4, 2025Oct 4 by TheWoodser
October 18, 2025Oct 18 Hi. Just installed this and it created the VM fine. BUT there was an error in the log when it did.Running latest version of Unraid 7Warning: exec(): Unable to fork [TIMESTAMP='1760812599' EVENT='HomeAssistantinabox' SUBJECT='Home Assistant' DESCRIPTION='VM setup successfully completed. The VM is now ready to be run.' IMPORTANCE='normal' CONTENT='' LINK='' bash /boot/config/plugins/dynamix/notifications/agents/Pushover.sh] in /usr/local/emhttp/webGui/scripts/notify on line 228Here is the log:version check passed. Continuing...Host path for '/domains' is /mnt/user/domainsHighest Q35 machine type available is pc-q35-9.2The default VM network type is br0Icon 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/16.2/haos_ova-16.2.qcow2.xzdownloading the Home Assistant vdisk from the official sourceextracting the vdisk to /config/vdisk1.qcow2.xz (removing the .xz).../config/vdisk1.qcow2.xz: 324.6 MiB / 861.6 MiB = 0.377, 25 MiB/s, 0:34Moving 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/9f056e44-615b-43b3-bae4-966d37c83336_VARS-pure-efi.fd', fmt=raw size=65536All required files are present. Attempting to define the VM...Domain Home Assistant defined from /config/tmp.xmlWarning: exec(): Unable to fork [TIMESTAMP='1760812599' EVENT='HomeAssistantinabox' SUBJECT='Home Assistant' DESCRIPTION='VM setup successfully completed. The VM is now ready to be run.' IMPORTANCE='normal' CONTENT='' LINK='' bash /boot/config/plugins/dynamix/notifications/agents/Pushover.sh] in /usr/local/emhttp/webGui/scripts/notify on line 228current status of VM 'Home Assistant': shut offVM 'Home Assistant' is not running.RESTART is set to 'Yes'. Attempting to start the VM...Attempting to start VM 'Home Assistant' (Attempt 1/5)...Domain Home Assistant startedVM 'Home Assistant' started successfully.current status of VM 'Home Assistant': runningVM 'Home Assistant' is running.Checking for the IP address of the running VM...Guest agent is not responding. Waiting for 5 seconds before retrying... (1/9)Guest agent is not responding. Waiting for 5 seconds before retrying... (2/9)Guest agent is not responding. Waiting for 5 seconds before retrying... (3/9)Guest agent is not responding. Waiting for 5 seconds before retrying... (4/9)Guest agent is connected.The IPv4 address of the VM 'Home Assistant' is: 192.168.2.120Reloading Nginx with the new configuration...* Reloading nginx configuration nginx...done.Waiting for 5 minutes before checking again to ensure VM is still running... Edited October 18, 2025Oct 18 by manilx
December 1, 2025Dec 1 On 7/5/2025 at 6:21 PM, VulpesDormiens said:Whenever I reboot the unraid server itself, I have to reconfigure the USB devices for my home assistant VM:After a reboot, these are all unchecked. Not an issue when only rebooting the VM.Is there anyway to prevent this setting from being cleared?@VulpesDormiens Did you ever find a reliable solution to this? I've tried everything I can think of to get it to automatically connect and it just won't.If anyone else has suggestions, I'm all ears. This is the device (I don't usually check Optional, must have double clicked or whatever a moment ago):This is my trying and failing to connect it in docker settings:And this is the device info:It really seems like it should work, but no, every reboot requires manually reselecting the device.
December 23, 2025Dec 23 On 12/1/2025 at 4:26 PM, DrPeril said:@VulpesDormiens Did you ever find a reliable solution to this? I've tried everything I can think of to get it to automatically connect and it just won't.If anyone else has suggestions, I'm all ears. This is the device (I don't usually check Optional, must have double clicked or whatever a moment ago):This is my trying and failing to connect it in docker settings:And this is the device info:It really seems like it should work, but no, every reboot requires manually reselecting the device.On 12/1/2025 at 4:26 PM, DrPeril said:@VulpesDormiens Did you ever find a reliable solution to this? I've tried everything I can think of to get it to automatically connect and it just won't.If anyone else has suggestions, I'm all ears. This is the device (I don't usually check Optional, must have double clicked or whatever a moment ago):This is my trying and failing to connect it in docker settings:And this is the device info:It really seems like it should work, but no, every reboot requires manually reselecting the device.@DrPeril , unfortunately no. I've just been dealing with the annoyance and just hoping I don't have to reset the server too often. I also feel like it should just work. Perhaps we are the only two that have ran into this.
December 23, 2025Dec 23 5 hours ago, VulpesDormiens said:@DrPeril , unfortunately no. I've just been dealing with the annoyance and just hoping I don't have to reset the server too often. I also feel like it should just work. Perhaps we are the only two that have ran into this.You are not the only two, I just read the thread also hoping to get this solved. Will try the USB manager plugin to see what that does.
December 23, 2025Dec 23 22 minutes ago, liquidate said:You are not the only two, I just read the thread also hoping to get this solved. Will try the USB manager plugin to see what that does.Fwiw, the USB Manager seems to work. The VM settings page still shows my USB devices unselected, but I instructed the USB manager to attach to HA on VM start. When I reboot and start the array, the USB device is passed through correctly. Thank you @Espressomatic!
December 31, 2025Dec 31 Have installed this and have some things working but it seems very basic. I've been trying to install HACS but been going round in circles . Can I install it on this setup, if so how?
January 20Jan 20 EDIT - 1/21/26: Did a backup and yolo'd updating through the Home Assistant GUI. So far so good! I am wanting to update Home Assistant Operating System from 16.3 to 17.0 as it looks like many people are reporting a smooth update with no issues. Curious if anyone has suggestions on how to do this properly when running HomeAssistant_inabox? I run most of my apps in docker but this VM/docker app always seemed like magic and I wasn't sure how it works. It works so I never questioned it. I'd image to update the operating system will require some extra steps? Edited January 21Jan 21 by o0atomos0o
January 30Jan 30 I am trying to manually edit some HA core files in the storage folder, but I'm having trouble accessing them due to this VM in a box setup. I've tried using the file editor add-on, but I can't use it while the application is stopped, and the changes just revert if I edit the files while HA is running. The files don't seem accessible through Krusader. Any tips? My goal is to delete an orphaned device, and this is my last resort.
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.