What LiftMaster's myQ API Lockdown Means for Driveway Gate Owners

In late 2023, Chamberlain Group — the parent company of LiftMaster, Chamberlain, and the myQ app platform — shut off unauthorized third-party access to the myQ cloud API. Automations built with Home Assistant, Homebridge, and custom scripts stopped working. No migration path was offered. No official replacement API followed.

Most of the coverage at the time concentrated on garage door owners. The driveway gate picture is different, and in some ways more constrained.

What Chamberlain Closed

The myQ ecosystem routes commands from the app through Chamberlain’s cloud servers to the hardware installed at the garage or gate. Third-party developers had been calling this API endpoint directly via HTTP — reading status, triggering open and close — using reverse-engineered credentials. The Home Assistant myQ integration alone had hundreds of thousands of active users.

Chamberlain cited customer security and experience quality as the rationale for the closure. The effect was to push all remote access through the official myQ app. Basic open and close commands remain free. Activity history, automated routines, and smart-home-platform integration sit behind a subscription that runs roughly $10 per month.

Why Gate Owners Have Fewer Off-the-Shelf Workarounds

For garage door owners, an independent hardware alternative emerged: ratgdo, an open-source controller board that wires directly into Security+ 2.0 garage door openers through their internal serial bus. ratgdo talks to the opener’s control board at the protocol layer, bypassing the myQ cloud entirely. For a full breakdown of what ratgdo does and does not support, see our ratgdo review.

Driveway gate operators are a different category of hardware. LiftMaster’s commercial-grade gate operators — the swing-arm and slide-gate machines commonly installed on residential properties — do not expose the same serial bus. Their control boards accept dry-contact inputs on clearly labeled terminals: separate contacts for open, stop, and close commands. The myQ module wired to those terminals is a wireless relay sitting on top of that dry-contact layer, not integrated into the gate’s control board at the firmware level.

ratgdo does not support gate operator hardware. The serial-bus approach is specific to LiftMaster garage openers.

The dry-contact terminals, however, remain open to any controller. A Remootio Gen 3 or an iSmartGate wired to the same open and close terminals will operate the gate without any dependency on the myQ cloud. Neither requires a myQ account to function. For a direct comparison of those two options, see myQ vs Remootio for Driveway Gates.

Gate status — is it open or closed? — requires a separate sensor input, typically a magnetic contact or a limit switch output from the gate operator’s own board. Most dry-contact retrofit devices have a dedicated status input for exactly this purpose.

The Longer Pattern

Chamberlain is not the first manufacturer to restrict third-party access after establishing an installed base on informal openness. The sequence is consistent: release hardware with accessible APIs, allow an integration ecosystem to build up around them, then tighten access once penetration is sufficient. Subscription revenue provides the visible incentive.

For gate owners, the useful framing is not whether the decision was justified but whether the gate hardware itself still functions and whether a control path exists that does not depend on a commercial cloud.

The gate operator hardware is fine. LiftMaster’s commercial-grade swing and slide machines are built to industrial duty cycles and are largely insulated from software decisions. The dry-contact terminals on the control board have not changed, and any relay-output device can still trigger them.

The software dependency, by contrast, is structural. Any gate automation that requires a third-party commercial cloud — whether that is myQ, a competitor’s platform, or an app ecosystem — will inherit whatever business decisions that cloud makes. Hardware that wires directly to the gate’s dry-contact terminals sits below that layer and is not exposed to it.

For a foundation on how the underlying gate hardware works — control boards, limit switches, and what the dry-contact inputs actually do — How a Residential Gate Opener Actually Works covers the control board mechanics that apply across brands.

For the full myQ product picture — hardware generations, subscription tiers, and how the open/close workflow compares to alternatives — see myQ Smart Garage Hub Review.

---

FAQ

Did Chamberlain block all third-party access or just Home Assistant?

Chamberlain blocked the unofficial myQ HTTP API endpoint used by Home Assistant, Homebridge, and any custom automation that called it directly. The official myQ app was not affected. No official developer API was made available in its place, leaving integrators without an authorized alternative path.

Can I still use myQ with Home Assistant after the lockdown?

There is no officially supported path for Home Assistant to control myQ devices as of mid-2026. Community workarounds have appeared and disappeared as Chamberlain updates its app and back-end. Users who need reliable home automation control for gate hardware have generally moved to dry-contact retrofit controllers that do not depend on the myQ cloud.

Does the myQ API change affect LiftMaster gate operators specifically?

Yes. LiftMaster commercial-grade gate operators that used a myQ module for remote access lost third-party cloud integration on the same timeline as garage openers. The gate operator control board itself is unaffected. Its dry-contact open and close terminals accept any relay-output controller, independent of myQ or any other cloud service.