Nest & Ecobee thermostat OAuth (operators)

Enable Nest and Ecobee OAuth on your ThermalTrace deployment so Pro households can connect thermostats for indoor context on freeze and leak alerts.

Close-up of white Cat-5e Ethernet cables with RJ45 connectors
Probe JSON usually leaves the LAN over Ethernet or a nearby relay, not the public internet directly. Photo: DiscDepotDundee.co.uk. CC BY-SA 4.0

Pro households can connect a Nest or Ecobee thermostat so indoor temperature and setpoint appear next to attic, crawlspace, and shop probes on the dashboard, and freeze alerts can include that context. End users connect from Dashboard → Temperature; this page is for the site operator enabling OAuth on a self-hosted or production deployment.

When the connect button appears

The thermostat card is hidden until the deployment has the provider's client credentials in Worker secrets. After secrets are pushed, Pro managers see Connect for each configured provider.

Nest (Google Device Access)

Production (thermaltrace.dev) redirect URI: copy exactly into Google Cloud Console: 

https://thermaltrace.dev/api/integrations/nest/callback
  1. Create a project in the Device Access Console (one-time fee).
  2. Create a Google Cloud OAuth client (Web application) in the same GCP project linked to Device Access.
  3. Enable the Smart Device Management API in that GCP project (OAuth can succeed without this, but live readings will 403 until it is on).
  4. Add the redirect URI above (self-hosted: https://YOUR_SITE/api/integrations/nest/callback).
  5. Set Worker secrets: NEST_CLIENT_ID, NEST_CLIENT_SECRET, NEST_PROJECT_ID (the UUID at the top of your Device Access project, not the Google Cloud project number).
  6. Add keys to .env and push: pnpm secrets:push

Ecobee

Production redirect URI: 

https://thermaltrace.dev/api/integrations/ecobee/callback
  1. Register at the Ecobee developer portal.
  2. Create an app with the redirect URI above (self-hosted: https://YOUR_SITE/api/integrations/ecobee/callback).
  3. Set Worker secret: ECOBEE_CLIENT_ID (Ecobee does not use a client secret).
  4. Add to .env and pnpm secrets:push.

User experience

Each household stores its own refresh token after OAuth, there is no shared global thermostat token. Managers can disconnect from the dashboard; tokens are revoked in the database on disconnect.

See also: Integrations hub, ThermalTrace vs Nest, vs Ecobee.

FAQ

Which thermostats connect to ThermalTrace?
Nest (Google Device Access / SDM) when Worker secrets are set, and Ecobee when developer signup is open. Guide: thermaltrace.dev/about/thermostat-oauth.

Is Nest required for freeze alerts?
No. Freeze alerts use your probes. Nest/Ecobee add indoor house context on Overview when entitled (Pro).

What if Ecobee developer signup is closed?
Use Home Assistant → ingest → Indoor reference on Dashboard → Devices so house ambient still overlays your week chart.