Dyson Pure Hot+Cool HP04

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 confirmed Dyson Pure Hot+Cool HP04 already set up on my local network (HP04 identity and the product type required by the compatible libdyson device class confirmed, using the device's current MQTT endpoint — an open MQTT port or Dyson MAC prefix is not proof that authentication or this model's commands work), existing device serial, product type and local MQTT password/credential in approved secret storage, a model-compatible libdyson client using HomeLink's TCP connection initialized with the supplied local values rather than invoking account/cloud discovery, and my permission for changes, especially heating mode or temperature. Installing the file configures none of that. Install "Dyson Pure Hot+Cool HP04" for me. It reads Dyson Pure Hot+Cool HP04 status and operates supported fan or heating controls through Muse Home Link, using only a compatible local MQTT interface and existing device credentials. It is used when the confirmed device is a Dyson Pure Hot+Cool HP04 and compatible local MQTT credentials are already available: HP04 identity and the product type required by the compatible libdyson device class are confirmed, and the device's current MQTT endpoint is used — an open MQTT port or Dyson MAC prefix is not proof that authentication or this model's commands work. A model-compatible libdyson client using HomeLink's TCP connection is initialized with the supplied local values rather than invoking account/cloud discovery; it connects, authenticates and subscribes to the model's status topics before requesting its current state, and reads available fan, airflow, oscillation, heating and environmental state through the client's model-specific properties, keeping units and missing/stale sensor values explicit. For the requested change it calls the matching documented HP04 operation, such as fan power/speed, supported oscillation or heating target, respecting device ranges and modes and never sending guessed generic MQTT payloads, then waits for and inspects the subsequent state update, preserving device thermal protections and any mode restrictions. Authentication success is separate from receiving fresh state, and the changed property must be confirmed in a new state message — a publish acknowledgment is not an appliance acknowledgment; sensor readings are treated as device measurements, not a guarantee of room-wide air quality or temperature. Limits: no cloud credential retrieval, no account login, no firmware changes and no universal Dyson-family support in this runtime path; an unavailable key or incompatible product type is a setup blocker, not a reason to brute-force credentials or use an unauthenticated fallback. Repository: https://github.com/facebookincubator/muse-gadget-sdk (the skill is the whole skills/gadget-dyson-pure-hot-cool-hp04/ 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-dyson-pure-hot-cool-hp04/ 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 9cd49b6ac2406c73886def34179f0e6095c93977b3ad819c3a3a13200b2b7558 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,469 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 Dyson HP04 over its local MQTT interface through a model-compatible libdyson client on HomeLink's TCP connection: local authentication with my existing serial, product type and local MQTT password/credential from approved secret storage, status-topic subscriptions and documented HP04 operations. No cloud credential retrieval or account login happens at use time. - The skill does not do cloud credential retrieval, account login, firmware changes or universal Dyson-family support, and an unavailable key or incompatible product type is never a reason to brute-force credentials or use an unauthenticated fallback. - 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-dyson-pure-hot-cool-hp04 folder into the agent's skills directory, in a folder named exactly "gadget-dyson-pure-hot-cool-hp04", 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-dyson-pure-hot-cool-hp04), 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 Dyson Pure Hot+Cool HP04 already set up on my local network, and keep its existing serial, product type and local MQTT password/credential in approved secret storage; heating changes require my explicit permission; 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.