Product Library / Garage & Access
Research profile · last verified 2026-07-19Meross Smart Wi-Fi Garage Door Opener (MSG100)
Compatibility
| Ecosystem | Support | The catch |
|---|---|---|
| Apple Home | WorksWorks with this ecosystem | 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. |
| Amazon Alexa | WorksWorks with this ecosystem | Works through Meross's cloud-to-cloud skill. Two things to know. Amazon's own Smart Home API forces a spoken voice PIN to OPEN a garage door while closing is unrestricted — that is Alexa's rule for the garage-door device type, not a Meross limitation, and it is a safety feature rather than a defect. And because the path is cloud-to-cloud, it stops working when your internet does. |
| Google Home | WorksWorks with this ecosystem | 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. |
| SmartThings | PartialPartial support — see the catch | 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 | PartialPartial support — see the catch | There is NO official Home Assistant integration — home-assistant.io/integrations/meross/ returns 404 and 'meross' is absent from the entire home-assistant/core component tree. Meross never mentions Home Assistant anywhere in its own materials either, so nothing here is a vendor-supported path. The community option github.com/krahabb/meross_lan is well maintained and genuinely local, exposing the MSG100 and MSG200 as a cover with device class GARAGE over LAN HTTP or local MQTT. Two catches: even this local path requires a device key extracted from your Meross cloud account, so it is not cloud-free to set up; and the alternative community integration is cloud-only, with its own maintainer warning that Meross throttles high-rate API users. Recorded as partial because a well-supported community integration is not a supported integration. |
Protocols: WIFI
Needs before it works: 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.
Subscription reality
✓ Works without a subscription: Yes.
No subscription of any kind — Meross states plainly on its product pages, 'No monthly fee or any other subscription fee!' and no feature was found gated behind a paid tier. This is the core of the anti-myQ pitch and it holds up on inspection. The only money beyond the device is the RGR551C adapter, which Meross's support documentation says it will ship free on request with proof of purchase, but which it simultaneously sells for $13.99 — see the adapter note in theCatch.
Maintenance reality
- Batteries: None — mains-powered. The bundled door sensor is wired to the controller rather than battery-powered.
- Cloud dependence: Yes — a server shutdown would degrade or brick this device
- Cloud-dependent for most paths, with two genuine exceptions. Meross makes an explicit marketing claim — 'When the internet is down, you can still control your devices in home network via Meross app' — but that claim appears ONLY in marketing and is not repeated in the manual, which documents just a solid-red LED for 'No internet connection' and never enumerates what survives. What holds up: the Home Assistant meross_lan path is genuinely local (local_polling over LAN HTTP or local MQTT), and HomeKit control from within the home via an Apple home hub is local by HomeKit's architecture — though note honestly that Meross's own documentation does not confirm that specific scenario, so it is architectural inference. What breaks: remote app access, Alexa, Google and SmartThings, all cloud-routed. Whether schedules and auto-close continue to run during an outage is UNKNOWN — Meross claims local schedule persistence for its light strips and makes no equivalent claim for this product. SENSOR BEHAVIOUR, AN UNDOCUMENTED GAP: the included sensor is the sole means of state detection and Meross has four separate FAQs on sensor failure, all framed as display and status troubleshooting. Meross never documents whether the device will still execute a close command when the sensor has failed or is mis-reporting. No interlock or fail-safe is documented, and on a crushing-hazard device that absence is itself the finding.
The catch
If you own a yellow-learn-button Chamberlain, LiftMaster or Craftsman opener — Security+ 2.0, which is most of what those brands sold between 2011 and 2022, and therefore exactly the myQ-refugee population this product is aimed at — the MSG100 and MSG200 do not wire to your opener at all. Those openers use a digital serial protocol on the wall-button terminals, so shorting them does nothing, and Meross's compatibility checker responds to a yellow learn button with 'You need an accessory to continue configuration'. That accessory, the RGR551C, is described in Meross's own FAQ as 'a universal remote with an extra signal cable soldered on it' — you pair a remote to your opener and the Meross unit presses one of its buttons for you. That works, but it is a materially more fragile architecture than a wired connection, and none of it is surfaced at the point of sale. Two ways out: the MSG150 at $62.99 handles Security+ 2.0 natively with no adapter, and if your learn button is purple, red or orange you can use the MSG100 directly. If your learn button is WHITE — Security+ 3.0, from November 2025 — no Meross model works at all. The other soft spot is safety on paper: the audible alarm is optional and user-disableable, Meross's own setting describes it as sounding 'when door is closing' rather than before the door moves, no visual warning is documented anywhere, no UL 325 claim is made, and the manual contains no entrapment warning despite remote closing being the entire purpose of the product.
Who it's for
Apple Home households wanting native HomeKit garage control with no subscription — buy the HK SKU, and buy it from Meross rather than guessing on Amazon. The cleanest install is a purple, red or orange learn button, or any non-Chamberlain opener that passes Meross's terminal-short test, because those wire directly with no adapter. If you have a yellow-button Chamberlain, LiftMaster or Craftsman, the MSG150 at $62.99 is the model to buy — it skips the adapter and the sensor entirely. The MSG200HK covers up to three doors on one device. Home Assistant users get real local control through the community meross_lan integration, with the caveat that setup still touches the Meross cloud for a device key. It is the wrong buy for anyone with a white learn button, since no model works; for anyone who wants Matter, which none of these have; for anyone building SmartThings automations keyed to door state, given a three-year-old unresolved sync defect; for anyone who needs a documented audible-and-visual warning before an unattended close; and for anyone shopping Amazon without checking for the non-HomeKit variant, which defeats the whole reason to choose this over myQ.
Sources & method
shop.meross.com/collections/smart-garage-door-opener/products.json and the per-product .js endpoints, retrieved 2026-07-19: MSG100HK-US $49.99, MSG150HK-US $62.99, MSG200HK-US $69.99, all available:true. Meross's own MSG150 copy positions it as brand-specific ('Works with Chamberlain, LiftMaster, and Craftsman. For other brands, please check out Meross MSG100HK'), which establishes coexistence rather than succession. MSG150's compatibility page is dated 2025-11-24. — vendor-data research, verified 2026-07-19 · A POST to shop.meross.com/cart/add.js for variant 39962441482396 followed by reading /cart.js back confirmed the MSG200HK in cart at $69.99 with item_count 1 on 2026-07-19. Cart cleared afterwards; no checkout performed. The $89.99 strike-through means the $69.99 is promotional and is recorded as price at time of research. — vendor-page research (cart state), verified 2026-07-19 · Every model on Meross's own store carries an HK suffix, but a non-HomeKit MSG100 is sold on Amazon under a listing explicitly titled '(Non HomeKit Versions)' at amazon.com/meross-Smart-Control-Compatible-Assistant/dp/B07L5DPK8P, and Meross also lists an 'MSG100 (Non-HomeKit Version)' on its own store. Recorded prominently because the buyer most likely to choose this product is one escaping myQ's HomeKit removal, and that is precisely the buyer the near-identical Amazon listing harms. — vendor-page and retailer research, verified 2026-07-19 · Meross's compatibility checker at meross.com/en-gc/mTerminal/compatibility-check/garage-door-opener was driven programmatically; selecting the YELLOW learn button returns verbatim 'You need an accessory to continue configuration, please Tap Here to Claim the Accessory'. Meross FAQ 257 and FAQ 405 describe the RGR551C accessory as 'a universal remote with an extra signal cable soldered on it', with instructions to 'Press the yellow learn button on your ceiling opener once' and noting 'The wires connect to the bottom right button, so only this button is working'. So on Security+ 2.0 the device does not communicate with the opener at all — it actuates a paired remote. COUNTERPARTY CONFIRMATION that yellow means Security+ 2.0: support.chamberlaingroup.com/s/article/Determine-the-Color-of-the-Learn-Button-on-Your-Garage-Door-Opener gives Yellow (round) = 'Security+ 2.0 (Rolling Code)', 310/315/390 MHz, 2011–2022. — vendor-tool and counterparty-source research, verified 2026-07-19 · Meross support text says it will ship the proper accessory free on request, requiring an order number or receipt plus opener brand, model, learn-button colour and delivery address. But FAQ 405 itself does not state it is free, and Meross simultaneously sells RGR551C-ACCESSORY for $13.99 in its own accessories store (available:true, verified 2026-07-19). Recorded as: free on claim with proof of purchase per support docs, $13.99 if bought outright. — vendor-page research, verified 2026-07-19 · Meross's MSG150 compatibility page at bucket-meross-static.meross.com/production/h5/StaticPage/2025/11/24/202511240257069315189.html states the model works with 'yellow, purple, red, or orange learn buttons' on 'Security+ 1.0 or 2.0 protocols' and explicitly does NOT support 'white learn button-Security+ 3.0, green learn button'. This is a first-party exclusion. — vendor-page research, verified 2026-07-19 · csa-iot.org/csa-iot_products/?p_keywords=meross was driven in a real browser and paginated through all 6 pages, extracting every result row: 69 certificates across exactly 3 products — Smart Roller Shutter Switch (17), Smart Power Strip (25), Smart Plug Mini (27). Zero garage products, zero MSG-series products. The keyword matches the company field 'Chengdu Meross Technology Co., Ltd.', so this captures the full Matter portfolio. An initial filtered query was correctly distrusted and re-run unfiltered. STRUCTURAL CORROBORATION: the registry's own Device Type filter list was read in full and contains Door Lock, Door Lock Controller, Window Covering, Window Covering Controller and Shade Controller, but NO garage door device type — so at the time of this sweep a Matter-certified garage controller from any vendor had nowhere to certify to under the device types this registry exposes. Note the HK in MSG200HK means HomeKit, not Matter; any source reading it as Matter is wrong. — registry research (rendering browser, full pagination), verified 2026-07-19 · home-assistant.io/integrations/meross/ returns HTTP 404, and 'meross' is absent from all components in the home-assistant/core source tree — a stronger check than reading the rendered integrations index, which is client-side. The community option github.com/krahabb/meross_lan (728 stars, v5.8.0 February 2026) declares iot_class local_polling and exposes MSG100/MSG200 as a cover with DeviceClass.GARAGE. The alternative github.com/albertogeniola/meross-homeassistant (849 stars) is cloud-only and its maintainer warns that Meross throttles high-rate API users and imposes MQTT limits above roughly 10 devices; its fully-local broker addon has been dormant since December 2024. Meross never mentions Home Assistant in its own materials. — counterparty-source research, verified 2026-07-19 · developer.amazon.com/en-US/docs/alexa/device-apis/alexa-securitypanelcontroller.html for Alexa's spoken-PIN requirement on opening a garage door, and developers.home.google.com/cloud-to-cloud/enhancements/secondary-user-verification for Google's secondary user verification. Both require verification to open and neither to close. Recorded as platform safety behaviour rather than as a Meross limitation, and sourced to each platform rather than to Meross. — counterparty-source research, verified 2026-07-19 · Meross's Advanced Settings expose a toggle labelled verbatim 'Closing alarm: Sound alarm when door is closing' — concurrent with motion rather than before it, with no documented warning period or duration, and user-disableable. Whether it defaults on or off is UNKNOWN, and whether it fires on a TIMER-triggered auto-close is NOT documented, which is a real gap for an unattended operation. No visual or flashing warning is documented anywhere: the manual's LED table assigns every LED state to connectivity or sensor events and none to a closing warning, which is meaningful negative evidence. Certifications claimed are 'FCC, IC, ETL, CE, RoHS, WEEE' — ETL is Intertek's general product-safety mark and must not be read as UL 325 unattended-operation compliance. There is NO UL mark and no UL 325 claim, and the manual's safety text is generic electrical boilerplate with no warning about remote or unattended closing and no entrapment warning. — vendor-documentation research; explicit negatives recorded, verified 2026-07-19 · shengrikuaile.com and mgahv.in both assert that the MSG200HK 'does not meet UL 325 standards for unattended operation'. Both were rejected as sources: they are wholesale scraped republications of Wirecutter content on unrelated domains, carrying identical URL slugs that confirm a common scrape. The underlying claim may well be true, but it is not citable from these, and the defensible primary-sourced fact is recorded instead — that Meross makes no UL 325 claim, documents no visual alarm, and documents no pre-motion warning period. Recorded explicitly so a later pass does not re-litigate it or mistake the scraped version for a source. — source-quality audit, verified 2026-07-19 · meross.com/en-gc/mTerminal/support/download returns 'No data' with zero manuals listed for any garage model, so all manual wording in this record comes from manuals.plus, a SECONDARY MIRROR, corroborated verbatim across four independent mirror pages and labelled as secondary. Also unreachable: Wirecutter (blocked), Amazon customer Q&A (503), and several third-party pages (403). Additional rejected sources: grokipedia.com (AI-generated; every fact it asserted was independently re-derived from Meross's store JSON and nothing rests on it), plus trunetto.com, diysmarthomehub.com, ventsmagazine.co.uk, findingdulcinea.com and thecutlist.com as AI-SEO aggregators, all unused. — source-quality audit, verified 2026-07-19 · The MSG200HK page markets 'The built-in sound alarm makes closing the door safer, especially for families with children and pets' while the documented feature is an optional, disableable toggle sounding concurrent with motion, with no visual component — the sharpest marketing-versus-documentation gap in the line. The alarm is promoted on the MSG200HK page, absent from the MSG100 page despite the MSG100 manual documenting it, and unmentioned for the MSG150. SmartThings is claimed for the MSG100 but absent from MSG150 copy while Meross's corporate 'Our Story' makes a blanket company-level SmartThings claim. Offline capability is claimed in marketing and absent from the manual. And 'Broader Compatibility' on the MSG150 in fact means narrower — three brands only. — vendor-page research, verified 2026-07-19. This is a research profile: compiled from manufacturer documentation, certification registries, and published testing — we state facts, not verdicts, and we have not physically tested this unit. How we work →
Compatibility and lifecycle information reflects the last-verified date above and can change without notice (firmware updates, cloud-service changes, discontinuations). It is provided as-is, for information — verify with the manufacturer before purchasing. Spot an error? Tell us and we'll fix it. Full terms: Terms of Service.