Chris wrote:
Hi dominic16 — you can do this today with a per-app override. Tom's team tested it on their bench before writing this. On your server, create one file: sudo nano /opt/sparkbox/state/overrides/homeassistant.yml Paste exactly this (the spacing matters), save, then run sudo sparkbox up: yaml services: homeassistant: networkmode: host networks: !reset {} ports: !reset [] Home Assistant restarts on the host network, so Chromecast / HomeKit / Sonos discovery works, and it stays at the same address (port 8123). It survives updates. To undo, delete the file and run sudo sparkbox up again. One heads-up: if you reach it through a custom domain, point that proxy entry at your server's IP:8123 instead of the container name. Tom has a one-click switch for this on the list too.
Chris wrote:
Update — the proper switch shipped in 1.6.641, so you no longer need the override file. In the Classic dashboard: Home Assistant → settings → turn on host networking; or from a terminal on the server: sudo sparkbox set-env HOMEASSISTANTHOSTNETWORK=1 && sudo sparkbox up homeassistant. If you already set the override up, leave it or remove it — the switch does the same thing. Guide: https://tomsparkbox.com/guides/home-assistant-host-network. Shout if discovery still does not find your devices after that.