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
In an October 2026 report, home automation builder Spencer Kittleson describes a decade-old rule: core household functions should keep working when the internet is unavailable. His setup uses locally controlled devices and a Raspberry Pi, while cloud services such as Alexa remain optional rather than the only way to control the home.
Home automation builder Spencer Kittleson says the core systems in his house continue to work when the internet is disconnected, describing a design approach developed over about ten years. His October 2026 report argues that lights and other essential functions should not depend on a vendor’s cloud service, a concern for households whose devices can lose remote features when a connection or online service fails.
Kittleson’s system relies on hardware he owns, including ESP-based devices running Tasmota, an MQTT messaging broker and Node-RED automation software on a Raspberry Pi. He says these components let devices communicate locally and allow automations to run without relying on a manufacturer’s server. He describes cloud services, including Amazon Alexa and some AWS services, as optional ways to control devices rather than required links in the system.
His stated rule is that core functions must work with the internet unplugged. Alexa can provide another control method, but it should not be the only one: wall switches and a wall dashboard remain available in his home. He also advises keeping familiar controls when adding smart features, so, for example, an automated light does not become unusable because someone must leave a smart bulb permanently powered.
The report gives examples of cloud dependence that prompted this approach. Kittleson says a Nest integration stopped working after Google changed its API. He also recounts a Samsung refrigerator displaying a TLS certificate error and a Camp Chef grill controller that, according to him, needed Wi-Fi to show its temperature. These are his reported experiences, not a broad assessment of every product from those companies.
Keeping Household Controls Available
When an internet connection or vendor service is unavailable, a cloud-dependent device may lose some or all of its smart functions. Kittleson’s approach treats local control and ordinary switches as a way to reduce that dependency, while also preserving options for people who prefer voice assistants or apps. The practical point is not that every smart device must be built the same way, but that buyers should know which functions rely on an outside service.
Local operation can also affect how much control a household retains over its devices and automations. Kittleson says he keeps configuration in one place rather than across multiple vendor apps and uses MQTT so devices can publish information without being tightly tied to a single controller. Those choices give him flexibility, though they also require setup and maintenance that a packaged cloud service may handle for the user.
His report is a personal account, not independent testing or a survey of product reliability. Still, the examples underline a choice shoppers can make before buying: whether a device has a usable manual control, local operation, or a documented way to integrate with other systems if its cloud connection changes.
Products Worth Considering
Apple Watch SE 3 GPS 40mm Smartwatch
Bose Smart Soundbar 700 with Alexa, Black
Amazon Kindle Paperwhite Signature Edition (12th Generation, 2024), 32 GB, Metallic Raspberry
As an affiliate, we earn on qualifying purchases.
Lessons From a Decade of Automation
Kittleson’s October report revisits two talks about his home automation projects, including a sprinkler controller and a garage-door setup. The projects use local hardware and automation flows, and he describes the garage system as checking whether the door is closed before opening it and turning on a fan. He says the system can also notify him if the garage is left open.
His other rules grew out of operating the system over time. He recommends checking automations so multiple schedules do not control the same device in conflicting ways, keeping systems inexpensive to modify as household needs change, and avoiding battery-powered sensors unless their batteries last at least a year. For cloud-connected devices, he says he wants an API with logs rather than a black box. These are his design preferences, based on his own experience, rather than universal technical requirements.
The report also describes three ways he handles automations: Node-RED for flows he builds, Alexa routines and similar services for tasks he does not want to implement himself, and MQTT for communication between devices and systems. Kittleson presents this mix as a way to retain local operation without rejecting every cloud feature.
“No internet, no problem. Core stuff has to work with the internet unplugged.”
— Spencer Kittleson, in his October 2026 report
Limits of One Household’s Experience
The report does not provide independent tests comparing local and cloud-dependent products, or measure how often internet outages disable particular devices. Its examples come from Kittleson’s own home and projects; they do not establish how frequently the cited failures occur across a product line or whether the same issue remains in current versions.
It is also not clear from the report how every device behaves during a power failure, a failure of the home network, or a fault in the Raspberry Pi or other local equipment. Local control can reduce reliance on outside servers, but it does not by itself guarantee that a device will work through every type of outage. Product capabilities and the exact functions available offline can vary, so readers should check the specifications for the devices they own or plan to buy.
Check Offline Features Before Buying
Kittleson’s report does not announce a product launch or a scheduled technical milestone. For readers, the next practical step is to check whether a device offers local control, physical operation and documented integrations, and to identify which features stop working without internet access. Households can also test their own devices by briefly disconnecting internet service and confirming that essential controls still work.
Any broader assessment will depend on product documentation and further testing across manufacturers and devices. Until then, Kittleson’s account offers a set of design rules from one long-running installation, while leaving open how well those rules apply to other homes and equipment.
Key Questions
What is the main point of Kittleson’s report?
He says core household functions should keep working without internet access. In his home, cloud services such as Alexa provide additional control options rather than serving as the only way to operate devices.
What technology does his setup use?
Kittleson describes using Tasmota on ESP-based devices, an MQTT broker and Node-RED running on a Raspberry Pi. He says these locally managed components support device communication and automations without depending on a vendor’s server.
Does the report show that all smart home devices fail offline?
No. It shares one builder’s experiences with particular integrations and products. It does not test all devices or establish how common cloud-related failures are.
What should shoppers check before buying a smart device?
Check whether it can be controlled locally or with a physical switch, what features require an internet connection, and whether the manufacturer documents an API or other integrations. Offline behavior can differ by model and feature.
Source: docodethatmatters.com
