Skip to content
Port OS

Control Google Nest thermostats and cameras with AI

Connect supported Nest thermostats, cameras and doorbells to Port OS through Google Device Access. Read temperatures and use supported thermostat or live-view controls.

Ask your AI for the temperature, change a supported Nest thermostat's target or open an available camera live view. Port OS connects through Google's Smart Device Management service using your own Device Access project.

Read the Google Nest setup guide · Choose an AI assistant

What you can do

  • Read current temperature and available thermostat information.
  • Set the target temperature and supported thermostat mode.
  • Open live views for supported cameras and doorbells.
  • Read available temperature and humidity information from supported displays.

Start with “What is the hallway temperature?” or “Set the downstairs thermostat to 21 degrees Celsius.” Use the controls reported by the connected device.

What you need

This connection needs a personal Google account with a supported Nest home, a Google Cloud OAuth client and a Device Access project linked to that client. A Google Workspace account cannot register for Device Access. Google's registration and account requirements apply.

The setup guide walks through creating the client, configuring the redirect URI and entering the Device Access project ID in Port OS. Use the account and project for the home you want to access.

This is the Nest integration. It does not import every device connected to Google Home or provide Google's separate Home MCP service.

Connect your Nest home

  1. Follow the Google Nest guide to prepare the OAuth client and Device Access project.
  2. Choose Google Nest, save the requested setup values and approve access through Google.
  3. Check Your Devices, then connect your AI with the intended permissions.

Camera and event limits

A connection made with your own Device Access project supports available camera live views. Port OS does not subscribe to Google's event feed on this connection. Motion, person and doorbell notifications, event-image snapshots and event-triggered subscriptions are therefore unavailable through it. No Pub/Sub setup is needed for this connection.

If authorization fails, compare the redirect URI with the one Port OS displays and check that the Device Access project is linked to the correct OAuth client. Changing the client or Device Access project requires connecting again. The guide includes recovery steps.

To control the thermostat from your own code, read the Google Nest API guide.

Review the privacy policy before sharing camera access. For other device platforms, explore all integrations or compare smart home MCP services.