How to add driveway arrival detection locally
Detect when you arrive at your driveway using local hardware and Home Assistant, with practical notes for HomeKit and Hubitat users.
On this page
Detecting when you arrive at your driveway is a common smart home use case. It can turn on lights, open a gate, or send a notification. (To wire up the door itself locally, see the best local-first garage door controllers.) While many cloud cameras do this, building a local-first solution with Home Assistant, HomeKit, or Hubitat gives you more control, privacy, and reliability. This guide walks through the realistic building blocks.
Start with a motion or presence sensor at the driveway, add a camera with Frigate or on-device detection to confirm it was a car, and run the automation in Home Assistant. HomeKit is a clean option for Apple households, and Hubitat suits people who want native Zigbee and Z-Wave.
Use a motion or presence sensor for detection
The simplest trigger is a motion sensor near the driveway. Both Zigbee and Z-Wave have good battery sensor options, and Matter-over-Thread sensors are increasingly common.
The Matter pick is the Aqara Motion and Light Sensor P2, a Matter-over-Thread device (it needs a Thread border router and a Matter controller). It also reports an illuminance value, which is handy for “only at night” automations. I haven’t run the P2; the pick is based on the spec sheet and what other owners say about it. If you prefer Zigbee, sensors like the frient Motion Sensor Pro (Zigbee, also reports light and temperature) work well once paired to a Zigbee coordinator.
Outdoors, plain PIR motion sensors are weather-limited and prone to false triggers from animals or passing cars. For more reliable detection, pair motion with another signal: a beam-break sensor across the driveway, a phone-based geofence/GPS trigger in the Home Assistant Companion app, or a camera with on-device object detection (see below).
The main tradeoff with battery sensors is maintenance: coin cells and AA batteries need periodic replacement, and cold weather shortens their life.
Use a camera or doorbell for visual confirmation
A motion sensor tells you something moved; a camera tells you what. For local-first setups, look for cameras with RTSP/ONVIF streams or strong Home Assistant integration so footage stays on your network.
The Reolink Doorbell (PoE/Wi-Fi) exposes RTSP and integrates with Home Assistant, and many Reolink cameras do on-device person/vehicle detection you can use as triggers. Frigate (an add-on for Home Assistant) can run local object detection on almost any RTSP camera, letting you fire an automation specifically on “car detected in driveway.” Frigate is built around the expectation that a real object detector is attached to the machine running it: an Intel iGPU through OpenVINO, a Hailo-8 or 8L module, or an NVIDIA GPU, with a Coral now recommended mainly for low-power builds. Budget for that hardware alongside the camera; how to build a Frigate NVR from scratch walks through the options. The same approach works for detecting package deliveries locally.
If you want a simple visual cue when someone arrives, a Philips Hue light or lightstrip can flash or change color as an indicator. (Most Hue bulbs are Zigbee and run through the Hue Bridge or a Zigbee coordinator; newer generations also carry Thread. Either way, a bulb is not a sensor itself.)
The downside of cameras is storage and bandwidth. Local recording to an NVR, NAS, or SD card keeps data private but requires setup and disk space.
Automate with Home Assistant, HomeKit, or Hubitat
Once you have a trigger, build the automation.
Home Assistant is the most flexible: when the trigger fires, turn on driveway lights, send an actionable notification, announce on a speaker, or kick off any other action. Combining triggers (motion AND camera vehicle detection AND after sunset) sharply reduces false positives.
HomeKit automations are simpler but capable: a Matter or HomeKit-compatible motion sensor can trigger lights or notifications through a Home hub (a HomePod or an Apple TV; iPads are no longer supported as hubs). Apple’s Home app handles the logic; the Shortcuts app can extend it.
Hubitat uses Rule Machine for complex logic and runs locally. It supports Zigbee and Z-Wave natively and joins Matter devices over Wi-Fi and Ethernet, so a Zigbee, Z-Wave, or Matter-over-Wi-Fi sensor works as a trigger. One caveat if you picked the Aqara P2 above: the standard C-8 Pro has no Thread radio, so a Matter-over-Thread sensor needs a separate Thread border router on the network before Hubitat can reach it at all. Hubitat’s newer Thread Special Edition C-8 Pro is listed with integrated Thread connectivity, so check which version you own.
A note on latency: local automation is generally fast. Mesh networks (Zigbee/Z-Wave/Thread) add a small hop delay, but it’s usually imperceptible for lighting.
Add a smart plug or switch for the output
To act on arrival, you need a controllable device. A Philips Hue Smart Plug can switch a lamp at the driveway, or a Sonoff Mini R4 (Wi-Fi/eWeLink, locally controllable) can drive a relay for a gate or floodlight. In Home Assistant you trigger these directly; no cloud round-trip is needed once they’re set up locally.
If you’re on HomeKit, you’ll need devices that are HomeKit- or Matter-compatible, or bridge non-native devices through Home Assistant.