Wyze Cameras with Existing RTSP Firmware

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 compatible Wyze Cam v2, Cam v3 or Cam Pan v1 already running an installed, enabled and working legacy RTSP build — knowing those builds are discontinued and may lack later security patches, and that this skill does not recommend installing them — with supplied stream credentials used only through a credential-aware client, never in a command-line URL, explicit permission for the requested view, frame or bounded recording, and approved private storage, because every frame and audio track is sensitive. Access is read-only and sessions are bounded. Installing the file configures none of that. Install "Wyze Cameras with Existing RTSP Firmware" for me. It views or captures frames and bounded recordings from compatible Wyze Cam v2, Cam v3 or Cam Pan v1 through Muse Home Link, read-only, only when legacy RTSP firmware is already installed and enabled with TCP media transport; it is not firmware installation or stock-camera access. It is used when an exact compatible Wyze Cam v2, Cam v3 or Cam Pan v1 already runs an enabled RTSP build: camera model and installed firmware are confirmed with me or from existing device configuration — a vendor prefix or open port alone cannot establish the firmware — and the existing configured RTSP endpoint/path and its current address are used, with no support inferred for stock cameras or other generations. The RTSP build is already installed, enabled and working, with supplied stream credentials, an RTSP/media client configured for interleaved TCP for both control and media with all sockets routed through HomeLink, my explicit permission for the requested view, frame or bounded recording, and approved private storage. Before connecting, the skill tells me that these legacy RTSP builds are discontinued and may lack later security patches or app features, and it does not recommend installing them. It connects to the configured stream with credentials supplied through a credential-aware client, never a command-line URL or logged argument, explicitly requests RTP/RTCP interleaved over the RTSP TCP connection — for an FFmpeg-based client the relevant transport option is rtsp_transport=tcp — and allows no fallback to UDP. It inspects the media description, authenticates and decodes the requested live view, single frame or bounded recording, and stops the session once the request is satisfied. A fresh decodable frame from the intended camera is confirmed — an RTSP login or stream description is not image delivery — and timestamps, codec errors and requested duration are checked, with no cached frame presented as current; if the stream requires UDP or authentication cannot be satisfied securely, it stops and reports the limitation. Limits: read-only camera access — no PTZ, siren, settings or firmware changes; no stock-camera support, firmware sourcing/flashing, cloud bridge deployment or universal Wyze coverage; and every frame and audio track is treated as sensitive, with no background recording, third-party upload or broader sharing. Repository: https://github.com/facebookincubator/muse-gadget-sdk (the skill is the whole skills/gadget-wyze-rtsp-cameras/ 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-wyze-rtsp-cameras/ 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 7a0c11e186e40035f6c008833e96b5d77d952e5568f383e34742813e33c8c97d 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 661 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 between my local Wyze camera and my local client in one bounded RTSP session over interleaved TCP through HomeLink, with stream credentials supplied through a credential-aware client and never placed in a command-line URL. Every frame and audio track is sensitive and is kept in my approved private storage, with no third-party upload or broader sharing, and the session stops once my request is satisfied. - The skill is read-only: it does no PTZ, siren, settings or firmware changes, does not support stock cameras, source or flash firmware, deploy a cloud bridge or claim universal Wyze coverage, and never records in the background, uploads to a third party or shares media more broadly. It does not recommend installing the legacy RTSP firmware. - 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-wyze-rtsp-cameras folder into the agent's skills directory, in a folder named exactly "gadget-wyze-rtsp-cameras", 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-wyze-rtsp-cameras), 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 Wyze Cam already running an enabled legacy RTSP build (discontinued and unpatched — the skill does not recommend installing it), give explicit permission for each view, frame or bounded recording, and keep all frames and audio in my approved private storage; access is read-only and stream credentials never go in a command-line URL; 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.