ratgdo32

This is the controller Selora fits when a client wants their garage in Home Assistant, and the reason we do not specify myQ. Three wires land on the opener’s own control and obstruction terminals, and the wall panel and the safety sensors pass back through the board’s own connectors, so on a Security+ 2.0 opener (yellow learn button, excluding the 8500 and RJ020) it talks the opener’s serial protocol with nothing soldered to the logic board and nothing taken away from the wall panel. ESPHome then exposes a cover, a light for the opener bulb, a lock for the remotes, and binary sensors for obstruction and motor, plus motion where the opener has a motion-sensing wall control panel. Security+ 1.0 (purple, orange, or red button) is supported but is still flagged experimental upstream and does not pair with every wall panel. An opener or gate that exposes dry contact terminals runs that way instead, which needs the ratgdo encoder or the opener’s own limit switches before Home Assistant can tell open from closed; an opener with no dry contact terminals needs an interface of its own and is not a ratgdo job. Firmware is not preloaded: flash the ESPHome build from the browser over USB-C, or adopt the board into the ESPHome dashboard. The door then needs one full open and close cycle to learn its travel time, after which percentage position is computed from elapsed travel rather than measured, until an encoder is fitted. In the box are the board, a 3D printed holster, a USB-C cable and power supply, and the opener wire harness.