TL;DR
Get the latest gadgets delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
A home automation developer says the core functions in his house run locally, so they continue working if the internet or a vendor service goes down. His account describes a decade-long design approach built around local hardware, multiple controls and cloud services as optional add-ons, not requirements.
Home automation developer Spencer Kittleson says the core systems in his house keep working when the internet is disconnected, describing a design approach that avoids relying on vendors’ servers for essential functions. In a report published by Do Code That Matters, he details a local setup and argues that smart-home devices should retain basic controls even when cloud services are unavailable.
Kittleson says his system runs on hardware he owns, including ESP-based devices running Tasmota, an MQTT message broker and Node-RED on a Raspberry Pi. These components handle local device communication and automation. He also uses some cloud services, including Alexa and AWS services, but says Alexa is an additional control method rather than a requirement: wall switches and a wall dashboard remain available if the service is down.
His central rule is that core functions must work with the internet unplugged. Other practices follow from it: keep the old control method when adding a smart one, make automations easy to change, review them for conflicts, and keep configuration in one place rather than scattered across vendor apps. He says cloud-connected devices should have an API with logs, so their behavior is not an opaque “black box.”
The report gives practical examples, including a sprinkler controller and a garage door setup. Kittleson says local sensors and automations can operate these systems without depending on a vendor cloud. He also recounts cloud-related problems he has encountered: a Nest integration stopped working after Google changed an API, while a Samsung refrigerator displayed a TLS certificate error and a Camp Chef grill controller required Wi-Fi to show its temperature. These are his reported experiences, not an independent assessment of the products.
Keeping Basic Controls Available
When a smart device depends on a remote service, an internet outage, service disruption or vendor-side change can affect whether people can use it. That matters most for functions people expect to work routinely, such as turning on lights or operating household equipment. Kittleson’s approach treats local operation and familiar physical controls as ways to reduce that dependency.
The report also highlights a trade-off for buyers and builders. Cloud-connected products may be simpler to install, while locally controlled equipment can take more setup and maintenance. A design with several control paths—such as a wall switch alongside an app or voice assistant—can make the system less dependent on any single interface. Kittleson presents this as a personal set of rules, not a universal technical standard or a guarantee that every local setup will remain trouble-free.
Products Worth Considering
Apple AirPods Pro (2nd Generation) Wireless Earbuds with USB‑C Charging, Up to 2X More Active Noise Cancelling, Transparency Mode, Adaptive
Bose Smart Soundbar 700 with Alexa, Black
LG UltraGear 32GX850A-B 32-inch 4K UHD OLED Gaming Monitor
As an affiliate, we earn on qualifying purchases.
From Cloud Links to Local Control
Kittleson says his rule against making core home functions dependent on the internet has guided his setup for about ten years. He has presented the approach in two talks and says the later version added rules based on living with the system and having more people in the house. Among those additions are keeping device configuration centralized, using more than one way to control a function, and preferring devices whose batteries last at least a year.
His report distinguishes between cloud services used for convenience and systems that must work locally. In his example, Alexa can flip a switch, but it is not the only way to do so. The distinction reflects a broader design choice in his own home: device communication through MQTT publish-and-subscribe messaging lets sensors send readings without being tied to one specific app or automation. The source does not compare this setup with other smart-home platforms or provide measured reliability data.
“Nothing core in my house depends on a vendor’s server. If the internet goes down, the house keeps running.”
— Spencer Kittleson, in the Do Code That Matters report
Limits of One Household’s Experience
The report is a first-person account of one person’s system, not a controlled test of how often smart-home products fail during outages. It does not quantify service interruptions, compare costs, or establish how widely the described problems affect the named products. The precise scope of the Nest API change and the circumstances behind the refrigerator and grill examples are not detailed in the material provided.
It is also unclear how the system performs during failures beyond loss of internet access, such as a local power outage, hardware failure or a problem with the home network. Local control can reduce dependence on a remote service, but the source does not claim it removes every point of failure. Kittleson says some cloud services remain in use, so the setup is not wholly disconnected from the internet.
Rules Tested as the System Changes
Kittleson’s report does not announce a product launch, policy change or scheduled follow-up. He describes home automation as ongoing work: rooms and routines change, new devices are added, and automations can conflict or break. He says users should periodically check that scheduled triggers and device interactions still make sense together.
For readers considering similar systems, the immediate next step in his approach is to identify which functions are essential, then check whether they still work if internet access or a vendor service is unavailable. The report offers examples and rules rather than a formal checklist or independent product recommendations; further details would depend on the devices and local setup chosen.
Key Questions
What does “work without the internet” mean in this report?
It means that core functions in Kittleson’s home, including local automations and controls, do not require a vendor’s remote server to operate. He says cloud tools such as Alexa can still be used as additional control methods.
Which technologies does Kittleson say he uses?
He names Tasmota on ESP-based devices, an MQTT broker and Node-RED running on a Raspberry Pi. The report describes these as parts of his own home setup, not as a required combination for every home.
Does the report say all smart-home devices need to be offline?
No. Kittleson says some cloud services are useful, but argues that essential functions should have another way to work. He describes voice assistants and cloud services as optional paths rather than the sole means of control.
What problems does Kittleson cite with cloud dependence?
He reports that a Nest integration stopped working after a Google API change, and describes a Samsung refrigerator certificate error and a grill controller that needed Wi-Fi to display its temperature. These are examples from his experience; the report does not establish how common they are.
Source: docodethatmatters.com
