eufy RoboVac

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 Wi-Fi eufy RoboVac whose exact model and firmware are confirmed to use the documented local Tuya interface already set up on my local network (model code, local device ID, protocol and matching datapoint schema confirmed, with no broad generation table), a ready robot and my permission for the intended cleaning or docking action, existing local key and device ID supplied securely, and a compatible local eufy/TinyTuya client using HomeLink's TCP transport, as described in the generic Tuya skill (gadget-tuya-wifi-devices, same lot of this vetting, a separate listing from the same repository) — the cross-reference is disclosed here and the tested install of this listing remains the copy of its own folder only. Installing the file configures none of that. Install "eufy RoboVac" for me. It reads status and sends basic cleaning or docking commands to compatible Tuya-based eufy RoboVacs through Muse Home Link, with a confirmed model schema and existing local key; it excludes non-Wi-Fi and AIOT/X10 models. It is used when the exact Wi-Fi RoboVac model and firmware are confirmed to use the documented local Tuya interface: the model code, local device ID, protocol and matching datapoint schema are confirmed, without using a broad generation table, and this is not support for non-Wi-Fi models such as 11S or for X10/AIOT models. It uses a compatible local eufy/TinyTuya client using HomeLink's TCP transport, as described in the generic Tuya skill (gadget-tuya-wifi-devices, same lot of this vetting, a separate listing from the same repository); that cross-reference is part of this listing, while the tested install here remains the copy of this folder only. The client is initialized with the confirmed model/protocol, current endpoint and supplied credentials, and state is read before commands are sent. Cleaning mode, battery, error and docking state are decoded using the exact model's schema — datapoint numbers are never copied from a different RoboVac. For the user's requested action it uses the documented clean/start, pause/stop or return-to-dock operation supported by that model, then reads new status and monitors the relevant mission transition, keeping unsupported map, room and station operations out of the command set. A reported mission/state change must be confirmed — a TCP or encrypted-packet acknowledgment alone is insufficient — a command to dock is distinguished from successful docking, error/battery states are reported without overriding them, and state is read before retrying an uncertain movement command. Limits: no AIOT/X10 support, no non-Wi-Fi model support, no broad room/map/station promises and no cloud key retrieval in the runtime path; no credential extraction through debugging, no provisioning changes or re-pairing; and the existing documented model match and credentials are mandatory — guessed datapoints are never written. Repository: https://github.com/facebookincubator/muse-gadget-sdk (the skill is the whole skills/gadget-eufy-robovac-tuya/ 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-eufy-robovac-tuya/ 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 f76aefeb9e1ec9d2fdbdd311ab645d5ec8e2ee61d273f3d90af11bb2df6db32d 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,527 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. Cross-reference disclosed by the skill itself: it uses a compatible local eufy/TinyTuya client as described in the generic Tuya skill (gadget-tuya-wifi-devices, same lot of this vetting, a separate listing from the same repository). The tested install of this listing is still the copy of its own folder only. - 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 eufy RoboVac over the local Tuya interface through a compatible local eufy/TinyTuya client on HomeLink's TCP transport, as described in the generic Tuya skill (gadget-tuya-wifi-devices, same lot, separate listing from the same repository): status reads and the model's documented clean/start, pause/stop or return-to-dock commands, using my existing local key and device ID supplied securely. No cloud key retrieval and no credential extraction happen at use time. - The skill does not support AIOT/X10 or non-Wi-Fi models, makes no broad room/map/station promises, does no cloud key retrieval in the runtime path, no credential extraction through debugging, no provisioning changes or re-pairing, and never writes guessed datapoints. - 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-eufy-robovac-tuya folder into the agent's skills directory, in a folder named exactly "gadget-eufy-robovac-tuya", 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-eufy-robovac-tuya), 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 Wi-Fi eufy RoboVac already set up on my local network with its exact model schema confirmed, keep its existing local key and device ID supplied securely, and have the generic Tuya skill's client approach available as described in gadget-tuya-wifi-devices (same lot, separate listing from the same repository); 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.