VIZIO D40f-G9

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 VIZIO D40f-G9 already configured on my local network exposing a compatible SmartCast local management service, a compatible pyvizio client over HomeLink HTTPS, normal on-screen PIN pairing when required with secure storage of the returned authentication token and appropriate device-specific TLS trust, my permission for the requested TV operation, and, for media, the companion gadget-google-cast skill plus a suitable receiver-reachable source (see step 2). Installing the file configures none of that. Install "VIZIO D40f-G9" for me. It controls supported VIZIO D40f-G9 TV functions through paired local SmartCast HTTPS using Muse Home Link. It is used when the confirmed VIZIO D40f-G9 exposes a compatible SmartCast local management service: exact model and firmware are confirmed from existing device information and the current service endpoint, and VIZIO SmartCast management and Google Cast are kept as different interfaces — a SmartCast product name alone does not prove a currently available Cast receiver. The TV is already configured, with a compatible pyvizio client over HomeLink HTTPS, normal on-screen PIN pairing when required, secure storage of the returned authentication token, appropriate device-specific TLS trust and my permission for the requested TV operation; media playback also requires a suitable receiver-reachable source. It uses the documented SmartCast pairing challenge/PIN flow with me, or reuses valid stored credentials, and never bypasses the pairing prompt. It reads available power, input, app and remote-control state using the model-compatible client, resolving IDs from device responses, performs the requested supported input/app/remote action and retains API result/error information, never assuming a generic endpoint works on every firmware, then reads state after the action; if the TV is in a standby mode that disables its network API, it reports that limitation. Token-authorized access and the resulting TV state are confirmed separately, and a remote-key acknowledgment may need visual confirmation — it does not prove successful navigation. For an independently advertised Cast receiver, it follows the shared Google Cast skill (gadget-google-cast, ../gadget-google-cast/SKILL.md) for media/status/volume, keeping its sessions and verification distinct from SmartCast management, and a Cast load is successful only under the shared skill's playback checks. Limits: no UDP wake, universal standby access, cloud control, firmware changes or general app installation, and no duplicate Cast procedure or assumed media hosting. Repository: https://github.com/facebookincubator/muse-gadget-sdk (the skill is the whole skills/gadget-vizio-d40f-g9/ 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-vizio-d40f-g9/ 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 44486ec7c623d7c7ff9c58097e29fb9f0e668c63067e083c178d7cc6f691e901 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 474 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: for media only, when a separate Cast receiver is actually advertised, this skill delegates to the shared Google Cast skill (gadget-google-cast, ../gadget-google-cast/SKILL.md), a separate lot 1 listing from the same repo at the same pin, keeping SmartCast and Cast sessions and verification distinct. Installed alone, this folder keeps a relative link to that companion; the exact folder name gadget-vizio-d40f-g9 keeps that link resolvable when the companion is installed alongside it, and installing the companion is recommended for the Cast part. The tested installation of this listing is still the copy of this skill's 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 VIZIO D40f-G9: paired SmartCast HTTPS management through pyvizio, with my stored authentication token from normal on-screen PIN pairing, and — only for an independently advertised Cast receiver — the shared Google Cast procedure (gadget-google-cast) for media/status/volume, kept distinct from SmartCast. No cloud control happens at use time. - The skill does not do UDP wake, universal standby access, cloud control, firmware changes or general app installation, and it carries no duplicate Cast procedure and no assumed media hosting. - 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-vizio-d40f-g9 folder into the agent's skills directory, in a folder named exactly "gadget-vizio-d40f-g9", 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-vizio-d40f-g9), 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 confirmed VIZIO D40f-G9 already configured on my local network; complete normal on-screen PIN pairing when required and keep the returned authentication token stored securely; for Cast media, have the companion gadget-google-cast skill installed; 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.