gadget-sinricpro-cloud-devices
Skill2.8k starsChanged 26 days agoApache-2.0View on GitHub
Cloud only: needs internet access and a SinricPro account API key; does not use Muse Home Link or the local network. Read status and control the user's SinricPro devices through the SinricPro cloud REST API: homes and rooms, device state, actions with confirmation over the event stream, scenes, schedules and a read-only automation list. Device actions, scene runs and scene or schedule edits need the user's confirmation. Prefer a device-specific or local skill when one matches.
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-insignia-fire-tvSkill
- 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-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
9 rules. About 0 are common, 3 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
Read and follow the safety rules in ~/docs/devices/home_link.md.
- Very specific: line 29
Every response carries success.
- Very specific: line 54
Wait for a stream event with event: "deviceMessageArrived" whose message.payload.replyToken equals the messageId.
- Distinctive: line 64
Before any device action, scene run, or scene or schedule create, update or delete, read back the device and its room (or the scene or …
- Very specific: line 72
Do not resend an unconfirmed action, scene run or toggle until its outcome has been checked.
- Very specific: line 78
No camera live view, streaming or snapshots.
- Distinctive: line 79
No adding, removing or renaming devices, rooms or homes, and no creating or editing automations.
- Very specific: line 80
Never read /devices/{id}/credential, and never repeat a device's unlockPin or accessKey fields to anyone.
- Distinctive: line 81
Only the user's own account devices behind their key.
≈ “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
SinricPro Cloud Devices: REST API Control
Use this skill when a SinricPro API key is available and the user asks to control or query devices from their SinricPro account. SinricPro devices are typically ESP32, ESP8266, Raspberry Pi Pico or Linux boards running the SinricPro SDK; they are reached through the cloud, so no local address or firmware-specific protocol is needed. For a device that also exposes a local API, prefer its own skill, such as ESPHome devices.
Identify the Device
- List devices with
GET /devices. Each entry indevices[]carriesid,name,isOnline,room.name,room.home.name,product.code(the type, such assinric.devices.types.LIGHT) andproduct.actions[](the actions the device accepts). Current state is in fields on the same object:powerState,brightness,color,colorTemperature,powerLevel,temperature,humidity,targetTemperature,thermostatMode,rangeValue,volume,muted,lockState,garageDoorState,contactStateandlastMotionState, present only where the device has them.GET /homes?includeRooms=trueandGET /roomslist homes and rooms. - Match the user's words against
name, room and type. With multiple matches, list the candidates with their rooms and ask. isOnline: falsemeans report the device as offline and command nothing.deactivated: truemeans the device has no active license and cannot be controlled.
Prerequisites
Read and follow the safety rules in ~/docs/devices/home_link.md; its local networking rules do not apply, because this skill reaches the devices through the SinricPro cloud.
- Cloud only. This skill needs a SinricPro account with the devices already added, and internet access from Muse to
https://api.sinric.proandhttps://sse.sinric.pro. Use the normal internet path, never the Home Link proxy; a Muse Home Link is not required. If the cloud is unreachable, report that rather than trying a local path. - A SinricPro API key, created by the account owner in the SinricPro portal and supplied through approved secret storage. It grants full access to the account and has no scopes. Send it only in the
X-SINRIC-API-KEYheader through a credential-aware client, never in a credential-bearing shell command, and never log or echo it. If no key is available, explain this setup instead of asking for the key in chat. - Send
X-SINRIC-API-KEY: <key>on every call tohttps://api.sinric.pro/api/v1. Send request bodies as JSON. - Every response carries
success. Treatsuccess: falseas a failure even with HTTP 200; some update routes report validation errors that way.401means the key is wrong or was deleted: stop and ask the owner to supply a new key securely. - Device reads are limited to 20 per minute per account, and sustained use at the limit triggers a 30-minute slow mode of 2 per minute. List devices once and reuse the result; on
429wait the number of seconds inresetTimebefore any further read.
Workflow
Identify the device as above, and choose an action from its own
product.actions[]. Build its value:Action Value setPowerState{"state":"On"}/{"state":"Off"}setBrightness/adjustBrightness{"brightness":50}/{"brightnessDelta":-25}setPowerLevel/adjustPowerLevel{"powerLevel":50}/{"powerLevelDelta":-25}setColor{"color":{"r":255,"g":0,"b":0}}setColorTemperature{"colorTemperature":2700}targetTemperature{"temperature":22}setThermostatMode{"thermostatMode":"COOL"}—COOL,HEAT,AUTO,OFF,ECOsetRangeValue/adjustRangeValue{"rangeValue":3}/{"rangeValueDelta":-1}— fan speed, blinds 0–100setVolume/setMute{"volume":25}/{"mute":true}mediaControl{"control":"Pause"}—Play,Pause,Stop,Next,PrevioussetMode{"mode":"MOVIE"}; on a garage door{"mode":"Close"}setLockState{"state":"lock"}For relative asks ("a bit brighter"), use the
adjust*action with a delta when the device lists it. Custom devices with several range, mode or toggle capabilities also need the capability'sinstanceId, found underproduct.deviceTemplate.capabilities.- Open the event stream before sending:
GET https://sse.sinric.pro/sse/streamwith the same key header andAccept: text/event-stream. It is a long-lived outbound HTTP connection that deliversdata:lines of JSON. Keep it running in the background, and send the action only once it has connected and stayed open. - Send
POST /devices/{id}/actionwith{"type":"request","action":"...","value":"<value as JSON text>","clientId":"muse","messageId":"<new UUID>","createdAt":<unix seconds>}, addinginstanceIdwhen needed.valueis the value object from the table encoded as a JSON string, as in the API guide:"value":"{\"state\":\"On\"}".createdAtmust be current; stale messages are discarded. A200withsuccess: truemeans the command was queued, not that it took effect. - Wait for a stream event with
event: "deviceMessageArrived"whosemessage.payload.replyTokenequals themessageId. Itspayload.successandpayload.valueare the device's own answer. Wait up to 8 seconds, or 20 seconds for locks, garage doors and blinds, then close the stream.
Scenes, Schedules and Automations
- Scenes:
GET /sceneslists scenes with theirdeviceActions[](device,action,actionValue). Before running one, read itsdeviceActions(parsing any stringactionValue) and refuse if it contains an action the Limits below forbid or a value that can't be parsed; then run it withPOST /scenes/test/{id}. The response only confirms the actions were queued. Create withPOST /scenesand{"name","description","deviceActions":[{"device":"<id>","action":"...","actionValue":{...}}]}, using the same actions and values as the workflow table; names are 3–50 characters and unique.PUT /sceneswithidin the body replaces the whole scene.DELETE /scenes/{id}removes it.actionValuecan come back as a JSON string that needs a second parse. - Schedules:
GET /scheduleslists them. Create withPOST /schedulesand{"name","enable":true,"scheduleType":"time","deviceId":"<id>","action":"...","actionValue":"...","weekdays":["monday",...],"hour":0-23,"minute":0-59}. Schedule actions are labels, not device actions:Turn OnandTurn Off(withactionValue"On"/"Off"), andSet Brightness,Set PowerLevel,Set Blinds,Set Fan SpeedandSet Temperature(with a numeric string). Any other label is stored but never runs. Times are in the account's time zone. There is no enable or disable endpoint:PUT /scheduleswithidand every field replaces the schedule. Read it first withGET /schedules/{id}and rebuild the write body from it: the stored schedule names its device asdevice(an object withid, or the id itself), but the write needsdeviceId, so map it; then sendname,description,enable,scheduleType,deviceId,action,actionValue,weekdays,hourandminutewith only the change applied.DELETE /schedules/{id}removes it. - Automations:
GET /automationslists them. They are read-only here.
Confirm Before Acting
- Before any device action, scene run, or scene or schedule create, update or delete, read back the device and its room (or the scene or schedule), the action and the value, and wait for the user's yes. A yes covers that one action only.
- Exceptions: brightness, color, volume and media control on a device the user named need only the user's own request, and reads need no confirmation.
Verify the Result
- Report a device action as done only from the device's reply on the event stream. If none arrives in time, say the command was sent but not confirmed; the device may be offline or on weak Wi-Fi.
- A scene run queues device actions: report it as started, not as done, unless a later
GET /devicesshows the expected state. - Scene and schedule create, update and delete change stored configuration and get no device reply. Confirm them from
success: trueand a freshGET /scenesorGET /schedulesshowing the change. - Do not resend an unconfirmed action, scene run or toggle until its outcome has been checked. A later
GET /devicesshows the last state the device reported. - A stream that closes at once with
Invalid API Keyin its body means the key was rejected, even though the status is200.
Limits
- Never unlock a lock or open a garage door through this skill. Locking and closing are allowed after confirming the intended device; for unlocking and opening, say so and point to the SinricPro app. Do not run, create or update a scene that contains such an action, and do not create or update a schedule for a lock or garage door, because schedule labels such as
Turn Offdo not say which way it would move. - No camera live view, streaming or snapshots; never send
getWebRTCAnswerorgetCameraStreamUrl. - No adding, removing or renaming devices, rooms or homes, and no creating or editing automations.
- Never read
/devices/{id}/credential, and never repeat a device'sunlockPinoraccessKeyfields to anyone. - Only the user's own account devices behind their key. Send batch commands one at a time.
Sources
- sinricpro-agent-skills — upstream skill and reference CLI this was adapted from.
- SinricPro API guide
- SinricPro API reference
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.

