11 Smart Garage Controllers Compared: Your Learn Button Decides (2026)

SwitchBot Garage Door Opener — the catch, per ecosystem ~$36 $35.99 list on SwitchBot's own US store, with an on-page promo code showing 25% off ($26.99) at time of research. Amazon listed it at $24.99, in stock, shipped by Amazon and sold by SwitchBot US. Multi-packs are $69.99 for two and $139.99 for four. Availability established from cart state — a cart/add POST returned status ok and accepted the item at 3599 cents — not from price display.

• ◐ Amazon Alexa: partial — Exposed as a switch rather than as a garage door device type. That has a consequence beyond cosmetics: Alexa's voice guardrails for garage doors — PIN entry and spoken confirmation — attach to the proper device type, and whether they apply to a device presenting as a switch is UNKNOWN and should not be assumed. A buyer who expects Alexa to ask for a PIN before opening their garage should verify it rather than rely on it.
• ◐ Google Home: partial — Same switch semantics as Apple and Alexa; no native garage-door trait was confirmed. Google's own garage-door handling, including its open-by-voice PIN requirement, is tied to the correct device type, so the protections a buyer might expect may not be present on a device presenting as a switch.
• ◐ Apple Home: partial — It connects, but it does not appear as a garage door. SwitchBot's own screenshots depict it in Apple Home as a plain on/off switch DECOUPLED from the contact sensor, so the tile cannot show true open or closed state, and owner reviews on SwitchBot's own product page report it surfacing as a switch ('I wish the app and Apple home will see it as a device rather than a switch', 2026-07-15) or as a lock ('It currently shows up as a lock (like door lock) instead of a garage door opener', 2026-04-30). Siri 'open garage' is reported to work, but you lose the garage-specific interface and Apple Home's own safety confirmation behaviour for garage doors. Recorded as partial rather than full for that reason: the connection is real, the device type is wrong.
• ◐ SmartThings: partial — Listed as supported and connects over Matter. SmartThings is reported to be the ecosystem most likely to have shipped support for the Matter 1.5 Closures cluster — but that improvement cannot reach this device, because the device does not EXPOSE closures. It presents as a switch, so the ecosystem being ready makes no difference here. This is the sharpest illustration of the gap between 'Matter certified' and 'Matter garage support'.
• ✓ Home Assistant: works — The one ecosystem that treats this as an actual garage door, and it does so without a hub and without the cloud. Home Assistant's own integration documentation lists 'Garage Door Opener' among the devices that receive COVER entities, and states that a SwitchBot hub is not required — so Home Assistant gives it the garage-door abstraction that every Matter ecosystem withholds. Two catches: it needs working Bluetooth on the Home Assistant host with BLE range to the garage, which is a real constraint for a detached or distant garage; and taking the Matter over Wi-Fi route into Home Assistant instead would yield only a switch, so the local Bluetooth path is the one that matters. Worth noting the irony plainly — the platform Chamberlain blocked is the one that handles this product correctly.

Connection: Matter · Wi-Fi · Bluetooth · Hub for full use: Yes (No SwitchBot hub is required. The device joins 2.4 GHz Wi-Fi directly — 2.4 GHz only — with Bluetooth as a fallback control path, and the Matter path does not need a SwitchBot hub either because the underlying relay is a native Matter-over-Wi-Fi device. It additionally acts as a Bluetooth repeater for other SwitchBot BLE devices. READ THE MATTER LISTING CAREFULLY THOUGH: matter is recorded in protocols because the device genuinely holds a Matter certification, but it certifies as an On/Off Switch, not as a garage door or closure device type. That distinction is the whole story of this product and is spelled out in theCatch.) · Works offline: Partly — some of it keeps working without the internet and some of it does not

Full sourced profile for SwitchBot Garage Door Opener →

Meross Smart Wi-Fi Garage Door Opener (MSG100) — the catch, per ecosystem ~$49.99 $49.99 for the US model MSG100HK-US, read from Meross's own store on 2026-08-08. Never treated as a live price.

• ✓ Amazon Alexa: works — Works through Meross's servers talking to Amazon's. Two things to know. Amazon requires a spoken voice PIN to OPEN a garage door while closing is unrestricted — that is Alexa's rule for garage doors, not a Meross limitation, and it is a safety feature rather than a defect. And because the connection runs between two companies' servers, it stops working when your internet does.
• ✓ Google Home: works — Works through cloud-to-cloud account linking. As with Alexa, Google requires secondary user verification — a PIN — before opening a garage door by voice, per Google's own developer documentation, while closing needs none. Cloud-routed, so it fails in an internet outage.
• ✓ Apple Home: works — Native HomeKit — a real accessory in the Home app with Siri and CarPlay, not a cloud bridge, and the clearest single answer to Chamberlain having removed HomeKit from myQ. BUT YOU CAN BUY THE WRONG BOX, and this is the most consequential purchasing trap in the record: Meross also makes a NON-HomeKit MSG100, sold on Amazon under a near-identical listing explicitly titled '(Non HomeKit Versions)'. Every SKU on Meross's own store carries an HK suffix, so buying direct is safe; buying on Amazon requires reading the variant title carefully. A buyer choosing this product specifically to escape myQ's HomeKit removal can end up with a box that has no HomeKit at all. Remote access additionally needs an Apple home hub, which is Apple's requirement rather than Meross's.
• ◐ SmartThings: partial — An official cloud-to-cloud linked service exists, but state synchronisation is chronically unreliable and has been for years. If the door is moved by anything other than SmartThings — the wall button, a remote, the Meross app — SmartThings frequently fails to update, which silently breaks any automation keyed to door state. SmartThings support has attributed it to expired callback tokens, and the fix is to unlink and relink, which destroys your existing automations. Reports run from 2023 through February 2026 with no resolution. ALSO DO NOT GENERALISE ACROSS THE FAMILY: Meross claims SmartThings for the MSG100 but not in the MSG150's copy.
• ◐ Home Assistant: partial — There is NO official Home Assistant integration — the page one would live at does not exist, and 'meross' appears nowhere in Home Assistant's own code. Meross never mentions Home Assistant in its own materials either, so nothing here is a route the maker supports. The community option, krahabb's meross_lan, is well maintained and genuinely runs on your own network, presenting the MSG100 and MSG200 as a garage door. Two catches: even that local route needs a device key taken from your Meross account, so it is not server-free to set up; and the rival community project is server-only, with its own maintainer warning that Meross throttles heavy users. We call it partial because a well-supported community project is not a supported integration.

Connection: Wi-Fi · Hub for full use: Yes (No hub or bridge — the device joins 2.4 GHz Wi-Fi directly (2.4 GHz only, no 5 GHz) and HomeKit pairing is native rather than cloud-bridged. ONE CAVEAT THAT IS APPLE'S RULE, NOT MEROSS'S: remote HomeKit access requires an Apple home hub (HomePod or Apple TV), which Meross states in its own FAQ — 'the Home app can NOT control your device remotely unless you set up a Home Hub in your home as required by Apple.' Note also that the genuinely local Home Assistant path still requires a device key extracted from your Meross cloud account, so 'no hub needed' is true while 'no cloud needed' is not.) · Works offline: Not checked — we have not established whether this keeps working without the internet

Full sourced profile for Meross Smart Wi-Fi Garage Door Opener (MSG100) →

Genie Aladdin Connect Smart Garage Door Controller — the catch, per ecosystem ~$50 $49.99 on Genie's own store, re-verified 2026-08-12 and in stock ('In Stock! Usually ships within 24 hours'), unchanged from the previous read. SKU 42869R for kit model ALKT2-R2. The additional door position sensor is a separate purchase. Never treated as a live price.

• ✓ Amazon Alexa: works — Two live skills and a well-supported path. Opening by voice requires a spoken PIN, which is Amazon's rule for garage doors rather than a Genie limitation. It routes through servers, so it stops with your internet. Amazon Key In-Garage Delivery is separately supported, announced 2023-08-24, and is Prime-only with ZIP-code eligibility — noting honestly that Amazon's own compatibility page would not open for us, so that claim rests on Genie's page plus corroborating search results rather than on Amazon's own current statement.
• ✓ Google Home: works — Works through Works-with-Google account linking under the name 'Genie Smart Garage'. Opening by voice requires a PIN and, unlike some implementations, it cannot be disabled — that is a safety feature rather than a defect, but it is worth knowing before you buy if you expected frictionless voice opening. Cloud-routed and fails in an outage.
• ✗ Apple Home: doesn't work — No native Apple Home support, and — contrary to a widely repeated premise — no evidence that a HomeKit-enabled model ever shipped, so this is recorded as an absence rather than as a removal with a date. Genie's own 23-partner list includes 'Siri Shortcuts' but not Apple Home; the two are not equivalent, and Siri Shortcuts means running an app action by voice, not an accessory in the Home app with automations, hub access or sharing. Genie's support position is that there is no time frame for adding HomeKit. Apple Home access requires third-party Homebridge or HOOBS plugins.
• ✓ SmartThings: works — Works-With-SmartThings certified, announced 2021-01-21, and the strongest of the mainstream integrations here. It has also quietly become the community's recommended bridge INTO Home Assistant, since Genie routes Home Assistant users through SmartThings rather than offering a direct free path. Cloud-to-cloud, so it fails in an internet outage, and it inherits any future SmartThings platform changes.
• ◐ Home Assistant: partial — The most unusual arrangement in this category. Genie changed how its service works in January 2024 and broke the community integration; Home Assistant's own version failed to load in release 2024.7, and the rewrite needed sign-in credentials ordinary users could not obtain. The integration was then restored — and is now maintained by a GENIE EMPLOYEE as its code owner, built on a toolkit Genie publishes. The catch is what that restoration costs: Home Assistant's own documentation states it requires 'an active Home Assistant Cloud subscription, since the integration authenticates through it'. So the honest description is not 'removed' and not 'restored' but something in between — broken by the maker changing its own plumbing, then brought back under the maker's control behind a paid third-party subscription. It works through Genie's servers, so there is no local path. We call it partial for exactly that reason.

Connection: Wi-Fi · Hub for full use: Yes (No hub. The door control module joins 2.4 GHz Wi-Fi directly and itself acts as the hub for the wireless door position sensor: Genie's own installation steps pair a Door Position Sensor to the powered 'Door Control Hub', and Genie sells an 'Aladdin Connect Door Position Sensor (for 2nd and 3rd doors)' separately, so one module covers up to three doors. ⚠ Genie's own page also states 'The Door Position Sensor (ALDPS-R) is not compatible with this model.' — so at least one sensor part number in that family will NOT work here. Both statements are Genie's, on the same page; check the part number before buying a second or third sensor. 2.4 GHz only, and Genie is unusually explicit about it: 'Your door control module is only compatible on 2.4 GHz networks... The door control module is not compatible with 5 GHz networks.' Its FCC filing authorises 2412–2462 MHz only, with no 5 GHz band on any document, which independently confirms it. Bluetooth hardware appears in the FCC paperwork but no Genie document describes any Bluetooth control, so we record its role as setup or an internal sensor link with the exact function unknown. Every platform connection runs between Genie's servers and the platform's; nothing documents a way to reach it on your own network.) · Works offline: Not checked — we have not established whether this keeps working without the internet

Full sourced profile for Genie Aladdin Connect Smart Garage Door Controller →

ratgdo32 — the catch, per ecosystem ~$62 $62.00 for the ratgdo32 (SKU 32k) on the vendor's own store at time of research. The ratgdo32 disco (SKU 32disco, $94.00) is the same garage control plus a laser vehicle-presence sensor, a beeper with adjustable close delay, a speaker and an aimable mount. Prices and stock read from the store's own product JSON rather than rendered marketing copy.

• ✗ Amazon Alexa: doesn't work — No native support, stated plainly by the vendor's own FAQ: 'we don't support them natively.' The only route is Home Assistant as middleware, and per Home Assistant's own documentation that leg requires either a paid Nabu Casa subscription or a manual Amazon Developer plus AWS Lambda setup with Home Assistant publicly exposed over HTTPS. Either way it reintroduces both a cloud dependency and a recurring cost — which defeats the entire reason to buy this device. Recorded as none rather than partial because there is no vendor-supported path at all.
• ✗ Google Home: doesn't work — Same as Alexa: no native support per the vendor's own FAQ, Home Assistant as the only middleware route, and the same cloud-and-subscription cost that negates the product's purpose. One additional detail from Google's side: Home Assistant's documentation notes that covers of device type door, garage or gate are treated as secure devices and 'cannot be opened by Google Assistant unless a secure_devices_pin code is set up' — closing needs no PIN, opening requires a spoken one.
• ✓ Apple Home: works — Genuinely native and genuinely rare — the homekit-ratgdo32 firmware implements HomeKit Accessory Protocol on the board itself, and its README states it works 'over your local network using HomeKit… It requires no supporting infrastructure such as Home Assistant, Homebridge, MQTT, etc.' No bridge, no hub, no cloud. Three catches. First and most important, this firmware is MUTUALLY EXCLUSIVE with the ESPHome build, so choosing Apple Home means giving up the Home Assistant path on that board. Second, HomeKit itself has no stop action — the README says so plainly, 'there is no _stop_ command' — but the firmware adds one back as an optional extra HomeKit control on the ratgdo32 boards specifically (it is not offered on the older v2.5 boards). This record previously said only the first half, which understated the board it covers. Third, Apple Home's automation UI may only expose lock/unlock triggers for the accessory. ESP32 boards only; the older ESP8266 v2.5x cannot run it.
• ✗ SmartThings: doesn't work — No official SmartThings support from the vendor, and SmartThings is not mentioned anywhere in ratcloud's FAQ. A third-party community project ('ESPHome for SmartThings') exists as an Edge driver announced on the SmartThings forums, but it is community-created and community-maintained with no vendor backing and no stability guarantee. Recorded as none rather than partial because treating an unaffiliated community driver as a supported integration is exactly the overstatement this catalogue exists to avoid.
• ✓ Home Assistant: works — The most thoroughly documented path here, and Home Assistant's own recommended replacement for myQ after it removed that integration in December 2023. The esphome-ratgdo firmware connects via ESPHome, which Home Assistant classifies in its own documentation as a core integration at the Platinum quality tier, using Local Push over a persistent local TCP connection with mDNS discovery and no cloud. Two catches: it requires running a Home Assistant instance, which is real ongoing work rather than a one-time setup; and it is mutually exclusive with the native HomeKit firmware, so a household wanting both Apple Home and Home Assistant needs to pick one or bridge from Home Assistant.

Connection: Wi-Fi · Hub for full use: Yes (No hub for the Apple Home path — the homekit-ratgdo32 firmware implements HomeKit Accessory Protocol on the device itself, so it appears in Apple Home directly with no bridge, no Homebridge and no Home Assistant. Every other ecosystem requires Home Assistant in the middle. The device needs local Wi-Fi but no vendor cloud and no account. FIRMWARE IS NOT INCLUDED and this is the most commonly misreported fact about the product: both product pages state 'Firmware not included', and the buyer flashes it themselves using a Chrome or Chromium web installer. The three firmware builds are mutually exclusive — flashing the HomeKit build means no ESPHome or Home Assistant integration on that board, and vice versa.) · Works offline: Yes — the core function runs on the device or your home network

Full sourced profile for ratgdo32 →

Chamberlain myQ Smart Garage Control — the catch, per ecosystem ~$64.99 $64.99 on Chamberlain's own product page, checked 2026-08-28 and unchanged since 2026-07-19; retailer prices were not checked

• ◐ Amazon Alexa: partial — There is no general-purpose myQ Alexa skill. What exists is Amazon Key In-Garage Delivery, which links the accounts so a driver can open the door; Chamberlain lists Amazon Key as a supported partner and documents the setup. It requires Prime and both apps, is limited to what Chamberlain calls 'several cities and their surrounding areas' in the US and Canada, and opening by voice requires a spoken PIN. Recorded as partial rather than full because 'works with Alexa' would overstate it: this is a delivery integration that happens to involve Alexa, not general voice control. We could not read Amazon's own Key page on the research day, so Amazon's current description of the programme is unverified and this rests on Chamberlain's documentation alone.
• ✗ Google Home: doesn't work — Removed. Chamberlain discontinued the Google Assistant integration for new users after Google shut down the feature it relied on in June 2023, telling the press the integration 'is not a user-friendly experience'. Google Home now appears in the unsupported list on Chamberlain's own integrations article. People who were already linked may keep it working, but if they log out of Google they cannot relink; it is a decaying grandfather clause, and a new buyer gets nothing. We could not retrieve the Google community thread, so there is no Google-authored statement here; this rests on Chamberlain disclaiming its own integration plus trade press from the time.
• ✗ Apple Home: doesn't work — There is no Apple Home support and no Matter path. The myQ Home Bridge, the accessory that provided it, was discontinued in August 2022; Chamberlain said under 1% of users used it. People who moved to the community Homebridge workaround were cut off in October 2023 when Chamberlain blocked third-party access. Chamberlain's own integrations article lists Apple HomeKit and Siri as unsupported. Watch the logo list: the same page shows Apple Watch as supported. That is the myQ app's own watch app, not Apple Home, and a buyer scanning logos will misread it.
• ✗ SmartThings: doesn't work — Chamberlain's integrations article lists SmartThings as unsupported and discontinued. The community side agrees: the long-running community integration is archived and labelled obsolete in its own title. A successor exists but requires you to run a bridge program continuously on a computer at home, and it is exposed to the same blocking that killed its predecessor. There is no sanctioned path.
• ✗ Home Assistant: doesn't work — Removed from Home Assistant core in release 2023.12 on 2023-12-06, announced by Home Assistant itself: 'we cannot continue to work around Chamberlain Group if they keep blocking access to third parties', with a maintainer describing 'a game of cat and mouse with MyQ and right now it looks like the cat is winning'. Home Assistant also states it declined authorised-partner status because it would require paying fees, which conflicts with its open-source model. Chamberlain's own position was published 2023-10-25 by CTO Dan Phillips, claiming unauthorised integrations came from 0.2% of myQ users yet generated more than half of platform traffic and 'at times constituted a substantial DDOS event'. Home Assistant's own recommended replacement is ratgdo — a local board that bypasses the cloud entirely.

Connection: Wi-Fi · Hub for full use: Yes (No separate hub; this device is the bridge. It joins your 2.4 GHz Wi-Fi and pairs with your existing opener through the opener's learn button, with a wireless sensor on the door to report open or closed. Bluetooth is used only during setup. A myQ account is mandatory and there is no documented way to control it on your home network, so Chamberlain's cloud is an unavoidable dependency. The myQ Home Bridge, the accessory that once added Apple Home, is discontinued; Chamberlain's own support article says so in its title.) · Works offline: No — the core function depends on the vendor's servers

Full sourced profile for Chamberlain myQ Smart Garage Control →

Nexx Smart Wi-Fi Garage Door Controller (NXG-300) — the catch, per ecosystem ~$79.99 $79.99 on the maker's own store, re-read 2026-08-13: available, and the store shows no struck-through original, so this is the list price and not a promotion. Unchanged since 2026-07-19. The two predecessor models named in the federal advisory, NXG-100B and NXG-200, are still sold out. The stored figure was a rounded $80 until 2026-08-13.

• ◐ Amazon Alexa: partial — Works through an Alexa smart-home skill, published under the maker's company name SimpalTEK, over the maker's cloud. The maker's own page carries a real limit: 'Routines are not available due to Amazon Restrictions', so the device cannot take part in Alexa Routines. Two skill generations exist with different phrasing: the older one needs 'Alexa, ask Nexx Garage to open garage door', the newer smart-home skill does not. We could not read the Amazon skill store pages, so the skill's rating, review count and last update are unknown.
• ◐ Google Home: partial — Works through a cloud-to-cloud Google Home Action. Opening by voice requires a spoken PIN and it cannot be disabled; closing requires none. That is Google's safety behaviour for garage doors rather than a vendor limitation. Google's own works-with directory listing could not be retrieved, so the directory status is UNKNOWN and this rests on hands-on reporting plus the vendor's own materials.
• ✗ Apple Home: doesn't work — Not an Apple Home accessory — it never appears in the Home app, and there is no HomeKit hub access, automation or sharing. The vendor's own NXG-300 page lists 'Siri' under Works With and makes no HomeKit claim, and its documentation describes Siri SHORTCUTS setup, which runs an app action by voice. So this is not a false vendor claim. But the retail listing title reads 'Compatible with Alexa, Google Assistant, Siri', which is accurate and easily misread by a buyer as Apple Home support.
• ◐ SmartThings: partial — A cloud-to-cloud SmartThings connection exists under the brand NexxHome, and the maker states outright that it does not work with a SmartThings hub; there is no local path, only cloud to cloud. One forward-looking catch that also affects the Home Assistant workaround: per Home Assistant's own documentation, Samsung begins phasing out free third-party access to SmartThings in October 2026 in favour of a paid plan, so a route that is free today may not stay free.
• ✗ Home Assistant: doesn't work — No official integration and no community add-on exist. Home Assistant community requests date back to 2018 and remain unfulfilled. The maker's own answer is a support article routing Home Assistant users through SmartThings, a two-cloud chain from Home Assistant to Samsung's cloud to Nexx's cloud, and the maker disclaims even that: 'shared by one of our Nexx users and hasn't been fully tested by our team. Please use at your own risk.' The only genuinely local path is destructive: owners of the NXG-200 have replaced its firmware entirely, which voids the warranty and abandons the Nexx app. Recorded as no because a maker-disclaimed two-cloud chain and a firmware replacement are not integrations.

Connection: Wi-Fi · Bluetooth · Hub for full use: Yes (No hub; the controller joins your 2.4 GHz Wi-Fi directly. Bluetooth is advertised on the product page as 'New Bluetooth connectivity', and the maker's blog claims the predecessor works over Bluetooth so you can control the door when the internet is out. Treat that claim as thinly documented: the quick-start guide filed with the FCC does not mention Bluetooth at all, and the maker publishes nothing about its range, whether it works only with a phone nearby, or whether it reports status as well as opening the door. All of that is unknown. Every ecosystem connection runs through the maker's cloud; no way to control it on your own network is documented.) · Works offline: Not checked — we have not established whether this keeps working without the internet

Full sourced profile for Nexx Smart Wi-Fi Garage Door Controller (NXG-300) →

Smart Garage Door Opener blaQ — the catch, per ecosystem ~$89 $89.00 on Konnected's own store (konnected.io, SKU GDOv2-Q) with an active add-to-cart control, read 2026-07-28. Price at time of research, not a live price.

• ✓ Amazon Alexa: works — Works through Konnected's free cloud service and its Alexa skill, and Konnected documents the actual voice commands — status, close, and open. Two catches, and the second comes from Amazon rather than Konnected. First, this is the cloud half of the product: the local-only configuration that makes the device attractive to Home Assistant owners does not carry Alexa with it. Second, Amazon's own developer documentation for garage-door devices states that after a user asks to open the garage door, 'Alexa asks What is your voice code? before opening the garage door' — so voice-opening requires a spoken code by Alexa's design, a step Konnected's own setup page does not mention. Konnected also notes its Alexa skill 'is currently only available in countries with English as the primary language.'
• ◐ Google Home: partial — Same experimental Matter beta as before: Konnected's explicitly uncertified firmware, which renders the opener as blinds or shades in the controller app, with a Nest Hub or Nest Audio acting as the Matter controller, and Konnected states it has not tested the device against every Matter hub. Since 2026-08-22 that page also requires acceptance into Konnected's Matter early-access programme and a Konnected account enabled for Matter beta access before the device can be configured. THE VENDOR'S OWN SURFACES DO NOT AGREE ABOUT ANY NON-MATTER GOOGLE ROUTE, and the disagreement is recorded rather than resolved. Konnected's Konnected Cloud article names exactly two cloud platforms — 'cloud-based smart home platforms like SmartThings and Amazon Alexa' — and there is no Google setup guide in the GDO blaQ's Platform Integrations section, which does carry one each for SmartThings, Alexa, Home Assistant, Hubitat and Apple Home. Konnected's general FAQ says instead 'You can link to Google Home through SmartThings', which is SmartThings' Google integration rather than a Konnected one. And the GDO blaQ product page's own FAQ lists 'Alexa, SmartThings, and Google Home' as things Konnected's cloud 'may still be used for'. No first-party procedure for a Konnected-to-Google link exists on any of them, so the level stays on the route the vendor actually documents.
• ◐ Apple Home: partial — There is now a direct route, and it is still a beta. Konnected publishes a HomeKit-native alternate firmware for the GDO blaQ, described on its own support site as enabling 'direct integration with Apple Home (HomeKit) without requiring any third-party tools or bridges' — flashed from install.konnected.io over a micro-USB cable from a desktop running Chrome or Edge, then added in the Home app with the setup code Konnected prints, with an Apple Home hub (HomePod, HomePod mini or Apple TV) on the network. Konnected lists Siri control, automations, scenes, status notifications and away-from-home control through that hub. Two costs are the vendor's own words rather than our inference. The build is labelled 'Experimental Status: This is an experimental open-source firmware', and 'not all features and customizations available in the standard GDO blaQ firmware are available yet' — Konnected does not enumerate what is missing. And it is an ALTERNATE firmware, not an addition: Konnected's route back is to 'reflash your device with the original firmware' to regain 'full feature support and integration with the Konnected app'. Recorded as partial for that reason — Apple Home is reached natively, on firmware the vendor does not call production-ready and which the buyer installs themselves with a computer. The older Matter beta is still documented as a second way in, and it renders the door as blinds or shades.
• ✓ SmartThings: works — Konnected publishes a real, current setup guide for this — which distinguishes it from the advertised-but-undocumented SmartThings claims elsewhere in this category — and states that the GDO blaQ 'connects to SmartThings via the Konnected Cloud, and does not require a SmartThings hub.' The catch is what that sentence also means: no SmartThings hub is needed because nothing is local. This route depends on Konnected Cloud staying free and staying alive, which is precisely the dependency the local ESPHome path avoids. VENDOR-WORD-ONLY: the working state of this integration is sourced to Konnected's documentation; no SmartThings-published listing for the device was found, so the claim is not cross-verified from the platform side.
• ✓ Home Assistant: works — The strongest path here and the one the product is built around. The device runs ESPHome firmware and Konnected states it 'integrates natively and locally with Home Assistant', working '100% locally via ESPHome' with automatic discovery after Wi-Fi setup. Home Assistant's own documentation backs the transport rather than the vendor's word: ESPHome is a core integration at Platinum quality with IoT class Local Push, over a persistent local TCP connection with mDNS discovery. No Konnected Cloud account, no subscription and no internet are needed for this route. The cost is the usual one — you have to run and maintain a Home Assistant instance.

Connection: Wi-Fi · Hub for full use: Yes (No hub for the Home Assistant path — the device speaks ESPHome's native API directly over your LAN and Home Assistant discovers it by mDNS, so there is no bridge and no vendor cloud in that route. No SmartThings hub either: Konnected's own guide states the GDO blaQ 'connects to SmartThings via the Konnected Cloud, and does not require a SmartThings hub', and the Alexa guide says the same thing about an Echo, working through Konnected's free cloud service and Alexa skill. Apple Home and Google Home both need a firmware change first, and since 2026-08-22 they no longer need the same one. Apple Home has its own HomeKit-native alternate firmware, after which an Apple Home hub (HomePod, HomePod mini or Apple TV) must be on the network. Google Home is still reachable only through Konnected's experimental Matter firmware, which then needs a Matter controller in the house (a Nest Hub or Nest Audio, a SmartThings Hub or Station, or a supported Echo or eero) plus acceptance into Konnected's Matter early-access programme. Wi-Fi is 2.4 GHz only and the device is powered by an included 12 V DC adapter.) · Works offline: Yes — the core function runs on the device or your home network

Full sourced profile for Smart Garage Door Opener blaQ →

Tailwind iQ3 2.0 Smart Garage Door Controller — the catch, per ecosystem ~$89.99 Re-checked 2026-08-18 and unchanged: 'From $89.99 USD' for the iQ3 2.0 with no door sensor (IQ3-20-00), rising to $114.99 with either the J-Track or Universal door sensor (IQ3-20-JT / IQ3-20-UN). The parallel iQ3 2.1 line runs $99.99 to $124.99 on the same storefront. Never treated as a live price.

• ✓ Amazon Alexa: works — Works through a cloud skill, and the vendor is explicit that the local control key is 'NOT required for cloud-based integrations such as Google Home and Alexa' — which is the same sentence telling you these break in an internet outage. Amazon separately requires a spoken voice PIN to open a garage door. So the 'works when the internet is down' promise on the product page covers the app and the local integrations, not this one.
• ✓ Google Home: works — Cloud-dependent for the same reason as Alexa, and breaks in an outage. Two Android-specific annoyances the vendor documents: background-location permission is required for auto-open, and Android forces a persistent 'Auto-open permission enabled' notification that cannot be dismissed without breaking the feature.
• ✓ Apple Home: works — Native HomeKit with no bridge and no hub — the setup code lives in the Tailwind app and is emailed with a QR at registration, and the vendor confirms the local control key is 'NOT required for Apple HomeKit'. This is one of the clearer answers to Chamberlain having removed HomeKit from myQ. The catch is scope rather than reliability: Apple Home exposes door open and close only, while auto-open, Night Mode and per-user activity attribution stay inside the Tailwind app. A HomeKit reset by holding the config button for about five seconds is the vendor's standard fix for a 'not responding' accessory.
• ◐ SmartThings: partial — Advertised but undocumented, and recorded as partial for exactly that reason. SmartThings appears on Tailwind's works-with page as an image tile with NO link, while neighbouring integrations link to setup documentation. A search of the vendor's own help centre for SmartThings returned zero articles, no Tailwind-authored setup guide could be found, and there is no first-party Samsung listing — only a community forum thread. The integration may well work; what does not exist is any vendor instruction for setting it up. This is the weakest claim in an otherwise well-documented product.
• ✓ Home Assistant: works — An official Home Assistant core integration at Platinum quality tier, added in Home Assistant 2024.1, with IoT class Local Polling at roughly five-second intervals — sourced to Home Assistant's own documentation rather than to Tailwind. It exposes cover, a binary sensor for operational problems, an identify button and LED brightness control. Two catches: it needs the six-digit local control key from the vendor's web portal plus a minimum firmware version that Home Assistant's page does not actually name, and because it is local polling the entities go unavailable if the device is unreachable. Home Assistant's page lists 'Tailwind iQ3' without enumerating which of the 2.0 and 2.1 models are covered.

Connection: Wi-Fi · Hub for full use: Yes (No hub or bridge. The vendor states it directly: 'The Tailwind smart garage (and gate) opener controllers do not need a hub or bridge.' The controller joins 2.4 GHz Wi-Fi — 2.4 GHz only, no 5 GHz — or can run on wired Ethernet with the optional $39 PoE board, which is unusual in this category and worth knowing for a detached garage with poor Wi-Fi. Apple Home pairing is native and needs no bridge.) · Works offline: Partly — some of it keeps working without the internet and some of it does not

Full sourced profile for Tailwind iQ3 2.0 Smart Garage Door Controller →

Remootio 3 — the catch, per ecosystem ~$129 price at time of research, seen on the maker's own store on 2026-07-29 and unchanged on 2026-08-30; it is a sale price, the regular price is $149, and the item was listed as sold out on both days

• ◐ Amazon Alexa: partial — Works through Remootio's cloud, and you must say a PIN before Alexa will open the door. You will need a Remootio account, which the basic product does not otherwise require, and link it to Alexa. Asking whether the door is open needs no PIN. Amazon's own rules require a spoken code before Alexa opens any garage door, so this is not unique to Remootio. We could not confirm the Remootio skill from Amazon's side, because the listing would not load when we checked, which is why this stays 'partial' rather than 'full'.
• ◐ Google Home: partial — Works through Remootio's cloud, and you set a PIN that Google asks for before opening. You will need a Remootio account linked to Google Home. The device appears in the Google Home app as a lock. Nothing in Remootio's instructions suggests Google talks to the device on your home network, so expect this path to stop when your internet does. We could not find Remootio in Google's own list of supported devices, so this stays 'partial'.
• ✓ Apple Home: works — The one Remootio path with real step-by-step setup instructions from the maker. Remootio's guide walks through adding the device in the Apple Home app and shows the door's status changing live on the Home tile, from 'Closed' to 'Opening' and back. Siri can open it, close it and tell you whether it is open. What Remootio does not say is whether Apple Home talks to the device directly or through Remootio's own bridge software, or whether you need a home hub such as a HomePod or Apple TV. That unanswered question decides whether this keeps working if Remootio ever stops updating its software, so we leave it open rather than guess. Apple Home support for this generation arrived through an app update, not in the box.
• ◐ SmartThings: partial — Works through Remootio's cloud, and it is the path that makes you create a Remootio account. Remootio's own instructions say so: you normally need no account, but linking to SmartThings requires one plus a shared key. No SmartThings hub is mentioned. Samsung's own directory of SmartThings products does not list Remootio, checked 2026-07-29 and again 2026-08-30. Missing from a list is not the same as unsupported, so this stays 'partial' rather than 'full' or 'none'.
• ◐ Home Assistant: partial — Home Assistant support is unofficial. Home Assistant publishes no integration for Remootio, and Remootio's own list of platforms does not mention Home Assistant. What exists is a community-built add-on, and it is a good one: it talks to the device directly over your home network with no Remootio cloud in the path, using two keys you copy out of the Remootio app. What sets Remootio apart is that the community did not have to reverse-engineer anything. Remootio publishes the technical interface itself and promises that new versions will keep working with old ones, so the local path rests on a written commitment rather than on the company's goodwill. Recorded as 'partial' because the add-on is community-maintained, and because we found no source that reports how reliable it is in real homes.

Connection: Wi-Fi · Bluetooth · Hub for full use: Yes (We could not confirm whether it needs a hub. Remootio lists three ways to reach the device: Bluetooth when you are standing near the gate, your home Wi-Fi from inside the house, and the internet when you are away. That reads like a device that stands on its own, but the company never says so outright, and we do not turn a list of connections into a hub answer. One thing is confirmed: the Home Assistant route reaches the device directly over your home network with nothing in between.) · Works offline: Partly — some of it keeps working without the internet and some of it does not

Full sourced profile for Remootio 3 →

Chamberlain B4643T Smart Belt Drive Garage Door Opener with Built-in Camera — the catch, per ecosystem

• ◐ Amazon Alexa: partial — There is no general-purpose myQ Alexa skill, and 'works with Alexa' would overstate what exists. Chamberlain's supported list carries Amazon Key — in-garage delivery, which links the accounts so a courier can open the door — and Walmart+ InHome alongside it, but no general voice-control integration. Recorded as partial precisely because the thing that exists is a delivery programme that happens to involve Amazon, not the voice control a buyer expects from the logo. Amazon Key also carries its own conditions: Prime membership, both apps, and geographic limits. Note that Ring now appears on Chamberlain's supported list as well; Ring is Amazon-owned, but a Ring integration is not an Alexa garage-door integration and is not recorded as one.
• ✗ Google Home: doesn't work — Google Home appears on Chamberlain's own 'not supported or have been discontinued' list. This is a removal rather than an absence: the Google Assistant integration was discontinued for new users after Google shut down Conversational Actions in June 2023. There is no Matter path to route around it, because Chamberlain lists Matter as unsupported on the same page.
• ✗ Apple Home: doesn't work — Chamberlain states it outright: on its own integrations page, Apple HomeKit sits under platforms that are 'not supported or have been discontinued', with the explicit sentence 'You cannot control your myQ devices directly from the Apple Home app or with Siri voice control.' Matter and Thread are on the same unsupported list, so there is no standards-based back door either. WATCH THE LOGO LIST: the same page lists 'Apple Watch' among SUPPORTED smart-home integrations. That is the myQ app's own watch app, not Apple Home, and a buyer scanning logos will misread it — the same trap this category's myQ retrofit record flags.
• ✗ SmartThings: doesn't work — Samsung SmartThings is named on Chamberlain's own 'not supported or have been discontinued' list. The other side agrees and has for years: the long-running community project for this is archived and labelled '(Obsolete)' by its own author. There is no sanctioned path, and the unsanctioned ones are exactly what Chamberlain's blocking was built to stop.
• ✗ Home Assistant: doesn't work — Removed by Home Assistant itself, not merely unsupported by Chamberlain — and this cell is sourced to Home Assistant rather than to the vendor, per the cross-party rule. Home Assistant removed the myQ integration in release 2023.12 on 2023-12-06, stating that Chamberlain Group 'have released a public statement saying they will continue blocking access to third-party apps, like the MyQ integration'. Home Assistant's own recommended replacement is ratgdo, 'a fully local, ESPHome-based, solution that is compatible with MyQ's security+ protocol' — which is the shape of the answer for this whole product line: the way to get a Chamberlain door into Home Assistant is to bypass myQ entirely with a retrofit board, and on a Security+ 2.0 opener like this one that route is open.

Connection: Wi-Fi · Hub for full use: Yes (No hub and no bridge — Wi-Fi is built into the opener. The manual requires '2.4 GHz, 802.11b/g/n' Wi-Fi signal in the garage and a smartphone running the myQ app; there is no 5 GHz option and no Ethernet. A myQ cloud account is mandatory and no local or LAN control path is documented anywhere in the manual, so this is a cloud appliance rather than a device with an optional cloud. Note also that this model has NO battery backup: Chamberlain's own warranty table lists a battery-backup warranty term for the B4613T, B6713T and B6753T and a dash for the B4643T. That matters more than it sounds, because the manual states that 'myQ App control and camera WILL NOT work if the garage door opener is operating on battery power' — on this model there is no battery power to fall back to at all.) · Works offline: No — the core function depends on the vendor's servers

Full sourced profile for Chamberlain B4643T Smart Belt Drive Garage Door Opener with Built-in Camera →

LiftMaster 84505R Secure View Ultra-Quiet Belt Drive Smart Opener — the catch, per ecosystem

• ◐ Amazon Alexa: partial — "Works with Alexa" would overstate it. There is no general-purpose myQ Alexa skill; what Chamberlain's own supported-integrations list carries is Amazon Key — in-garage delivery, which links an Amazon account to the opener so a courier can open it. Useful, and genuinely not the same thing as saying "Alexa, open the garage."
• ✗ Google Home: doesn't work — Google Home appears on Chamberlain's own "not supported or have been discontinued" list. This is a removal rather than an absence — the myQ Google Assistant integration was withdrawn, and the vendor states the outcome plainly rather than leaving it to be discovered.
• ✗ Apple Home: doesn't work — Chamberlain states it outright on the same list: Apple HomeKit is not supported, and "You cannot control your myQ devices directly from the Apple Home app or with Siri voice control." The Matter route is closed by the same page, which puts both "Matter" and "Thread" on the unsupported list — a vendor declaring in advance that the standard everyone expects to fix this will not be the fix.
• ✗ SmartThings: doesn't work — Samsung SmartThings is named on Chamberlain's own "not supported or have been discontinued" list, alongside Hubitat and Wink.
• ✗ Home Assistant: doesn't work — Removed by Home Assistant itself rather than merely unsupported by the maker: Home Assistant published the removal of its myQ integration in November 2023 after Chamberlain began blocking third-party access. Chamberlain's own page states the policy in its words: 'Chamberlain blocks unauthorized or unapproved third-party integrations to protect customer safety.'

Connection: Wi-Fi · Hub for full use: No — verified that none is needed · Works offline: Not checked — we have not established whether this keeps working without the internet

Full sourced profile for LiftMaster 84505R Secure View Ultra-Quiet Belt Drive Smart Opener →

OpenGarage — the catch, per ecosystem

• ? Amazon Alexa: inconclusive — NOT ESTABLISHED, same basis as Apple Home and Google Home. No Alexa skill is named in any reachable vendor documentation, and the manual's integration list does not include Alexa — but no vendor statement denies it, so the cell is unknown rather than none. Worth knowing regardless: even where a garage integration does exist, Amazon's own developer documentation requires a spoken voice code before Alexa will open a garage door, so an Alexa route would carry that step.
• ? Google Home: inconclusive — NOT ESTABLISHED, same basis as Apple Home. Google Home appears nowhere in the vendor's enumerated integration list, and no vendor statement denies it either. The one indirect route the manual does document is IFTTT, via a webhook service key — but IFTTT's own relationship with Google Assistant has changed repeatedly and is not something the vendor's documentation speaks to, so it is not recorded as a Google path. Treat Google Home as a bridge-it-yourself proposition through Home Assistant or MQTT.
• ? Apple Home: inconclusive — NOT ESTABLISHED, and deliberately not guessed. The vendor's own v1.2.4 user manual enumerates its integrations by name — Home Assistant, MQTT, IFTTT, OpenThings Cloud and Blynk — and Apple Home is not among them. That is an absence from a list, not a denial: no vendor statement says Apple Home is unsupported, and this catalogue does not convert silence into a 'no'. The pages that would settle it live on opensprinkler.com, which refuses our requests. What a buyer can act on today: there is no documented native Apple Home path, and anyone needing one should treat this device as requiring a bridge they build themselves — via Home Assistant or MQTT — rather than as a HomeKit product.
• ? SmartThings: inconclusive — NOT ESTABLISHED. SmartThings is absent from the vendor's enumerated integration list and no vendor statement addresses it either way, and no SmartThings-published listing or community driver for OpenGarage was found from a reachable source. Recorded as unknown rather than none because the vendor documentation that would settle it sits behind a host that refuses us.
• ✓ Home Assistant: works — The one thoroughly established integration, and it is a genuine one. The vendor states plainly that 'OpenGarage has an official Home Assistant integration' which 'adds the device as a cover entity. It allows door control, status monitoring, and automation.' Home Assistant's own documentation backs that from the platform side rather than the vendor's word: opengarage is a Home Assistant integration in the Cover and DIY categories with IoT class Local Polling, added in Home Assistant 0.44, set up through the UI. TWO HONEST QUALIFIERS. It is Local POLLING, not Local Push — Home Assistant asks the device for its state on an interval rather than being told the instant it changes, so expect a short lag versus a push integration. And it is a small integration by adoption, reported at 511 active installations in Home Assistant's own analytics on 2026-08-22 (515 at the previous check), which is a fair signal of how much community testing sits behind it.

Connection: Wi-Fi · Hub for full use: Yes (No hub and no bridge. OpenGarage is a self-contained Wi-Fi device with its own built-in web UI, reached at its address on your network — that web UI is the primary interface, and actions on it are authorised by a Device Key (factory default 'opendoor') rather than by any account. Home Assistant talks to it directly over the LAN using its official core integration. Power is a microUSB cable into a USB adapter. There ARE vendor apps: OpenGarage publishes a browser web app plus native iOS and Android apps for door control, status and managing several units, and the vendor's own instructions include the step 'Proceed without logging in...' for using them. Remote access from outside your network is the one thing that needs the vendor's optional cloud (OpenThings Cloud) or Blynk, and getting either token means registering an opensprinkler.com/openthings.io account — a choice rather than a requirement.) · Works offline: Yes — the core function runs on the device or your home network

Full sourced profile for OpenGarage →