mrwhiski/Infrastructure
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Infrastructure/docker/homeassistant/README.md

1 KiB
Raw Permalink Blame History

Home Assistant

Runs on the OptiPlex homeserver (192.168.30.20) in ~/homeassistant, as the official container image (not Home Assistant OS). UI: https://ha.home.staffenberger.at (via NPM) or http://192.168.30.20:8123.

Reverse proxy

Configured in the UI, not in configuration.yaml: Settings → System → Network → HTTP server → Reverse proxy:

  • Trust X-Forwarded-For on
  • Trusted proxies: 172.16.0.0/12 (Docker's internal range; NPM connects from 172.19.0.2)

Gotcha: this version migrated the YAML http: block into the UI once and ignores it afterwards. A typo during migration (use_x_forward_for) left the switch off, causing 400: Bad Request. Keep no http: block in the YAML.

Notes

  • Bluetooth errors in the log are harmless; installing bluez on the host or removing the Bluetooth integration stops them.
  • Login through ha.home.staffenberger.at was unreliable — first check that Websockets Support is on for the NPM proxy host (see ../../docs/todo.md).