gadget-google-nest-thermostats
Skill2.6k starsChanged 25 days agoApache-2.0View on GitHub
Read and adjust Google Nest thermostats through Google's Smart Device Management API via an existing self-hosted bridge on the home network (for example Home Assistant on a Raspberry Pi) using Muse Home Link. Not Google Cast, not the Google Home app, and not Matter commissioning.
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 repository48 other files it gives its agents.
- esp32/AGENTS.mdAGENTS.md
- linux/AGENTS.mdAGENTS.md
- gadget-apple-homepod-miniSkill
- gadget-apple-tv-4kSkill
- 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-pixel-tabletSkill
- gadget-google-tv-streamerSkill
- 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-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-wifi-devicesSkill
- gadget-unifi-network-consolesSkill
- gadget-velux-klf200Skill
- 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
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Use this skill when the home's Nest thermostats are already bridged into a local system Muse can reach — most commonly Home Assistant on a …
- Distinctive: line 20
Read current ambient temperature, humidity, mode, and setpoint from the bridge before changing anything, so a change can be verified …
- Distinctive: line 25
If no bridge or no thermostat is reachable, stop and give the user these steps — do not create projects, consent to OAuth, or handle tokens …
- Very specific: line 39
Read and follow the Home Link networking and safety rules in ~/docs/devices/home_link.md.
- Distinctive: line 60
If reads return stale data, say so and give the last-update time rather than presenting it as current.
- Distinctive: line 65
No changes to the Device Access project, OAuth grants, account sharing, or thermostat schedules and learning features from a skill session.
≈ “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
Google Nest Thermostats — Smart Device Management Bridge
Use this skill when the home's Nest thermostats are already bridged into a local system Muse can reach — most commonly Home Assistant on a Pi — through Google's Device Access program, and the user asks about indoor temperature, setpoints, or HVAC mode.
Identify the Device
- Confirm which thermostats the bridge exposes and match them to rooms with the user; SDM device names rarely match room names out of the box.
- Read current ambient temperature, humidity, mode, and setpoint from the bridge before changing anything, so a change can be verified against the prior state.
Guided Setup Check
If no bridge or no thermostat is reachable, stop and give the user these steps — do not create projects, consent to OAuth, or handle tokens on their behalf.
- In the Google Device Access Console, create a Device Access project and enable the Smart Device Management API. Google charges a one-time US$5 registration fee; it is a developer program, and Google can change its terms, quotas, or availability.
- As the Google account owner, complete the OAuth consent flow and connect the project in the local bridge (for example the Home Assistant Google Nest integration). Refresh tokens stay in the bridge; if they expire, only the owner can re-consent.
- List the devices the project exposes and match each thermostat to its room with the user before answering questions about it.
Prerequisites
Read and follow the Home Link networking and safety rules in ~/docs/devices/home_link.md.
- The guided setup check passes: a Device Access project exists, the bridge holds valid tokens, and the thermostats are reachable through the bridge's local API or entities.
- Note: SDM writes can lag and occasionally report success before the thermostat applies them; the workflow below verifies after every write. Newer Nest models may also support Matter locally — prefer whichever path the home already runs rather than migrating as a side effect.
Workflow
- For status questions, read the thermostat traits through the bridge's local API or entities: ambient temperature and humidity, HVAC status, mode, active setpoint.
- For an adjustment the user requested, set the mode or setpoint through the bridge, then re-read the device state after a short wait to confirm it applied.
- Report temperatures in the units the household uses, with the read time.
Verify the Result
- A successful API response is not proof the thermostat changed: confirm via a fresh state read showing the new setpoint or mode.
- If reads return stale data, say so and give the last-update time rather than presenting it as current.
Limits
- No changes to the Device Access project, OAuth grants, account sharing, or thermostat schedules and learning features from a skill session.
- Comfort control only: never present thermostat automation as freeze, heat-safety, or occupancy protection.
- Temperature history is household data; report what the user asked for, nothing more.
Sources
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.

