Files
vanlink/HOMEASSISTANT.md
T
andreas 6d9c4f69cd Fix DNS resolver after disabling systemd-resolved
Root cause: /etc/resolv.conf was a broken symlink to systemd-resolved's
stub resolver, which doesn't exist after disabling the service.

Fixed by creating proper /etc/resolv.conf pointing to dnsmasq on 10.42.1.1
and upstream resolvers (1.1.1.1, 8.8.8.8).

This fix allows apt-get to work again and enables podman installation.

**Result: ✅ podman installed, homeassistant container starting**
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
2026-09-19 13:52:05 -04:00

65 lines
1.9 KiB
Markdown

# 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 Fix Applied
**Root Cause:** /etc/resolv.conf was a broken symlink to /run/systemd/resolve/stub-resolv.conf (which doesn't exist after disabling systemd-resolved)
**Fix Applied:**
```bash
sudo rm -f /etc/resolv.conf
sudo sh -c 'echo nameserver 10.42.1.1 > /etc/resolv.conf'
sudo sh -c 'echo nameserver 1.1.1.1 >> /etc/resolv.conf'
sudo sh -c 'echo nameserver 8.8.8.8 >> /etc/resolv.conf'
```
This restores DNS resolution, allowing apt-get and podman image pulls to work properly.
**Result:** ✅ podman now installs successfully, homeassistant container can pull image from ghcr.io