There is not enough model-specific evidence to draw a supported connection. Read the evidence and limits below.
Product Library / Garage & Access
Research profile · verified 2026-10-12 · sources re-checked 2026-11-16OpenGarage
Compatibility at a glance
Does it work with your home?
Choose your platform to see its setup and functions. Your choice carries across product pages.
A connection can work while individual controls or automations remain unconfirmed. Read the connection details ↓
Before you buy
What do you need to make it work?
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.[8][30][35]
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.[5][30]
There is not enough model-specific evidence to draw a supported connection. Read the evidence and limits below.
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.[5][30]
There is not enough model-specific evidence to draw a supported connection. Read the evidence and limits below.
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.[5][30]
There is not enough model-specific evidence to draw a supported connection. Read the evidence and limits below.
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.[5][30]
Follow the recorded connection below. Equipment details and setup limits explain what else this path needs.
Connection summary
OpenGarage
- OpenGarageOpenGarage
- Official integrationHome AssistantPlatform control
What you gainThis connection communicates locally.
Keep in mindIntermediate equipment and transport are not mapped in this summary. Read the setup notes before choosing hardware. Check the function table for supported controls and routines. A connection diagram does not establish every function or remote access.
How to read the equipment roles
This shows the connection route, not every network cable or a shopping list. One device may provide several roles, including a Matter controller and a Thread border router. Only a Thread connection needs the Thread role. Read the equipment cards for all recorded requirements.
Sources for these setup paths
- Setup documentation · checked 2026-11-06
- Setup documentation · checked 2026-11-06
- Setup documentation · checked 2026-11-06
- Setup documentation · checked 2026-11-09
These paths summarize documented setup options. Check the function table for the connection covered by each recorded capability.
The one thoroughly established integration, and it is a genuine one. OpenGarage's current manual, for firmware 1.2.5, says 'Home Assistant includes a built-in OpenGarage integration for the stock firmware' and that it 'provides door control, vehicle presence and distance readings, and optional temperature/humidity readings.' For Security+ extras such as the opener light and remote lock, OpenGarage points to an alternative ESPHome-based firmware instead, and installing it replaces the stock firmware. Home Assistant's own documentation backs that from its side rather than resting on the vendor's word: it lists OpenGarage under Blinds & curtains, says the integration works over your own network, was added in Home Assistant 0.44 and is set up through the interface, and adds that on supported devices it also creates a light entity for the opener's light. TWO HONEST QUALIFIERS. Home Assistant asks the device for its state on an interval rather than being told the instant it changes, so expect a short lag. And it is a small integration by adoption, reported at 505 active installations in Home Assistant's own figures on 2026-11-06, which is a fair signal of how much community testing sits behind it.[4][30][32][33][34][35][41]
The equipment list for this platform is not fully specified here. Use the documented setup above; an empty list does not mean no equipment is needed.
One device can provide more than one role. These are setup requirements, not a shopping list of separate purchases.
What could you do with this?
Put its functions to use.
Start with a documented control or event. The selected connection shows what is confirmed for that platform.
Apple Home · Inconclusive
Open/close
This device supports open/close.
- Control
- Inconclusive
- Automation
- —
Setup: See the equipment information above.
Setup and sources
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.
Connection documentation: [5] [30]
Device documentation: [14] [30] [35]
opengarage.github.io · checked 2026-08-20
opengarage.github.io · checked 2026-11-06
opengarage.github.io · checked 2026-07-28
opengarage.github.io · checked 2026-10-28
Google Home · Inconclusive
Open/close
This device supports open/close.
- Control
- Inconclusive
- Automation
- —
Setup: See the equipment information above.
Setup and sources
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.
Connection documentation: [5] [30]
Device documentation: [14] [30] [35]
opengarage.github.io · checked 2026-08-20
opengarage.github.io · checked 2026-11-06
opengarage.github.io · checked 2026-07-28
opengarage.github.io · checked 2026-10-28
Alexa · Inconclusive
Open/close
This device supports open/close.
- Control
- Inconclusive
- Automation
- —
Setup: See the equipment information above.
Setup and sources
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.
Connection documentation: [5] [30]
Device documentation: [14] [30] [35]
opengarage.github.io · checked 2026-08-20
opengarage.github.io · checked 2026-11-06
opengarage.github.io · checked 2026-07-28
opengarage.github.io · checked 2026-10-28
SmartThings · Inconclusive
Open/close
This device supports open/close.
- Control
- Inconclusive
- Automation
- —
Setup: See the equipment information above.
Setup and sources
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.
Connection documentation: [5] [30]
Device documentation: [14] [30] [35]
opengarage.github.io · checked 2026-08-20
opengarage.github.io · checked 2026-11-06
opengarage.github.io · checked 2026-07-28
opengarage.github.io · checked 2026-10-28
Home Assistant · Works
Open/close
This device supports open/close.
- Control
- Not stated
- Automation
- —
Setup: See the equipment information above.
Setup and sources
The one thoroughly established integration, and it is a genuine one. OpenGarage's current manual, for firmware 1.2.5, says 'Home Assistant includes a built-in OpenGarage integration for the stock firmware' and that it 'provides door control, vehicle presence and distance readings, and optional temperature/humidity readings.' For Security+ extras such as the opener light and remote lock, OpenGarage points to an alternative ESPHome-based firmware instead, and installing it replaces the stock firmware. Home Assistant's own documentation backs that from its side rather than resting on the vendor's word: it lists OpenGarage under Blinds & curtains, says the integration works over your own network, was added in Home Assistant 0.44 and is set up through the interface, and adds that on supported devices it also creates a light entity for the opener's light. TWO HONEST QUALIFIERS. Home Assistant asks the device for its state on an interval rather than being told the instant it changes, so expect a short lag. And it is a small integration by adoption, reported at 505 active installations in Home Assistant's own figures on 2026-11-06, which is a fair signal of how much community testing sits behind it.
Connection documentation: [4] [30] [32] [33] [34] [35] [41]
Device documentation: [14] [30] [35]
opengarage.github.io · checked 2026-08-20
opengarage.github.io · checked 2026-11-06
home-assistant.io · checked 2026-11-06
api.github.com · checked 2026-11-06
api.github.com · checked 2026-11-09
A documented control or event is one part of a setup. It does not by itself establish a complete automation.
A platform connection does not confirm every function. Controls and reported events are shown separately from what an automation can use.
- Controls
- 1 documented
- Reported events
- 2 documented
Compare all five platforms. On a narrow screen, scroll the table sideways.
| Device function | Apple HomeInconclusive[5][30] | Google HomeInconclusive[5][30] | AlexaInconclusive[5][30] | SmartThingsInconclusive[5][30] | Home AssistantWorks[4][30][32][33][34][35][41] |
|---|---|---|---|---|---|
| Open/closeDevice control | Control Inconclusive | Control Inconclusive | Control Inconclusive | Control Inconclusive | Control Not stated |
| Contact stateReported event | Event Inconclusive | Event Inconclusive | Event Inconclusive | Event Inconclusive | Event Not stated |
| Vehicle detectedReported event | Event Inconclusive | Event Inconclusive | Event Inconclusive | Event Inconclusive | Event Not stated |
Automation availability for this model is not established.
✓ Documented for this connection. × A stated limit. ◐ A partial function. ? Not established. A listed device function does not establish a complete routine, its other equipment or any plan requirements.
Setup and sources
Apple Home
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.[5][30]
Google Home
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.[5][30]
Alexa
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.[5][30]
SmartThings
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.[5][30]
Home Assistant
The one thoroughly established integration, and it is a genuine one. OpenGarage's current manual, for firmware 1.2.5, says 'Home Assistant includes a built-in OpenGarage integration for the stock firmware' and that it 'provides door control, vehicle presence and distance readings, and optional temperature/humidity readings.' For Security+ extras such as the opener light and remote lock, OpenGarage points to an alternative ESPHome-based firmware instead, and installing it replaces the stock firmware. Home Assistant's own documentation backs that from its side rather than resting on the vendor's word: it lists OpenGarage under Blinds & curtains, says the integration works over your own network, was added in Home Assistant 0.44 and is set up through the interface, and adds that on supported devices it also creates a light entity for the opener's light. TWO HONEST QUALIFIERS. Home Assistant asks the device for its state on an interval rather than being told the instant it changes, so expect a short lag. And it is a small integration by adoption, reported at 505 active installations in Home Assistant's own figures on 2026-11-06, which is a fair signal of how much community testing sits behind it.[4][30][32][33][34][35][41]
Platform documentation:
opengarage.github.io · checked 2026-07-28
opengarage.github.io · checked 2026-10-28
home-assistant.io · checked 2026-11-06
opengarage.github.io · checked 2026-11-06
api.github.com · checked 2026-11-06
api.github.com · checked 2026-11-09
Listed device functions are established from vendor documentation. An ability missing here is unestablished, not necessarily absent.
Connection details and setup sources
| Ecosystem | Support | The catch |
|---|---|---|
| Apple Home | InconclusiveWe researched this and the evidence doesn't settle it — the catch explains why[5][30] | 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. |
| Google Home | InconclusiveWe researched this and the evidence doesn't settle it — the catch explains why[5][30] | 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. |
| Amazon Alexa | InconclusiveWe researched this and the evidence doesn't settle it — the catch explains why[5][30] | 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. |
| SmartThings | InconclusiveWe researched this and the evidence doesn't settle it — the catch explains why[5][30] | 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 | WorksWorks with this ecosystem[4][30][32][33][34][35][41] | The one thoroughly established integration, and it is a genuine one. OpenGarage's current manual, for firmware 1.2.5, says 'Home Assistant includes a built-in OpenGarage integration for the stock firmware' and that it 'provides door control, vehicle presence and distance readings, and optional temperature/humidity readings.' For Security+ extras such as the opener light and remote lock, OpenGarage points to an alternative ESPHome-based firmware instead, and installing it replaces the stock firmware. Home Assistant's own documentation backs that from its side rather than resting on the vendor's word: it lists OpenGarage under Blinds & curtains, says the integration works over your own network, was added in Home Assistant 0.44 and is set up through the interface, and adds that on supported devices it also creates a light entity for the opener's light. TWO HONEST QUALIFIERS. Home Assistant asks the device for its state on an interval rather than being told the instant it changes, so expect a short lag. And it is a small integration by adoption, reported at 505 active installations in Home Assistant's own figures on 2026-11-06, which is a fair signal of how much community testing sits behind it. |
? Inconclusive means we researched that ecosystem and the evidence doesn’t settle it — the catch says why, and the sources are listed below. It is a statement about the available evidence, never a verdict on the product. A Setup Check researches your exact setup where the official sources don’t answer.
Plans and ongoing costs[7][39]
✓ Works without a subscription: Yes.
Vendor account required: Optional — there is a documented way to use it without one.[18][26][40]
No subscription exists anywhere in the product, and since 2026-08-22 that rests on a vendor answer rather than on an absence. The project FAQ asks and answers it directly: 'Q: Is there a subscription fee for cloud access? No. Cloud access is completely free.' The device is open source, runs its own web UI on your LAN, and the vendor's optional remote-access service (OpenThings Cloud) is documented as giving 'full remote access to the built-in web UI. All features are supported except firmware upgrade' with no fee attached to it in any reachable documentation. ONE LIMIT ON WHAT WE CHECKED REMAINS: the vendor's store and its commercial terms live on opensprinkler.com, which refuses our requests, so this is established from the product, FAQ and firmware documentation rather than from a terms-of-sale page. Getting a remote-access token does require registering a free opensprinkler.com/openthings.io account — an account, not a fee.
Maintenance and offline use
- Batteries: None — powered by a microUSB cable into a USB power adapter.
- 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.[17][39]
- Local by construction. The device serves its own web page on your network and Home Assistant talks to it there; the optional cloud services (OpenThings Cloud, Blynk) add remote access rather than being the control path. INSTALL AND SAFETY, from the vendor's own v1.2.4 manual: on v2.3+ hardware 'CTRL must go to your opener's Red (Signal) terminal' and 'GND must go to your opener's White (Ground) terminal', for LiftMaster, Chamberlain and Craftsman openers operating at 12 V DC, with an explicit damage warning that 'Applying AC voltage or DC voltage above 20V can permanently damage the v2.3+ circuit.' The ultrasonic sensor mounts facing down from the ceiling or outward from a side mount and does double duty: door status and whether the car is there. The manual also cautions during setup that 'the door may activate or move during this time. Ensure the door's path is clear before proceeding.' A SAFETY BEHAVIOUR WORTH NAMING PRECISELY: the manual states 'A minimum 5-second sound alarm is enforced before auto-close' — enforced, not optional. That is the audible half of what the US safety standard for unattended closing requires; no visual warning is documented anywhere in the manual, and none is claimed here.
Security updates
No security-update support date is on record for this model yet. We haven't yet checked whether OpenGarage publishes one, so this is a gap in our research — not a statement about the manufacturer.
Who it's for
Home Assistant households who want a local, open-source garage controller with no account, no subscription and no vendor app — and specifically those with a Chamberlain, LiftMaster or Craftsman opener on Security+ 2.0 or 1.0, where v2.3+ hardware gives full state and the opener's light and lock. It is also the one product here worth a look if you have a Security+ 3.0 opener with a white learn button and are willing to run the sacrifice-remote workaround, accepting a spare remote as a consumable, no light control, and a configuration no vendor formally supports. The ultrasonic sensor makes it unusual in a second way that suits tinkerers: it reports car presence as well as door position, which an automation can trigger on. The buyer needs to be comfortable wiring two conductors to an opener's signal and ground terminals, mounting a sensor with a clear line to the door, and living in a browser-based web UI rather than a polished phone app. It is the wrong buy for Alexa, Google Home, Apple Home or SmartThings households, where no documented path exists and you would be building the bridge yourself; for anyone who wants push-speed status, since the Home Assistant integration polls; for anyone who wants to compare prices before committing, because the seller's site refuses automated requests and the vendor's own site quotes two different figures; and for anyone expecting the pre-close safety warning to be the full audible-and-visual pair the federal rule describes — the manual documents an enforced five-second sound alarm and no visual warning.
This opens OpenGarage's own website. We earn nothing from this link.
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 →
41 numbered sources· read them in the source's own words
- [1] opengarage.io, the product's own site, read 2026-07-28: 'At its core, OpenGarage is a WiFi-enabled device with an ultrasonic distance sensor and a relay.' The publisher is OpenThings — openthings.io carries 'Copyright © 2026 OpenThings' and presents itself as the home of both OpenSprinkler and OpenGarage, and the firmware's own cloud service is named OpenThings Cloud. Hardware generations are taken from the project's own documentation: v1.0–v1.2 predate 2018 with 2 MB flash, 'All newer versions (v1.3 and above) include 4MB flash and support the latest firmware', and v2.3+ is the generation that added native Security+ signalling. NO LEGAL ENTITY TYPE IS ESTABLISHED — see src/data/manufacturers/openthings.json; fccid.io returns no grantee for 'OpenGarage'. — Read on the maker's own site, verified 2026-07-28Backs: Product identitypage changed on 2026-11-16, after this reading
- [2] Every route our reading rules allow was tried in turn and produced no usable figure. (1) The store, opensprinkler.com/product/opengarage/, refused our requests on 2026-07-19 and again on 2026-07-28 — two observations, recorded as a blocked host, never retry-looped and never evaded. (2) The alternate first-party host, opengarage.io, ANSWERS but contradicts itself, carrying both 'Order for just $35!' and 'Order for just $45!' on the same page with no variant attached to either. RE-READ 2026-08-22: the page still carries both figures, unchanged and still unexplained, alongside 'We will ship your order right away' and 'Our garage door controller is ready to ship to you immediately' — so the contradiction is 25 days old rather than a transient edit, and no price can be published. (3) rayshobby.net, the author's older domain, 301-redirects into the blocked host; the redirect was not followed. (4) No US first-party retail listing exists — the product is not sold on Amazon, and the reachable distributors are Australian and German, quoting non-USD prices for a non-US region. (5) A Wayback snapshot was deliberately NOT used: it would be a stale figure presented as current, which is the failure this catalogue's price rule exists to prevent. OWNER RULING 2026-07-28: publish the profile with no price and the reason stated, rather than skip the product — consistent with the claim-vocabulary price playbook, which names conflicting sources as a valid reason for leaving a price unpublished. PURCHASE STATE IS SEPARATELY UNESTABLISHED, which is why lifecycle.market.soldUntil is 'unknown' and not 'current'., verified 2026-08-22Backs: Price, Market availabilitypage changed on 2026-11-16, after this reading
- [3] The vendor's own user manual, firmware documentation v1.2.4, at opengarage.github.io/OpenGarage-Firmware/1.2.4/manual/ — a first-party host that answers, which is why this record could be written at all. Quoted: power is 'a microUSB cable' into 'a USB power adapter'; the device has 'a built-in ultrasonic distance sensor for detecting door status and car presence'; on v2.3+ hardware 'CTRL must go to your opener's Red (Signal) terminal' and 'GND must go to your opener's White (Ground) terminal' for LiftMaster, Chamberlain and Craftsman openers at 12 V DC; 'Applying AC voltage or DC voltage above 20V can permanently damage the v2.3+ circuit'; and during setup 'the door may activate or move during this time. Ensure the door's path is clear before proceeding.' SAFETY FINDING, STATED PRECISELY: the manual says 'A minimum 5-second sound alarm is enforced before auto-close.' This is the THIRD product in this category to document a pre-close warning and the second to make it non-defeatable — but it is the AUDIBLE HALF ONLY. 16 CFR 1211 §1211.14 requires an audible AND visual warning; no visual warning appears anywhere in this manual, and none is claimed here. The distinction is recorded because a half-compliant warning reads as compliant on any comparison table. — Read on the maker's own site, verified 2026-07-28page changed on 2026-11-09, after this reading
- [4] The vendor's v1.2.4 manual states 'OpenGarage has an official Home Assistant integration' which 'adds the device as a cover entity. It allows door control, status monitoring, and automation.' Per 09 §3 the platform-side claim is sourced to the platform: home-assistant.io/integrations/opengarage/ lists the integration under the Cover and DIY categories with IoT class Local Polling, introduced in Home Assistant 0.44, configured through the UI, and reported roughly 515 active installations in Home Assistant's own analytics when this entry was first written on 2026-07-28. BOTH QUALIFIERS ARE RECORDED IN THE CELL rather than smoothed over: Local Polling is not Local Push, and a figure in the low hundreds is a small integration. RE-READ 2026-08-22: home-assistant.io/integrations/opengarage/ still lists the integration in the Cover and DIY categories and still states 'Its IoT class is Local Polling.' The adoption figure has moved slightly, to '511 active installations', and the record's prose is corrected to match. — Read on the maker's own site, verified 2026-08-22Backs: Home Assistant compatibility
- [5] The vendor's v1.2.4 user manual enumerates the product's integrations by name and describes each: Home Assistant (official, cover entity), MQTT ('OpenGarage exposes… MQTT support'), IFTTT (via a 'Webhook service key'), OpenThings Cloud ('Allows full remote access to the built-in web UI. All features are supported except firmware upgrade') and Blynk ('Allows remote status checks and door control, but does not allow settings, logs, or firmware upgrade'). Alexa, Google Home, Apple HomeKit and SmartThings appear NOWHERE in that documentation. RECORDED AS UNKNOWN, NOT NONE, DELIBERATELY: #23 forbids unevidenced negatives, and an absence from a list is weaker evidence than a vendor statement of non-support — the ratgdo record could record 'none' precisely because that vendor's FAQ says 'we don't support them natively', and OpenGarage's reachable documentation says no such thing in either direction. The vendor surfaces that might settle it (the store's own compatibility and FAQ pages) are on opensprinkler.com, which refuses our requests. This is, in practice, the situation our reading rules call a blocked and unwatchable site, described here before the record had a way to say it. — Read on the maker's own site, verified 2026-07-28Backs: Amazon Alexa compatibility, Google Home compatibility, Apple Home compatibility, SmartThings compatibilitypage changed on 2026-11-09, after this reading
- [6] The vendor-authored technical write-up at opensprinkler.com/security-3-0-how-to-use-it-with-opengarage/ (dated 2026-01-23), read 2026-07-19 in a rendering browser and again during grind run 2 on 2026-07-28. THE HOST NOW REFUSES PLAIN REQUESTS, and under our reading rules a site that later refuses us does not invalidate an earlier read — this is a real prior read, dated, not a reconstruction. It documents the sacrifice-remote method (wire OpenGarage to the button contacts of a spare paired remote so Chamberlain's own hardware sends the encrypted signal), states of the 2025 generation that 'RatGDO, Konnected, Tailwind, you name it, none supports it', and states the limitation directly: OpenGarage 'can send commands to trigger door actions, but it will not receive feedback or status updates from the remote.' The configuration requires Classic v2.2 or v2.3+ with the Security+ version set to None, which is what costs the garage-light sense and control. THIS CORRECTS OUR OWN DOC 02 §16, which summarised the method as 'one-way with no status feedback'. The second half was wrong: the one-way limit applies to the REMOTE leg, while OpenGarage's ultrasonic distance sensor reports door position independently of the opener, so door status is not lost. Doc 02 corrected in the same change. The v2.3+ native Security+ 2.0/1.0 capability is separately sourced to the reachable firmware documentation: 'v2.3+ can communicate directly with Security+ 2.0 and 1.0 systems (commonly used by LiftMaster, Chamberlain, and Craftsman brands)', giving 'opening, closing, stopped (partially open)' status and control of 'the opener's light and lock', where v2.2 and earlier 'rely solely on the distance sensor for detecting door status'., verified 2026-07-28page changed on 2026-11-09, after this reading
- [7] No subscription, fee or paid tier appears anywhere in the reachable documentation set, and as of the 2026-08-22 re-read the vendor states it outright rather than merely omitting it: the project FAQ at opengarage.github.io/OpenGarage-Firmware/faq/ reads 'Q: Is there a subscription fee for cloud access? No. Cloud access is completely free.' The v1.2.4 manual describes OpenThings Cloud as giving 'full remote access to the built-in web UI. All features are supported except firmware upgrade' and Blynk as allowing 'remote status checks and door control', neither with a price. The device's own web interface, MQTT, IFTTT and its direct web-command control carry no fee in any document read. MAINTENANCE FACTS from the same manual, unchanged on re-read: mains power over microUSB with no batteries, an enforced 'minimum 5-second sound alarm … before auto-close', and firmware updated over the air through the web UI. WHAT WAS NOT CHECKED, stated rather than implied: opensprinkler.com carries the commercial terms and refuses our requests, so no terms-of-sale page backs this. No paid tier was found; none is asserted to be impossible. — Read on the maker's own site, verified 2026-08-22Backs: Subscription, Batteriespage changed on 2026-11-09, after this reading
- [8] The device is documented throughout as a Wi-Fi device that 'creates an open WiFi Access Point (AP)' for setup and then joins the home network; no radio specification beyond that appears in the manual, and no second control radio is documented. MATTER IS NOT LISTED and no source encountered claimed Matter certification for this product — worth recording explicitly, because fabricated Matter claims are the common failure mode in this category and this is one of the products where none appeared. A csa-iot.org registry query could not be run reliably on the day of the read (the search form returned its empty default rather than results), so the absence of a certificate is recorded as UNCHECKED at the registry rather than as a confirmed negative — the vendor makes no Matter claim to contradict. RE-READ 2026-08-22: the v1.2.4 manual still documents AP-mode setup at 192.168.4.1 followed by local access over the home Wi-Fi network by device IP or mDNS hostname, with no second control radio and no Matter claim anywhere in the manual or its command reference. The hub-requirement wording is revised here for two facts the manual now carries and the old wording denied: the Device Key ("The Default Device Key is: opendoor") is what authorises door actions and settings changes, and the vendor now publishes native iOS and Android apps alongside the browser web app., verified 2026-08-22Backs: Protocols, Required hub or bridgepage changed on 2026-11-09, after this reading
- [9] Load-bearing claims rest on opengarage.io, opengarage.github.io (the project's own documentation) and home-assistant.io, plus one dated historical read of opensprinkler.com from 2026-07-19. Search-result summaries were used only to locate URLs and were treated as evidence for nothing — this matters here, because a search summary asserted a '$33.00' price for this product that we could not reproduce from any page we read, and it was NOT used. HOST CONDUCT per the policy ratified 2026-07-28: opensprinkler.com refused our requests on 2026-07-19 and 2026-07-28 (last successful read 2026-07-19; the working alternatives are opengarage.io and opengarage.github.io); it was tried once on the day of the read and never repeatedly. rayshobby.net 301-redirects into that host and the redirect was not followed. NO user-agent, proxy or header manipulation was used anywhere. THIS RECORD IS THE FALLBACK LADDER WORKING AS DESIGNED: the store blocked, the documentation subdomain answered and carried better facts, and the one thing no rung could supply — a price — is left unset with the reason stated rather than filled from a stale or contradictory figure., verified 2026-07-28
- [10] Re-read 2026-08-22 across the project's own documentation set and product site. Firmware and documentation remain actively maintained and openly published: opengarage.github.io/OpenGarage-Firmware/ still presents v1.2.4 as the current release with a user manual and a command reference dated 'Oct 6, 2025', the manual still documents over-the-air firmware updates through the web UI, and the v2.3+ hardware generation's native Security+ 2.0/1.0 signalling is unchanged. The documentation has GAINED material since the last check rather than lost it — a Native App section naming iOS and Android clients, and an OpenGarage support article on cloud connection modified 10 Oct 2025. Home Assistant's integration for the device remains in core. No withdrawal, sunset or capability-removal notice appears on any surface read. The two qualifiers on this record's service note are unchanged and neither is a vendor retreat: OpenThings Cloud is an optional service that could end, and Security+ 3.0 is a lockout imposed by the opener manufacturer. — Read on the maker's own site, verified 2026-08-22Backs: Service statuspage changed on 2026-11-09, after this reading
- [11] A scheduled re-check of this record's published facts, 2026-08-22. The primary source re-read for this stamp is the vendor's own v1.2.4 user manual at opengarage.github.io/OpenGarage-Firmware/1.2.4/manual/, checked line by line against the record: the AP-mode-then-local-IP setup, the 'Device Key' authorisation with default 'opendoor', 'Cloud Token (Optional)', 'OTC (OpenThings Cloud): Allows full remote access to the built-in web UI. All features are supported except firmware upgrade', the ultrasonic door and vehicle sensing, the CTRL/GND wiring for v2.3+ at 12 V DC with the 'Applying AC voltage or DC voltage above 20V can permanently damage the v2.3+ circuit' warning, and 'A minimum 5-second sound alarm is enforced before auto-close'. All still present and all still matching the record. The pass also found three things the record did not carry and corrected them here: native iOS and Android apps, a direct vendor answer on cloud dependence and on subscription fees, and the account requirement that attaches to remote access only. Price and four ecosystem cells remain unestablished for the reason this record already gives — opensprinkler.com refuses us — and no date was advanced on any of them. — Read on the maker's own site, verified 2026-08-22Backs: Research statuspage changed on 2026-11-09, after this reading
- [12] OpenGarage Firmware v1.2.4 User Manual — Read on the maker's own site, verified 2026-08-17Backs: Power sourcepage changed on 2026-11-09, after this reading
- [13] The vendor's own firmware manual v1.2.4 at opengarage.github.io and home-assistant.io/integrations/opengarage, both already cited on this record — Recorded from our own earlier read, verified 2026-08-19Backs: What it provides to your home
- [14] The OpenGarage firmware manual (v1.2.4), read 2026-08-20: "A short click (less than 2 sec) → triggers the onboard relay and consequently garage door action"; "The device uses the distance sensor to detect the door's open status" and reports "closed, open, stopped (partially open), closing, opening"; car presence is detected by the same distance sensor when positioned for it. Automation surfaces are enumerated: "Select which events generate notifications. Applies to all of Blynk, Email, IFTTT, and MQTT", plus rules that "automatically notify you or close the door if it has been left open beyond a certain amount of time", and an official Home Assistant integration. — Read on the maker's own site, verified 2026-08-20Backs: Capabilitiespage changed on 2026-11-09, after this reading
- [15] No source was read for this entry. It records an edit so the edit is not silent, per the freshness guard's own instruction. — Re-checked this against its sources, verified 2026-08-20
- [16] Two first-party surfaces read 2026-08-22. The v1.2.4 user manual's 'Step 6: Browser, Mobile App, and Home Assistant Integration' now carries a Native App section: 'The official OpenGarage Web app is available for installation in both the iOS App Store and Google Play Store. It provides a native app interface for door control, status, and multiple device management', with links to apps.apple.com/us/app/opengarage-web/id6758858574 and play.google.com/store/apps/details?id=io.opengarage.app. The same section keeps the browser paths: 'OpenGarage provides a built-in web UI accessible directly from any browser using the device's local IP or hostname', and a 'lightweight OpenGarage Web App … runs entirely in your browser — no installation required.' The product site says the same thing in its own words: 'Use our free iOS, Android, Windows, or Kindle apps on your phone, tablet, or desktop.' Only ios, android and web are recordable in this field; the Windows and Kindle clients the vendor names have no enum value and are noted here instead. — Read on the maker's own site, verified 2026-08-22Backs: App platformspage changed on 2026-11-09, after this reading
- [17] The vendor answers this question in as many words on two of its own surfaces, read 2026-08-22. The project FAQ at opengarage.github.io/OpenGarage-Firmware/faq/: 'Q: Does it require a cloud connection? No. By default it connects only to your local WiFi network and does NOT rely on the Internet. Cloud connection is optional and only needed for remote access.' The product site at opengarage.io: 'For privacy- and security-minded users, OpenGarage is designed with you in mind. It does not require any cloud connection—everything works locally. Cloud access is used only when you enable it, giving you full control over your data and connectivity', under the heading 'Monitor, Control, and Automate Your Garage Door — Local-Only, or Remotely From Anywhere'. The firmware documentation matches the claim rather than merely permitting it: the v1.2.4 manual's setup runs AP mode → browser at 192.168.4.1 → 'Step 3: Access the Device Locally on Your Network' by device IP or mDNS hostname, with 'Cloud Token (Optional)' offered and skippable, and the command reference lists the cloud option's default as '0:none'. What the cloud buys is remote access only: 'To control and monitor your OpenGarage remotely from anywhere, you'll need to set up a cloud connection.' Home Assistant's own integration page independently classifies the device's local path — 'Its IoT class is Local Polling' — so the local route is attested from the platform side too. — Read on the maker's own site, verified 2026-08-22Backs: Works without the internetpage changed on 2026-11-09, after this reading
- [18] First-party, read 2026-08-22, and the two halves the vocabulary demands are separately stated. NO ACCOUNT FOR THE CORE FUNCTION: OpenThings' own OpenGarage support article, 'OpenGarage Cloud Connection for Remote Access' (created by Ray Wang, modified 10 Oct 2025), opens 'This article is relevant if you want to remotely access your OpenGarage device. If you do not need to remotely access your OpenGarage (for example, you use Home Assistant to manage your OpenGarage devices), you do NOT need to use cloud connection.' The same article's own app instructions carry the step 'Run the OpenGarage mobile app, then click Proceed without logging in…' — the vendor's app, stated by the vendor to work unsigned-in. Authorisation for door control and settings is a Device Key instead: the v1.2.4 manual says 'To perform certain actions like triggering the door or changing settings, you need to enter a Device Key. The Default Device Key is: opendoor.' AN ACCOUNT UNLOCKS REMOTE ACCESS: the same article's OTC and Blynk instructions both begin 'Go to www.openthings.io and log in using your opensprinkler.com login email/username and password. If you do not yet have an opensprinkler.com account, please go to www.opensprinkler.com and click on "My Account" at the top, then register for a new user account.' WHAT THE ACCOUNT-FREE ROUTE LOSES, named per the ladder ruling: control and status from outside the home network. Everything on the LAN — the built-in web UI, the apps pointed at the device IP, the Home Assistant cover entity, MQTT and direct web commands — is unaffected. Note on hosts: opensprinkler.com refuses our requests and was NOT read; the registration requirement is quoted from the vendor's own support article on a host that answers. — Read on the maker's own site, verified 2026-08-22Backs: Vendor account required
- [19] The project FAQ at opengarage.github.io/OpenGarage-Firmware/faq/, read 2026-08-22, answers it directly twice. 'Q: Does it have built-in wireless? Yes, OpenGarage has built-in 2.4GHz Wi-Fi (based on ESP8266).' And in its router-compatibility checklist: '2.4 GHz only: The controller's ESP8266 chip is compatible with 2.4 GHz only. Make sure your router has 2.4 GHz enabled and uses a different SSID than 5 GHz.' The same page also states 'Q: Does it have built-in wired Ethernet? No, it doesn't.' No 5 GHz or 6 GHz capability is claimed anywhere in the manual, the command reference or the product site. — Read on the maker's own site, verified 2026-08-22Backs: Wi-Fi bands it can usepage changed on 2026-11-09, after this reading
- [20] the record's own customer-facing prose fields as they stood before 2026-09-10 (no new external read), verified 2026-09-10
- [21] opengarage.github.io — OpenGarage user manual (firmware 1.2.4), 'Hardware Setup', read 2026-09-16. Verbatim: 'To connect the wires: Loosen the screws on the bottom two terminals. Strip the wire ends to an appropriate length.'; 'Using tweezers, a small screwdriver, or needle-nose pliers, wrap the wire around the screw at least one full turn.'; 'Finally, strip the other ends of the cable and insert them into your opener's wall-button terminals, following the color guide.'; 'Once you've chosen a good location, use screws or strong double-sided tape to mount the device securely.' — Read on the maker's own site, verified 2026-09-16Backs: Installationpage changed on 2026-11-09, after this reading
- [22] this record's own lifecycle note as it stood before 2026-09-18 (no new external read): its wording was rewritten so it reads in plain language. No fact, date, source or value changed, and the earlier wording is kept on this record., verified 2026-09-18
- [23] the record's own customer-facing prose fields as they stood before 2026-09-23 (no new external read), verified 2026-09-23
- [24] OpenGarage's own site, opengarage.io, read in full on 2026-10-12; the fingerprint matches change detection's copy. Verbatim: "At its core, OpenGarage is a WiFi-enabled device with an ultrasonic distance sensor and a relay" · "We will ship your order right away. Order for just $35!" · "Our garage door controller is ready to ship to you immediately. Order for just $45!" — Read on the maker's own site, verified 2026-10-12Backs: Product identity, Price, Market availabilitypage changed on 2026-11-16, after this reading
- [25] The OpenGarage firmware documentation home, read in full on 2026-10-12; the fingerprint matches change detection's copy. Verbatim: "Firmware v1.2.5 NEW User Manual API Reference Firmware v1.2.4 User Manual API Reference" · "Download OpenGarage stock firmware 1.2.5 for boards with 4 MB flash." · "The alternative ESPHome-based OpenGarage firmware provides native Home Assistant integration". — Read on the maker's own site, verified 2026-10-12Backs: Service statuspage changed on 2026-11-09, after this reading
- [26] OpenThings' own support article 'OpenGarage Cloud Connection for Remote Access' (created by Ray Wang, modified Fri, 10 Oct, 2025), read in full on 2026-10-12; the fingerprint matches change detection's copy. Verbatim: "If you do not need to remotely access your OpenGarage (for example, you use Home Assistant to manage your OpenGarage devices), you do NOT need to use cloud connection." · "Run the OpenGarage mobile app, then click Proceed without logging in..." — Read on the maker's own site, verified 2026-10-12Backs: Vendor account required
- [27] The OpenGarage firmware manual 1.2.4, as quoted on entry hw-2026-07-28: "CTRL must go to your opener's Red (Signal) terminal" · "GND must go to your opener's White (Ground) terminal"; and the OpenGarage site, as quoted on entry bq107-u1-20261012b-opengarage-site: "At its core, OpenGarage is a WiFi-enabled device with an ultrasonic distance sensor and a relay"., verified 2026-07-28Backs: What it provides to your home
- [28] OpenGarage's own site, opengarage.io, read in full on 2026-10-28. Verbatim: "At its core, OpenGarage is a WiFi-enabled device with an ultrasonic distance sensor and a relay" · "We will ship your order right away. Order for just $35!" · "Our garage door controller is ready to ship to you immediately. Order for just $45!" · "It does not require any cloud connection—everything works locally." — Re-checked this against its sources, verified 2026-10-28Backs: Product identity, Pricepage changed on 2026-11-16, after this reading
- [29] The OpenGarage firmware documentation home, read in full on 2026-10-28. Verbatim: "Download OpenGarage stock firmware 1.2.5 for boards with 4 MB flash." · "The alternative ESPHome-based OpenGarage firmware provides native Home Assistant integration, including door controls, distance and vehicle sensing, editable thresholds, and—on compatible Security+ hardware/openers—opener light, remote lock and reported obstruction status." Its firmware list links a manual for 1.2.5 and for 1.2.4. — Re-checked this against its sources, verified 2026-10-28Backs: Service statuspage changed on 2026-11-09, after this reading
- [30] OpenGarage's 'Firmware 1.2.5 User Manual', the current manual its documentation index links, read in full on 2026-10-28 (the page prints no date). Verbatim: "Home Assistant includes a built-in OpenGarage integration for the stock firmware." · "It provides door control, vehicle presence and distance readings, and optional temperature/humidity readings." · "For more native Home Assistant integration with additional features such as Security+ opener light and remote lock, use the alternative ESPHome-based OpenGarage firmware" · "Installing it replaces the stock firmware." · "Tap and release within about 0.8 seconds to toggle the door, similar to a wall button." · "CTRL must go to your opener's Red (Signal) terminal" · "Applying AC voltage or DC voltage above 20V can permanently damage the v2.3+ circuit" · "A minimum 5-second sound alarm is enforced before auto-close" · "To connect the wires: Loosen the screws on the bottom two terminals." · "The official OpenGarage Web app is available for installation in both the iOS App Store and Google Play Store" · "The Default Device Key is: opendoor". Power is "a microUSB cable", setup starts when the device "creates an open WiFi Access Point (AP)", and the manual names Home Assistant, MQTT, IFTTT, OpenThings Cloud and Blynk and no Alexa, Google Home, Apple Home or SmartThings route., verified 2026-10-28Backs: Home Assistant compatibility, Capabilities, Power source, Batteries, Protocols, Required hub or bridge, Installation, App platforms, Amazon Alexa compatibility, Google Home compatibility, Apple Home compatibility, SmartThings compatibilitypage changed on 2026-11-09, after this reading
- [31] OpenGarage's 'Firmware 1.2.4 User Manual [Oct 6, 2025]', still published beside the 1.2.5 manual, read in full on 2026-10-28. Verbatim: "OpenGarage has an official Home Assistant integration that adds the device as a cover entity." · "A short click (less than 2 sec) → triggers the onboard relay and consequently garage door action." — Re-checked this against its sources, verified 2026-10-28page changed on 2026-11-09, after this reading
- [32] Home Assistant's OpenGarage integration page, read in full on 2026-10-28 as its source file in the documentation repository on GitHub through tools/page-read.mjs (the file's base64 content decoded; blob 3a9a68bb10ba). Verbatim: "ha_iot_class: Local Polling" · "ha_release: 0.44" · "ha_config_flow: true". Its platforms list names binary_sensor, button, cover and sensor, and its category line reads 'blinds_curtains'. — Re-checked this against its sources, verified 2026-10-28Backs: Home Assistant compatibility
- [33] Home Assistant's OpenGarage integration page as published on www.home-assistant.io, read in full on 2026-11-06 through tools/page-read.mjs (plain). Verbatim: "On supported devices, the integration also provides a light entity for controlling the garage door opener light." · "The light entity is created only when OpenGarage reports light support." · "Its IoT class is Local Polling." · "OpenGarage is listed under: Blinds & curtains". The same line gives 0.44 as the release that introduced it and 505 active installations. — Read the platform's own documentation, verified 2026-11-06Backs: Home Assistant compatibility
- [34] Home Assistant's OpenGarage integration page, read in full on 2026-11-06 as its source file in the documentation repository on GitHub through tools/page-read.mjs (the file's base64 content decoded; blob 93b8defcd99e). Verbatim: "ha_release: 0.44" · "ha_domain: opengarage" · "On supported devices, the integration also provides a light entity for controlling the garage door opener light." The front matter no longer carries ha_category, ha_iot_class, ha_config_flow or ha_platforms. — Re-checked this against its sources, verified 2026-11-06Backs: Home Assistant compatibility
- [35] OpenGarage's 'Firmware 1.2.5 User Manual', the current manual its documentation index links, read in full on 2026-11-06 (the page prints no date). Verbatim: "Home Assistant includes a built-in OpenGarage integration for the stock firmware." · "It provides door control, vehicle presence and distance readings, and optional temperature/humidity readings." · "For more native Home Assistant integration with additional features such as Security+ opener light and remote lock, use the alternative ESPHome-based OpenGarage firmware" · "Installing it replaces the stock firmware." · "Tap and release within about 0.8 seconds to toggle the door, similar to a wall button." · "CTRL must go to your opener's Red (Signal) terminal" · "Applying AC voltage or DC voltage above 20V can permanently damage the v2.3+ circuit" · "A minimum 5-second sound alarm is enforced before auto-close" · "To connect the wires: Loosen the screws on the bottom two terminals." · "The official OpenGarage Web app is available for installation in both the iOS App Store and Google Play Store" · "The Default Device Key is: opendoor". Power is "a microUSB cable", setup starts when the device "creates an open WiFi Access Point (AP)", and the manual names Home Assistant, MQTT, IFTTT, OpenThings Cloud and Blynk and no Alexa, Google Home, Apple Home or SmartThings route., verified 2026-11-06Backs: Home Assistant compatibility, Capabilities, Power source, Batteries, Protocols, Required hub or bridge, Installation, App platforms, Research statuspage changed on 2026-11-09, after this reading
- [36] OpenGarage's 'Firmware 1.2.4 User Manual [Oct 6, 2025]', still published beside the 1.2.5 manual, read in full on 2026-11-06. Verbatim: "OpenGarage has an official Home Assistant integration that adds the device as a cover entity." · "A short click (less than 2 sec) → triggers the onboard relay and consequently garage door action." — Re-checked this against its sources, verified 2026-11-06page changed on 2026-11-09, after this reading
- [37] The OpenGarage firmware documentation home, read in full on 2026-11-06. Verbatim: "Download OpenGarage stock firmware 1.2.5 for boards with 4 MB flash." · "The alternative ESPHome-based OpenGarage firmware provides native Home Assistant integration, including door controls, distance and vehicle sensing, editable thresholds, and—on compatible Security+ hardware/openers—opener light, remote lock and reported obstruction status." Its firmware list links a manual for 1.2.5 and for 1.2.4. — Re-checked this against its sources, verified 2026-11-06Backs: Service statuspage changed on 2026-11-09, after this reading
- [38] OpenGarage's own site, opengarage.io, read in full on 2026-11-06. Verbatim: "At its core, OpenGarage is a WiFi-enabled device with an ultrasonic distance sensor and a relay" · "We will ship your order right away. Order for just $35!" · "Our garage door controller is ready to ship to you immediately. Order for just $45!" · "It does not require any cloud connection—everything works locally." — Re-checked this against its sources, verified 2026-11-06Backs: Product identity, Pricepage changed on 2026-11-16, after this reading
- [39] OpenGarage's documentation FAQ, read in full on 2026-11-06 through tools/page-read.mjs (plain). Verbatim: "Q: Does it require a cloud connection? No. By default it connects only to your local WiFi network and does NOT rely on the Internet." · "Q: Is there a subscription fee for cloud access? No. Cloud access is completely free." · "Yes, OpenGarage has built-in 2.4GHz Wi-Fi (based on ESP8266)" · "The controller's ESP8266 chip is compatible with 2.4 GHz only." — Read the original source directly, verified 2026-11-06Backs: Works without the internet, Wi-Fi bands it can use, Subscriptionpage changed on 2026-11-09, after this reading
- [40] OpenThings' own support article 'OpenGarage Cloud Connection for Remote Access' (created by Ray Wang, modified Sun, 25 Oct, 2026), read in full on 2026-11-06 through tools/page-read.mjs (plain). Verbatim: "If you do not need to remotely access your OpenGarage (for example, you use Home Assistant to manage your OpenGarage devices), you do NOT need to use cloud connection." · "Run the OpenGarage mobile app, then click Proceed without logging in..." — Read on the maker's own site, verified 2026-11-06Backs: Vendor account required
- [41] Home Assistant's integration metadata file for its OpenGarage integration (home-assistant/home-assistant.io, source/_data/integrations/opengarage.json on branch current, blob 34ff90d33cb6bd0308f4bd0d8282a0c5c70318c6), read in full on 2026-11-09 through GitHub, the file's base64 content decoded (readHash 136cc2f2e001). Verbatim: "iot_class": "local_polling" · "platforms": ["binary_sensor", "button", "cover", "light", "sensor"]. Home Assistant generates this file from its core code at the released version, and the integration page renders it., verified 2026-11-09Backs: Home Assistant compatibility
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 OpenGarage with your setup.
Your platform, exact hub and the functions you need determine the answer. A Setup Check researches how they fit together.