Local-First Home Automation: A Decade of Rules Without Cloud Dependency
The author maintains a smart home system where critical functions don’t require cloud connectivity. His foundational rule, in place for roughly ten years, requires that core devices operate if internet fails. This approach emerged from practical failures: Google broke the Nest API, a Samsung fridge displayed a TLS certificate error on its screen, and a Camp Chef grill required Wi-Fi merely to show temperature readings. His infrastructure uses Tasmota firmware on ESP boards, an MQTT message broker, and Node-RED running on a Raspberry Pi, with optional cloud services including Alexa and AWS.
The author developed eleven operational rules across two phases. The initial five emphasize maintaining internet-independent core functionality, preserving manual controls alongside automation, enabling cheap changes as household needs evolve, preventing automation conflicts through monitoring, and treating rule violations as exceptions. After year five, when multiple residents moved into the house, he added six additional rules addressing multi-user complexity: requiring cloud devices to have accessible APIs and logs, consolidating configuration in a single location, offering multiple control methods (app, Alexa, QR codes, NFC tags), implementing MQTT pub/sub architecture for device communication, and enforcing one-year-minimum battery lifespans.
His frequently discussed builds include a Tasmota-based sprinkler controller and a garage automation system that reads door sensors before initiating cooling operations and alerts when cooling is already running. The overall approach balances convenience, privacy, and reliability while supporting multiple household members using shared infrastructure.
Read the full article
Continue reading at Hacker News →This is an AI-generated summary. Read the original for the full story.