Hi everyone,
I wanted to share my challenges for anyone considering migrating their Supervised installation to the new haos-one Docker container, specifically if you are running on Linux (Ubuntu/Debian) and connected via Wi-Fi.
I spent the last few hours trying to get this working and hit a major roadblock that leaves you stuck between “crashing your network” or “breaking your devices.”
The Problem:
- Host Mode Crashes Network: The documentation recommends
network_mode: host. On my Linux machine, doing this caused the container to hijack my host’s network interfaces. It literally renamed my virtual interfaces toeth0, killing my SSH connection and taking the host offline. I had to restart to recover. - Bridge Mode Breaks Discovery: To stop the crashing, I switched to bridge mode. While Home Assistant starts and is accessible, discovery protocols fail. My Govee lights (Local API) and Matter/HomeKit devices stopped working because the container can’t send/receive the necessary broadcast packets through the Docker bridge.
- IPVLAN doesn’t work on Wi-Fi: Trying to give the container its own IP (IPVLAN) fails because Wi-Fi access points generally block multiple IPs on a single MAC address.
Summary:
If you are on Ethernet, you might be fine (or maybe Macvlan works for you). But if you are on Wi-Fi, be very careful. haos-one seems to try to manage the underlying network hardware in a way that conflicts with the host OS, and there is currently no easy workaround to get local device control (Govee/Matter) working without risking your host connection.
Just a heads-up before you start your migration!