https://github.com/caarlos0/esp8266-garage-door

Homekit controller and firmware for an ESP8266-based automated garage door
https://github.com/caarlos0/esp8266-garage-door

arduino esp8266 home-automation

Last synced: about 2 months ago
JSON representation

Homekit controller and firmware for an ESP8266-based automated garage door

• Host: GitHub
• URL: https://github.com/caarlos0/esp8266-garage-door
• Owner: caarlos0
• License: mit
• Created: 2023-11-02T20:22:14.000Z (about 1 year ago)
• Default Branch: main
• Last Pushed: 2024-10-15T13:16:30.000Z (2 months ago)
• Last Synced: 2024-10-24T06:05:26.598Z (2 months ago)
• Topics: arduino, esp8266, home-automation
• Language: Go
• Homepage:
• Size: 97.7 KB
• Stars: 9
• Watchers: 2
• Forks: 2
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE.md

Awesome Lists containing this project

README

        
# esp8266-garage-door

This is the third revision of this project.

1. the first revision used a shelly1 and "forwarded" the pulses to an esp8266, which forwarded to the correct remote button

2. the second revision ditched the shelly, and was connected directly to the remote. This version also introduced the Homekit controller and the mqtt api

3. the thrid revision adds a dual relay, so the remote electric circuit is isolated from the esp8266's

---

## Wiring

![image](https://github.com/caarlos0/esp8266-garage-door/assets/245435/ad5000ea-42c2-4b7c-be9f-4c4d9f2810d8)

Basically, the firmware publish to the `espgate/sensor` mqtt topic, which `homekit-garage` subscribes.

`homekit-garage` publishes `open`, `close` and `ping` events to the `espgate/act` mqtt topic, and the firmware acts accordingly.

The firmware is pretty "dumb", on purpose, as its the hardest part to maintain/update.

The Homekit controller runs in a raspberry pi, and is very lightweight too.

## Configuration

In the firmware, you might want to change the `PULSE` (default 500ms) time.

You'll also need to create an `arduino_secrets.h` with the Wifi info and MQTT server IP.

In the Homekit controller, you'll need to set the `operationTimeout` (default 30s) and the MQTT server IP.

## Future

Maybe ditch the separated Go Homekit controller and run it directly in the ESP?

Not sure if worth it, as its painful to update/debug...