HomeAssistant_inabox_v3 spaceinvaderone/ha_inabox:latest https://hub.docker.com/repository/docker/spaceinvaderone/ha_inabox/general bridge bash false https://forums.unraid.net/topic/176028-support-homeassistant_inabox https://github.com/SpaceinvaderOne/Home_Assistant_inabox https://github.com/SpaceinvaderOne/Home_Assistant_inabox/blob/main/README.md HomeAssistant_inabox installs Home Assistant OS as a virtual machine on your Unraid server through a short setup wizard - it does not run Home Assistant itself inside this container. Open this container's WebUI, pick a Home Assistant OS release and a few settings, and it creates the VM, downloads and attaches the disk, and hands you back a normal Unraid VM. Once a Home Assistant VM exists - whether this wizard created it or you already had one running - this container's WebUI becomes a small status panel instead of the wizard: it shows the VM's address, whether Home Assistant has answered there, and a Start button if the VM is stopped. If you stop or remove this container, the Home Assistant VM keeps running; it is managed by Unraid's own VM tab like any other virtual machine, not by this container. Keeping a VM running - an automatic restart if it stops unexpectedly, plus a notification - is opt-in per VM from the status panel and off by default; nothing is ever turned on for you. If you already run Home Assistant in a VM on this server, the wizard finds it by reading the VM's own disk rather than guessing from its name, and the status panel lists it alongside anything this container installs - there is no separate "adopt" step to click through. The wizard can also pass a USB device on this server through to the Home Assistant VM, for a Zigbee, Z-Wave or similar radio, and calls out devices it recognises as likely candidates rather than presenting a bare, unlabelled list. This needs direct access to your VM manager (libvirt), your Domains share, Docker's own socket and a handful of Unraid system paths in order to build and manage the VM correctly - that is expected and required, not a mistake in this template. It has no login of its own, so keep it on a trusted LAN rather than exposing it to the internet. HomeAutomation: http://[IP]:[PORT:9123] https://raw.githubusercontent.com/SpaceinvaderOne/Docker-Templates-Unraid/master/spaceinvaderone/HomeAssistant_inabox_v3.xml https://raw.githubusercontent.com/SpaceinvaderOne/Docker-Templates-Unraid/master/spaceinvaderone/docker_icons/HomeAssistant.png homeassistant home assistant hass hassio haos supervised vm virtual machine zigbee zwave z-wave smarthome automation domotics Unraid's VM service must be enabled: Settings then VM Manager. The wizard checks this before it lets an install start and tells you if it is off, so nothing is lost if you forget - but it cannot create a VM without it. Hardware virtualisation (Intel VT-x or AMD-V) needs to be on in your BIOS. If you have ever run a VM on this server, it already is. No Home Assistant knowledge is needed. The wizard downloads Home Assistant OS itself, builds the VM and hands it to you set up. ### v3 A complete rewrite. Everything is now driven from the container's own web page instead of template variables. - A setup wizard replaces the old template variables. Pick a Home Assistant OS release, a name, network, CPU and memory, and it builds the VM while showing you real progress - the download with actual percentages, a checksum check against the official release, and the first boot milestones as they happen. - The page becomes a status panel afterwards, listing every Home Assistant VM on the server with its address and a button to open it. - Existing Home Assistant VMs are found by reading the VM's own disk rather than guessing from its name, so an install you already had is recognised even while it is switched off. - Keeping a VM running is now opt-in per VM rather than one global setting, and notifications go out through whatever you have already configured in Unraid. - USB passthrough for Zigbee, Z-Wave, Bluetooth and similar, using Home Assistant's own device data to tell you what a stick is. Your Unraid boot flash is never offered. - Follows Home Assistant if it changes the address it answers on once onboarding finishes, so the links to it keep working. - Watch settings survive a container restart. Coming from v2: install this alongside your existing container, check your VM appears, then delete the old one. Your Home Assistant VM is untouched either way - it belongs to Unraid's VM manager, not to this container. /mnt/user/appdata/HomeAssistant_inabox_v3 /mnt/user/domains /var/run/libvirt/libvirt-sock /var/run/docker.sock /usr/local/emhttp/plugins/dynamix.vm.manager/templates/images /boot/config/domain.cfg /usr/share/qemu /tmp/notifications /usr/local/emhttp /var/local/emhttp /boot/config/plugins/dynamix 9123 3