The Problem with Connected Everything
When you buy a smart home device today, you’re often buying a service subscription disguised as a product. A thermostat that can’t change temperature without an app. A fridge that shows TLS certificate errors on its own screen. A grill controller that needs Wi-Fi just to display the current temperature. A meat thermometer that stopped working entirely when the company went out of business.
These aren’t edge cases — they’re the norm. And they represent a fundamental design failure: the assumption that internet connectivity is always available and always reliable.
After a decade of building and maintaining a home automation system, one developer has distilled the lessons learned into a set of principles that should guide smart home design. The core principle is simple: nothing core in my house depends on a vendor’s server to work.
The Core Rules
These principles emerged from ten years of experience and evolved as the household grew from one person to several:
Rule 1: No Internet, No Problem
Core functionality must work with the internet unplugged. This means:
- Lights can be controlled with physical switches
- Thermostats can be adjusted manually
- Doors can be locked and unlocked without an app
- Safety systems function independently
Cloud services can enhance functionality (like remote access or voice control), but they should never be required for basic operation.
Rule 2: Don’t Remove the Old Way While Adding the New One
When automating a light, don’t disable the physical switch. If someone tapes a wall switch on so a smart bulb keeps power, you’ve failed. The solution is an in-wall smart switch that still works like a normal switch.
Rule 3: Be Agile
Rooms get used differently. People move in and out. New devices appear. Everything must be cheap to change. This argues for modular systems and avoiding vendor lock-in.
Rule 4: Check Your Automations
It’s easy to end up with multiple automations fighting over the same device. Regularly audit your automation rules to ensure they still make sense together.
Rule 5: Exceptions Must Be Exceptional
You can break the rules, but only for reasons you’d still agree with six months later. “I was in a hurry” doesn’t count.
Extended Rules (After Year Five)
When the household grew, additional rules emerged:
Rule 6: A cloud device needs an API with logs or it doesn’t get installed. No black boxes.
Rule 7: Config lives in one place instead of five vendor apps.
Rule 8: More than one way in: an app, voice control, a QR code, or an NFC tag.
Rule 9: If you keep doing the same steps, they become a routine. Automate routines, not individual actions.
Rule 10: Devices talk pub/sub over MQTT instead of point-to-point. This decouples devices and makes the system more flexible.
Rule 11: No batteries unless they last a year or more between changes. Nobody wants to swap a door sensor battery at 2am.
The Technology Stack
Implementing these principles requires the right tools:
Hardware
- ESP32 D1 Mini: Handles custom automation tasks. Runs Tasmota firmware for local control.
- Raspberry Pi 4: Runs Node-RED for logic, Grafana for monitoring, and MQTT broker for message routing.
- Smart switches and plugs: Tasmota-compatible devices that work locally without cloud dependency.
- Sensors: Temperature, humidity, motion, door/window sensors that report via MQTT.
Software
- Node-RED: Visual programming for automation logic. Runs locally, no cloud required.
- Tasmota: Open-source firmware for smart devices. Replaces proprietary firmware with local-first alternatives.
- MQTT: Lightweight publish/subscribe protocol for device communication.
- Grafana: Monitoring and visualization of system state and history.
- Home Assistant: Optional hub for more complex integrations.
Architecture
The system uses MQTT as the central nervous system. Devices publish sensor data and subscribe to control commands. Node-RED flows implement the automation logic. Grafana provides visibility into what’s happening. Everything runs locally on the home network.
Real-World Examples
The Sprinkler Controller
One of the most successful builds is a custom sprinkler controller built with an ESP8266, a solid-state relay, and Tasmota firmware. It includes:
- Temperature, humidity, and pressure sensors
- Local OLED display showing status
- MQTT integration for remote monitoring
- Node-RED scheduling
- No cloud dependency whatsoever
The controller has been running reliably for years, requiring no maintenance beyond occasional firmware updates.
The Garage Door System
The garage door automation includes:
- Door position sensor (reed switch)
- Relay module to simulate button press
- Node-RED logic to prevent accidental opens
- Telegram notifications for alerts
- Grafana tracking of opens and on-time
The system works even if the internet is down. The physical garage door opener still functions normally.
The Wall Dashboard
A cheap tablet mounted on the wall serves as the primary interface for the household. It provides:
- Garage door control
- Door lock status and control
- Light on/off and brightness
- Temperature and humidity display
- Quick access to common automations
No app required. No account needed. Just tap the screen.
What Readers Shared
When the developer shared these principles, dozens of people responded with their own horror stories:
- A fridge whose temperature can’t be changed because of a bug in the manufacturer’s app
- A TV that can’t switch inputs when the internet is down
- A heating system whose app doesn’t work from the local network
- A smart plug that can’t be set up on an isolated network
- Noise-cancelling headphones that search for Bluetooth forever if they can’t connect to the internet
- Synthesizers that need cloud login for firmware updates
- A meat thermometer that stopped working when the company went out of business
The last one is particularly telling. The hardware outlived the company, but it became useless anyway.
Practical Advice from the Community
Use Local Protocols
Zigbee and Z-Wave are better than Wi-Fi for smart home devices because they don’t require internet connectivity and tend to be more stable long-term.
Let AI Find Firmware
One reader buys the cheapest hardware that does the job, ignores reviews complaining about the app, and asks an LLM to find or create local-first custom firmware. This has worked for switches, thermostats, air quality monitors, and more.
Right to Repair Matters
The right-to-repair movement is crucial for smart home sustainability. Devices that can be repaired and modified are devices that can be kept working long-term.
Plan for Offline Operation
Decide what must work offline: turning things on and off, temperature controls, safety systems, and anything guests need to use without learning an app. If a visitor can’t turn something on or adjust the temperature without an app account, the design has failed.
The Bigger Picture
The smart home industry’s obsession with cloud connectivity reflects a business model problem, not a technical necessity. Companies would rather sell you a service than a product. They want recurring revenue and data collection opportunities.
But this model is increasingly untenable. Consumers are waking up to the problems:
- Services get shut down
- APIs change or disappear
- Privacy concerns mount
- Devices become e-waste when services end
- Reliability depends on external factors beyond your control
The alternative is local-first smart home design: devices that work independently, communicate locally, and treat internet connectivity as an optional enhancement rather than a requirement.
Building Your Own System
Starting a local-first smart home system doesn’t require deep technical expertise:
- Start small: Pick one device or automation to automate
- Choose local-first hardware: Look for devices that support Tasmota or similar open firmware
- Set up MQTT: A Raspberry Pi running Mosquitto MQTT broker is a good starting point
- Use Node-RED: Visual programming makes automation logic accessible
- Add monitoring: Grafana helps you understand what’s happening
- Iterate: Add more devices and automations as you learn
The learning curve is real, but the payoff is a system that works reliably, doesn’t depend on any company’s servers, and can be modified to suit your needs.
Conclusion
After a decade of building and maintaining a smart home system, the lesson is clear: smart home devices should work without the internet. This isn’t a nice-to-have feature — it’s a fundamental requirement for a reliable, sustainable smart home.
The technology to build such systems exists today. Open-source firmware like Tasmota, local automation platforms like Node-RED, and standard protocols like MQTT make it possible to build smart homes that are:
- Reliable: No dependence on external services
- Private: Data stays on your network
- Flexible: Easy to modify and extend
- Sustainable: Devices don’t become e-waste when services shut down
- Accessible: No app required for basic operation
The smart home industry needs to embrace these principles. Until it does, the safest approach is to build your own system using open-source tools and local-first architecture. Your future self will thank you when the cloud service you relied on gets shut down, and your home keeps working anyway.
In case you have found a mistake in the text, please send a message to the author by selecting the mistake and pressing Ctrl-Enter.