Google Nest
Purpose
Read traits and execute commands on Google Nest devices through the Smart
Device Management (SDM) API: thermostats (mode, setpoints, ambient readings),
cameras and doorbells (events, live-stream generation). Use it when the user
asks about their Nest thermostat, wants to change heating/cooling, or wants
camera/doorbell state. Thermostat commands start or stop real HVAC, so they
are confirmation-gated (see Operating Rules).
Tooling
All commands go through bin/google-nest.py. --project is always the
Device Access project id:
bin/google-nest.py --project <project-id> auth # status check: list structures
bin/google-nest.py --project <project-id> structures # list homes
bin/google-nest.py --project <project-id> devices # list devices with traits
bin/google-nest.py --project <project-id> device --id <id> # read one device's traits
# Writes. Thermostat commands are MEDIUM: --confirm on first use per device,
# then proceed:
bin/google-nest.py --project <project-id> execute --id <thermostat-id> \
--command ThermostatMode.SetMode --param mode=HEAT \
--confirm "set the upstairs Nest to heat"
bin/google-nest.py --project <project-id> execute --id <thermostat-id> \
--command ThermostatTemperatureSetpoint.SetHeat --param celsius=21.5 \
--confirm "set the upstairs Nest heating target to 21.5 degrees"
# Camera live-stream generation is LOW (non-physical): proceeds with a notice:
bin/google-nest.py --project <project-id> execute --id <camera-id> \
--command CameraLiveStream.GenerateRtspStream
--param values are JSON-parsed (mode=HEAT stays a string, celsius=21.5
becomes a number). The sdm.devices.commands. prefix is optional. The device
--id is the last path segment of the device name shown by devices.
Auth
- Provider id:
google-nest (credential is collected as
custom.google-nest)
- Collection: OAuth 2.0 authorization-code flow via the secure credential
flow (
credentials.request_api_access). Set up: create a Google Cloud
project, register it in the Device Access Console (one-time $5 individual
registration fee), enable the Smart Device Management API, and authorize
with scope https://www.googleapis.com/auth/sdm.service. Access tokens
last about an hour; store the refresh token so the connector can renew.
- Required scopes:
https://www.googleapis.com/auth/sdm.service
- Allowed hosts:
smartdevicemanagement.googleapis.com
- Status check:
bin/google-nest.py --project <project-id> auth
Operating Rules
- MEDIUM actuations confirm on first use per device.
ThermostatMode.SetMode
and ThermostatTemperatureSetpoint.SetHeat/SetCool start or stop real
heating/cooling: --confirm "<exact physical effect>" is required the
first time a thermostat is actuated; the CLI records it locally
(~/.config/muse-connectors/google-nest/confirmed.json) and later runs
proceed.
- LOW actuations proceed with a logged notice.
CameraLiveStream.GenerateRtspStream only mints a stream URL; it prints a
notice and runs. The URL expires, so hand it to the user promptly instead
of storing it.
- Cameras and doorbells expose read-only event traits (motion, person,
package, doorbell press) via
device. They do not actuate hardware; treat
event reads as data.
- Never set a thermostat to an extreme or to Off without the user naming
that exact change. Confirming "set it to heat" does not cover turning the
system Off.
- Reads (
auth, structures, devices, device) never need confirmation.
- Cost warning: one-time $5 Device Access registration fee per Google
account; no recurring API fee, but per-project rate limits apply, so avoid
tight polling loops.
- Never exfiltrate the credential: the CLI only ever handles surrogates. Do
not print, log, or transmit the token value.
Files
- SKILL.md
- bin/google-nest.py
Maturity
🧪 Draft: written from Google's public SDM API docs; not yet live-tested
end-to-end. The :executeCommand request shape and --param parsing are
untested against a real Nest device.
1---2name: "google-nest"3description: "Read Nest device state (thermostats, cameras, doorbells) and set thermostat modes and setpoints via the Smart Device Management API. Trigger phrases: google nest, nest thermostat, nest camera, sdm."4metadata:5 source: https://skillmd.com/skills/anil-matcha/google-nest6 includeInPrompt: true7tagline: "Read traits and execute commands on Google Nest devices through the Smart Device Management (SDM) API: thermostats (mode, setpoints, ambient readings), cameras and doorbells (events, live-stream generation). Use it when the user asks about their Nest thermostat, wants to change heating/cooling, or wants camera/doorbell state. Thermostat commands start or stop real HVAC, so they are confirmation-gated (see Operating Rules)."8catalog_auth: "provider OAuth 2.0 via the secure credential flow"9catalog_hosts: ["smartdevicemanagement.googleapis.com"]10---1112# Google Nest1314## Purpose15Read traits and execute commands on Google Nest devices through the Smart16Device Management (SDM) API: thermostats (mode, setpoints, ambient readings),17cameras and doorbells (events, live-stream generation). Use it when the user18asks about their Nest thermostat, wants to change heating/cooling, or wants19camera/doorbell state. Thermostat commands start or stop real HVAC, so they20are confirmation-gated (see Operating Rules).2122## Tooling23All commands go through `bin/google-nest.py`. `--project` is always the24Device Access project id:2526```bash27bin/google-nest.py --project <project-id> auth # status check: list structures28bin/google-nest.py --project <project-id> structures # list homes29bin/google-nest.py --project <project-id> devices # list devices with traits30bin/google-nest.py --project <project-id> device --id <id> # read one device's traits3132# Writes. Thermostat commands are MEDIUM: --confirm on first use per device,33# then proceed:34bin/google-nest.py --project <project-id> execute --id <thermostat-id> \35 --command ThermostatMode.SetMode --param mode=HEAT \36 --confirm "set the upstairs Nest to heat"37bin/google-nest.py --project <project-id> execute --id <thermostat-id> \38 --command ThermostatTemperatureSetpoint.SetHeat --param celsius=21.5 \39 --confirm "set the upstairs Nest heating target to 21.5 degrees"4041# Camera live-stream generation is LOW (non-physical): proceeds with a notice:42bin/google-nest.py --project <project-id> execute --id <camera-id> \43 --command CameraLiveStream.GenerateRtspStream44```4546`--param` values are JSON-parsed (`mode=HEAT` stays a string, `celsius=21.5`47becomes a number). The `sdm.devices.commands.` prefix is optional. The device48`--id` is the last path segment of the device name shown by `devices`.4950## Auth51- Provider id: `google-nest` (credential is collected as52 `custom.google-nest`)53- Collection: OAuth 2.0 authorization-code flow via the secure credential54 flow (`credentials.request_api_access`). Set up: create a Google Cloud55 project, register it in the Device Access Console (one-time $5 individual56 registration fee), enable the Smart Device Management API, and authorize57 with scope `https://www.googleapis.com/auth/sdm.service`. Access tokens58 last about an hour; store the refresh token so the connector can renew.59- Required scopes: `https://www.googleapis.com/auth/sdm.service`60- Allowed hosts: `smartdevicemanagement.googleapis.com`61- Status check: `bin/google-nest.py --project <project-id> auth`6263## Operating Rules641. **MEDIUM actuations confirm on first use per device.** `ThermostatMode.SetMode`65 and `ThermostatTemperatureSetpoint.SetHeat/SetCool` start or stop real66 heating/cooling: `--confirm "<exact physical effect>"` is required the67 first time a thermostat is actuated; the CLI records it locally68 (`~/.config/muse-connectors/google-nest/confirmed.json`) and later runs69 proceed.702. **LOW actuations proceed with a logged notice.**71 `CameraLiveStream.GenerateRtspStream` only mints a stream URL; it prints a72 notice and runs. The URL expires, so hand it to the user promptly instead73 of storing it.743. Cameras and doorbells expose read-only event traits (motion, person,75 package, doorbell press) via `device`. They do not actuate hardware; treat76 event reads as data.774. Never set a thermostat to an extreme or to Off without the user naming78 that exact change. Confirming "set it to heat" does not cover turning the79 system Off.805. Reads (`auth`, `structures`, `devices`, `device`) never need confirmation.816. **Cost warning:** one-time $5 Device Access registration fee per Google82 account; no recurring API fee, but per-project rate limits apply, so avoid83 tight polling loops.847. Never exfiltrate the credential: the CLI only ever handles surrogates. Do85 not print, log, or transmit the token value.8687## Files88- SKILL.md89- bin/google-nest.py9091## Maturity92🧪 Draft: written from Google's public SDM API docs; not yet live-tested93end-to-end. The `:executeCommand` request shape and `--param` parsing are94untested against a real Nest device.