Document homeassistant migration and network blocker
Added HOMEASSISTANT.md with migration steps and configuration details. Home Assistant config copied to R5C at /srv/homeassistant. **BLOCKED**: podman installation fails on R5C due to extreme network latency (1000+ ms Starlink connection) and DNS resolution failures. Package downloads fail consistently. Migration can proceed once R5C network is stable enough for apt-get to complete. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -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
|
||||
Reference in New Issue
Block a user