Sonoff RF Bridge R2

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 stock Sonoff RF Bridge R2 already configured for LAN operation on my local network, with its existing device ID and devicekey supplied through approved credential storage (no cloud key retrieval is part of this skill), and a private, user-confirmed channel-to-action mapping (channels 0-15). Only user-approved fixed-code 433 MHz actions are captured or transmitted: no rolling codes and no key extraction; the AES key derived from the devicekey never leaves my machine and never appears in commands or logs. Installing the file configures none of that. Install "Sonoff RF Bridge R2" for me. It captures or transmits user-approved fixed-code 433 MHz actions through a stock Sonoff RF Bridge R2 using Muse Home Link, using compatible HTTP zeroconf firmware, existing device credentials and a confirmed channel map; it is not rolling codes. It is used when fresh discovery identifies a compatible stock Sonoff RF Bridge R2 — _ewelink._tcp, exact bridge model and firmware matched, the HTTP zeroconf service commonly on 8081 with the discovered endpoint used, and firmware 3.x HTTP zeroconf kept distinct from older WebSocket recipes, with compatibility never inferred from radio frequency or brand alone. The bridge already has LAN operation configured and its device ID/devicekey are supplied through approved credential storage; no cloud key retrieval is part of this procedure. I maintain a private, user-confirmed channel-to-action mapping over channels 0-15 — the bridge does not provide a reliable local learned-channel inventory — and the physical target, channel and effect are confirmed before capture or transmission, particularly doors, alarms and power outlets. For each command it builds a fresh request envelope: it derives the 16-byte AES key as the raw MD5 digest of the devicekey, uses a fresh random 16-byte IV, AES-128-CBC, PKCS#7 padding and base64 ciphertext/IV, encrypts the UTF-8 JSON command payload, then POSTs to the corresponding /zeroconf/<command> endpoint with sequence (millisecond string), deviceid, literal selfApikey:"123", encrypted data, encrypt:true and iv — keeping all key material out of commands and logs, and the derived AES key never leaves the machine. For learning I request on a confirmed free channel N, it sends {"cmd":"capture","rfChl":N} to /zeroconf/capture, then I press the intended remote near the bridge; an existing mapping is never overwritten without my explicit authorization, and a confirmed channel assignment is recorded privately after successful learning. For a known learned action it sends {"cmd":"transmit","rfChl":N} to /zeroconf/transmit once, inspects the application response including any device error, and decodes an encrypted response according to its envelope. HTTP 200 is not physical proof: the intended device actually acting is confirmed through independent state feedback or by me, RF device state is never inferred from the channel map or an uncertain transmit response, and an uncertain RF transmission is never automatically repeated, since some learned actions toggle state or move a device. Limits: fixed-code 433 MHz only in this scope — no rolling-code replay, infrared or universal remote support; no companion client is required and the agent may implement the documented envelope; and no replacement firmware is installed, no keys are extracted from accounts and no cloud fallback is created. Repository: https://github.com/facebookincubator/muse-gadget-sdk (the skill is the whole skills/gadget-sonoff-rf-bridge/ 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-sonoff-rf-bridge/ 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 b6288e113e1fa652a748a727106f31c4d8ffe6d9f0e40f1393f57247f1101b69 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 (3 306 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 stock Sonoff RF Bridge R2 over its encrypted HTTP zeroconf endpoints: capture or transmit envelopes for user-approved fixed-code actions on channels from my confirmed channel map. The devicekey comes from approved credential storage, all key material stays out of commands and logs, and the derived AES key never leaves my machine — it only encrypts the payload locally for my own bridge. No rolling code is captured or replayed and no key is extracted. - The skill does not replay rolling codes, support infrared or universal remotes, install replacement firmware, extract keys from accounts or create a cloud fallback, and it never automatically repeats an uncertain RF transmission. - 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-sonoff-rf-bridge folder into the agent's skills directory, in a folder named exactly "gadget-sonoff-rf-bridge", 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-sonoff-rf-bridge), 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 stock RF Bridge R2 already configured for LAN operation and keep its existing device ID/devicekey in approved credential storage; maintain my private, confirmed channel-to-action map — only my approved fixed-code actions are captured or transmitted, never rolling codes, and the derived AES key never leaves my machine nor appears in commands or logs; 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.