Product Library / Garage & Access
Research profile · last verified 2026-07-29Remootio 3
Compatibility
| Ecosystem | Support | The catch |
|---|---|---|
| Apple Home | WorksWorks with this ecosystem | The only one of this product's ecosystem paths where the vendor publishes a step-by-step setup procedure rather than a logo, and the only one whose behaviour is documented rather than merely asserted. Remootio's own step-by-step guide walks through adding the device in the Apple Home app, choosing 'Garage' as the location, and testing the button — and documents live status behaviour: 'While the garage door is moving, the text on the button in the Home App will change from "Closed" to "Opening" or from "Open" to "Closing".' The vendor's HomeKit page lists the supported commands as 'Open garage door. Close garage door. Is garage door open?' WHAT IS NOT ESTABLISHED, and it matters: NOWHERE on any page we could read does the vendor say whether HomeKit support is native on the device or delivered through a bridge, and no HomeKit home-hub requirement is stated either way. That is why path and transport are 'unknown' rather than 'native'/'local' — the difference decides whether this keeps working if the vendor's software stops being updated, and guessing it would be the kind of plausible inference this catalogue exists to avoid. Note also that Apple Home support arrived for this generation through an app update rather than shipping with the hardware. |
| Amazon Alexa | PartialPartial support — see the catch | Advertised in two first-party places and documented in neither that we could read — recorded as partial for exactly that reason, the same treatment this catalogue gives Tailwind's SmartThings claim. Remootio's product page names Amazon Alexa among its supported platforms, and the vendor's App Store description states that gates can be controlled via 'Alexa and Google Assistant'. The vendor does publish an Alexa tutorial, but its knowledge-base pages could not be retrieved this session because remootio.com began returning HTTP 429 partway through and did not recover after an honoured Retry-After. NO ECOSYSTEM-SIDE CONFIRMATION WAS OBTAINED EITHER: an Amazon skill listing for Remootio appears in search, but the listing itself returned HTTP 500 to us, so it is not cited here. Mechanism, transport and whether status can be queried by voice are all unestablished. Worth knowing regardless of vendor: Amazon's own developer rules require a spoken voice code before Alexa will open a garage door, so expect that step on any Alexa garage path. |
| Google Home | PartialPartial support — see the catch | Same basis and same limits as Alexa, and recorded identically. Remootio's product page names Google Assistant among its supported platforms and the App Store description states control via 'Alexa and Google Assistant'. No vendor setup documentation could be read this session, and no Google-published listing for Remootio was obtained, so nothing here rests on a source from Google's side. Mechanism and transport are unestablished; a cloud-brokered Action is the likely shape given the category, but likely is not established and is not recorded as such. |
| SmartThings | PartialPartial support — see the catch | The weakest of the four vendor-named platforms, and the one where the counterparty's own directory is silent. Samsung SmartThings appears on Remootio's product page as a supported platform. But SmartThings' own partner product directory returns HTTP 404 for Remootio (partners.smartthings.com/products/remootio, checked 2026-07-29) — an ABSENCE FROM A LIST, NOT A DENIAL, and this catalogue does not convert silence into a 'no', which is why the cell is partial rather than none. The vendor's SmartThings tutorial exists but could not be retrieved this session. Nothing about the mechanism, the transport, or whether a SmartThings hub is involved is established. |
| Home Assistant | PartialPartial support — see the catch | THERE IS NO OFFICIAL HOME ASSISTANT INTEGRATION — home-assistant.io/integrations/remootio returns HTTP 404, checked 2026-07-29 — and that is the fact a Home Assistant buyer needs first, because the vendor's platform list does not mention Home Assistant at all. What exists is a community custom component installed through HACS or by dropping a folder into `custom_components/`, and it is a genuinely local one: its documentation describes a 'Local WebSocket handshake with session encryption (no Remootio cloud required)', configured with the device's IP address plus the API Secret Key and API Auth Key taken from the Remootio app. THE UNUSUAL AND GENUINELY GOOD PART: the API underneath it is not reverse-engineered. Remootio publishes its own WebSocket API specification at github.com/remootio/remootio-api-documentation, versioned v1 through v3, with a stated commitment that newer versions remain supersets of older ones. That is the opposite of the pattern this category usually shows, where local control is obtained by working around a vendor rather than with one — and it means the local path does not depend on the vendor's goodwill continuing, only on the device continuing to speak a documented protocol. Recorded as partial rather than full because the integration is community-maintained rather than official, and because its real-world coverage and reliability were not verified from a source this session. |
Protocols: WIFI · BLUETOOTH
Needs before it works: Not established, and deliberately not answered from the shape of the product. The vendor's product page lists the device's connectivity as Bluetooth — 'also works when there is no Wi-Fi / Internet access' — plus Wi-Fi on the local network and internet access via Wi-Fi, which reads like a self-contained device needing no hub. But no vendor statement we could reach says 'no hub required' in those terms, and this catalogue does not convert a connectivity list into a hub answer. What IS established: the Home Assistant community integration talks to the device directly over the LAN by WebSocket with no Remootio cloud involved, so at least one automation path needs nothing between the platform and the device.
Subscription reality
✓ Works without a subscription: Yes.
AFFIRMATIVELY SOURCED, not inferred from an absence: Apple's App Store listing for the Remootio app states the app is 'Subscription-free' and lists its price as Free, with no In-App Purchases shown (read 2026-07-29). That statement carries more weight than the same words on a vendor page would, because Apple requires accurate disclosure of in-app purchases and subscriptions as a condition of listing — so this is the vendor's claim made on a host with an enforcement interest in it. RECORDED WITH A LIMIT ON WHAT WE CHECKED: the vendor's own pricing, terms and account pages live on remootio.com, which rate-limited us mid-session, so no paid tier was found and none is asserted to be impossible.
Maintenance reality
- Cloud dependence: No — core function survives without the vendor's cloud
- Recorded as not cloud-dependent on a specific and narrow basis: the device exposes a local WebSocket API on the LAN, the manufacturer publishes that API's specification openly, and the Home Assistant community integration built on it performs a 'Local WebSocket handshake with session encryption (no Remootio cloud required)'. Bluetooth control is separately documented by the vendor as working 'when there is no Wi-Fi / Internet access'. So a working local control path exists and is vendor-documented. THAT IS NOT A CLAIM THAT EVERY FEATURE IS LOCAL — remote access away from home, and most likely the Alexa, Google Home and SmartThings paths, will involve the vendor's cloud, and the pages that would establish exactly which parts depend on it were unreachable this session.
The catch
The single most important thing about this product is the one thing the vendor never says: WHETHER IT ANSWERS CHAMBERLAIN'S SECURITY+ 3.0 LOCKOUT. That is this category's decisive question — Chamberlain's 2025-generation openers, identified by a white learn button, cut off every third-party controller here at once — and nothing on Remootio's product page, its HomeKit pages, or its app-store listings addresses Security+ in any version. If you own a Chamberlain, LiftMaster or Craftsman opener, that silence is the fact to act on: do not assume this works with a white-learn-button opener, and treat the question as open until the vendor answers it. THE SECOND CATCH IS AVAILABILITY. The vendor's own store showed 'Sold out' on the day this profile was researched, with a price still displayed. Nothing suggests the product is discontinued — the app was updated weeks earlier and the API documentation is current — but you cannot buy it from the manufacturer today, and a price on a page is not an offer. THE THIRD IS THE SHAPE OF THE EVIDENCE ITSELF, and it is only fair to say it plainly. Four of the five ecosystem answers here rest on the vendor naming a platform rather than documenting one, because remootio.com began refusing our requests partway through research and the knowledge-base articles that would settle mechanism could not be read. The exception is Apple Home, where a real step-by-step setup guide exists and documents live open/closed status. WHAT IS GENUINELY, UNUSUALLY GOOD: the manufacturer publishes its local WebSocket API in the open, versioned, with a written promise that new versions stay backwards-compatible. In a category where local control is normally obtained by reverse-engineering a vendor who would rather you did not, a documented local protocol with a compatibility commitment is a real structural advantage — it is the difference between a device you control and a device you are permitted to control. It also means the Home Assistant path, community-built though it is, sits on a foundation the vendor has committed to rather than one it could quietly break.
Who it's for
Someone who wants a gate or garage controller they can drive locally and who values a documented, vendor-published API over a polished ecosystem story — particularly Home Assistant households comfortable installing a community integration through HACS and pasting API keys out of a phone app. It suits gates as well as garage doors, which is unusual here, and the Bluetooth path is a real advantage for a gate at the end of a driveway where Wi-Fi does not reach: the vendor documents control working 'when there is no Wi-Fi / Internet access', which most competitors in this category cannot claim. It is the wrong buy in several specific situations. If you own a Chamberlain, LiftMaster or Craftsman opener with a white learn button, do not buy this on hope — the vendor publishes no Security+ position at all, and this catalogue will not infer one. If you need Alexa, Google Home or SmartThings and want to know exactly how they work before committing, the honest answer today is that we could not establish it beyond the vendor naming them. If you want an official, supported Home Assistant integration rather than a community one, there is not one. And if you want to buy it right now, the manufacturer's own store says sold out.
Sources & method
The vendor's own product page (remootio.com/products/remootio-3, read 2026-07-29) names the product 'Remootio 3'. The legal entity comes from an ecosystem-controlled host rather than the vendor's site: Apple's App Store listing for the Remootio app names the seller as 'Assemblabs Ltd' — see src/data/manufacturers/assemblabs.json. Generation detail comes from that same listing's release notes, which record 'Remootio 2 Apple Home support' and 'Apple Home support for Remootio 3 devices' as separate items, establishing that Apple Home arrived per generation via app updates. No model number is published on any page we could read, so modelNumber is null rather than guessed. — vendor-page and app-store-listing research, verified 2026-07-29 · remootio.com/products/remootio-3, read 2026-07-29: 'Sale price $129.00 USD; Regular price $149.00 USD' with the item shown as 'Sold out'. Price and purchase state are recorded as two independent facts because they disagree — a displayed price on an unbuyable item is precisely the trap 16 #94 was filed for. soldUntil is 'unknown' rather than 'ended': no end-of-life notice, no named successor, and active maintenance on the same day (app v8.3, released May 27; a current v3 API specification published by the vendor). The catalogue has ruled this shape before — the Nest Hub 2nd gen was out of stock in every colour with no EOL notice and was recorded with availability unresolved rather than skipped. — vendor-page research, purchase state read from the page's own stock label, verified 2026-07-29 · remootio.com/products/remootio-3, read 2026-07-29, lists connectivity as 'Bluetooth (also works when there is no Wi-Fi / Internet access)', 'Wi-Fi (local network)' and 'Internet (via Wi-Fi)'. The package is listed as including a 'Sensor (for detecting if your gate is open or closed)' and the feature list includes 'Open / Close status sensor'. No Thread, Zigbee, Z-Wave or Matter support is claimed anywhere on the page and none is recorded. DELIBERATELY EXCLUDED: a search result summarising this product's electrical specification (relay output, voltage range, accessory ports) was encountered and NOT used — search summaries are not sources, a rule this catalogue has had to apply repeatedly, and no page carrying those specifications could be retrieved. That is why powerSource and installEffort are 'unknown' on a device that is obviously wired. — vendor-page research, verified 2026-07-29 · Apple's App Store listing for the Remootio app (apps.apple.com/us/app/remootio/id1456463154, read 2026-07-29) states the app is 'Subscription-free', lists Price as Free, and shows no In-App Purchases. Recorded as an affirmative statement rather than an absence argument, and sourced deliberately to Apple's listing rather than to the vendor's own marketing, because Apple requires accurate subscription and in-app-purchase disclosure as a condition of distribution. LIMIT STATED: the vendor's commercial terms live on remootio.com, which rate-limited us mid-session, so no paid tier was found and none is asserted to be impossible. — app-store-listing research, verified 2026-07-29 · remootio.com/pages/homekit-garage-door-opener-setup-using-remootio, read 2026-07-29: a numbered setup procedure that ends with the accessory in the Apple Home app, includes selecting 'Garage' as the location, and documents status behaviour verbatim — 'While the garage door is moving, the text on the button in the Home App will change from "Closed" to "Opening" or from "Open" to "Closing".' The vendor's HomeKit landing page (remootio.com/pages/homekit-garage-door-opener, read the same day) lists supported commands as 'Open garage door. Close garage door. Is garage door open?' NEITHER PAGE STATES WHETHER HOMEKIT IS NATIVE ON THE DEVICE OR DELIVERED VIA A BRIDGE, and neither states whether an Apple home hub is required — both were checked for exactly that and both are silent, which is why path and transport are 'unknown'. appPlatforms is established from the existence of first-party listings on both stores: Apple's App Store listing above, and a Google Play listing for com.remootio.app confirmed to exist and to carry the Remootio name. — vendor-documentation research plus app-store listings on both platforms, verified 2026-07-29 · remootio.com/products/remootio-3 (read 2026-07-29) names 'Amazon Alexa' and 'Google Assistant' among supported platforms, and the Remootio App Store description states gates can be controlled via 'Alexa and Google Assistant'. The vendor's own tutorial articles for both were NOT retrieved: remootio.com returned HTTP 429 with Retry-After: 60 partway through the session, the wait was honoured once, and the host returned 429 again, so it was stopped per fetch-conduct rule 1. NO ECOSYSTEM-SIDE SOURCE WAS OBTAINED for either platform — an Amazon Alexa skill listing for Remootio appears in search results, but the listing itself returned HTTP 500 to us and is therefore not cited. Recorded 'partial' with mechanism unestablished, matching how this catalogue records tailwind-iq3's advertised-but-undocumented SmartThings support. — vendor-page and app-store research; ecosystem-side verification attempted and unavailable, verified 2026-07-29 · remootio.com/products/remootio-3 (read 2026-07-29) lists 'Samsung SmartThings' among supported platforms. THE COUNTERPARTY'S OWN DIRECTORY IS SILENT: partners.smartthings.com/products/remootio returned HTTP 404 on 2026-07-29 (reached via a 301 from www.smartthings.com/products/remootio, followed as a same-intent redirect). That is an absence from a list rather than a statement of non-support, so the cell is 'partial' with the gap named, not 'none' — the same rule this catalogue applied to OpenGarage's unlisted ecosystems. The vendor's SmartThings tutorial article exists but could not be retrieved before the host rate-limited us. — vendor-page research plus ecosystem-side directory check, verified 2026-07-29 · Home Assistant publishes no integration for this device: home-assistant.io/integrations/remootio returned HTTP 404 on 2026-07-29. What exists is a community custom component — github.com/undecomposed/remootio-v3-ha-integration, read the same day — whose documentation states it is installed by dropping a folder into '/config/custom_components/' or via HACS, and that it performs a 'Local WebSocket handshake with session encryption (no Remootio cloud required)', configured with the device's IP address plus the API Secret Key and API Auth Key obtained from the Remootio mobile app. THE PROTOCOL UNDERNEATH IT IS OFFICIALLY PUBLISHED BY THE MANUFACTURER: github.com/remootio/remootio-api-documentation exists under Remootio's own GitHub organisation and carries v1, v2 and v3 WebSocket API specifications, with the compatibility statement 'New versions of the API shall be a superset of the original API, so all programs written based on the older API specification shall continue to work with the newer version.' That distinction — documented protocol versus reverse-engineered one — is recorded because it changes how durable the local path is, and it is the opposite of what this catalogue found for iSmartGate. — platform-side documentation check plus reading the integration and API repositories directly, verified 2026-07-29 · NO SECURITY+ STATEMENT OF ANY VERSION appears on the vendor's product page, either HomeKit page, or either app-store listing, all read 2026-07-29 and all checked specifically for it. Security+ 3.0 is the decisive compatibility question in this category — Chamberlain's 2025-generation openers with white learn buttons lock out third-party controllers, a fact this catalogue has sourced from Chamberlain's and Home Assistant's own publications on other records — and a vendor silence is not a 'works' and not a 'does not work'. It is recorded here as an explicit unknown with the reason, per this category's rule that every record answers the signature question with either a sourced statement or a calibrated unknown. The vendor's knowledge base may address it; it could not be read this session because the host rate-limited us. — targeted absence check across every reachable first-party page, verified 2026-07-29. This is a research profile: compiled from manufacturer documentation, certification registries, and published testing — we state facts, not verdicts, and we have not physically tested this unit. How we work →
Compatibility and lifecycle information reflects the last-verified date above and can change without notice (firmware updates, cloud-service changes, discontinuations). It is provided as-is, for information — verify with the manufacturer before purchasing. Spot an error? Tell us and we'll fix it. Full terms: Terms of Service.