This is the third revision of this project.
- the first revision used a shelly1 and "forwarded" the pulses to an esp8266, which forwarded to the correct remote button
- the second revision ditched the shelly, and was connected directly to the remote. This version also introduced the homekit controller and the mqtt api
- the thrid revision adds a dual relay, so the remote electric circuit is isolated from the esp8266's
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 firware acts accordingly.
The firware 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.
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.
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...