homebridge-gpio-motorized-door
v1.0.3
Published
Exposes a door accessory to HomeBridge that uses a RaspberryPi GPIO pins
Downloads
16
Maintainers
Readme
homebridge-gpio-motorized-door
Sample configuration
{
"bridge": {
"name": "My RPi bridge",
"username": "00:00:00:00:00:00",
"pin": "000-00-000"
},
"accessories": [
{
"accessory": "MotorizedDoor",
"name": "Garage door",
"initialFallbackState": 0,
"closedSensor": {
"pin": 31,
"activeValue": true
},
"openSensor": {
"pin": 32,
"activeValue": true
},
"switch": {
"pin": 33,
"activeValue": false,
"cycle": 600
},
"maxTransitionTime": 14,
"canBeStopped": true
}
]
}
- for
switch
,openSensor
andclosedSensor
pin
value is the pin-number (GPIO number, not physical pins)activeValue
is the value used to set/determine the on-state of the pin
switch
defines the relay triggering the door to open or closecycle
is the time in milliseconds the relay is set toactiveValue
rpioSettings
is being passed to rpio when initializingmaxTransitionTime
is the time in seconds the transistion from open to closed (and vice versa) should take. If more time is spent before a sensor is triggered, the door is assumed to be stopped (either blocked by a foreign object or faulty).openSensor
andclosedSensor
defines sensors triggered when the door reaches fully opened or closed states (magnetic reed-switches is useful for this).
If only one or no sensors are defined, a timeout-trigger will be used instead based onmaxTransitionTime
.canBeStopped
configures whether the door can be stopped mid transition. If it does, it's assumed triggering the switch will stop the door and anothertriggering will make the door reverse direction.initialFallbackState
defines the initial state of the door if no sensors are defined or active