Smart Home

📌 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 cause false triggers, wrong forecasts, and broken automations. 🎯 Limitations of the Default Wizard During initial setup, Home Assistant asks to pick a location on a map. However: ❌ 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. ...

📌 This is Part 2 of the series. Part 1: Theory explains why this matters. 📦 Unboxing and Preparation Heltec V4 Contents Component Purpose Board ~60×30 mm ESP32-S3R2 + SX1262, OLED 128×64, USB-C Antenna (IPEX) Connect to ANT port - mandatory! USB-C cable Power + flashing + debugging Pins (optional) For external sensors/antennas ⚠️ Important: without antenna connected, the radio module may be damaged. Always attach antenna before powering on. Heltec V4 Specifications Component Description MCU ESP32-S3R2 (WiFi + Bluetooth) LoRa Transceiver Semtech SX1262 Frequencies 863–870 MHz (EU), 902–928 MHz (US) Display 0.96" OLED 128×64 Power Up to +28±1 dBm (High Power option) Power Supply USB-C + optimized LiPo management Connectors USB-C, U.FL/IPEX for LoRa, 1.25-8Pin GNSS, 1.25-2Pin Solar Form Factor Pin-compatible with V3/V3.1 ⚡ Flashing: Web Flasher Official flasher: https://flasher.meshtastic.org ...

Imagine: you’re hiking, at a dacha, in an area with poor signal - or you just want to communicate without carriers, clouds, and surveillance. Solution: decentralized LoRa network - low-power radio with range up to several kilometers. 💡 This isn’t an internet replacement. It’s “internet for emergencies, privacy, and experiments”. Who this series is for: ✅ Friends and relatives who want to understand “why do I need this” ✅ Beginners in radio/electronics (no soldering required!) ✅ Anyone who values privacy and infrastructure independence 📡 LoRa and mesh networks (in simple terms) LoRa (Long Range) Parameter Value Range 1–10 km urban, 50+ km line-of-sight Power ~100 mA transmit, ~10 mA idle Speed 0.3–50 kbps (text, coordinates, small data only) Frequency 433 MHz (RU), 868 MHz (EU), 915 MHz (US) Simple analogy: ...