The original 2024 forum post is mainly a pointer to a BigBear tutorial, so it should not be treated as a complete frozen installation recipe. The good current news is that BigBearCasaOS still maintains a Home Assistant package using Home Assistant's official container image. The important architectural decision is not just “can it run?” but which Home Assistant installation type you want.
Home Assistant Container runs well on CasaOS/Docker and gives you the normal Home Assistant Core UI/integrations. Current upstream documentation is explicit, however: Container does not include Home Assistant Supervisor or the apps/add-ons ecosystem available in Home Assistant OS. If you need the full HAOS/Supervisor experience, run Home Assistant OS on supported hardware or in a VM instead.
BigBearCasaOS Still Maintains Home Assistant
The current BigBearCasaOS catalog lists ghcr.io/home-assistant/home-assistant and continues syncing app packages across its supported platforms.
Use the current BigBearCasaOS catalog.
Persist the /config Directory
Home Assistant's configuration, database and integration settings live under /config in the container model. Map that folder to persistent CasaOS storage and back it up before major upgrades.
Recreating the container should not erase the Home Assistant instance when /config remains intact.
Home Assistant Commonly Uses Host Networking
Current Home Assistant Container guidance uses --network=host, which helps local discovery protocols and avoids manually publishing every service port.
Host networking also means the container shares the host's network namespace, so review port conflicts and firewall exposure carefully.
Bluetooth Needs Additional Host Access
Current upstream instructions say a D-Bus mount is optional but needed for the Bluetooth integration in the documented Docker setup. USB Zigbee/Z-Wave radios may also require explicit device mapping.
Do not assume a USB radio will appear in Home Assistant merely because CasaOS can see the USB device.
Container Does Not Have Supervisor Apps/Add-ons
This is the biggest difference from Home Assistant OS. Current Home Assistant documentation says the Container installation has no access to apps/add-ons and that HAOS is the recommended installation type for most users who want the complete managed ecosystem.
Use the current Home Assistant Container documentation.
Use Home Assistant OS in a VM for the Full Managed Experience
If the CasaOS host has enough CPU/RAM and virtualization support, HAOS in a VM gives Home Assistant its own OS, Supervisor and add-ons while CasaOS remains the host for other services.
Plan USB-radio passthrough separately if the VM needs Zigbee/Z-Wave hardware.
Keep Home Assistant Remote Access Intentional
Home Assistant controls cameras, locks, sensors and automation state. Do not publish port 8123 directly to the Internet without a deliberate remote-access/authentication design. Prefer the official Home Assistant cloud option, VPN/overlay, or a hardened authenticated reverse proxy.
Back Up Home Assistant Before Updates
For Container installs, protect the persistent /config directory and any external database used by the instance. Test a restore before relying on the NAS as the only copy of your home-automation state.
Home Assistant on CasaOS FAQ
Is BigBearCasaOS still packaging Home Assistant?
Yes. The current BigBear catalog still lists the official Home Assistant container image.
Does Home Assistant Container include Supervisor add-ons?
No. Current Home Assistant documentation explicitly says Container installations do not have apps/add-ons.
What if I want the full HAOS experience?
Use Home Assistant OS on supported hardware or in a VM, with passthrough configured for any required USB radios.
