GarHAge allows two "dumb" garage door openers to be controlled (open/close) and report garage door status (open/closed) via MQTT.
GarHAge is almost completely compatible with Home Assistant's "MQTT Cover" platform. It responds to HASS's open and close commands and reports door status to keep HASS's GUI in sync with the door state. GarHAge does not implement HASS's "stop" command (as this functionality varies between garage door openers) or "tilt" functionality. Sample HASS configuration snippets are provided in this repository to get your garage door openers connected to HASS as quickly and painlessly as possible.
GarHAge should be controllable via any home automation software that can configure an MQTT cover, rollershutter, garage door, or send commands over MQTT, including OpenHAB.
GarHAge has both hardware and software components. The required hardware components include an ESP8266-based microcontroller (such as the NodeMCU), a relay module, and reed/magnetic switches. The software component is found in this repo.
Best of all, if you select the proper parts, building and installing a GarHAge requires no soldering!
GarHAge subscribes to a configurable MQTT topic for each of two garage doors (by default, garage/door/1/action and garage/door/2/action).
When the OPEN payload is received on either of these topics, GarHAge momentarily activates a relay connected to the relevant garage door opener to cause the door to open.
When the CLOSE payload is received on either of these topics, GarHAge momentarily activates a relay connected to the relevant garage door opener to cause the door to close. By default, GarHAge is configured to activate the same relay for the OPEN and CLOSE payloads, as most (if not all) garage door openers operate manually by momentarily closing the same circuit to both open and close.
When the STATE payload is received on either of these topics, GarHAge publishes the status (open or closed) of the relevant garage door to the configurable topic garage/door/1/status or garage/door/2/status. These messages are published with the "retain" flag set. (Note: To address a current issue in Home Assistant that may result in MQTT platforms not showing the correct garage door status (open/closed) after a HASS restart, I recommend creating an automation in Home Assistant that publishes the STATE payload for each door on HASS start. An example is provided in the Configuring Home Assistant section of this documentation.)
When the state of a garage door changes (either because GarHAge has triggered the door to open or close, or because the door has been opened or closed via a remote, pushbutton switch, or manually), GarHAge publishes the status (open or closed) of the relevant garage door to garage/door/1/status or garage/door/2/status. These messages are published with the "retain" flag set.
GarHAge also publishes a "birth" message on connection to your MQTT broker, and a "last-will-and-testament" message on disconnection from the broker, so that your home automation software can respond appropriately to GarHAge being online or offline.
Building GarHAge to control two garage door openers requires:
| No. | Qty | Part | Link | Approx Price |
|---|---|---|---|---|
| 1. | 1 | ESP8266-based microcontroller (e.g. NodeMCU) | Link | $ 7.00 |
| 2. | 1 | Dual-relay module | Link | $ 4.00 |
| 3. | 2 | Reed/Magnetic door switches | Link | $ 12.00 |
| 4. | 1 | 5v MicroUSB power supply | Link | $ 6.00 |
| 5. | 1 | Mini solderless breadboard (170 tie-point) | Link | $ 4.00 |
| 6. | Bell/low voltage two-conductor wire | |||
| 7. | Male-to-female breadboard jumper wires | |||
| 8. | Project box or case |
Approximate total cost for major components: $ 33.00, even less if you don't mind a long lead time and source your components from AliExpress/BangGood.
Note: If you are building GarHAge to control only one garage door opener, you will only require a single-relay module, and a single reed switch.
I recommend the NodeMCU as GarHAge was developed and is tested on it. Its advantages are:
Accordingly, this guide is written with the NodeMCU in mind.
But, Garhage should also work with the Adafruit HUZZAH, Wemos D1, or similar, though you may need to adjust the GPIO ports used by the sketch to match the ESP8266 ports that your microcontroller makes available.
A dual 5v relay module (as opposed to individual 5v relays) makes setup easy: just plug jumper wires from the module's VCC, CH1, CH2, and GND pins to the NodeMCU. These relay modules generally also include LEDs to ease troubleshooting.
Most importantly, because the relay module is powered by 5v, its inputs can be triggered by the NodeMCU's GPIOs.
GarHAge will work with relay modules that are active-high or active-low; if using an active-low relay, be sure to set the relevant configuration parameter in config.h, described below, and test thoroughly to be sure that your garage door opener(s) are not inadvertently triggered after a momentary power-loss.
GarHAge will work with both normally-open and normally-closed reed switches; if using a normally-closed switch, be sure to set the relevant configuration parameter in config.h, described below, to match the type of switch in use. Many switches with screw terminals are available, making placement and wiring easy.
Power your NodeMCU via the same type of power supply used to charge Android phones or power a RaspberryPi. Powering the NodeMCU via MicroUSB is important since the relay module can then be powered via the NodeMCU VIN (or VU on the LoLin variant) port.
The NodeMCU mounts to this breadboard nicely, leaving one female port next to each NodeMCU port and making it easy to use male-to-female jumper wires to make connections from the NodeMCU to the relay module. The bell wire attached to the reed switches will also plug into the breadboard ports, making for a clean and solderless installation. Finally, these mini breadboards often also have an adhesive backing, making mounting in your project box easy.
To install GarHAge, you will also require:
Done!
You will modify the configuration parameters and upload the sketch to the NodeMCU with the Arduino IDE.
Tools - Boards in the Arduino IDE (e.g. "NodeMCU 1.0 (ESP-12E Module)").GarHAge's configuration parameters are found in config.h. After loading GarHAge.ino, select the config.h tab in the Arduino IDE. This section describes the configuration parameters and their permitted values.
IMPORTANT: No modification of the sketch code in GarHAge.ino is necessary (or advised, unless you are confident you know what you are doing and are prepared for things to break unexpectedly).
WIFI_SSID "your-wifi-ssid"
The wifi ssid GarHAge will connect to. Must be placed within quotation marks.
WIFI_PASSWORD "your-wifi-password"
The wifi ssid's password. Must be placed within quotation marks.
STATIC_IP false
Set to true to use the IP / GATEWAY / SUBNET parameters that follow. Set to false to use DHCP. (Default: false)
IP 192,168,1,100
The static IP you want to assign to GarHAge. (Default: 192.168.1.100)
GATEWAY 192,168,1,1
The gateway you want GarHAge to use. (Default: 192.168.1.1)
SUBNET 255,255,255,0
The subnet mask you want GarHAge to use. (Default: 255.255.255.0)
Note: There are commas (,) not periods (.) in the IP / GATEWAY / SUBNET parameters above!
MQTT_BROKER "w.x.y.z"
The IP address of your MQTT broker. Must be placed within quotation marks.
MQTT_CLIENTID "GarHAge"
The Client ID you want GarHAge to use. Should be unique among all the devices connected to your broker. Must be placed within quotation marks. (Default: GarHAge)
MQTT_USERNAME "your-mqtt-username"
The username required to authenticate to your MQTT broker. Must be placed within quotation marks. Use "" (i.e. a pair of quotation marks) if your broker does not require authentication.
MQTT_PASSWORD "your-mqtt-password"
The password required to authenticate to your MQTT broker. Must be placed within quotation marks. Use "" (i.e. a pair of quotation marks) if your broker does not require authentication.
ACTIVE_HIGH_RELAY true
Set to false if using an active-low relay module. Set to true if using an active-high relay module. (Default: true)
DOOR1_ALIAS "Door 1"
The alias to be used for Door 1 in serial messages. Must be placed within quotation marks. (Default: Door 1)
MQTT_DOOR1_ACTION_TOPIC "garage/door/1/action"
The topic GarHAge will subscribe to for action commands for Door 1. Must be placed within quotation marks. (Default: garage/door/1/action)
MQTT_DOOR1_STATUS_TOPIC "garage/door/1/status"
The topic GarHAge will publish Door 1's status to. Must be placed within quotation marks. (Default: garage/door/1/status)
DOOR1_OPEN_PIN D2
The GPIO pin connected to the relay that is connected to Door 1's garage door opener's open terminals. (Default: NodeMCU D2 / Arduino 4)
DOOR1_CLOSE_PIN D2
The GPIO pin connected to the relay that is connected to Door 1's garage door opener's close terminals. If your garage door opener is like most (all?), the same terminals control open and close via a momentary connection of the terminals. In this case, set DOOR1_CLOSE_PIN and DOOR1_OPENPIN to the same pin. (Default: NodeMCU D2 / Arduino 4)_
DOOR1_STATUS_PIN D5
The GPIO pin connected to the reed/magnetic switch attached to Door 1. (Default: NodeMCU D5 / Arduino 14)
DOOR1_STATUS_SWITCH_LOGIC "NO"
The type of reed/magnetic switch used for Door 1. Must be placed within quotation marks. Set to "NO for normally-open. Set to "NC" for normally-closed. (Default: NO)
DOOR2_ENABLED false
Set to true to enable GarHAge to control/monitor Door 2. Set to false to disable Door 2. (Default: false)
DOOR2_ALIAS "Door 2"
The alias to be used for Door 2 in serial messages. Must be placed within quotation marks. (Default: Door 2)
MQTT_DOOR2_ACTION_TOPIC "garage/door/2/action"
The topic GarHAge will subscribe to for action commands for Door 2. Must be placed within quotation marks. (Default: garage/door/2/action)
MQTT_DOOR2_STATUS_TOPIC "garage/door/2/status"
The topic GarHAge will publish Door 2's status to. Must be placed within quotation marks. (Default: garage/door/2/status)
DOOR2_OPEN_PIN D1
The GPIO pin connected to the relay that is connected to Door 2's garage door opener's open terminals. (Default: NodeMCU D1 / Arduino 5)
DOOR2_CLOSE_PIN D1
The GPIO pin connected to the relay that is connected to Door 2's garage door opener's close terminals. If your garage door opener is like most (all?), the same terminals control open and close via a momentary connection of the terminals. In this case, set DOOR2_CLOSE_PIN and DOOR2_OPENPIN to the same pin. (Default: NodeMCU D1 / Arduino 5)_
DOOR2_STATUS_PIN D6
The GPIO pin connected to the reed/magnetic switch attached to Door 2. (Default: NodeMCU D6 / Arduino 12)
DOOR2_STATUS_SWITCH_LOGIC "NO"
The type of reed/magnetic switch used for Door 2. Must be placed within quotation marks. Set to "NO for normally-open. Set to "NC" for normally-closed. (Default: NO)
If using the NodeMCU, connect it to your computer via MicroUSB; press and hold the reset button on the NodeMCU, press and hold the Flash button on the NodeMCU, then release the Reset button. Select Sketch - Upload in the Arduino IDE.
If using a different ESP8266 microcontroller, follow that device's instructions for putting it into flashing/programming mode.
Open the Serial Monitor via Tools - Serial Monitor. Reset your microcontroller. If all is working correctly, you should see something similar to the following messages:
Starting GarHAge...
Relay mode: Active-High
Connecting to your-wifi-ssid.. WiFi connected - IP address: 192.168.1.100
Attempting MQTT connection...Connected!
Publishing birth message "online" to GarHAge/availability...
Subscribing to garage/door/1/action...
Subscribing to garage/door/2/action...
Door 1 closed! Publishing to garage/door/1/status...
Door 2 closed! Publishing to garage/door/2/status...If you receive these (or similar) messages, all appears to be working correctly. Disconnect GarHAge from your computer and prepare to install in your garage.
Done!
GarHAGE supports both Home Assistant's "MQTT Cover" and "MQTT Binary Sensor" platforms.
Testing has shown that the MQTT platform in Home Assistant sometimes does not update the status of an entity (such as the cover or binary sensor) in accordance with a retained message on the status topic on HASS start or restart. This can leave the cover entity in an "unknown" state, and the binary sensor may show "closed" even if the door is open.
The entities will, however, update to show the correct state when the door next changes state and GarHAge publishes the state to the door's status topic.
A temporary workaround (until this issue is resolved in HASS, or possibly in the underlying Paho MQTT library used in HASS) is to use an automation to send the "STATE" payload to the doors' action topics on Home Assistant start. This will ensure that the cover and binary sensor show the correct door state on HASS start and restart.
Place the following in your automations.yaml (adjusting if you have only one door controlled by GarHAge); replace id: xyz with the next sequential automation number according to your own automations.yaml.
- id: xyz
alias: Update garage door state on startup
trigger:
- platform: homeassistant
event: start
action:
- service: mqtt.publish
data:
topic: "garage/door/1/action"
payload: "STATE"
- service: mqtt.publish
data:
topic: "garage/door/2/action"
payload: "STATE"cover:
- platform: mqtt
name: "Garage Door 1"
state_topic: "garage/door/1/status"
command_topic: "garage/door/1/action"
availability_topic: "GarHAge/availability"
- platform: mqtt
name: "Garage Door 2"
state_topic: "garage/door/2/status"
command_topic: "garage/door/2/action"
availability_topic: "GarHAge/availability"Note: GarHAge's default parameters match Home Assistant's defaults and, as such, the above minimal configuration will work.
_Note: the "availability_topic" configuration parameter will be available in Home Assistant as of version 0.55; it allows Home Assistant to display the cover as "unavailable" if GarHAge goes offline unexpectedly. When GarHAge reconnects to your broker, the cover controls will again be available in Home Assistant. GarHAge forms its availability topic by suffixing "/availability" to the MQTTCLIENTID parameter in config.h, and publishes "online" to that topic when connecting or reconnecting to the broker and "offline" when disconnecting from the broker.
Note: If you want to guard against your GarHAge configuration breaking if a Home Assistant update changes one of its defaults, the complete configuration below can be added.
cover:
- platform: mqtt
name: "Garage Door 1"
state_topic: "garage/door/1/status"
command_topic: "garage/door/1/action"
availability_topic: "GarHAge/availability"
qos: 0
optimistic: false
retain: false
payload_open: "OPEN"
payload_close: "CLOSE"
payload_stop: "STATE"
state_open: "open"
state_closed: "closed"
payload_available: "online"
payload_not_available: "offline"
- platform: mqtt
name: "Garage Door 2"
state_topic: "garage/door/2/status"
command_topic: "garage/door/2/action"
availability_topic: "GarHAge/availability"
qos: 0
optimistic: false
retain: false
payload_open: "OPEN"
payload_close: "CLOSE"
payload_stop: "STATE"
state_open: "open"
state_closed: "closed"
payload_available: "online"
payload_not_available: "offline"Note: Setting payload_stop to STATE allows you to trigger a status update from GarHAge for a Door by pressing the stop button for that door in the HASS GUI. The stop button in the HASS GUI is otherwise unused.
binary_sensor:
- platform: mqtt
name: "Garage Door 1"
state_topic: "garage/door/1/status"
payload_on: "open"
payload_off: "closed"
availability_topic: "GarHAge/availability"
device_class: opening
qos: 0
- platform: mqtt
name: "Garage Door 2"
state_topic: "garage/door/2/status"
payload_on: "open"
payload_off: "closed"
availability_topic: "GarHAge/availability"
device_class: opening
qos: 0 _Note: the "availability_topic" configuration parameter will be available in Home Assistant as of version 0.54; it allows Home Assistant to display the binary sensor as "unavailable" if GarHAge goes offline unexpectedly. When GarHAge reconnects to your broker, the door state will again be displayed in Home Assistant. GarHAge forms its availability topic by suffixing "/availability" to the MQTTCLIENTID parameter in config.h, and publishes "online" to that topic when connecting or reconnecting to the broker and "offline" when disconnecting from the broker.
In the examples that follow, replace id: xyz with the next sequential automation number according to your own automations.yaml.
Place the following in your automations.yaml:
- id: xyz
alias: Close garage door if open for longer than 30 minutes
trigger:
- platform: state
entity_id: cover.garage_door_1
to: "open"
for:
minutes: 30
action:
- service: cover.close_cover
entity_id: cover.garage_door_1Of course, you can replace 30 with any length of time in minutes you wish. Be sure to replace cover.garage_door_1 if the name of your garage door in Home Assistant is different.
To use this automation, you must have the Home Assistant iOS app installed on your iPhone and must have the ios: and notify: platforms in your configuration.yaml.
Place the following in your automations.yaml:
- id: xyz
alias: Notify iOS device when garage door opens or closes
trigger:
- platform: state
entity_id: cover.garage_door_1
action:
- service: notify.ios_your_device_name_here
data_template:
message: >
Garage Door 1 just changed from {{ trigger.from_state.state }} to {{ trigger.to_state.state }}!Replace notify.ios_your_device_name_here with the name assigned to your device by Home Assistant (for example, if Home Assistant knows your device as "steves_iphone", your notify statement would be: notify.ios_steves_iphone.
Be sure to replace cover.garage_door_1 if the name of your garage door in Home Assistant is different.
If you wish to notify only when the garage door either opens or closes, add a to statement to the trigger following entity_id and specify either "open" or "closed", e.g.:
- id: xyz
alias: Notify iOS device when garage door opens
trigger:
- platform: state
entity_id: cover.garage_door_1
to: "open"
action:
- service: notify.ios_your_device_name_here
data_template:
message: "Garage Door 1 just opened!"An actionable notification will raise a notification on your iPhone with a "Close Garage" button allowing you to close the garage door directly from the notification (i.e. without needing to open the Home Assistant app).
To use this automation, you must have the Home Assistant iOS app installed on your iPhone. You must also have the notify: platform in your configuration.yaml.
To the ios: platform in configuration.yaml, add:
ios:
push:
categories:
- name: Garage
identifier: "GARAGE"
actions:
- identifier: "CLOSE_GARAGE"
title: "Close Garage"
activationMode: "background"
authenticationRequired: no
destructive: yes
behavior: "default"If you want to be required to authenticate (i.e. enter your passcode or unlock with TouchID) before being able to access the "Close Garage" button, change authenticationRequired: no to authenticationRequired: yes.
You will also need to add the following two automations to your automations.yaml:
- id: xyz
alias: Notify iOS device when garage door has been open for 30 minutes
trigger:
- platform: state
entity_id: cover.garage_door_1
to: "open"
for:
minutes: 30
action:
- service: notify.ios_your_device_name_here
data:
message: "Garage Door 1 has been open for 30 minutes!"
data:
push:
category: "GARAGE"
- id: xyz
alias: Close garage when triggered from iOS notification
trigger:
- platform: event
event_type: ios.notification_action_fired
event_data:
actionName: CLOSE_GARAGE
action:
- service: cover.close_cover
entity_id: cover.garage_door_1In the first automation, replace notify.ios_your_device_name_here with the name assigned to your device by Home Assistant (for example, if Home Assistant knows your device as "steves_iphone", your notify statement would be: notify.ios_steves_iphone.
Of course, you can replace 30 with any length of time in minutes you wish.
In both automations, be sure to replace cover.garage_door_1 if the name of your garage door in Home Assistant is different.
Restart Home Assistant for the configuration and automation changes to take effect.
Finally:
Now, when your garage door has been open for 30 minutes, you will receive a Home Assistant notification saying "Garage Door 1 has been open for 30 minutes!", and the notification will contain a button labelled "Close Garage" which will close your garage when tapped.
Forthcoming. Please submit a pull request with a working OpenHAB configuration if you can assist!
Fork this repository and submit a pull request.
Please open an issue in this repository and describe your issue in as much detail as possible with the steps necessary to replicate the bug. It will also be helpful to include the content of your config.h in code tags and indicate whether (and how) you modified GarHAge.ino.
Please also request new features via issues!