gadget-insignia-fire-tv
Skill2.8k starsChanged 26 days agoApache-2.0View on GitHub
Control compatible Insignia Fire TVs through their PIN-paired local HTTP/HTTPS remote API using Muse Home Link. Covers installed apps, app launch, remote keys, volume, mute, supported playback toggles and normal-standby wake. Not for Insignia Roku TVs.
Trending
More talk lately.thin dataabout the whole repository
Who's talking about facebookincubator/muse-gadget-sdk
- @j4ck.xyz“I still wouldn't trust Meta with my personal context for agents, but what they're doing with Muse is pretty …”Bluesky · Oct 2, 2026 · 7 likes
- A Hacker News story“Open source SDK to build Muse gadgets”Hacker News · Oct 3, 2026 · 2 points
- ComBba/muse-gadget-sdk“CI preflight: wait for the installer serial close before SDK token setup”GitHub · Oct 17, 2026 · 1 reactions
- @sarubot.bsky.social“muse-gadget-sdk — Metaが放つ、ESP32やラズパイをAIガジェットへ変貌させるSDK。今週スター急増中の注目作! …”Bluesky · Oct 7, 2026 · 1 likes
- aegisfleet/tool-survey-report“feat: add survey report for Muse Gadget SDK”GitHub · Nov 9, 2026
The biggest 5 of 14 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 14
Talked about on GitHub, Bluesky and Hacker News (14 times).
On GitHub · 11
- Oct 17, 2026CI preflight: wait for the installer serial close before SDK token setup — ComBba/muse-gadget-sdk1 reaction · 2 comments
- Nov 9, 2026feat: add survey report for Muse Gadget SDK — aegisfleet/tool-survey-report0 reactions · 4 comments
- Oct 14, 2026Fix S3-2.06 ES7210 microphone and native USB serial console — polygoku/waveshare-amoled-206-debug0 reactions · 5 comments
- Oct 12, 2026Integration blocker: native Muse gadget command invocation — 1chris2many/muse-portal-kit0 reactions
- Oct 12, 2026Integration blocker: authoritative per-device reply correlation — 1chris2many/muse-portal-kit0 reactions · 2 comments
6 more on GitHub
- Oct 11, 2026[fork CI preflight] #181 candidate a6fd89c — ComBba/muse-gadget-sdk0 reactions · 1 comment
- Oct 11, 2026[fork CI] #179 Use the custom avatar in the UI simulator — ComBba/muse-gadget-sdk0 reactions · 1 comment
- Oct 11, 2026[fork CI] #181 Add validated avatar restore and host status — ComBba/muse-gadget-sdk0 reactions · 1 comment
- Oct 11, 2026[fork CI] #180 Validate avatar candidates before replacing the current renderer — ComBba/muse-gadget-sdk0 reactions · 1 comment
- Oct 11, 2026[fork CI] #174 Reject incomplete bench screenshots without padding pixels — ComBba/muse-gadget-sdk0 reactions · 1 comment
- Oct 11, 2026[fork CI] #177 Abort bench screenshots when USB console output stalls — ComBba/muse-gadget-sdk0 reactions · 1 comment
On Bluesky · 2
- Oct 2, 2026I still wouldn't trust Meta with my personal context for agents, but what they're doing with Muse is pretty cool & fun icl… — @j4ck.xyz7 likes and reposts
- Oct 7, 2026muse-gadget-sdk — Metaが放つ、ESP32やラズパイをAIガジェットへ変貌させるSDK。今週スター急増中の注目作! ・C言語製のESP32/Linux用SDK。センサーやオーディオをMuseエコシステムに即統合 ・AIエージェント「Muse… — @sarubot.bsky.social1 likes and repost
On Hacker News · 1
- Oct 3, 2026Open source SDK to build Muse gadgets2 points
In this repository57 other files it gives its agents.
- esp32/AGENTS.mdAGENTS.md
- linux/AGENTS.mdAGENTS.md
- gadget-amazon-echoSkill
- gadget-apple-homepod-miniSkill
- gadget-apple-tv-4kSkill
- gadget-bambu-lab-p2sSkill
- gadget-bambu-lab-printersSkill
- gadget-brother-printersSkill
- gadget-dyson-pure-hot-cool-hp04Skill
- gadget-ecowitt-gatewaysSkill
- gadget-elgato-key-lightSkill
- gadget-epson-printersSkill
- gadget-esphome-devicesSkill
- gadget-espsomfy-rtsSkill
- gadget-eufy-robovac-tuyaSkill
- gadget-freebox-player-popSkill
- gadget-google-castSkill
- gadget-google-home-maxSkill
- gadget-google-home-speakerSkill
- gadget-google-nest-audioSkill
- gadget-google-nest-hub-maxSkill
- gadget-google-nest-hubSkill
- gadget-google-nest-miniSkill
- gadget-google-nest-thermostatsSkill
- gadget-google-pixel-tabletSkill
- gadget-google-tv-streamerSkill
- gadget-homewhiz-laundrySkill
- gadget-hp-color-laserjet-pro-m254dwSkill
- gadget-irobot-roomba-braavaSkill
- gadget-lg-webos-tvsSkill
- gadget-logitech-squeezeboxSkill
- gadget-lutron-smart-bridgesSkill
- gadget-meross-smart-plugsSkill
- gadget-miele-g7566-dishwasherSkill
- gadget-moonraker-3d-printersSkill
- gadget-philips-hue-bridgesSkill
- gadget-pixoo-64Skill
- gadget-ratgdo-v32-garage-doorSkill
- gadget-roborock-vacuumsSkill
- gadget-roku-tvs-and-playersSkill
- gadget-samsung-tizen-tvsSkill
- gadget-shelly-plugsSkill
- gadget-sinricpro-cloud-devicesSkill
- gadget-sonoff-rf-bridgeSkill
- gadget-sonos-speakersSkill
- gadget-teslaSkill
- gadget-tplink-kasa-ep10Skill
- gadget-tplink-kasa-ep25Skill
- gadget-tuya-cloud-devicesSkill
- gadget-tuya-wifi-devicesSkill
- gadget-unifi-network-consolesSkill
- gadget-velux-klf200Skill
- gadget-vesync-humidifierSkill
- gadget-vizio-d40f-g9Skill
- gadget-wyze-rtsp-camerasSkill
- gadget-yi-hack-camerasSkill
- gadget-zigbee2mqtt-gatewaysSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 8 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Use the supplied IP or Home Link discovery.
- Very specific: line 26
Read and follow the Home Link networking and safety rules in ~/docs/devices/home_link.md.
- Distinctive: line 32
If files are used, use directory mode 0700 and file mode 0600, outside source control.
- Distinctive: line 33
Keep tokens out of chat, logs and command arguments.
- Very specific: line 40
If activation is needed for requested pairing, wake or control, send bodyless POST http://<tv-ip>:8009/apps/FireTVRemote.
- Distinctive: line 51
Stop on mismatch; do not automatically replace the pin or re-pair.
- Distinctive: line 63
If a PIN prompt closes or returns no token, retain existing credentials and use a fresh user-assisted prompt.
- Distinctive: line 105
Use finite request timeouts.
- Distinctive: line 106
If fresh user-assisted pairing also fails, stop rather than looping.
- Very specific: line 113
No reliable foreground-app, playback or mute-state read-back is established here.
- Distinctive: line 127
No cloud fallback, ADB fallback, pairing bypass, screenshots, sideloading, account setup, purchases, firmware changes or assumed Cast …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Insignia Fire TVs
Local remote control through Muse Home Link: HTTP on port 8009 activates the remote service; HTTPS on port 8080 handles pairing and controls. This community-observed API requires no ADB or developer mode.
Identify the Device
- Confirm an Insignia TV running Fire TV, its current address and firmware. Tested on
INSIGNIA_NS-55F501NA26, Fire OS8.1.8.5(RS8185/3885); compatibility can vary. - Use the supplied IP or Home Link discovery. If a DIAL description URL is advertised, use that URL rather than guessing paths. If discovery fails, ask for the IP; do not scan the subnet. The model and OS version were supplied by the user, not the API.
- Port 8009 is HTTP/DIAL here; it does not establish Google Cast support.
Prerequisites
Read and follow the Home Link networking and safety rules in ~/docs/devices/home_link.md.
- A configured TV and HTTP/HTTPS client routed through Home Link to ports 8009 and 8080.
- A person able to read the normal on-screen pairing PIN when credentials are absent.
- Securely retained per-TV client token and device-specific TLS trust. Use the runtime's existing private credential facility; do not assume storage on Home Link hardware. If files are used, use directory mode 0700 and file mode 0600, outside source control. Keep tokens out of chat, logs and command arguments; discard temporary PIN payloads.
- Permission for the requested screen/audio action. Launching an app or pressing Home can interrupt playback. Service activation can wake the display, so do not activate automatically for a status-only request.
TLS and Pairing
- If activation is needed for requested pairing, wake or control, send bodyless
POST http://<tv-ip>:8009/apps/FireTVRemote. The tested response was201 Created. Activation restored port 8080 and woke the display from normal standby. - Preserve existing per-TV trust and credentials. The tested TV's certificate chain failed normal CA verification. For first enrollment, use an independently verified public key if available, otherwise explain trust on first use on the user's trusted local network. Capture the leaf public key without sending credentials and retain it per TV. Seeing a PIN on screen is not independent certificate verification.
- Enforce that key on subsequent HTTPS requests, including pairing. Curl supports
--insecuretogether with--pinnedpubkey <saved-public-key-file>for this device; never fall back to--insecurealone. A wrong pin failed before HTTP with curl error 90. Stop on mismatch; do not automatically replace the pin or re-pair. Keep requests on the authorized TV origin and do not follow redirects to other hosts. - Request a PIN with
POST https://<tv-ip>:8080/v1/FireTV/pin/display, headersX-Api-Key: 0987654321andContent-Type: application/json, and body{"friendlyName":"Muse"}. Ask the user for the displayed PIN without echoing it. - Submit
{"pin":"<displayed-pin>"}toPOST /v1/FireTV/pin/verifywith the same headers and TLS trust. A successful response contains the token indescription. An incorrect PIN returned HTTP 200 with{"description":""}: HTTP success is not pairing success. Require a nonempty token other thanOK, then validate it with an authenticated app-list read before replacing stored credentials. - Reuse the saved token via
X-Client-Token, alongside the API-key header. Both the token and pinned key survived normal standby and a user-performed TV restart. If a PIN prompt closes or returns no token, retain existing credentials and use a fresh user-assisted prompt. One fresh prompt recovered successfully in testing.
Request Shape
Except activation, use https://<tv-ip>:8080 with X-Api-Key: 0987654321,
X-Client-Token: <saved-token> and Content-Type: application/json.
Send no request body for the controls below, rather than an empty JSON object.
A custom User-Agent was not needed for the tested YouTube launch.
| Operation | Method and path | Behavior |
| Installed apps | GET /v1/FireTV/appsV2 | Array with name, appId, isInstalled and optional shortcut/icon fields. |
| Remote key | POST /v1/FireTV?action=<key> | home, dpad_up, dpad_down, dpad_left, dpad_right, select, back, menu. Menu returned OK with no visible effect in YouTube's sidebar. |
| App launch | POST /v1/FireTV/app/<appId> | Use a returned installed-app ID; encode it as a path segment. |
| Volume step | POST /v1/FireTV?action=volume_up or volume_down | On-screen volume changes confirmed, including one-step decreases. |
| Mute toggle | POST /v1/FireTV?action=mute | Confirmed mute/unmute toggle. volume_mute was rejected with HTTP 400. |
| Playback toggle | POST /v1/media?action=play or pause | In YouTube, both actions toggled playing/paused, including resuming when repeated while paused. Neither is a discrete play or pause operation. |
Missing and invalid client tokens returned HTTP 403 with descriptions identifying
missing client token or contains invalid client token. The app-list read accepted
an omitted API-key header with a valid token, but retain the header for compatibility.
Workflow
- Select the intended TV, establish trusted HTTPS and reuse valid credentials or pair normally. Keep service availability, authentication and visible control separate.
- For app launch, query the app list and resolve the user's requested app. Confirmed
launches: YouTube (
com.amazon.firetv.youtube), Netflix (com.netflix.ninja), HBO Max (com.hbo.hbonow), Apple TV (com.apple.atve.amazon.appletv) and Disney+ (com.disney.disneyplus). Prime Video was omitted from the list but launchingcom.amazon.firebatworked on the tested configuration.com.amazon.cloud9is Silk on this TV, despite an incorrect Prime Video label in a community reference. - Send the requested operation and allow app loading before further navigation. Launch may show a profile chooser or resume a profile. Do not automatically press Select: confirm the chooser and intended highlighted profile when selection is requested. Back is context-dependent; it opened YouTube's sidebar rather than exiting.
- For explicit mute/unmute or pause/resume requests, establish the current state first. Send nothing if already in the desired state. Do not blindly repeat a toggle or volume step after an uncertain response.
- For connection refusal/timeout, activate the remote service once when appropriate, then try at most three authenticated reads within a total 30-second recovery window. Use finite request timeouts. Stop on TLS mismatch; diagnose HTTP 401/403 separately. If fresh user-assisted pairing also fails, stop rather than looping.
Verify the Result
- HTTP 200 and
description: OKdo not prove the screen changed. A nonexistent app ID also returned OK but produced an App not found popup. Use actual app IDs and inspect available state or obtain visual confirmation before claiming success. - No reliable foreground-app, playback or mute-state read-back is established here.
DIAL
FireTVRemotestate reportedstoppedeven while controls worked; it is not display-power or foreground-app state. - Preserve the user's intended final screen. Do not send Home immediately after a launch, select content, start playback or switch profiles without the corresponding request.
Limits
- Normal-standby wake worked through service activation; unplugged power, deeper sleep and other model/firmware combinations may differ. Direct restart/power-off is not established. Do not substitute an unobserved Settings key sequence.
- App launch does not establish subscription entitlement. Playback toggles are confirmed in YouTube; other apps can behave differently. Hold/repeat timing, seeking, text/search, HDMI inputs, numeric volume setting/read-back and voice are outside this procedure.
- No cloud fallback, ADB fallback, pairing bypass, screenshots, sideloading, account setup, purchases, firmware changes or assumed Cast support.
Sources
- FireTVRest — PIN pairing, keys, media and app launch; resolve IDs against the TV.
- HMS FireTV — app discovery and remote protocol.
- HMS mute routing —
muteaction. - python-androidtv constants — Prime Video's
com.amazon.firebatID. - Node-RED Fire TV remote — volume actions; its
volume_mutecandidate failed on this TV. - curl public-key pinning — key matching and trust behavior.
- Amazon developer response — no public remote-control API was offered as of July 2024.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

