Garage Door and Bolt
homebridge-gdoorandbolt-coordinator · v0.4.19
Coordinates one garage door and a separate bolt as a combined garage door and lock accessory.
What it says it supports
Devices it names
- garage door
- bolt
Shows up in Apple Home as from its README
What people report
Garage and bolt controller using Tailwind openers, deCONZ relays and Aqara openers; recent merged PRs add Tailwind sensors and separate bolt relays.
- Works4
The plugin’s own supported-device list
| Device | Status | What they said | Source |
|---|---|---|---|
| Aqara opener output | Works | Treated as separate motor path; pulse lengths configurableSaved copy… state means locked and use relay feedback for the owner's bolt. Two relays operating a mechanical bolt do not supply physical bolt-position sensing. The Aqara opener output is a separate named motor path; check its pulse lengths and released state independently. Homebridge mappings use the source bridge's HAP accessory port and privately stored PIN, with unpaired accessory control/insecure mode enabled. Discovery pins the bridge identity, accessory fingerprint and service. Supported services include GarageDoorOpener, LockMechanism, Switch/Lightbulb and supported button inputs. Choose feedback … Excerpt saved from GitHub on 2026-10-22. | Docs: device-checks.md |
| deCONZ relays for bolt/lock | Works | Separate lock/unlock relays with momentary pulses supportedSaved copyThe bolt can require independent lock and unlock outputs, including short ON/OFF pulses. The existing bolt adapter only supports one maintained output. Add a deCONZ Bolt relay setup choice under Devices → Bolt / Lock. Single relay keeps existing behavior. Separate mode requires selecting both outputs and one coordinated HomeKit Lock tile, automatically checked and required. Optional momentary operation defaults to 0.2 seconds; maintained mode releases the opposite output before activation. Both outputs are pinned and exclusively reserved. Pulse results are labeled command estimates, forgotten … Excerpt saved from GitHub on 2026-10-22. | PR #10 · 2026-10 |
| Tailwind garage door controller | Works | Local control key; closed sensor, optional second sensor for fully-openSaved copyDevice checks and feedback The operational test build keeps checks separate from enabling a garage. An uncommissioned profile makes no startup hardware requests. Discovery and explicit probes read identities/current values without actuator writes. A commissioned profile also observes devices during operation. Use owner-test.md and the validated revisions in status.md for installation. Homebridge settings provides device discovery, private connection-key entry and Check connections. From 0.4.2, the Homebridge settings check also verifies each motor relay is released and each enabled physical … Excerpt saved from GitHub on 2026-10-22. | Docs: device-checks.md |
| Tailwind optional open-position sensor | Works | Spare Tailwind input gives confirmed fully-open positionSaved copyA single Tailwind contact reports closed or not-closed, so the controller previously estimated fully-open arrival. A spare Tailwind input can now supply a second physical endpoint without connecting another opener. Add a checkbox and distinct input picker under the garage's Tailwind device. Link it to Behavior → A sensor confirms fully open; reserve both inputs against competing garage mappings. Read both sensors in one response. Extra-input `close` means fully open; its Door control may remain disabled. Motor commands and control restrictions continue to use only the primary input. Replace … Excerpt saved from GitHub on 2026-10-22. | PR #6 · 2026-10 |
Gathered from the plugin’s GitHub issues, pull requests, discussions, wiki and docs, and from r/homebridge. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Local
Local inputs and relays
Compatibility
| Verified by Homebridge | No |
|---|---|
| Homebridge versions | ^2.0.0 |
| Homebridge 2.0 | Yes |
| Node.js | ^22.0.0 || ^24.0.0 |
| Settings in Homebridge UI | Yes |
| Matter | No |
| Platform name | GDoorAndBoltCoordinator |
| License | UNLICENSED |
Community signals
| Downloads a week | 2,505 |
|---|---|
| Downloads a month | 2,505 |
| GitHub stars | 0 |
| Open issues | 0 |
| Closed issues | 0 |
| Last code push | 2026-10-19 |
| Latest version | 0.4.19 (2026-10-07) |
| First published | 2026-10-06 |
| Releases | 19 |
In ReReHome
Whatever this plugin publishes reaches Apple Home as a normal HomeKit accessory behind your Homebridge bridge, so ReReHome shows and controls it like any other.
Bridges get their own settings page listing the accessories behind them.
Caveats from the README
- Still under testing per README