ratgdo Review: Features, Install Difficulty & Alternatives

ratgdo — Rage Against The Garage Door Opener — is the open-source community’s answer to myQ. If you own a LiftMaster or Chamberlain Security+ 2.0 garage door opener and you’ve gotten tired of myQ subscriptions, the rolling cloud outages, the in-vehicle integration paywall, or just the philosophical objection to your garage door being someone else’s cloud problem, ratgdo is the canonical fix. This review covers what ratgdo actually is, where it shines, where it falls short, and the alternatives — including a section on the gap Proxly fills.

This article is aimed at the Home Assistant / HomeKit crowd. If you’re not already running a home-automation host and the words “MQTT broker” don’t mean anything to you, ratgdo probably isn’t your starting point — skip to the alternatives section.

About ratgdo

ratgdo started as a community-led hardware project to bypass myQ’s increasing cloud and subscription dependencies on LiftMaster and Chamberlain Security+ 2.0 openers. The project name is a deliberate jab at the situation it was created to solve: garage doors that used to “just work” with a clicker now require an app, an account, a cloud round-trip, and (since 2023) a subscription if you want them to work with your car.

The project’s premise is straightforward — Security+ 2.0 openers have a wall-control port that uses a well-understood protocol. A small ESP8266 (later ESP32) microcontroller can be wired to that port to send open/close commands and read door state. The firmware exposes the door via standard home-automation protocols (Home Assistant, HomeKit, MQTT). No cloud. No subscription. No internet dependency for control.

Hardware has gone through several revisions:

• v1 / v2 (~2022-2023): community-assembled PCBs, ESP8266-based, requires manual flashing.
• v2.5 (~2024): the standard reference design as of this writing. Better Security+ 2.0 protocol support, faster response, status reporting.
• Konnected ratgdo (commercial): a productized version of the v2.5 design sold by Konnected (a small commercial vendor). Pre-assembled, pre-flashed, easier install. Slightly more expensive but closer to a turn-key product.

The ratgdo community is centered on the project’s GitHub and the Home Assistant community forum. Support is responsive — bug reports and protocol questions get answered, often by the original maintainer.

Overview of ratgdo variants

ratgdo v2.5 (open-source DIY)

• Cost: ~$50 for the PCB + components, plus an ESP32 if not included.
• Assembly: requires soldering or pre-assembled PCB purchase.
• Firmware: requires flashing via ESPHome or the prebuilt ratgdo firmware.
• Best for: users comfortable with electronics, wanting maximum control and zero markup.

Konnected ratgdo (commercial)

• Cost: ~$80-$100.
• Assembly: pre-assembled, pre-flashed.
• Firmware: ships with ratgdo firmware loaded; Home Assistant and HomeKit integrations work out of the box.
• Best for: users who want the ratgdo experience without flashing or assembly.

Both variants use the same underlying design and provide the same functional capabilities. The choice is purely about how much DIY you want to do.

ratgdo review

Features

• Local-only control of LiftMaster / Chamberlain Security+ 2.0 garage door openers via the wall-control port
• Door state reporting (open / closed / opening / closing) read directly from the opener
• Optional motion / obstruction reporting on some configurations
• Home Assistant integration (first-class; the official integration is well-maintained)
• HomeKit integration via ESPHome HomeKit support or HomeBridge bridge
• MQTT support for any MQTT-aware system
• ESPHome support for users who want to manage firmware via the ESPHome dashboard
• No cloud account required, no subscription, no internet dependency for control
• Local-network response time typically under 1 second for open/close commands

What ratgdo does NOT include:

• A native app from ratgdo (no ratgdo-branded mobile app — control happens through Home Assistant, HomeKit, or whatever client speaks to it)
• Built-in hands-free arrival (the user has to build it in Home Assistant or HomeKit Automation)
• Gate-opener support (Security+ 2.0 is a garage-door protocol; gate operators use different signaling)
• Out-of-box support for non-LiftMaster/Chamberlain openers
• Tag-based or in-car triggering (no Tag, no Bluetooth proximity, no key fob)

Pricing

• Open-source v2.5 board: ~$50 (PCB kit + components)
• Konnected ratgdo (commercial): ~$80-$100
• Subscription: none, ever
• Total cost of ownership over 10 years: $50-$100, plus replacement if hardware fails

For comparison, myQ subscription pricing for the same garage door over 10 years runs $179-$299 (Tesla-tier) or higher with additional in-car integrations. ratgdo’s economics are strongly in favor of the buyer who’s willing to do the install.

Pros

• Local-only, no cloud, no subscription. The entire ratgdo design philosophy is “your garage door should work without the internet.” It does.
• First-class Home Assistant integration. If you run HA, the integration is one of the best maintained third-party options in the entire HA ecosystem. Door state, open/close, motion, obstruction — all exposed cleanly.
• HomeKit support. Via ESPHome or HomeBridge. Once configured, the door appears as a native HomeKit accessory with proper state reporting.
• Bypasses myQ entirely. The whole point. No more myQ app, no more myQ subscription, no more myQ outages affecting whether the garage opens.
• Status reporting is genuinely accurate. Because the board reads the opener’s actual state through the wired connection, the reported state matches reality — not “I sent the open command 4 seconds ago so the door is probably open” guesswork.
• Strong community. The maintainers are responsive. Bug fixes ship. Protocol changes (when LiftMaster updates the opener firmware) get reverse-engineered and patched.
• Cheap. $50-$100 one-time cost beats almost any commercial alternative on lifetime cost.

Cons

• DIY install is required. Opening the opener housing, identifying the wall-control terminals, wiring the board. For someone who’s never done this, it’s a barrier. For someone who has, it’s 30-60 minutes.
• No hands-free arrival out of the box. ratgdo controls the door. It doesn’t open the door automatically when you arrive home. To get hands-free behavior, you have to build it in Home Assistant with a phone geofence automation — and that automation is subject to the same ~50m OS geofence floor that limits Tesla Garage Auto-Open and HomeKit Automation. Long driveways still misfire.
• Security+ 3.0 is the hard wall. ratgdo’s cleanest, fullest support is on Security+ 2.0 (the yellow-learn-button generation). It also supports Security+ 1.0 and offers a dry-contact mode for many older or non-Chamberlain openers, but those paths report more edge cases. The line it cannot cross is Security+ 3.0 — that protocol leaves the wall wires power-only and locks out every wired controller (see the Security+ 3.0 section above). Driveway gate operators are out of scope regardless of generation.
• No gate support. This is a garage-door-only project. Driveway gate operators use different protocols and signaling, and ratgdo doesn’t target them.
• Requires a home-automation host. ratgdo by itself doesn’t have a useful UI. It needs Home Assistant, HomeKit, or an MQTT client. Households without one of those will find ratgdo’s appeal limited.
• Flashing firmware is non-trivial for first-timers. ESPHome installation, USB-serial drivers, YAML configuration — these are not hard for an embedded-systems person but they are unfamiliar to most consumers.
• Protocol drift risk. LiftMaster occasionally updates the opener firmware in ways that affect the wall-control protocol. The community has caught and fixed each of these so far, but there’s an inherent dependency on continued reverse-engineering effort.
• Security+ 1.0 support can be inconsistent. ratgdo supports older Security+ 1.0 openers as well as 2.0, but owners report the 1.0 path is less polished — intermittent ghost door-state (the board reporting a state the door isn’t in) and, in some firmware combinations, a sent close command that opens the door instead. Other owners report 1.0 working perfectly on the same hardware, so it appears to be a firmware-version and install-specific interaction rather than a universal fault. If your opener is Security+ 1.0, expect to verify wiring carefully and possibly try a couple of firmware builds.

A note on Security+ 3.0 — the moving target

This is the single most important compatibility fact for anyone shopping ratgdo in 2026, and it is not specific to ratgdo.

Chamberlain/LiftMaster’s newest protocol, Security+ 3.0, changes the architecture that ratgdo, Konnected, OpenGarage, and similar wired controllers rely on. On Security+ 2.0 and earlier, the wall-control wires carry both power and data, which is exactly what those boards tap into. On Security+ 3.0, the two wall-button wires carry power only — accessory communication moves to encrypted Bluetooth Low Energy, and paired devices are verified against Chamberlain’s servers. Because the change is in the hardware and the encrypted protocol, it cannot be undone with a firmware update on the controller side, and no third-party wired controller — ratgdo included — can talk to a Security+ 3.0 opener over the wires.

What this means in practice:

• Identify your opener before buying anything. Security+ 2.0 openers have a yellow learn button and remain ratgdo-compatible. If your opener shipped recently and uses Security+ 3.0, ratgdo, Konnected’s board, and OpenGarage will not work with it as designed.
• The community escape hatch is well-precedented but DIY. Across the smart-garage forums, the consensus Security+ 3.0 workaround is the same: take a working OEM remote (the only thing that can still talk to a locked-down opener), solder a relay across its button contacts so a controller can “press” it electrically, and add a separate reed or tilt sensor for door state — since the wires no longer carry state data either. It works, but it is a hand-built project, not a product.

Proxly’s own architecture wires into the opener’s existing wall-button input, the same dry-contact assumption ratgdo and the others make, so the same Security+ 3.0 caveat applies — on a Security+ 3.0 motor where that input is no longer a simple dry contact, the wall-button approach does not bypass the lockout. We are being straight about that rather than over-claiming. For the openers most households actually have today, the dry-contact approach is well within scope.

ratgdo vs Proxly

ratgdo and Proxly aim at different problems for different audiences, which is the most useful frame for the comparison.

ratgdo’s primary problem is: “I have a LiftMaster Security+ 2.0 opener, I run Home Assistant, I want local-only control without paying myQ subscriptions.” ratgdo solves that problem extremely well.

Proxly’s primary problem is: “I want my gate or garage to open automatically when I arrive home, with no app, on any car, on any opener, with no subscription.” That’s a different problem with a different solution shape.

Feature	Proxly	ratgdo
Hands-free arrival (no app, no button)	Yes (Tag-based, dedicated GPS)	No (requires HA automation + phone geofence — bound by ~50m floor)
Works on any opener brand and protocol	Yes (dry-contact universal)	Partly (best on Security+ 2.0; dry-contact mode for some others; not Security+ 3.0)
Works on driveway gates	Yes	No (garage doors only)
Plug-and-play install (no opener housing modification)	Yes	No (requires opening opener housing, wiring terminals)
No home-automation host required	Yes	No (requires Home Assistant, HomeKit, or MQTT host)
Free app for remote open/close, schedules, notifications	Yes	No (uses HA / HomeKit as UI)
Status reporting (door state)	Yes	Yes
No subscription	Yes	Yes
Open-source firmware / hardware	No	Yes
Lifetime cost	One-time hardware	One-time hardware (lowest in category)
Anti-theft protection on the in-car trigger	Yes (Tag-side anti-theft)	N/A (no in-car device)

What ratgdo does better

• Lowest-in-category lifetime cost for households with one Security+ 2.0 opener and an existing HA / HomeKit setup. $50-$100 one-time and nothing else, forever.
• Open-source. The hardware design, the firmware, the protocol implementation — all public. Auditable, modifiable, forkable.
• First-class Home Assistant integration. For HA-native households, ratgdo plugs into the existing dashboards, automations, and notifications without any glue work.
• Local-only purity. No cloud, no internet dependency, no third-party services in the path. Some buyers value this above anything else.

What Proxly does better

• Hands-free arrival as a primary feature, not a DIY automation. The Tag has its own GPS and isn’t bound by the ~50m phone-geofence floor. The door opens when you actually approach, not when your phone happens to cross an OS-imposed boundary.
• Plug-and-play install. No opening the opener housing, no wiring three terminals, no firmware flashing. Plug the Hub into the opener’s existing wall-button input.
• Works on any opener and any car. Security+ 1.0, Security+ 2.0, Genie, gate operators, even older non-rolling-code openers via dry-contact. Any car with a windshield.
• Gate AND garage. Multi-opener households with a property-line gate and a garage at the house get both off one Hub.
• No home-automation host required. Proxly works on its own. Households without Home Assistant — which is most households — get hands-free arrival without first setting up HA.
• Free Proxly app for remote control, schedules, and notifications. Built-in. Not delegated to HA.

Why Proxly fits the cases ratgdo doesn’t

If you’re a Home Assistant power user with a Security+ 2.0 opener and you want local-only control, ratgdo is genuinely excellent and probably the right choice. We’re not trying to talk you out of it.

If your situation looks more like one of these, Proxly is the cleaner fit:

• You want the garage or gate to open automatically when you arrive — without writing automations or maintaining a HA instance for it
• Your opener isn’t Security+ 2.0, or isn’t LiftMaster/Chamberlain
• You have a driveway gate (not just a garage), or both
• You don’t run Home Assistant and don’t want to start
• You drive an EV that doesn’t have HomeLink and want a HomeLink alternative instead of paying $300+ for the retrofit just to get auto-open working

Proxly is built for hands-free arrival as the default, on any car, any opener, with no app required at the moment of arrival, no subscription, and no DIY install. Learn more at getproxly.com.

Frequently asked questions

Is ratgdo free?

ratgdo is open-source, so the firmware and the PCB designs are free. The hardware itself costs money — roughly $50 if you buy the open-source v2.5 board kit and assemble/flash it yourself, or ~$80-$100 if you buy the commercial successor (Konnected ratgdo) which arrives pre-assembled and pre-flashed. There are no recurring subscription fees.

What openers does ratgdo work with?

ratgdo is designed for LiftMaster and Chamberlain garage door openers that use Security+ 2.0 (the protocol myQ uses), and it also supports older Security+ 1.0 openers, though owners report the 1.0 path is less consistent. It wires into the opener’s wall-control port and emulates a wall-button + status sensor. It does not work with Security+ 3.0 openers — those moved accessory communication to encrypted Bluetooth and left the wall-button wires power-only, which locks out every wired third-party controller. It also doesn’t work with non-LiftMaster/Chamberlain brands or any driveway gate operator that uses different signaling.

Does ratgdo work with Security+ 3.0?

No. Security+ 3.0 is Chamberlain/LiftMaster’s newest protocol, and it changes the hardware: the two wall-button wires now carry power only, with accessory communication moved to encrypted Bluetooth Low Energy and paired devices verified against Chamberlain’s servers. ratgdo, Konnected’s board, and OpenGarage all rely on data over those wires, so none of them can talk to a Security+ 3.0 opener, and no firmware update fixes it. Security+ 2.0 openers (yellow learn button) remain compatible. The community workaround for 3.0 is to solder a relay across a working OEM remote’s button contacts and add a separate reed switch for door state — functional, but a DIY build rather than a product.

Does ratgdo require Home Assistant?

ratgdo doesn’t require Home Assistant specifically, but it does require some local home-automation host to talk to. The most common configurations are Home Assistant (via the official integration), HomeKit (via ESPHome with HomeKit support or a HomeBridge bridge), or MQTT (to any MQTT-aware system). Without one of those, the board doesn’t have a useful UI of its own.

Is ratgdo hands-free? Does it open the garage automatically when I arrive home?

No — not out of the box. ratgdo provides local control of the garage door but does not include hands-free arrival as a built-in feature. To get hands-free behavior, you have to build it yourself in Home Assistant using phone geofence automations (or HomeKit Automation, which has similar geofence behavior). Both use OS-level geofence APIs with a ~50m radius floor, which is the same limitation Tesla Garage Auto-Open and Apple’s HomeKit Automation are subject to.

How hard is it to install ratgdo?

Install requires opening the garage door opener housing, identifying the three Security+ 2.0 terminals on the wall-control port, wiring the ratgdo board to them, and either flashing firmware yourself (if using the open-source kit) or plugging in the pre-flashed commercial board. For someone comfortable with basic electronics — using a multimeter, stripping wires, following a wiring diagram — it’s a 30-60 minute job. For someone who’s never wired anything before, it’s harder and the community recommends asking for help in the forums first.

ratgdo vs myQ — which should I choose?

myQ is the official LiftMaster/Chamberlain platform — turn-key but cloud-dependent and increasingly behind subscriptions for in-vehicle integrations. ratgdo is the local-only DIY alternative — no cloud, no subscription, full Home Assistant / HomeKit / MQTT control, but you have to install hardware and own a home-automation host. If you already run Home Assistant and want local-only control without paying myQ subscriptions for car integrations, ratgdo is the better choice. If you want a turn-key consumer experience and don’t have Home Assistant, myQ is the easier path. Both are app-based, not hands-free; for hands-free arrival, neither is a complete solution.

What are the best alternatives to ratgdo?

If you’re shopping ratgdo for a specific reason, the alternative depends on that reason. For local-only control without the DIY install — Konnected Garage Door Opener Add-On (pre-assembled, $80-$100, plug-and-play) is the closest commercial cousin. For HomeKit-first households without HA — Meross Smart Garage Door is a turn-key HomeKit option (Wi-Fi only, but cheap and works). For hands-free arrival on top of any opener — Proxly is built for hands-free as the primary feature, with the Tag’s own GPS bypassing the ~50m phone geofence floor and a dry-contact universal interface that works on any opener (not just Security+ 2.0). Learn more at getproxly.com.

---

Last updated: 2026-06-04. This review reflects information available at the time of writing and is presented to the best of our knowledge from publicly available sources, the project’s GitHub repository, and community forum threads. Hardware pricing, firmware compatibility, opener protocol support, and product specifications may change after publication; please verify current details directly with the project maintainers (paulwieland/ratgdo on GitHub), Konnected for the commercial board, and the relevant opener manufacturer before purchasing. Proxly is an independent product and is not affiliated with, sponsored by, or endorsed by the ratgdo project, Konnected, Inc., The Chamberlain Group LLC, LiftMaster, or any other company mentioned in this article. All product names, logos, and trademarks are the property of their respective owners. If you spot an inaccuracy or have a correction, please email getproxly@gmail.com — we update reviews as new information becomes available.