Product Library / Garage & Access

ratgdo32

Compiled by SmartHomeWorkflow Research · ratgdo · Garage & Access · ~$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.)

Compatibility

Protocols: WIFI^[3][22]

Needs before it works: 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.^[10]

What it can do^[26]

Listed capabilities are what we could establish from vendor documentation. An ability missing here is unestablished — not necessarily absent.

Subscription reality^[10][20]

✓ Works without a subscription: Yes.

Vendor account required: No — no vendor account is involved.^[10][20]

One-time hardware purchase with no subscription, no cloud account and no recurring fee anywhere in the purchase or operation path. The vendor's FAQ states the HomeKit firmware 'does not require a home automation hub and works locally on your network without requiring a cloud service'. Worth stating plainly because it inverts the category: the subscription question that dominates every other product here does not exist for this one. NOTE THE INDIRECT COST though — the Alexa and Google paths route through Home Assistant, and exposing Home Assistant to those services requires either a paid Nabu Casa cloud subscription or a self-managed Amazon Developer and AWS Lambda setup. So 'no subscription' holds for Apple and Home Assistant and does not hold for Alexa or Google.

Maintenance reality^[17]

• Batteries: None — powered over USB from the included supply.
• Works without the internet: Yes — the core function runs on the device or your home network. A vendor cloud may still be involved in remote access.^[10][20]
• Genuinely local, verified from counterparty sources rather than vendor marketing: ESPHome's own documentation describes each device as its own server communicating over local TCP with no cloud dependency, and Home Assistant's ESPHome integration page classifies it as Local Push over a persistent local connection. The HomeKit firmware serves HAP from the device over the LAN. QUALIFIER WORTH KEEPING: local operation holds for the Apple Home and Home Assistant paths only — the Alexa and Google paths route through the internet by Home Assistant's own documentation, so choosing those forfeits the reason to buy this. Local Wi-Fi is still required; this is a network-local device, not a network-independent one. INSTALL AND SAFETY: soldering is not required as of version 2.0, and installation is three wires to the opener's terminal block plus USB power — but miswiring has consequences, since the vendor's FAQ warns that connecting obstruction sensors above 18 V 'will destroy the obstruction input circuit'. The vendor's own documentation carries an explicit disclaimer: 'Use this device at your own risk. To avoid risk of injury or property damage only operate the garage door within line of sight.' TWO HONEST UNKNOWNS: no primary source establishes whether the opener manufacturer's warranty is affected, and no affirmative vendor statement confirms that the opener's own entrapment protection is preserved — the device reads obstruction state and issues the same signal a wall button does, so the opener's logic board should still enforce its reversal behaviour, but that is reasoning rather than a sourced claim and the vendor's feature documentation makes no mention of UL 325 at all. Recorded as unknown rather than asserted in either direction. Vendor documentation also contradicts itself on obstruction sensor voltage: the FAQ says 5–16 V while the features page says peak 4.5–7 V.

Security updates^[27]

ratgdo publishes no security-update support date for this model. That is a gap in what the manufacturer has published, not evidence either way — some makers declare a support period and some say nothing at all.

No security-support period is published for this board, which follows from how it is built rather than from vendor silence about a closed product. The firmware is open source: buyers choose between the ESPHome and HomeKit builds, both distributed from public repositories, and the vendor's firmware and FAQ pages document how to flash and configure them without stating any period during which updates or patches will continue. There is no cloud service to withdraw and no subscription attached, so the practical support question here is whether the community repositories stay maintained rather than whether a manufacturer honours a commitment. Anyone weighing that should note the pattern already visible in the project: the HomeKit firmware for the older ESP8266-based v2.5 boards has been marked deprecated, which is the shape a lapse takes on an open-source device - a repository notice rather than an end-of-support date.

The catch

It does not work with Chamberlain Security+ 3.0 openers, and that is architectural rather than a firmware gap someone will patch. The vendor states it plainly in its own FAQ: 'Security + 3.0 openers are not supported.' The reason is that ratgdo works by reading the data signal on the wall-button wires, and Chamberlain's Security+ 3.0 generation — launched November 2025, identified by a WHITE learn button — moved accessory communication to encrypted Bluetooth LE. Be precise about what changed at the terminals, because the popular version of this is imprecise: the wall-button terminals still physically exist on a Security+ 3.0 opener, but the wired button is now a PAIRED device that must be learned to the opener rather than a dumb contact you can short. Either way there is nothing for a wire-tapping board to decode. So check your learn button colour before ordering: yellow, purple or red and this works; white and it does not, and no future firmware will change that. One exception to the colour shortcut, and it runs in the buyer's FAVOUR: the wall-mounted jackshaft openers 8500/RJ020 and 8500C/RJ020C carry a yellow button but are Security+ 1.0, not 2.0. They are supported — Security+ 1.0 uses a compatible wall control panel (the vendor names the 889LM and 041A7928-3MC) for door status, with dry-contact control as the documented fallback. Note that the vendor spells these codes two different ways on its own pages, RJ020 with a digit and RJO20 with a letter, so match yours by the rest of the string rather than by that character. Two smaller catches worth knowing before you buy. Firmware is not included and you flash it yourself, which several write-ups get wrong. And the three firmware builds are mutually exclusive, so the choice between native Apple Home and Home Assistant is made at flash time and is not a setting you toggle later.

Who it's for

Home Assistant households with a Security+ 1.0 or 2.0 opener — yellow, purple or red learn button — who lost myQ in 2023; this is the canonical fix and the one Home Assistant itself recommends. Also a fit for Apple Home households who want bridge-free, fully local garage control with no hub and no account, which almost nothing else in this category offers. And for owners of non-Chamberlain openers or gates with dry-contact terminals, where the generic path works. The buyer needs to be comfortable flashing firmware from a browser and wiring three conductors to a terminal block; realistically this is enthusiast-level rather than intermediate DIY. It is the wrong buy for anyone with a white learn button, for Alexa- or Google-primary households with no Home Assistant — since the workaround reintroduces the cloud dependency and subscription cost the product exists to avoid — for SmartThings households, for anyone expecting a pre-flashed app-in-a-box experience, and for anyone unwilling to accept an explicit 'use at your own risk' disclaimer on a device that moves a crushing hazard.

Sources & method

Numbered sources below back the facts marked with the matching number above. 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 →

1. [1] The vendor field on every SKU in ratcloud.llc's own product JSON reads 'ratcloud llc'. RECORDED EXPLICITLY BECAUSE THE COMMON ATTRIBUTION IS WRONG: Konnected sells a separate competing product, the GDO blaQ (SKU KIT-GDOv2-Q, $89.00), built by adapting ratgdo's open-source code into Konnected's own gdolib library. Konnected's founder describes it in their own forum as 'our open-source adaptation of ratgdo, packaged as a portable library for ESP32 devices' and confirms the relationship is independent and amicable, at community.konnected.io/t/how-konnected-re-wrote-ratgdo-to-secure-the-future-of-the-open-garage-door/36571. — vendor-data and counterparty-source research, verified 2026-07-19
   Backs: Product identity
2. [2] ratcloud.llc/products.json?limit=100, read 2026-07-19: ratgdo32 (32k) $62.00 available:true published 2024-12-02; ratgdo32 disco (32disco) $94.00 available:true published 2024-11-10; ratgdo encoder (enc) $28.00 available:true published 2026-06-10; ratgdo v2.53i kit (2.53iK) $54.00 available:FALSE published 2024-07-03. Availability read from the store's own inventory flags rather than from rendered price display. — vendor-data research (cart/inventory state), verified 2026-07-19
   Backs: Price, Market availability
3. [3] csa-iot.org certified-products searches for 'ratgdo', 'ratcloud', 'konnected' and 'wieland' all returned 'No Entries Found'. VALIDATED AS A TRUE NEGATIVE rather than a bot-wall by running control searches through the identical endpoint and user agent for 'aqara', 'eve' and 'nanoleaf', each of which returned live csa_product result slugs. The search mechanism demonstrably works; ratgdo is genuinely absent from the registry. Corroborated by the word 'Matter' appearing nowhere in the homekit-ratgdo32 documentation. — registry research with control test, verified 2026-07-19
   Backs: Protocols
4. [4] The vendor states it directly in its own FAQ at ratcloud.llc/pages/frequently-asked-questions: 'Security + 3.0 openers are not supported.' The mechanism is documented in OpenGarage's vendor-authored technical writeup at opensprinkler.com/security-3-0-how-to-use-it-with-opengarage/ (dated 2026-01-23, retrieved in a rendering browser after plain fetch returned HTTP 403), which states plainly that 'RatGDO, Konnected, Tailwind, you name it, none supports it.' Chamberlain's own materials independently confirm Security+ 3.0 exists, is identified by a white learn button, and uses BLE — see support.chamberlaingroup.com's learn-button article, the CH125 Security+ 3.0 wall control product page, and the L956W manual (114-6096-000) stating 'All Security+ 3.0 garage door openers have a white learn button'. MECHANISM STATED PRECISELY, BECAUSE THE POPULAR VERSION IS WRONG IN DETAIL: the widely repeated claim is that the wall-button terminals are gone or carry power only. Chamberlain's OWN wired push-button manual (114-6085-000, models 003-0853-000 / 041-0489-000) shows the terminals still exist — 'Connect one of the wires to the red terminal and the other wire to the white terminal' — but ALSO requires the button to be LEARNED to the opener (press LEARN, then 'within 30 seconds, press and hold the push button until the garage door opener lights flash'). A dry contact needs no pairing, so what actually changed is that the wired button became a paired device rather than a shortable contact. The stronger 'power only' claim traces to a scope measurement in esphome-ratgdo issue #492 (a user reporting 'no sort of signalling on the line, only a constant (approximately) 14V DC', 2025-10-28) and maintainer Paul Wieland stating he is '98% confident' of it (2025-11-20) — a named community inference with a stated confidence level, NOT a Chamberlain statement, and recorded as such. The practical conclusion is unaffected either way. — vendor-page and counterparty-source research (rendering browser), verified 2026-07-19
5. [5] Wiring a controller to the button contacts of a spare paired remote bypasses the encryption by letting Chamberlain's own hardware send the signal. OpenGarage documents the method (opensprinkler.com, 2026-01-23) and notes it is one-way: 'OpenGarage can send commands to trigger door actions, but it will not receive feedback or status updates from the remote.' In esphome-ratgdo issue #492 a user reports success (2025-12-12), with contributors noting the low-power MCU's high-impedance pull-up may need a MOSFET buffer rather than a bare relay, and rayshobby adding that the 3.0 wall button 'doesn't even need to be wired to the GDO — you can power it directly with a 12VDC adapter'. RECORDED BUT NOT RECOMMENDED: it is not a vendor-documented configuration for ratgdo or for any product in this category. — vendor-page and counterparty-source research (rendering browser), verified 2026-07-19
   Backs: Product identity
6. [6] github.com/PaulWieland/ratgdo/wiki and paulwieland.github.io/ratgdo/ for Security+ 2.0 full support (door, light, obstruction, wireless lockout, motion), Security+ 1.0 support since v2.5, and dry contact for any opener or gate with dry-contact terminals including non-Chamberlain units. ⚠ CORRECTED 2026-08-13 — this entry previously read 'Explicitly incompatible jackshaft models 8500, 8500C, RJO20, RJO20C are named in the vendor's own wiki'. That misread the wiki. The wiki's compatibility TABLE lists 'Chamberlain/LiftMaster | 8500, 8500C, RJ020, RJ020C | Security + 1.0 or Dry Contact' — i.e. SUPPORTED. The 'Excluding wall mounted jackshaft openers 8500, 8500C, RJO20, RJO20C' line is an exclusion from the YELLOW-BUTTON row (it sits beside 'yellow learn button, but older wireline control protocol'), not an exclusion from support. 'Model 8500W & RJ070 are ok' remains accurate as written. github.com/ratgdo/homekit-ratgdo32 documents a known limitation that Security+ 1.0 doors with the 0x37 digital wall panel do not work. — vendor-documentation research, verified 2026-07-19
7. [7] github.com/ratgdo/homekit-ratgdo32 README states the firmware works 'over your local network using HomeKit… It requires no supporting infrastructure such as Home Assistant, Homebridge, MQTT, etc.', and documents the absence of a native stop command. The ESP32-only constraint is stated in the same repository. Mutual exclusivity with the ESPHome build follows from these being separate firmware images for one board. — vendor-documentation research, verified 2026-07-19
   Backs: Apple Home compatibility
8. [8] home-assistant.io/integrations/esphome/ classifies ESPHome as a core integration at Platinum quality tier with IoT class Local Push, over a persistent local TCP connection on port 6053 with mDNS discovery. esphome.io/components/api.html describes each ESP as its own server with no cloud dependency by design. Per 09 §3, the claim about what Home Assistant supports is sourced to Home Assistant, not to the vendor. Home Assistant's own myQ removal post additionally recommends ratgdo by name as the replacement. — counterparty-source research, verified 2026-07-19
   Backs: Home Assistant compatibility
9. [9] ratcloud.llc/pages/frequently-asked-questions states of Alexa and Google: 'we don't support them natively.' The cost of the Home Assistant workaround is sourced to Home Assistant's own documentation: home-assistant.io/integrations/alexa/ requires either Home Assistant Cloud or a manual Amazon Developer and AWS Lambda setup with public HTTPS exposure, and home-assistant.io/integrations/google_assistant/ documents that door, garage and gate covers are secure devices requiring a secure_devices_pin to open by voice. — vendor-page and counterparty-source research, verified 2026-07-19
   Backs: Google Home compatibility, Amazon Alexa compatibility
10. [10] ratcloud.llc/pages/frequently-asked-questions states the HomeKit firmware 'does not require a home automation hub and works locally on your network without requiring a cloud service'. No cloud account exists in the purchase or operation path for the Apple Home or Home Assistant routes. — vendor-page research, verified 2026-07-19
    Backs: Subscription, Works without the internet, Vendor account required, Required hub or bridge
11. [11] paulwieland.github.io/ratgdo/ carries the vendor disclaimer 'Use this device at your own risk. To avoid risk of injury or property damage only operate the garage door within line of sight.' ratcloud.llc/pages/frequently-asked-questions warns that obstruction sensors above 18 V will destroy the input circuit. UNKNOWN 1: no affirmative vendor statement confirms the opener's own entrapment protection is preserved, and paulwieland.github.io/ratgdo/01_features.html makes no mention of UL 325 — so this is recorded as unestablished rather than inferred from how the device works. UNKNOWN 2: the vendor is silent on whether installation affects the opener manufacturer's warranty and no primary source was found either way, so neither claim is made. Vendor documents also disagree on obstruction sensor voltage: 5–16 V in the FAQ versus peak 4.5–7 V on the features page. — vendor-documentation research, verified 2026-07-19
12. [12] Multiple search angles for a cease-and-desist, lawsuit or formal action against ratgdo or ratcloud llc returned nothing, including a check of Chamberlain Group's own press page. Recorded as 'searched and not found' rather than as proven absence. Chamberlain's actions against third-party access have been technical and architectural rather than legal: the October 2023 API blocking and the November 2025 Security+ 3.0 hardware change. — negative-result search, recorded as such, verified 2026-07-19
13. [13] tarahome.ai and homeautomationworkshop.com publish 2026-dated 'complete guide' roundups on this product; not used for any load-bearing claim, though tarahome.ai's Security+ 3.0 detail later proved directionally correct — noted as low-trust-that-happened-to-be-right rather than treated as a source. enshitifai.com is an advocacy site, not a record source. A YouTube video titled 'Chamberlain HATES This' surfaced repeatedly on legal-action queries and was explicitly not treated as evidence of any Chamberlain action. Worth recording that NO source encountered falsely claimed Matter certification for this product — unusual in this category, where fabricated certification claims are the common failure mode. — source-quality audit, verified 2026-07-19
14. [14] Firmware is actively maintained across the github.com/ratgdo organisation in three separate builds (esphome-ratgdo, homekit-ratgdo32, mqtt-ratgdo), and a new accessory — the ratgdo encoder — was published to the store on 2026-06-10, indicating an active product line rather than a — migrated hand stamp, verified 2026-07-19
    Backs: Service status
15. [15] ratcloud.llc/products.json?limit=100, read 2026-08-13: ratgdo32 $62.00 available:true; ratgdo32 disco $94.00 available:true; ratgdo encoder $28.00 available:true. Both figures are byte-identical to the 2026-07-19 read, and compare_at_price is absent throughout, so $62.00 is list rather than a promotion. ⊕ ONE MOVEMENT, on a SKU this record does not price: 'ratgdo v2.53i kit' ($54.00) is still available:false, the same state as July — the ESP8266 generation this board supersedes has not come back. — vendor-data research (structured storefront endpoint, per the standing method rule), verified 2026-08-13
    Backs: Price, Market availability
16. [16] github.com/ratgdo/homekit-ratgdo32 latest release is v3.5.1, published 2026-07-22, whose notes fix an encoder watchdog false trigger and a HomeKit light-switch regression. Read through the GitHub releases API rather than the rendered repo page. This is the axis's whole argument: an open-source firmware with no vendor cloud cannot have its integrations revoked, but that is a structural claim about ARCHITECTURE — 'service: full' additionally needs someone still shipping fixes, and a dated release three weeks old is what establishes it. — counterparty-source research (release API), verified 2026-08-13
    Backs: Service status
17. [17] Two vendor pages read the same day and they still disagree. ratcloud.llc/pages/frequently-asked-questions: 'If the sensors are not 5-16v, ratgdo will still be able to control the door but it will not provide obstruction status' and 'CAUTION: connecting higher than 18v sensors will destroy the obstruction input circuit.' paulwieland.github.io/ratgdo/01_features.html: 'Obstruction sensors must have a peak voltage between 4.5 and 7 volts.' ⚠ METHOD NOTE ON HOW THIS WAS CONFIRMED: a first, topically-scoped read of the FAQ returned only the 5-16v sentence and would have supported deleting the 18v warning as unreproducible. An exhaustive re-read — asking for EVERY occurrence of the token rather than for the topic — returned both. A summariser answering 'what does this page say about X' can stop at the first match; a claim about ABSENCE has to be asked for exhaustively or not at all. — vendor-documentation research (exhaustive token read), verified 2026-08-13
    Backs: Maintenance
18. [18] This record's whoItsFor said the vendor 'lists as incompatible' the jackshaft models 8500/8500C/RJO20/RJO20C. Both halves were wrong, checked against the vendor's own two pages on 2026-08-13. ① THE SEMANTICS: the sentence those models appear in is about protocol GENERATION, not support — paulwieland.github.io/ratgdo/01_features.html reads 'All yellow learn button openers are Security + 2.0 EXCEPT the jackshaft wall mounted 8500/RJ020 & 8500C/RJ020C which use the Security + 1.0 protocol', and the same page documents Security+ 1.0 control ('Security + 1.0 opener with compatible wall control panel', the 889LM / 041A7928-3MC, with dry contact as the fallback). Security+ 1.0 is SUPPORTED; only Security+ 3.0 is not. ② THE MODEL STRINGS: the vendor writes R-J-zero-two-zero, we published R-J-letterO-two-zero — a difference that matters precisely because a buyer is meant to match it against the label on their opener. Corrected by deleting the exclusion and adding the exception to theCatch, where it belongs: it is the one case where the learn-button colour shortcut misidentifies an opener, and it runs in the buyer's favour. — vendor-documentation research (character-level transcription of the model codes), verified 2026-08-13
19. [19] raw.githubusercontent.com/ratgdo/homekit-ratgdo32 README read 2026-08-13. Still verbatim: 'It requires no supporting infrastructure such as Home Assistant, Homebridge, MQTT, etc' and 'works over your local network using HomeKit, or over the internet using your Apple HomeKit home hubs'. Board scope confirmed: it is for the 'ESP32-based ratgdo32 and ratgdo32-disco series boards' and 'will not work with the ESP8266-based ratgdo v2.5xi boards'. ⚠ ONE CORRECTION: on stop, the README says HomeKit has no stop command AND that the firmware offers an additional HomeKit control to stop a door while it is operating on ratgdo32 boards (not on v2.5). We had recorded only the limitation. Fixed. — counterparty-source research (raw file, not the rendered repo page), verified 2026-08-13
    Backs: Apple Home compatibility, Product identity
20. [20] ratcloud.llc/pages/frequently-asked-questions read 2026-08-13 with an exhaustive token sweep rather than a topical question. 'subscription': ZERO occurrences. 'account': ZERO occurrences. 'Matter': ZERO occurrences. Alexa/Google verbatim: 'These cloud based services are the antithesis of ratcloud and ratgdo, so we don't support them natively' — followed by 'however yes, you can integrate with them if you use another service such as Home Assistant or Node-RED to bridge between ratgdo local control and whatever cloud based integration you want to use', which is exactly the middleware-only route both cells record. Local operation verbatim: 'Note that the native HomeKit firmware does not require a home automation hub and works locally on your network'. ⚠ THE METHOD IS THE POINT: an earlier topical read of this same page THAT SAME DAY reported 'no sentences addressing subscriptions, cloud services, or account requirements' — which is true for two of the three and false for the third, because the local-operation sentence exists and the topical read missed it. Absence claims get an exhaustive token sweep. — vendor-documentation research (exhaustive token sweep), verified 2026-08-13
    Backs: Amazon Alexa compatibility, Google Home compatibility, Subscription, Works without the internet, Vendor account required
21. [21] home-assistant.io/integrations/esphome read 2026-08-13: still a CORE integration at '🏆 Platinum quality' with IoT class 'Local Push', maintaining persistent local connections via the native ESPHome API with no cloud service in the path. Both figures the record leans on — the tier and the local-push classification — are unchanged. Read from the counterparty's documentation rather than the vendor's, which is the whole reason this cell is rated on evidence rather than on marketing. — counterparty-source research, verified 2026-08-13
    Backs: Home Assistant compatibility
22. [22] csa-iot.org/csa-iot_products/?p_keywords=ratgdo read 2026-08-13 returns 'No Entries Found'. VALIDATED AS A TRUE NEGATIVE ON THE SAME DAY by running the identical endpoint with p_keywords=aqara, which returned a full page of Matter certificates (Aqara Camera Hub, Lumi United Technology, certificate IDs listed, multiple pages). The search mechanism demonstrably worked at the moment ratgdo returned nothing. ⊕ Corroborated vendor-side: the word 'Matter' has zero occurrences in ratcloud's FAQ under today's exhaustive token sweep. So protocols stays wifi-only. — registry research with same-session control test, verified 2026-08-13
    Backs: Protocols
23. [23] Re-verification performed 2026-08-13 (BQ-107 batch 33): prices and stock from the store's structured product JSON · firmware currency from the GitHub releases API (v3.5.1, 2026-07-22) · Alexa/Google/subscription/local-operation from an exhaustive token sweep of the vendor FAQ · Apple cell from the HomeKit firmware README · Home Assistant classification from home-assistant.io · Matter negative re-run with a live control test. ONE CUSTOMER-FACING CORRECTION made: the jackshaft exclusion in whoItsFor was wrong in both its semantics and its model strings. One cell improved: the Apple stop-command limitation was only half the story on this board. No integration level changed. — record re-verification (BQ-107 batch 33), verified 2026-08-13
    Backs: Research status
24. [24] github.com/PaulWieland/ratgdo/wiki read 2026-08-13 with an exhaustive token sweep. The compatibility table carries the row 'Chamberlain/LiftMaster | 8500, 8500C, RJ020, RJ020C | Security + 1.0 or Dry Contact', which lists these openers as SUPPORTED by two named routes. The line 'Excluding wall mounted jackshaft openers 8500, 8500C, RJO20, RJO20C.' sits beside 'yellow learn button, but older wireline control protocol' and excludes them from the Security+ 2.0 ROW, not from support. The tokens 'incompatible', 'not supported' and 'not compatible' appear NOWHERE on the page. ⚠ WHY THIS ENTRY EXISTS AT ALL: the same-day correction was made against the vendor's features page and FAQ, and only afterwards did a grep of this record surface a provenance entry citing THIS wiki for the opposite claim. The correction was right and the verification order was wrong — the source a claim cites is the first place to check before overturning it, not the last. ⊕ The wiki also spells the models BOTH ways in the space of two lines (RJ020 in the table, RJO20 in the exclusion), so the earlier note that 'the vendor writes them with a digit' was itself too confident and has been softened. — counterparty-source research (exhaustive token sweep of the cited source), verified 2026-08-13
25. [25] github.com/ratgdo/homekit-ratgdo32 README and the calibrated CSA-IoT registry searches, both already cited on this record — evidence read against sources this record already cites (BQ-191 provider-side backfill, D-7 bars), verified 2026-08-19
    Backs: What it provides to your home
26. [26] The homekit-ratgdo32 firmware documentation, read 2026-08-20, which enumerates the HomeKit accessories the board creates: a "Garage door with door state, obstruction detection, and lock (lock unavailable with Dry Contact protocol)", a "Light switch (unavailable with Dry Contact protocol)", a "Motion sensor (auto-added for doors with wall panels; optional trigger via button/obstruction)", and a "Contact sensor (ratgdo32 with rotary encoder enabled)". Control covers "opening and closing garage doors independently in the same HomeKit home". — vendor-and-ecosystem-doc research (BQ-187 capabilities population, batch 8 — sensors + garage-access), verified 2026-08-20
    Backs: Capabilities
27. [27] ratcloud llc first-party surfaces read 2026-08-22. ratcloud.llc/pages/firmware documents installing the ESPHome and HomeKit builds on ratgdo32 and ratgdo32 disco boards over Bluetooth, WiFi or USB web serial, and states no support period, end date or patching duration. ratcloud.llc/pages/frequently-asked-questions covers opener compatibility (Security+ 1.0 and 2.0 supported, Security+ 3.0 not) with no support-period statement. Neither page, nor the vendor's firmware installation pages, publishes a security-update commitment; the firmware is distributed from public repositories under open-source licences. — first-party security-support sweep (BQ-192, method note 69 rungs a-c walked, outcome recorded whichever way it fell), verified 2026-08-22
    Backs: Security-update support period
28. [28] No source was read for this entry, deliberately. It records a classification so the classification is not silent: what was classified is evidence this record already carried — the integration catches and the citations already listed on this page — and this pass altered none of it. — absence-classification reading pass (doc 16 #453) — this record's own integration catches and the provenance entries claiming them, re-read against the 2026-08-22 classification; no vendor page fetched and no new research done, verified 2026-08-22
29. [29] Record-keeping entry: the migrated research stamp was retired from this record on 2026-08-30 — internal, verified 2026-08-30

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.

Check it against YOUR setup →