Best local first garage door controllers

If you’re building a local-first smart home, you’re probably running Home Assistant and want to avoid cloud dependencies wherever you can. The garage door is a good example: most off-the-shelf “smart” openers (Chamberlain/LiftMaster myQ being the obvious one) route control through the manufacturer’s cloud, which means latency, outages when your internet drops, and no guarantee the API stays open. The good news is that the best local-first garage controllers are inexpensive, and the strongest options all run ESPHome and talk directly to Home Assistant over your LAN.

One thing to get straight up front: the popular local garage controllers are Wi-Fi/ESPHome devices, not Zigbee or Z-Wave. That’s fine for a local-first setup, because ESPHome’s native API talks straight to Home Assistant with no cloud and no separate coordinator. Don’t expect to find a mainstream Z-Wave or Zigbee garage door opener controller worth recommending; the category is dominated by ESPHome-based boards.

How these controllers actually work

A garage controller doesn’t replace your opener. It wires in alongside it and does two jobs:

1. Triggers the door (open/close), either through a simple dry-contact relay across the wall-button terminals, or by speaking the opener’s own protocol.
2. Reports door state (open/closed/moving), via a hardwired magnetic/optical sensor or a tilt sensor on the door.

The “speaks the opener’s protocol” approach matters for Chamberlain/LiftMaster openers, which since the late 1990s use Security+ and Security+ 2.0, where a plain dry-contact relay won’t work reliably. Note the 2026 reality: the newest Chamberlain/LiftMaster openers ship with Security+ 3.0, introduced in November 2025 on models like the Chamberlain D1000 and LiftMaster 2220L. Security+ 3.0 doesn’t just lock the serial connection down, it removes it: the wall-button terminals now carry power only, and accessory communication moved to encrypted Bluetooth LE. There is no data line left for a third-party board to read, which is why ratgdo, Konnected and Tailwind all state plainly that they do not support it.

Identify your opener by its learn button, not by its age. Purple, red or orange means Security+ 1.0; yellow means Security+ 2.0; a round white button means Security+ 3.0 (2025 and newer). Security+ 1.0 and 2.0 openers remain fully controllable by the boards below. For a dumb opener with a simple terminal-block button, a dry-contact relay is all you need.

Local-First Garage Door Controllers for Home Assistant

ratgdo

The ratgdo32 is the open-source board that put local garage control on the map. It’s an ESPHome (Wi-Fi) device that speaks Security+ and Security+ 2.0 to Chamberlain/LiftMaster/Craftsman openers over the opener’s serial connection, so you get both control and accurate door-position feedback without a separate tilt sensor. It also supports dry-contact mode for non-Security+ openers. Once flashed with the ratgdo ESPHome firmware, it’s discovered automatically by Home Assistant and runs entirely on your LAN, even with the internet down. It’s the tinkerer’s pick: cheap, fully local, and well documented, but you do the wiring and flashing yourself. It does not work with Security+ 3.0 openers.

Konnected Smart Garage Door Opener (GDO blaQ / GDO White)

If you want the ratgdo approach as a finished, supported product, the Konnected Smart Garage Door Opener is the one to look at. It’s ESPHome-based and 100% local via the ESPHome native API; Home Assistant auto-discovers it once it’s on your Wi-Fi, no cloud account required. The GDO blaQ speaks Security+ / Security+ 2.0 over serial (the same idea as ratgdo, productized), while the GDO White (v2) uses a built-in optical sensor for door-state detection. Konnected is a “Works with Home Assistant” partner, which makes it the easiest local pick for people who don’t want to solder. Konnected says the same thing ratgdo does about the newest openers: no Security+ 3.0 support.

Tailwind iQ3

The Tailwind iQ3 is a more conventional retail controller that earns a place here because it exposes a documented local control API. There’s a community Home Assistant integration that uses it: you enter a local control key, and it creates Cover entities with state polled locally every few seconds, no cloud round-trip required for control. It’s a reasonable middle ground if you want a packaged product with app setup but still want local Home Assistant control. It also supports Apple HomeKit: you generate a native HomeKit setup code in the Tailwind app (Device Settings) and add it in Apple Home, which makes it one of the few packaged garage controllers that gets you both local HA control and direct HomeKit without bridging.

Door-state sensors (pair with a dry-contact relay)

If your opener is a basic dumb unit, you can build a fully local solution from a generic ESPHome relay plus a separate door-position sensor. A tilt or contact sensor such as the Zigbee ThirdReality Garage Door Tilt Sensor reports open/closed into Home Assistant; combine it with a relay across the wall-button terminals and you have local open/close plus status. This is more of a roll-your-own approach, but it’s cheap and works with almost any opener.

If you have a Security+ 3.0 opener

None of the serial-aware boards above will talk to a Security+ 3.0 opener, but you are not stuck with myQ either. The workaround is the same one people used before serial support existed: wire a relay across the button contacts inside a spare remote that is already paired to the door, so the relay simply presses the remote for you. OpenGarage documents this approach explicitly. Because the opener will not report anything back, pair it with a separate tilt or contact sensor for door position — the OpenGarage board suits this well, since it carries its own ultrasonic door-position sensor. Treat it as a workaround rather than real integration: if clean local control matters more to you than a new opener, a Security+ 2.0 unit is the easier target.

HomeKit and Hubitat notes

A quick correction worth making: speakers and smart displays (HomePod, HomePod mini, Echo) are HomeKit/Matter hubs and border routers, not garage door controllers — they don’t actuate your door. You still need one of the controllers above for that.

• HomeKit: ratgdo firmware has a HomeKit build, so a ratgdo can appear directly in Apple Home without Home Assistant in the middle. The Tailwind iQ3 also supports HomeKit natively — generate a setup code in the Tailwind app and add it in Apple Home. Konnected’s GDO can be exposed to HomeKit via Home Assistant’s HomeKit Bridge. A HomePod or Apple TV acts as the HomeKit hub for remote access; it is not the controller.
• Hubitat: Hubitat (e.g. the Elevation C8) is a local hub, but it has no native ESPHome support, so ratgdo/Konnected integrate most cleanly with Home Assistant. If you’re on Hubitat, the simplest local path is usually a dry-contact relay plus a Zigbee/Z-Wave tilt sensor that Hubitat supports directly.

Quick Verdict

For a fully local-first garage, the answer is an ESPHome-based controller, not Zigbee or Z-Wave:

• Best DIY / cheapest: ratgdo — fully local, Security+ aware, you do the flashing.
• Best packaged / easiest: Konnected Smart Garage Door Opener — Works with Home Assistant, ESPHome under the hood, no soldering.
• Best retail option with a local API: Tailwind iQ3 — packaged product, documented local control.

Before you buy, look at your opener’s learn button (purple/red = Security+ 1.0, yellow = Security+ 2.0, round white = Security+ 3.0). That single fact determines whether you need a serial-aware controller, a relay plus a door sensor, or the spare-remote workaround above.

Once the door is controllable, pair it with local driveway arrival detection so it can open automatically as you pull in. For everything else out there, the best smart home devices for garages and workshops covers sensors, lighting, and monitoring for the rest of the space.