Driver Setup — Step 8 of 11

Authorization Code

Paste your SDM Project ID and OAuth Client ID from the Google Cloud console, then click Authorize with Google. You will be redirected to Google to sign in and grant device access, then bounced back here with an authorization code to paste into Crestron Home.

Device Access Console → your project → Project ID (UUID).
Google Cloud Console → APIs & Services → Credentials → OAuth 2.0 Client IDs → your Web client.
We always request the pubsub scope in addition to sdm.service so you can enable real-time thermostat events later just by setting GCP Project ID in the driver. If you only ever want polling-only operation, the extra scope is harmless — it just sits unused.
The Web OAuth client in Google Cloud must list https://zenturahome.com/oauth/nest/callback.html as an authorized redirect URI.
No authorization code in this URL.

This page is opened automatically at the end of the device-access consent flow. If you arrived here directly, please return to the Crestron Home setup wizard and follow the "Authorize" link.

✅ Authorization code generated. Next you MUST:
  1. Click Copy below.
  2. Switch to the Crestron Home setup app.
  3. Paste into the driver’s Authorization Code field and tap Apply.
⚠ If you skip this step the driver will keep using your old refresh token (if any) and Pub/Sub real-time updates will not work. The code expires in 5 minutes.
—
Code expires in 5:00
⚠️ Did the consent screen show BOTH permissions? During sign-in Google should have asked you to grant "See and/or control the devices that you selected" AND "View and manage Pub/Sub topics and subscriptions". If you only saw the SDM permission, the pubsub scope is not registered on your OAuth Consent Screen — add it there and re-authorize, otherwise the driver will hit 403 insufficient scope on every Pub/Sub pull.
Driver Setup — Steps 9 & 10 of 11

Set up Pub/Sub for real-time updates (recommended)

For sub-second updates from your thermostats, register a Pub/Sub topic in the Device Access Console. The driver auto-creates the topic and subscription on first start — you only need your GCP Project ID and one click in the Device Access Console. If you skip this, the driver still works in polling-only mode.

Step 9 — Note your GCP Project ID

  1. Open the Cloud Console dashboard and copy your Project ID from the top banner (e.g. my-home-nest-123456). This is the same project you used for the OAuth consent screen — not the SDM Device Access Project ID.
  2. In Crestron Home you'll paste this into the driver's GCP Project ID field. On first start the driver will automatically create the topic nest-events and pull subscription nest-events-sub in your project — no Pub/Sub console clicks required.
  3. The topic name to register in step 10 is shown here for easy copy:
    Replace {your-gcp-project-id} with your Cloud Project ID.

Step 10 — Register the topic in the Device Access Console

  1. Return to console.nest.google.com/device-access and open your project.
  2. Set Enable Events to Enabled.
  3. Paste the topic name from step 9 into the Pub/Sub topic field.
  4. Click Add & Validate (or Save). Google's SDM publisher group (sdm-publisher@googlegroups.com) is granted publisher access on your topic automatically by the Device Access Console; the driver creates the topic first so this grant succeeds. No manual Pub/Sub IAM steps required.
  5. In Crestron Home, set the driver's GCP Project ID field to the value from step 9 and leave Pub/Sub Subscription Path blank. After ~30s, enable EnableDebugLog and confirm the periodic PubSub: heartbeat state=RUNNING line appears.
This page runs entirely in your browser. The authorization code is read from the URL bar and is never transmitted to Zentura Home or any third party. Need help? Visit support.