U6 Security and Services
Home automation that works when the internet does not
Smart devices that depend on a vendor's cloud stop working when the vendor changes its mind, gets acquired or goes offline. Local-first home automation keeps the lights, heating and sensors under your control, responding instantly, with or without the internet.
At a glance
- Run a self-hosted automation hub and prefer devices that work with the internet unplugged.
- Low-power mesh radio protocols such as Zigbee and Z-Wave cannot reach the internet by design, which makes them excellent for privacy.
- Check whether an integration is local or cloud-based before you buy a device.
- Never put your network, firewall or UPS behind a smart plug or an experimental automation.
- Design for the least technical person in the house. Wall switches must still work.
Why local first
Cloud-dependent devices have three problems. They stop working when the vendor's service is down or discontinued. They send data about your home to companies you have never audited. And a compromised vendor account or cloud service can operate devices in your house. A local hub that talks to devices directly avoids all three, and responds faster, because the command never leaves the building.
The hub
The center of a local setup is an open-source automation platform running on hardware you control. Common options:
- A single-board computer with an SSD rather than an SD card. Inexpensive and low power.
- A small dedicated appliance sold for the purpose, if you prefer not to build one.
- A virtual machine on your hypervisor. Easy to snapshot and back up, but the hub now depends on the host being up, and radio adapters must be passed through to the VM. See Mini PC Hypervisor Build.
Give the hub a DHCP reservation and a proper DNS name, such as hub01.lab.example.net. In our example network it lives at 10.42.30.20 on the lab VLAN, and the IoT network is allowed to reach it and nothing else on the internal network. See VLANs and Segmentation.
How devices connect
| Connection | How it works | Strengths | Watch out for |
|---|---|---|---|
| Mesh radio (Zigbee, Z-Wave) | A USB radio adapter on the hub forms a low-power mesh; mains-powered devices relay for others | No IP stack, so devices cannot phone home; long battery life; mesh extends range | Needs a radio adapter; mesh size limits; keep the adapter away from USB 3 ports and wireless access points to reduce interference |
| Newer IP-based smart home standards | Devices use IP networking with a local control standard | Local control across ecosystems | Device support still maturing; check exact features |
| Wireless LAN devices with a local API or open firmware | Devices join your IoT wireless network and the hub talks to them locally | Cheap, no extra radio | Many devices ship with cloud-only firmware; vendors sometimes lock out open firmware in newer batches |
| Cloud integration | The hub talks to the vendor's cloud using your account | Works with almost anything | Fails when the internet or vendor fails; no privacy gain |
Caution
A device listed as "supported" by your hub may still depend on the vendor's cloud. Read the integration documentation and community reports before buying, and prefer devices explicitly described as working locally. Some vendors push firmware updates that remove local control; disable automatic device updates through the vendor where you can.
Choosing devices
- Smart switches over smart bulbs for most rooms. A smart wall switch still works as a normal switch for guests and when the hub is down, and nobody can accidentally cut power to a smart bulb with the old switch.
- Plugs with power monitoring show what each device actually draws, which is useful for your lab and for the electric bill.
- Respect ratings. Match plugs and switches to the load with headroom. Do not run heaters, dryers or other heavy appliances through consumer smart plugs.
- Battery sensors for doors, motion, temperature, humidity and water leaks are inexpensive and last a year or more. Leak sensors near the water heater, washer and rack have saved many homes.
- Infrared blasters can control older TVs, fans and air conditioners that have only a remote.
- Buy from mainstream brands that support open standards rather than unknown marketplace brands with unclear firmware.
Network placement
Put wireless smart devices on the IoT network. Allow them to reach the hub and, only if they need it, the internet. Block everything else. Devices that should never phone home can be denied internet access entirely; your firewall logs will reveal which ones try. Smart TVs with unwanted advertising are a common candidate.
Mesh radio devices do not touch your IP network at all, so only the hub needs care. If you give the hub interfaces on more than one network, it becomes a bridge between them; protect it accordingly with updates, strong authentication and backups.
Automations that earn their keep
- Lights on at sunset and off late at night, adjusted automatically for the seasons.
- Heating and cooling adjusted when everyone is away, based on presence or a schedule.
- Alerts when a leak sensor gets wet, a freezer warms up or a sump pump stops drawing power.
- A porch light that turns on when the camera recorder detects a person after dark.
- Notifications when the washer finishes, detected from its power draw dropping.
- Lab servers shutting down gracefully when the house is empty for a long trip, and waking by network command on your return. Check that scheduled backups are not affected.
Start from a real annoyance in your house, then find the device and integration that fixes it. A four-pack of plugs and a spare single-board computer is enough to begin.
Warning
Never control infrastructure with experimental automation. Some reflashed smart plugs default to off after a power cut, and some reboot when they lose wireless. A plug feeding your UPS, firewall or switch that does either can take down the whole network, and with it the hub you would use to fix it.
Dashboards for the whole household
The person who built the system knows what forty-five buttons do. Everyone else sees clutter. Build a separate, simple dashboard for the household:
- One large button per room that toggles its main lights; hold or long-press for detail.
- Show controls only when relevant, such as media controls only while the TV is on.
- Put the things people actually ask about on the first screen: house temperature, doors and locks, package alerts and camera snapshots.
- Keep advanced controls for the lab and network on a separate dashboard for yourself.
Reliability and backups
- Back up the hub off the box. Built-in backups stored on the same SD card or disk fail together with it. Copy them to the NAS and include them in your off-site backups.
- Update deliberately. Read release notes, back up first and be ready to roll back. Integrations occasionally break after updates and are usually fixed quickly.
- Plan for the hub being down. Lights must work from wall switches, heating must have a sensible default, and nothing safety-related should depend solely on automation.
- Test your alerts. An alert you have never seen fire is an alert you cannot trust.
Voice control and local AI
A voice assistant has four stages: a wake-word detector, speech-to-text, intent recognition and text-to-speech. Wake-word detection and natural-sounding speech synthesis now run comfortably on local hardware. Accurate local speech-to-text is the demanding part, and accuracy below roughly 95 percent is where people give up and reach for the switch. Local language models can also turn free-form requests into structured commands for your hub. If privacy is why you went local, keep voice processing local too, or accept the trade-off knowingly. Our field note Local AI in the Homelab covers local AI in more depth.