Open Source Home Automation
Home automation that routes through a manufacturer's cloud stops working the day the company folds, sunsets the product, or simply has an outage - a light that needs the internet to turn on is a downgrade from a dumb switch. So the real question is how much runs locally: whether your routines, schedules, and sensor history live on a box in your house and keep responding when the connection or the vendor does not. Open source hubs answer that by talking to devices over local protocols and keeping automation logic on hardware you own, with cloud bridges left as optional edges for the few things - voice assistants, remote access - that genuinely need them.
Home Assistant
Open source home automation with local control and privacy first
Homebridge
Lightweight Node.js server that adds HomeKit support to non-HomeKit smart home devices
Node-RED
Low-code flow editor for event-driven applications with a large library of nodes and flows
ESPHome
Turn ESP32, ESP8266, BK72xx, and RP2040 devices into smart home devices from configuration files
Domoticz
Free open source home automation system for monitoring and controlling lights, switches, and sensors
Gladys Assistant
Privacy-first open-source smart home assistant for local automation and device control
ioBroker
Open source IoT platform for home automation, data logging, and system integration on premise
openHAB
Vendor- and technology-agnostic open source home automation software
Our picks
A common setup pairs one hub with a device-firmware tool and a logic layer, plus a bridge to a phone ecosystem.
The broad local-first hub: Home Assistant Runs on a Raspberry Pi or local server and puts local control and privacy first, with more than 1500 integrations covering lights, sensors, locks, and media players. Its modular architecture lets you add device support or build custom components, and it is governed by the non-profit Open Home Foundation, which by charter cannot be sold.
DIY firmware for cheap microcontrollers: ESPHome Turns ESP32, ESP8266, BK72xx, and RP2040 boards into smart devices defined in YAML instead of hand-written firmware, with over-the-air updates so you never unmount them. Devices run locally with no cloud dependency and integrate closely with Home Assistant. It is the piece that makes custom sensors and switches cheap and fully under your control.
Visual automation logic: Node-RED A browser-based flow editor for wiring devices, APIs, and services into event-driven automations without writing everything from scratch. Built on Node.js, it runs happily at the edge on a Raspberry Pi as well as on a server, and a large library of community nodes and shared flows extends it.
Bridge non-HomeKit devices into Apple Home: Homebridge A lightweight Node.js server that emulates the HomeKit protocol, bridging devices without native support into Apple Home so they respond to Siri. Plugins cover lights, locks, sensors, thermostats, fans, and more, and version 2 can also expose accessories over Matter. The practical way to pull mixed-brand gear into an Apple Home household.
Choosing a hub that survives an outage
Automation fails at the edges, so the device layer decides more than the dashboard does. List the gear you already own and note how each piece talks - Wi-Fi, Zigbee, Z-Wave, Thread, Matter, Bluetooth, infrared, or a vendor cloud API - because the best hub is the one that controls your actual switches, locks, sensors, and thermostats, not the one with the longest integration count. Home Assistant leads on breadth with well over a thousand integrations and direct local control; openHAB takes a vendor-agnostic approach across hundreds of technologies; Domoticz stays light enough to run on a Raspberry Pi. Radio reliability, adapter placement, and mesh health end up mattering more than interface polish once devices are inside walls.
Decide how local the system must be, because in a house cloud dependence is not only a privacy question - it determines whether lights, heating, locks, and leak sensors keep working during an internet outage. Favor hubs where the automation engine runs on your own controller and devices can be paired locally, and treat cloud bridges as optional. ESPHome fits here by turning ESP32 and ESP8266 chips into local devices defined in YAML, and Node-RED lets you wire event-driven logic across devices and APIs without routing it through someone else's service. If a daily routine needs a vendor account to fire, assume it will fail at an inconvenient time.
Then match the automation model to whoever maintains the house. Some systems center on visual rule editors, some on text configuration, some on event buses and scripts. For locks, garage doors, alarms, and climate, look past cleverness to state history, safe restart behavior, manual overrides, permission boundaries, and backups that capture device databases and encryption keys, not just settings. An automation nobody can debug at 11 PM is a liability.
Related categories
Frequently asked questions
Will my automations keep working if the internet goes down?+
That depends on how your devices connect, not just which hub you run. Locally paired Zigbee, Z-Wave, or Wi-Fi devices can keep responding to schedules and manual controls when the automation engine runs on your own controller, which is the design goal of Home Assistant, openHAB, and Domoticz. Devices that need a vendor cloud may stop. Test it deliberately: unplug the WAN link and try the routines your household expects to work.
How do I match a hub to the devices I already own?+
Inventory first. Record each device's type, brand, and connection method, and whether it currently needs a hub or cloud account. Then check support at the protocol and integration level, favoring native local support over a cloud path. Home Assistant's large integration library and openHAB's vendor-agnostic design cover the widest range, but for battery sensors, pairing support and long-term mesh stability are not the same thing, so look for reports from users with similar radios.
Do I have to write code or YAML?+
Some, though how much varies. Gladys Assistant and Domoticz aim for automations without coding, Node-RED uses a visual flow editor, and Home Assistant mixes point-and-click with templates for advanced behavior. ESPHome is explicitly YAML-driven for device firmware. Text rules are not a downside - they are easier to review, version, and copy. The real question is whether whoever maintains the home can read the automations and change them safely.
Are open source systems appropriate for door locks and alarms?+
They can be, but treat those devices differently from lights and sensors. Require local control, explicit confirmations, good logs, and conservative rules. Avoid unlocking a door or opening a garage on a single presence signal; use multi-factor conditions and manual fallbacks. Check whether the system supports separate permissions so guests or children cannot operate safety-critical devices from every dashboard. Home Assistant and openHAB both expose user accounts and scoping for this.
What hardware does the controller need?+
A small always-on computer is usually enough, and reliability matters more than raw speed. Domoticz is efficient enough for a Raspberry Pi, and Home Assistant, Gladys, and ioBroker also run on modest hardware. Use stable power, decent storage, and a recovery plan for corruption. If you need Zigbee, Z-Wave, or Thread coverage, plan radio adapters and placement: USB extension cables and keeping radios away from noisy ports help more than a faster CPU.
How do voice assistants fit without giving up local control?+
Voice usually adds a cloud path even when the automation stays local. A practical setup keeps device state and rules on your controller, then exposes only selected entities to the voice platform. Homebridge does this for Apple Home and Siri, and Gladys connects to Alexa, Google Home, and Siri. Do not expose every lock, alarm, or camera by default; use clear naming, room scoping, and limited permissions so voice control stays helpful.
Can I move off a proprietary hub easily?+
The hard part is rarely exporting data - it is re-pairing devices and rebuilding automations. Many hubs give no clean export of rules, rooms, or scenes in a format another system can read, so expect to document your setup, move one room at a time, and factory-reset some devices. Keep the old hub online until each critical routine has been tested in the new system, whether that is Home Assistant, openHAB, or another controller.