diff --git a/HOMEASSISTANT.md b/HOMEASSISTANT.md
new file mode 100644
index 0000000..25d780c
--- /dev/null
+++ b/HOMEASSISTANT.md
@@ -0,0 +1,55 @@
+# Home Assistant + ESPHome on R5C
+
+## Status
+
+- ✅ Configuration copied: `/srv/homeassistant` on R5C (10.42.1.1)
+- ⏳ **BLOCKED**: podman installation failed due to R5C network issues
+  - Network latency: 1000+ ms (Starlink issue)
+  - DNS resolution failures preventing apt-get from downloading packages
+  - All podman dependencies (golang, netavark, crun, etc.) failed to download
+
+## Migration Steps (when network is stable)
+
+### 1. Install podman on R5C
+```bash
+ssh root@10.42.1.1
+sudo apt-get update
+sudo apt-get install -y podman
+```
+
+### 2. Start homeassistant container
+```bash
+podman run -d \
+  --name homeassistant \
+  --restart=always \
+  --privileged \
+  -v /srv/homeassistant:/config \
+  -v /run/dbus:/run/dbus:ro \
+  --network=host \
+  ghcr.io/home-assistant/home-assistant:stable
+```
+
+### 3. Access Home Assistant
+- URL: http://10.42.1.1:8123
+- Configuration: `/srv/homeassistant` (persistent across restarts)
+
+## Configuration
+
+Home Assistant config is at `/srv/homeassistant`:
+- `configuration.yaml` — Main config
+- `.storage/` — Automations, integrations, UI state
+- `custom_components/` — Custom integrations
+- Database: `home-assistant_v2.db`
+
+## ESPHome (Future)
+
+ESPHome setup deferred until network is more stable. When ready:
+1. Copy `/srv/esphome` from old vanrouter (4.8GB)
+2. Run ESPHome container on port 6052
+
+## Network Issue
+
+The R5C has extreme latency preventing reliable package installation:
+- Starlink connection appears unstable
+- Consider when deploying production services
+- May need to pre-download packages on local machine and transfer via USB