VELUX KLF200

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 existing commissioned VELUX KLF200 gateway on my local network and its existing Wi-Fi/API password, which is distinct from its web-login password, a compatible binary-protocol client such as pyvlx routed through HomeLink's TCP transport preserving the device's TLS requirements, and give explicit permission for window/shade movement with confirmation that the target area is safe. Installing the file configures none of that. Install "VELUX KLF200" for me. It reads positions and controls commissioned windows, blinds, shutters or existing scenes through a VELUX KLF200 using Muse Home Link, over the local binary TCP API with its API credential; it is not KLF150 or new motor pairing. It is used when the device is a VELUX KLF200 gateway with commissioned compatible windows, blinds or shutters: KLF200 model and its configured local API service are confirmed — a VELUX KLF150 is not covered by this API — and node and scene enumeration identifies the downstream actuators, which do not appear as independent LAN hosts. The KLF200 is existing and commissioned, with its Wi-Fi/API password, which is distinct from its web-login password, and a compatible binary-protocol client such as pyvlx is routed through HomeLink's TCP transport while preserving the device's TLS requirements; movement requires my explicit permission and confirmation that the target area is safe. It establishes the documented encrypted local API session and authenticates with the gateway's API credential, using the confirmed listener, commonly TCP 51200, not an assumed web endpoint, reads gateway information, enumerates nodes/scenes and obtains the target's current position, movement and error state. It uses the exact node type's position semantics and supported functions, sends the requested position or stop command, or activates a specifically requested existing scene — checking scene membership before execution so I know which actuators will move — and tracks the API command/session identifiers and completion/status notifications over the outbound connection, querying node state again after movement completes. Command acceptance is separated from completed motion and actual reported position, and blocked movement, rain protection, unreachable actuators or unknown position are reported without overriding protective behavior. Limits: no KLF150 support, native HAP assumption, new motor pairing or gateway reconfiguration; no universal device capacity or single-session restriction is assumed — the installed gateway's actual response is handled; and window safety, locks and rain protections are preserved. Repository: https://github.com/facebookincubator/muse-gadget-sdk (the skill is the whole skills/gadget-velux-klf200/ 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-velux-klf200/ 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 c505eee7b5d4561f9671eb9aef288410cb8eb717af6e199dba89c34dda403a9f 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 476 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 VELUX KLF200 gateway over its local binary TCP API: an encrypted authenticated session with the gateway's existing API password (distinct from its web-login password) through pyvlx over HomeLink's TCP transport, node/scene reads and the position, stop or existing-scene command I requested. Window safety, locks and rain protections are preserved. - The skill does not support KLF150, assume native HAP, pair new motors or reconfigure the gateway, and it never overrides window safety, locks or rain protections. - 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-velux-klf200 folder into the agent's skills directory, in a folder named exactly "gadget-velux-klf200", 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-velux-klf200), 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 existing commissioned VELUX KLF200 and keep its API password (distinct from its web-login password) available; window or shade movement always requires my explicit permission and a safe target area, with rain protections and locks preserved; 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.