Google Nest Thermostats
Read and adjust Nest thermostats through a local bridge, with every change verified by a fresh read.
- What
- Read and adjust Nest thermostats through a local bridge, with every change verified by a fresh read.
- Cost
- Free
- Needs
- real Google Nest thermostats on your home network, already bridged into a local system Muse can reach through Home Link (for example Home Assistant on a Raspberry Pi), plus a Google Device Access project with the Smart Device Management API enabled (one-time US$5 registration fee) and an OAuth consent flow completed by you, the Google account owner. Tokens stay in the bridge; only you can re-consent if they expire. A Muse setup that can reach the bridge through Home Link is required.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a gadget skill for homes whose Nest thermostats are already bridged into a local system Muse can reach, most commonly Home Assistant on a Raspberry Pi, through Google's Smart Device Management API. This is not the Google Home app, not Google Cast, and not Matter commissioning: it reads and adjusts through the bridge. For status questions it reports ambient temperature and humidity, HVAC status, mode, and the active setpoint, matched to rooms with the user first, since bridge device names rarely match room names. For a requested change it sets the mode or setpoint through the bridge, then re-reads the device after a short wait to confirm the change actually applied, because Smart Device Management writes can lag and occasionally report success before the thermostat applies them. The setup behind it is real work the owner does once: a Google Device Access project with a one-time US$5 registration fee, an OAuth consent flow completed by the account owner, and tokens that stay in the bridge, re-consented only by the owner if they expire. The skill draws firm lines: 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 presented as freeze, heat-safety, or occupancy protection, and temperature history is household data, reported only as asked. By @amanthakkar, listed here with credit to its creator. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Google Nest Thermostats is a free Muse skill that reads and adjusts Nest thermostats through a local bridge: ambient temperature, humidity, HVAC status, mode and setpoint, matched to rooms with you first. Every change is confirmed by a fresh read after a short wait, and it follows your Home Link rules if you have them, otherwise its own stay-local rules.
Install
Copy the install package below, then paste it into MusePrerequisites: real Google Nest thermostats on your home network, already bridged into a local system Muse can reach through Home Link (for example Home Assistant on a Raspberry Pi), plus a Google Device Access project with the Smart Device Management API enabled (one-time US$5 registration fee) and an OAuth consent flow completed by you, the Google account owner. Tokens stay in the bridge; only you can re-consent if they expire. A Muse setup that can reach the bridge through Home Link is required. Install "Google Nest Thermostats" for me. A gadget skill that reads and adjusts Google Nest thermostats through Google's Smart Device Management API via your existing self-hosted bridge, verifying every change with a fresh read. Repository: https://github.com/amanthakkar/musecases/tree/main/skills/gadget-google-nest-thermostats 1. Fetch the SKILL.md file from the repository into a temporary folder and summarize what it does in one or two sentences. Do not paste the full SKILL.md text into this chat. 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, credential harvesting). Tokens must never be pasted into chat. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "gadget-google-nest-thermostats". 4. Verify with no network calls: frontmatter valid, file in place. 5. Report what was installed, where, and what I still need to do myself (for example matching each thermostat to its room, or re-consenting in the bridge). If your setup has the Home Link networking and safety rules document (~/docs/devices/home_link.md), follow it; if not, apply the stay-local rules in this prompt. 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 is in the prerequisites above. Rules: do not touch anything outside the temp folder and the install target. Do not create Device Access projects, do not handle OAuth or tokens on my behalf, and do not change thermostat schedules or learning features. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.