Meross Smart Plugs

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 Meross plug whose exact model and firmware support the signed local HTTP interface already set up on my local network (device UUID, model and firmware confirmed — a Meross vendor label alone is insufficient, and HomeKit-branded variants must still be checked for this interface), with its discovered local HTTP service and documented /config endpoint, permission to switch the actual load attached to the plug, and the device UUID and existing local key supplied through approved secret storage — cloud account/key acquisition is not part of this skill, and it stops for missing credentials without resetting or re-pairing the plug. Installing the file configures none of that. Install "Meross Smart Plugs" for me. It reads status and switches compatible Meross smart plugs through Muse Home Link, using the signed local HTTP interface with an existing device UUID and key; it is not cloud key acquisition or generic HomeKit onboarding. It is used when the exact Meross plug and firmware support the signed local HTTP interface and its existing device key is available: the device UUID, model and firmware are confirmed (a Meross vendor label alone is insufficient), the discovered local HTTP service and documented /config endpoint are used, and HomeKit-branded variants are still checked for this interface. It uses a direct protocol client or an agent-authored implementation of the documented request envelope — the community implementation is a protocol reference and installing its host platform is not required. It sends a signed read for Appliance.System.All and, where supported, Appliance.System.Ability, using the protocol's message ID, timestamp, namespace, method, device context and signature exactly as documented, and inspects reported abilities and current channel states: a device may expose Appliance.Control.ToggleX, an older toggle namespace or another model-specific interface, and it chooses what the device actually supports. For a requested relay change it sends the documented SET for that namespace and channel with the desired on/off value, never guessing a channel or reusing an unrelated model's payload, validates the matching response, method/error information and message identity, then reads state again using the supported namespace. A transport success or signed acknowledgment does not prove relay state: a fresh state response is compared with the requested channel/value, and power consumption is never inferred from relay state or metering promised unless the device advertises and documents that feature. Limits: cloud account/key acquisition is not part of this runtime skill — it stops for missing credentials and does not reset or re-pair the plug — and there is no universal Meross model support, no arbitrary namespace writes, no firmware updates and no separate HomeKit onboarding procedure. Repository: https://github.com/facebookincubator/muse-gadget-sdk (the skill is the whole skills/gadget-meross-smart-plugs/ 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-meross-smart-plugs/ 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 f16e9a1f4c41d184a5fee83be34d62deffad4d819255bf7b083a10f70c476093 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,558 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 Meross plug over its signed local HTTP interface (/config endpoint): signed Appliance.System.All / Appliance.System.Ability reads and documented SET writes for the namespace and channel the device actually supports, signed with the existing device UUID and local key from approved secret storage. No cloud account or key acquisition happens at use time. - The skill does not do cloud account/key acquisition (it stops for missing credentials and does not reset or re-pair the plug), universal Meross model support, arbitrary namespace writes, firmware updates or a separate HomeKit onboarding procedure. - 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-meross-smart-plugs folder into the agent's skills directory, in a folder named exactly "gadget-meross-smart-plugs", 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-meross-smart-plugs), 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 Meross plug whose exact model and firmware support the signed local HTTP interface already set up on my local network, and keep its existing device UUID and local key in approved secret storage (no cloud key acquisition is part of this skill); 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.