Home-Assistant

📌 This is Part 3 of the series. Part 1: Theory, Part 2: Practice. 🔗 What We’re Integrating Component Purpose Difficulty ONEmesh MQTT Bridge between local mesh and global map + Telegram notifications 🟢 Low Home Assistant Node sensors, device_tracker, automations on mesh messages 🟡 Medium Notifications Alerts for new nodes, lost connection, mentions in chat 🟢 Low 💡 All examples tested on: HA 2026.4.2 (Docker) + Orange Pi 3B + built-in MQTT broker. ...

Home Assistant in Docker doesn’t see Bluetooth devices, even if everything works on the host. Causes: ❌ Container has no direct access to /dev/hci0 ❌ BlueZ inside container conflicts with host daemon ❌ Passive BLE scanning requires --experimental flag in BlueZ Solution: Don’t run Bluetooth stack inside container - passthrough D-Bus from host instead. ✅ Docker Compose Configuration Minimal Setup services: home-assistant: container_name: home-assistant image: ghcr.io/home-assistant/home-assistant:stable volumes: - config:/config - /run/dbus:/run/dbus:ro # ← Critical for Bluetooth cap_add: - NET_ADMIN - NET_RAW - SYS_ADMIN restart: unless-stopped networks: - traefik - prometheus volumes: config: driver: local networks: traefik: external: true name: traefik prometheus: external: true name: prometheus ⚠️ Don’t add devices: - /dev/hci0:/dev/hci0 - not needed with D-Bus passthrough and may cause conflicts. ...

The home zone (zone.home) is the foundation for: ✅ Presence detection (automations for “arrived/left”) ✅ Sunrise/sunset calculation (lighting, blinds) ✅ Weather forecasting (coordinate-based) ✅ Geofencing for devices and users Inaccurate coordinates = false triggers, wrong forecasts, broken automations. 🎯 The Default Wizard Problem During initial setup, Home Assistant asks to pick a location on a map. But: ❌ No manual coordinate input in the wizard ❌ IP-based auto-detection often has 1–10 km error ❌ Elevation above sea level is not requested Solution: configure precise coordinates after installation, via UI or YAML. ...