Lutron Smart Bridges

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 a compatible Lutron Smart Bridge already set up on my local network, identified by fresh discovery (bridge model and current advertised HAP or documented LEAP service matched, exact discovered endpoints used — Lutron product families do not all expose the same protocols), and authorized pairing material: for HAP, the eight-digit setup code for a pairable bridge or previously authorized controller pairing keys; for LEAP, its separate physical pairing flow and its own client certificate/private key (HAP credentials do not substitute for them) — with any existing Apple Home setup preserved, never resetting or removing an existing pairing, and pairing material kept in approved credential storage (private file permissions if file-backed). Installing the file configures none of that. Install "Lutron Smart Bridges" for me. It reads or controls lights and shades on compatible Lutron Smart Bridges through Muse Home Link, using authorized HAP pairing or independently paired LEAP, and preserves any existing Apple Home setup. It is used when fresh discovery identifies a compatible bridge: bridge model and current advertised HAP or documented LEAP service are matched, not the brand alone, and exact discovered endpoints are used, because Lutron product families do not all expose the same protocols. The HAP path is preferred when authorized pairing is available, using a maintained HAP client over the shared network access: when the advertisement has ff=1 it selects PairSetupWithAuth (plain PairSetup can fail at M2 with kTLVError_Authentication) and keeps that exchange on one persistent connection; successful pairing material is stored in approved credential storage (private file permissions if file-backed), an encrypted session is opened, and actual accessories, services and characteristics are enumerated. It reads the target light/shade state and supported ranges, resolves ambiguous generic accessory names before writing (any physical identification action must be explicitly requested), writes only the requested characteristic, then reads back the individual result; for partial batch failures each target is inspected before retrying uncertain operations. For a compatible bridge using LEAP instead, it follows pylutron-caseta's pairing routine with the user present, stores its own credentials, enumerates devices with the authenticated client and uses its documented level/cover operations. It verifies the intended accessory's resulting on/brightness/position state, not merely a successful session or write acknowledgement; for shade movement it observes progress and final state and preserves obstruction and motor behavior; and if pairing or a command fails it reports that exact limitation without implying the bridge has no local API. HAP requires the eight-digit setup code for a pairable bridge or previously authorized controller pairing keys; a bridge already in Apple Home does not automatically give Muse its credentials, an existing pairing is never reset or removed, and if access is unavailable only a supported independently authorized alternative is used or setup is requested; LEAP uses a separate physical pairing flow and client certificate/private key, and HAP credentials do not substitute for them. Limits: no assumed LIP/telnet access, no cloud fallback, no broad product compatibility and no replacement of someone's existing Home; no schedules are added, bridge configuration is not changed, and room mappings are not discovered by unrequested toggling. Repository: https://github.com/facebookincubator/muse-gadget-sdk (the skill is the whole skills/gadget-lutron-smart-bridges/ 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-lutron-smart-bridges/ 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 26074375567092222d1d6d3fe842dfdc40aa9d32498d18d333a195c66b45e4aa 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 (3,069 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. It has no dependency on any other gadget skill in this lot. - 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 local Lutron Smart Bridge: over HAP, an encrypted session with authorized pairing material (eight-digit setup code for pairing, or previously authorized controller pairing keys) enumerates accessories and reads/writes requested characteristics; over LEAP, an authenticated pylutron-caseta client with its own stored client certificate/private key enumerates devices and uses its documented level/cover operations. Pairing material stays in approved credential storage, and no existing Apple Home pairing is reset or removed. - The skill does not assume LIP/telnet access, use a cloud fallback, claim broad product compatibility or replace someone's existing Home, and it does not add schedules, change bridge configuration, discover room mappings by unrequested toggling, or reset or remove an existing pairing. - 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-lutron-smart-bridges folder into the agent's skills directory, in a folder named exactly "gadget-lutron-smart-bridges", 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-lutron-smart-bridges), 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 a compatible Lutron Smart Bridge already set up on my local network; have authorized HAP pairing material (the eight-digit setup code or previously authorized controller pairing keys) or LEAP pairing with its own client certificate/private key, kept in approved credential storage; and keep any existing Apple Home setup intact — never reset or remove an existing pairing; 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.