[ci skip] Update ha-sofia SSH to direct IP 192.168.1.8 and document limitations

This commit is contained in:
Viktor Barzin 2026-02-07 22:21:30 +00:00
parent 8cc4f022c3
commit fb2a830cb2
No known key found for this signature in database
GPG key ID: 0EB088298288D958
2 changed files with 20 additions and 18 deletions

View file

@ -402,7 +402,7 @@ jellyfin, jellyseerr, tdarr, affine
- **Default smart home**: Home Assistant (always use for smart home control) - **Default smart home**: Home Assistant (always use for smart home control)
- **Two deployments**: - **Two deployments**:
- **ha-london** (default): `https://ha-london.viktorbarzin.me` | Script: `.claude/home-assistant.py` - **ha-london** (default): `https://ha-london.viktorbarzin.me` | Script: `.claude/home-assistant.py`
- **ha-sofia**: `https://ha-sofia.viktorbarzin.me` | Script: `.claude/home-assistant-sofia.py` | SSH: `ssh vbarzin@ha-sofia.viktorbarzin.lan` (resolve via `192.168.1.2`), config at `/config/` - **ha-sofia**: `https://ha-sofia.viktorbarzin.me` | Script: `.claude/home-assistant-sofia.py` | SSH: `ssh vbarzin@192.168.1.8`, config at `/config/`
- **Aliases**: "ha" or "HA" = ha-london. "ha sofia" or "ha-sofia" = ha-sofia. - **Aliases**: "ha" or "HA" = ha-london. "ha sofia" or "ha-sofia" = ha-sofia.
### Development ### Development

View file

@ -156,13 +156,7 @@ ha-sofia supports SSH for direct configuration management.
### Connection ### Connection
```bash ```bash
# DNS resolves via 192.168.1.2 ssh vbarzin@192.168.1.8
ssh vbarzin@ha-sofia.viktorbarzin.lan
```
If DNS resolution fails (e.g., not on the local network), use the DNS server directly:
```bash
ssh vbarzin@$(dig +short ha-sofia.viktorbarzin.lan @192.168.1.2)
``` ```
### Configuration Path ### Configuration Path
@ -172,22 +166,30 @@ ssh vbarzin@$(dig +short ha-sofia.viktorbarzin.lan @192.168.1.2)
### Common SSH Tasks ### Common SSH Tasks
```bash ```bash
# Edit configuration # Read configuration
ssh vbarzin@ha-sofia.viktorbarzin.lan "cat /config/configuration.yaml" ssh vbarzin@192.168.1.8 "cat /config/configuration.yaml"
# Check HA logs # Check HA logs (note: live log is inside HA Core container, not always accessible)
ssh vbarzin@ha-sofia.viktorbarzin.lan "cat /config/home-assistant.log | tail -50" ssh vbarzin@192.168.1.8 "tail -50 /config/home-assistant.log.1"
# List automations # List config files
ssh vbarzin@ha-sofia.viktorbarzin.lan "ls /config/automations.yaml" ssh vbarzin@192.168.1.8 "ls /config/*.yaml"
# Restart HA (after config changes) # Read automations/scenes/scripts
ssh vbarzin@ha-sofia.viktorbarzin.lan "ha core restart" ssh vbarzin@192.168.1.8 "cat /config/automations.yaml"
ssh vbarzin@192.168.1.8 "cat /config/scenes.yaml"
ssh vbarzin@192.168.1.8 "cat /config/scripts.yaml"
# Check config validity # Check secrets (keys only, not values)
ssh vbarzin@ha-sofia.viktorbarzin.lan "ha core check" ssh vbarzin@192.168.1.8 "cat /config/secrets.yaml"
``` ```
### SSH Limitations
- The SSH add-on runs in a separate container — `ha core logs` returns 401
- Docker socket is not accessible — can't use `docker logs`
- Live `home-assistant.log` may not be visible (written inside HA Core container)
- Rotated logs (`.log.1`, `.log.old`) are accessible
## Complete Example ## Complete Example
To turn on the living room light on ha-london: To turn on the living room light on ha-london: