Authenticate and control a Nest thermostat via Google Smart Device Management (Device Access) API
domain: developers.google.com/nest/device-access · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register at console.nest.google.com/device-access with a consumer (gmail.com) Google Account and pay the one-time, non-refundable US$5 registration fee.
Create a Google Cloud project, enable the Smart Device Management API, and create an OAuth 2.0 Web application client ID.
Create a Device Access project linking that OAuth client ID, then run the authorization-code flow at nestservices.google.com/partnerconnections/{project-id}/auth with the sdm.service scope and exchange the code at oauth2.googleapis.com/token.
Call GET https://smartdevicemanagement.googleapis.com/v1/enterprises/{project-id}/devices to list thermostats and their traits.
POST to .../devices/{device-id}:executeCommand with sdm.devices.commands.ThermostatTemperatureSetpoint.SetHeat/SetCool/SetRange to change setpoints.
Known gotchas
The $5 fee and the Google account used are permanent and non-refundable/non-transferable — use a dedicated team email, not a personal one, and Workspace accounts are not supported for registration.
Refresh tokens are revoked after ~6 months of disuse; apps that mostly consume Pub/Sub events without periodic REST calls can silently lose access.
This is a distinct program from the older, deprecated Works with Nest API — do not reuse old Nest API credentials or docs.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?