poprhythm
2f1a988ac3
- watchtower: move Telegram token/chat ID to .env instead of plaintext in compose - plex: remove stale/dead PLEX_CLAIM token - uptime-kuma: mount docker.sock read-only (only needs to read container state) - home-assistant: drop privileged: true (no device passthrough configured) - glances: drop privileged: true, bind dashboard port to 127.0.0.1 - couchdb, docker-registry, leafweb: bind ports to 127.0.0.1 (proxy/localhost-only access confirmed, no direct LAN clients)
Home Assistant
Home automation platform that integrates with hundreds of smart home devices and services.
Access
- URL: https://homeassistant.kolpacksoftware.com
- Local: http://localhost:8123 (if needed)
Initial Setup
- Navigate to the URL above
- Create your admin account on first launch
- Follow the onboarding wizard to:
- Set your location
- Choose initial integrations
- Configure devices
Configuration
- Data directory:
/srv/home-assistant/ - Config file:
/srv/home-assistant/configuration.yaml - Logs:
docker logs home-assistant
Network Considerations
The container runs on npm-network and connects through the nginx reverse proxy.
For device discovery: Some integrations (like HomeKit, mDNS-based devices) work best with host networking. If you encounter discovery issues:
- Stop the container via Portainer
- Edit
docker-compose.ymland replace the networks section with:network_mode: host - Remove the VIRTUAL_HOST environment variables (not needed with host mode)
- Redeploy via Portainer
- Configure nginx-proxy-manager manually to proxy to localhost:8123
Common Integrations
- Smart lights: Philips Hue, LIFX, TP-Link
- Smart speakers: Google Home, Alexa
- IoT devices: Zigbee, Z-Wave, MQTT
- Media: Plex, Sonos, Chromecast
- Weather, calendars, notifications: Many built-in integrations
Useful Commands
# View logs
docker logs -f home-assistant
# Restart container
docker restart home-assistant
# Check configuration
docker exec home-assistant hass --script check_config
# Access container shell
docker exec -it home-assistant /bin/bash