ratgdo v32 Garage Door

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — Muse Home Link and a compatible physical device are required to USE this skill, not to install it: installing the skill file itself needs no account, no key and no device, and this install does NOT set up Home Link, pair anything or ask for any credential. But the skill is instructions only. To use it I must read and follow ~/docs/devices/home_link.md in my Muse environment, have the compatible physical device named below already set up on my local network, and have an already commissioned ratgdo v32 controller attached to a working opener on my local network, with credentials for its enabled HTTP or native TCP API, and give an explicit requested door/light/lock action with the intended door confirmed and movement safe, preserving all opener interlocks and obstruction protections. This device-specific skill is preferred over the generic gadget-esphome-devices skill for ratgdo controllers (see step 2). Installing the file configures none of that. Install "ratgdo v32 Garage Door" for me. It reads and operates installed ratgdo v32 garage-door, light and lock entities through Muse Home Link. It is used when current discovery and entity metadata identify an already-installed ratgdo v32 controller, not merely an arbitrary ESP32: ratgdo model, installed firmware version and actual garage-door cover, light, lock and obstruction entities are confirmed, and entity IDs are recorded from the live API — web-server paths and identifiers differ by ESPHome version and another firmware's URLs are never transplanted. The controller is already commissioned and attached to a working opener, with credentials for its enabled HTTP or native TCP API, and an explicit requested door/light/lock action: the intended door is confirmed, movement is safe, and all opener interlocks and obstruction protections are preserved. It reads the installed firmware's entity descriptions and current door, movement, lock and obstruction states using its enabled API — SSE may supply live state over an outbound HTTP connection, and the native API can list entities and subscribe over TCP. For HTTP it constructs the entity read/action URL from that firmware's documented web API; for the native API it uses a compatible aioesphomeapi client with the device's configured encryption key or credentials. It uses only the exposed cover open/close/stop, light or lock operation corresponding to my request, never inferring position-setting or lock semantics from the entity name alone, and it monitors the door and obstruction states until the requested state is reached or movement stops unexpectedly; if the command result is uncertain, it reads state before considering any retry. Command acceptance, opening/closing and final open/closed states are distinguished; obstruction, unknown position, offline sensors or a lock preventing movement are reported as unresolved and never overridden, and a light or lock response is checked against its entity state, not taken as proof of door movement. This device skill is preferred over the generic ESPHome skill (gadget-esphome-devices). Limits: no retrofit installation, flashing, OTA updates, opener rewiring or safety bypasses, and only capabilities present in the installed firmware are supported. Repository: https://github.com/facebookincubator/muse-gadget-sdk (the skill is the whole skills/gadget-ratgdo-v32-garage-door/ folder at the pinned commit: SKILL.md only, 1 file) Pinned version: install the code at commit e6fe5174092702ffddae6f90759a38d55a4ebae1 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/facebookincubator/muse-gadget-sdk into a temporary folder, check out commit e6fe5174092702ffddae6f90759a38d55a4ebae1, and copy the skills/gadget-ratgdo-v32-garage-door/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 d6b239039ab4488e46a5263b97701a948eda562998d175faf62afec0ea5f0c74 If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 1 file only: SKILL.md (2 824 bytes). There is no script, no code and no configuration in it; the procedure runs at use time through Muse Home Link against my own local device. - Cross-reference: this device-specific skill says to prefer it over the generic ESPHome skill (gadget-esphome-devices, ../gadget-esphome-devices/SKILL.md, lot 3 listing, same repo, same pin), the generic skill in return points ratgdo garage controllers to this one, and this skill lists the generic skill in its Sources. The tested installation of this listing is still the copy of this skill's own folder only. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit. No device is contacted, no pairing is started and no key is asked for during installation. - At use time, exchanges go only to my installed local ratgdo v32 controller over its enabled HTTP or native API: entity/state reads and only the exposed cover open/close/stop, light or lock operation I requested, with the controller's existing API credentials or configured encryption key. All opener interlocks and obstruction protections are preserved and never bypassed. - The skill does not do retrofit installation, flashing, OTA updates, opener rewiring or safety bypasses, and it supports only capabilities present in the installed firmware. - Do not pair any device, do not ask for or set any credential, do not run any control, print, scan or playback action, and do not use the skill in any way during this install: Home Link setup, pairing and use are my decisions, later, when I actually ask for them. 3. When I say "yes, install", install it as a skill: copy the whole gadget-ratgdo-v32-garage-door folder into the agent's skills directory, in a folder named exactly "gadget-ratgdo-v32-garage-door", keeping its 1 file (SKILL.md at its root). The exact folder name matters: relative links between sibling gadget skills depend on these exact names. 4. Verify with no network calls: frontmatter valid (name: gadget-ratgdo-v32-garage-door), the 1 file in place with matching fingerprint. Do not run anything and do not connect to any device to verify. 5. Report what was installed, where, and what I still need to do myself (for example: read ~/docs/devices/home_link.md in my Muse environment and follow its Home Link rules; have an already commissioned ratgdo v32 controller attached to a working opener, with credentials for its enabled HTTP or native API; door movement always requires my explicit action, the intended door confirmed and movement safe, with interlocks and obstruction protections preserved; this skill is preferred over the generic gadget-esphome-devices skill for ratgdo controllers; using the skill is a separate step that only starts when I ask for it, and the use-time exchanges disclosed above happen only then). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.