Miele G 7566 Dishwasher

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 Miele G 7566 whose local communications module supports the documented protocol, and the household's existing GroupID/GroupKey in approved secret storage — this skill never provisions those keys and never logs into any cloud. Status is read first; any command is allowed only if the exact module's protocol documents it and the appliance is safely prepared and armed by me at its panel, with all interlocks allowing it: remote start is NOT promised. Installing the file configures none of that. Install "Miele G 7566 Dishwasher" for me. It reads local Miele G 7566 dishwasher status through Muse Home Link when its module supports the documented protocol and existing GroupID/GroupKey are available, and considers commands only after confirming exact capabilities and local enablement; remote start is not promised. It is used when a Miele G 7566 has a compatible local communications module and the household's existing GroupID and GroupKey are available in approved secret storage: _mieleathome._tcp discovery and the appliance's model/type metadata are matched — a group identifier is not the secret GroupKey — and an unsigned 404 response with a Miele content type can indicate an authentication requirement without proving usable reads or permitted control. It implements or uses the local-protocol client component described by MieleRESTServer without deploying its REST server, preserving its MieleH256 signing, encrypted bodies and authenticated response handling, its exact signed host/path/headers, response validation and secure handling of the GroupKey. It uses authenticated GET /Devices/ to discover the exact device route returned by the local appliance API, never a guessed serial number, then the documented local Ident and State resources beneath that route, reading only fields actually returned by this module and reporting available status, program, remaining time and faults using the module's documented field meanings — no cloud-only field names, program lists or filling-level features are copied into the local interface. Status is read first. A command is considered only if the exact model/module protocol documents it and current appliance state permits it: remote start is conditional, not promised — I must prepare and arm the machine locally at its panel and all interlocks must allow it. For an allowed requested operation it uses that local protocol's documented command, then polls authenticated state; if the capability or prerequisites cannot be established, it remains read-only and explains what is missing. Model identification, successful decryption, readable state and successful physical operation are kept as separate checks; a sleeping module may return stale/invalid information and is never woken or started merely to check access without my permission, and HTTP acceptance alone does not prove start or stop. Limits: support is conditional on this unit's communications module and exposed capabilities; MieleRESTServer endpoints such as /generate-summary and /start/<name> belong to its wrapper server, not the appliance, and are never sent to the dishwasher; and there is no cloud login, no key provisioning, no reset/recommissioning, no generic program writes, no new server deployment and no bypassed door or remote-start interlocks. Repository: https://github.com/facebookincubator/muse-gadget-sdk (the skill is the whole skills/gadget-miele-g7566-dishwasher/ 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-miele-g7566-dishwasher/ 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 adbdf6546ee894babaab2060d57003a00a7feee3e4fd7c019271156f4c888387 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 309 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 Miele G 7566 module over its local signed/encrypted MieleH256 protocol: authenticated GET /Devices/ discovery and Ident/State reads beneath the returned route, using the household's existing GroupID/GroupKey from approved secret storage with secure GroupKey handling. A documented command is sent only if the exact module protocol documents it and the appliance is prepared and panel-armed by me; otherwise use stays read-only. No key is ever provisioned and no cloud login happens at use time. - The skill does not log into any cloud, provision any key, reset or recommission the appliance, write generic programs, deploy a new server or bypass door/remote-start interlocks, and it never sends the MieleRESTServer wrapper endpoints (/generate-summary, /start/<name>) to the dishwasher. Remote start is not promised. - 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-miele-g7566-dishwasher folder into the agent's skills directory, in a folder named exactly "gadget-miele-g7566-dishwasher", 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-miele-g7566-dishwasher), 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 Miele G 7566 with a compatible local communications module and keep the household's existing GroupID/GroupKey in approved secret storage (the skill never provisions them); status is read first, and any command additionally requires the exact module protocol to document it and the appliance prepared and armed by me at its panel — remote start is not promised; 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.