XDA published a note this week under the title “stop automating your schedule, use a cheap sensor to automate your actions instead.” The argument is old-school home-automation gospel: a schedule can only guess when you are in the room, a $12 motion sensor knows. In 2026, the difference between a home that fights you and one that keeps up is almost always a handful of contact, motion, and presence sensors wired into a controller that acts on them. These are the eight desktop apps we use to build sensor-driven flows.
What to look for in a sensor-triggered automation app
Not every controller thinks in triggers. The good ones do:
- First-class trigger primitives. State changes, “for X seconds,” edge detection, debouncing. Not just “at 7 am.”
- Local execution. The automation runs when your Wi-Fi drops. That means the whole engine lives in your house, not in someone’s cloud.
- Broad sensor protocol support. Zigbee, Z-Wave, Matter, ESPHome-native, LoRaWAN, Thread. The more the controller speaks, the fewer bridges you glue together.
- Reachable when things break. A dashboard, a REST API, and a mobile app for panic-mode overrides.
- A visual editor and a scriptable layer. Beginners want drag-and-drop; the flow you build in year three is a YAML or JavaScript blob you version in git.
- Community integrations. Every strange device you own is a search away from someone who already got it working.
Quick comparison
| App | Best for | Free plan | Platforms | Standout feature |
|---|---|---|---|---|
| Home Assistant | The default hub for any sensor stack | Fully free (open source) | Linux, Windows, macOS, Pi | 2,000+ integrations, huge community |
| Node-RED | Complex flowchart automations on top of HA | Fully free (open source) | Linux, Windows, macOS, Pi | Visual flow editor, state-in triggers |
| ESPHome | Building the sensor firmware itself | Fully free (open source) | Linux, Windows, macOS | Declarative YAML for ESP32/8266 devices |
| OpenHAB | Java-based hub with rich rules engine | Fully free (open source) | Linux, Windows, macOS | Blockly + JavaScript rules, mature Z-Wave |
| Domoticz | Lightweight controller for small setups | Fully free (open source) | Linux, Windows, macOS, Pi | Runs comfortably on a Pi Zero |
| Hubitat Elevation | Local-first commercial hub | One-time hardware cost | Web UI (hub is standalone) | Zero cloud dependency, Rule Machine |
| Homey Pro | Polished commercial hub | Included with hardware | Web UI + mobile apps | Homey Flow visual automations |
| Zigbee2MQTT | Bridge that turns Zigbee into events | Fully free (open source) | Linux, Windows, macOS | Broad device support, MQTT-native |
The 8 apps
1. Home Assistant — best default for any sensor stack
Home Assistant is the answer to “what should I run?” for the overwhelming majority of homelabbers. The trigger primitives cover state changes, time patterns, template evaluations, geolocation, MQTT, ZHA, Z-Wave, Matter, and a couple of dozen more. The automation editor now has both a YAML tab and a UI mode, and the mobile app doubles as a presence sensor. The community integration count is somewhere north of 2,000 as of 2026.
Where it falls short: The UI-mode automation editor cannot express every trigger combination the YAML mode can. Once your setup gets complex, you graduate to Node-RED or hand-written YAML.
Pricing:
- Free: fully open source, unlimited devices
- Paid: HA Cloud subscription (Nabu Casa) for remote access, not required
Platforms: Linux (Home Assistant OS on a Pi is the most popular install), plus Windows and macOS via Docker
Download: Home Assistant install
Bottom line: Start here. Everything else in this list is either a companion or an alternative for a specific reason.
2. Node-RED — best for complex sensor logic
Node-RED is the graduate school for Home Assistant automations. When “motion detected, if it is between sunset and sunrise, and if the TV is off, and if it has been at least three minutes since the last trigger, then turn on the lamp at 40% for six minutes” starts to look ugly in YAML, Node-RED’s visual canvas is where you build it. The events: state node reacts to any HA entity change, and the trigger and delay nodes cover the “wait for X seconds” and “reset if it fires again” patterns.
Where it falls short: The learning curve for the flow model is real. Beginners often over-complicate simple automations that HA’s built-in editor would handle in two clicks.
Pricing:
- Free: fully open source
- Paid: none
Platforms: Linux, Windows, macOS, Pi
Download: Node-RED install
Bottom line: The pick when your automations get more logic than the HA UI editor can express cleanly.
3. ESPHome — best for building the sensors themselves
ESPHome compiles YAML into ESP32 and ESP8266 firmware, and it belongs on this list because a lot of the cheap sensors you actually want to trigger on live at the firmware layer. A $6 PIR module wired to an ESP32 becomes a first-class Home Assistant sensor with a few lines of YAML, and the device talks to HA over the native API with sub-second latency.
Where it falls short: Not an automation engine. ESPHome handles device firmware; the trigger logic still runs in HA.
Pricing:
- Free: fully open source
- Paid: none
Platforms: Linux, Windows, macOS
Download: ESPHome install
Bottom line: The pick if the sensor you want does not exist off the shelf.
4. OpenHAB — best Java-based alternative
OpenHAB is the older, quieter cousin of Home Assistant. It runs on the JVM, ships a mature Z-Wave binding, and its Rules DSL plus Blockly editor is a nice middle ground between HA’s YAML and Node-RED’s flows. Setups that started on OpenHAB in the 2010s often stay there, because the migration cost is real and OpenHAB does its job well.
Where it falls short: Community integration count is smaller than HA’s. Documentation quality varies more than it should.
Pricing:
- Free: fully open source
- Paid: none
Platforms: Linux, Windows, macOS
Download: OpenHAB downloads
Bottom line: The pick if you have OpenHAB experience or a strong preference for a JVM-based stack.
5. Domoticz — best lightweight controller
Domoticz is the pick when the controller has to run on tiny hardware. A Pi Zero 2 W runs Domoticz well; a full HA install on the same hardware sweats. The trigger and event model is simpler, protocol support is decent (RFXCOM, Z-Wave, MQTT), and the whole system fits under 100 MB of RAM.
Where it falls short: UI feels a decade old. Community is a fraction of HA’s. Getting help with an obscure device takes longer.
Pricing:
- Free: fully open source
- Paid: none
Platforms: Linux, Windows, macOS, Pi
Download: Domoticz downloads
Bottom line: The pick if you are running on constrained hardware and the setup is modest.
6. Hubitat Elevation — best local-first commercial hub
Hubitat Elevation is the commercial answer to “I want the ease of a SmartThings hub without the cloud.” Everything runs on the box in your closet, the Rule Machine app expresses complex conditional automations in a UI, and the device compatibility list covers most of the Z-Wave, Zigbee, and Matter market. If you have a Ring or Google Nest household and you want to consolidate without moving to HA, this is where people land.
Where it falls short: Not open source. Hardware cost. The UI is functional, not modern.
Pricing:
- Free: none
- Paid: one-time hardware cost, no monthly fee
Platforms: Standalone hub, managed from any browser
Download: Hubitat
Bottom line: The pick when you want local automations without maintaining the stack yourself.
7. Homey Pro — best polished commercial hub
Homey Pro is the design-forward alternative to Hubitat. Homey Flow, the visual automation editor, is one of the best in the space. The hardware speaks Zigbee, Z-Wave, Matter, Thread, 433 MHz, infrared, and Bluetooth. If the household includes someone who is not going to touch a YAML file, Homey Pro is the setup that stays welcome in the living room.
Where it falls short: Not open source, and the hardware is not cheap. Advanced logic still ends up in the HomeyScript sandbox, which is JavaScript.
Pricing:
- Free: none
- Paid: one-time hardware cost
Platforms: Web UI, iOS, Android
Download: Homey Pro
Bottom line: The pick for a household that wants sensor automations without the DIY smell.
8. Zigbee2MQTT — best Zigbee bridge for any controller
Zigbee2MQTT turns a $30 USB Zigbee coordinator into a bridge that publishes every device event to MQTT. Any controller in this list that speaks MQTT (all of them do) then gets first-class Zigbee support, without paying the tax of a proprietary Zigbee hub. The device database is enormous; if someone on the internet has flashed the device, it is probably in the list.
Where it falls short: Not an automation engine. Adds an MQTT broker to the stack, which is one more thing to run.
Pricing:
- Free: fully open source
- Paid: none
Platforms: Linux, Windows, macOS
Download: Zigbee2MQTT docs
Bottom line: The pick when you want broad Zigbee support without buying a vendor hub.
How to pick the right combination
The XDA piece’s real point is that “sensor triggers your action” beats “schedule triggers your action” every time. Match the controller to how you want to build:
- Starting from scratch, want the easiest DIY path: Home Assistant on a Raspberry Pi, plus a USB Zigbee stick and Zigbee2MQTT. This covers 90% of what a house needs.
- Home Assistant is already running and the automations are getting hairy: Add Node-RED as an add-on. Move the ugly ones over.
- Not a tinkerer but wants local execution: Hubitat Elevation or Homey Pro. Both keep automations off the cloud.
- The interesting sensor does not exist yet: ESPHome plus a $6 ESP32 module.
- The old Java stack still works: OpenHAB. No reason to migrate for its own sake.
FAQ
Why sensor triggers instead of schedules? Schedules run whether you are in the room or not, whether it is a holiday or not, whether the sun rose an hour late because it is winter. Sensors describe the actual state you want to react to.
What sensors are worth starting with? Contact sensors on external doors, motion sensors in common rooms, and one presence sensor at the entryway. Those three together cover most of the useful “someone is home, awake, in this room” logic.
Is Home Assistant hard to install? Not any more. Home Assistant OS on a Raspberry Pi 4 or 5 is an SD-card flash and one screen of setup. Docker installs are only marginally harder.
Do I need Zigbee, Z-Wave, or Matter? For a homelab in 2026, Zigbee gives you the widest device selection at the lowest cost, Z-Wave is more expensive but has stronger range, and Matter is the future story but the device catalog is still catching up. Start with Zigbee unless a specific device forces the choice.
Can I run these automations if my internet is down? Yes, on Home Assistant, Node-RED, ESPHome, OpenHAB, Domoticz, Hubitat, and Homey Pro. All are local-first. Only the mobile-app “away from home” access requires connectivity.
