Tuya Wi-Fi Devices

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 Tuya device confirmed to support local TCP already set up on my local network, with its existing device ID, local key, protocol version and a trustworthy exact model/firmware datapoint schema supplied securely (device type and protocol version are never inferred from a manufacturer prefix or discovery ports 6666/6667, and the separate control endpoint, commonly TCP 6668, is confirmed), a compatible TinyTuya client with local TCP transport routed through HomeLink, and permission for the specific actuator/load — and, where a matching device-specific skill exists, I use that skill instead, such as the compatible eufy RoboVac skill (gadget-eufy-robovac-tuya, same lot of this vetting, a separate listing from the same repository). Installing the file configures none of that. Install "Tuya Wi-Fi Devices" for me. It reads status and controls mapped capabilities on compatible Tuya local-TCP devices through Muse Home Link, only with a known protocol version, device ID, local key and exact datapoint schema; a matching device-specific skill is preferred where one exists. It is used when the exact device is confirmed to support Tuya local TCP and its protocol, key and model-specific datapoint map are known: device ID, model, firmware and protocol version come from existing approved configuration/documentation, and device type or protocol version is never inferred from a manufacturer prefix or discovery ports 6666/6667 — the control endpoint is separate, commonly TCP 6668, and must be confirmed. A compatible TinyTuya client with local TCP transport routed through HomeLink initializes the appropriate local device class using the confirmed identity, current endpoint, existing local key and explicit protocol version, and no cloud setup wizard is run as part of control. It reads current status and maps each returned datapoint through the known schema, including data type, units, range and enumeration values; for a requested change it writes only the mapped datapoint and valid desired value using the compatible client, never assuming datapoint 1 is always an on/off switch, then reads fresh state and compares the mapped value, handling protocol errors, unavailable datapoints and optimistic devices explicitly. An encrypted connection or write acknowledgment is not proof of the intended physical result; unknown datapoints are reported as unknown and their purpose is never discovered by trial-and-error writes; if the key no longer works it stops for updated authorized credentials rather than re-pairing automatically. Limits: not all Tuya-branded devices expose this interface (battery devices, gateways and new firmware can differ), and there is no cloud wizard/login, no key extraction, no automatic re-pairing, no arbitrary raw datapoint writes and no firmware changes, and a protocol version or datapoint schema is never generalized across unrelated models. Cross-reference: prefer a specific skill where available, such as the compatible eufy RoboVac skill (gadget-eufy-robovac-tuya, same lot of this vetting, a separate listing from the same repository); this listing's tested install remains the copy of its own folder only. Repository: https://github.com/facebookincubator/muse-gadget-sdk (the skill is the whole skills/gadget-tuya-wifi-devices/ 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-tuya-wifi-devices/ 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 ac8655b982b7a6bc93fbfc007d3a93dc1444eeb13c5126beef244b28419ae83a 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,744 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: prefer a specific skill where available, such as the compatible eufy RoboVac skill (gadget-eufy-robovac-tuya, 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 Tuya device over local TCP through a compatible TinyTuya client routed through HomeLink (control endpoint confirmed, commonly TCP 6668): status reads and writes of known mapped datapoints only, using my existing device ID, local key and explicit protocol version supplied securely. No cloud wizard or login is run, and no key is extracted. - The skill does not do cloud wizard/login, key extraction, automatic re-pairing, arbitrary raw datapoint writes (unknown datapoints are reported as unknown, never probed by trial-and-error writes) or firmware changes, and it does not generalize a protocol version or datapoint schema across unrelated models. - 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-tuya-wifi-devices folder into the agent's skills directory, in a folder named exactly "gadget-tuya-wifi-devices", 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-tuya-wifi-devices), 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 Tuya device confirmed for local TCP already set up on my local network, with its existing device ID, local key, protocol version and exact datapoint schema supplied securely; and, where a matching device-specific skill exists (such as gadget-eufy-robovac-tuya, same lot, separate listing from the same repository), prefer that specific 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.