Request Sync triggers a SYNC
request to your fulfillment for any Google user
with devices that have the specified agentUserId
associated with them (which you sent in the original SYNC request). This allows
you to update users' devices without unlinking and relinking their account. All
users linked to this identifier will receive a SYNC
request.
You should trigger a SYNC
request:
- If the user adds a new device.
- If the user removes an existing device.
- If the user renames an existing device.
- If the user change a device location such as rooms (only if your application supports this).
- If you implement a new device type, trait, or add a new device feature.
Get started
To implement Request Sync, follow these steps:
Enable the Google HomeGraph API
-
In the Google Cloud Platform Console, go to the HomeGraph API page.
Go to the HomeGraph API page - Select the project that matches your smart home project ID.
- Click ENABLE.
Create a Service Account Key
Follow these instructions to generate a service account key from the GCP Console:
-
In the GCP Console, go to the Create service account key page.
Go to the Create Service Account Key page - From the Service account list, select New service account.
- In the Service account name field, enter a name.
- In the Service account ID field, enter a ID.
From the Role list, select Service Accounts > Service Account Token Creator.
For the Key type, select the JSON option.
- Click Create. A JSON file that contains your key downloads to your computer.
Call the API
Node.js
The Actions on Google library for Node.js supports Request Sync over HTTP.
- Place the downloaded service account JSON in your project directory.
- Pass the file location into your
smarthome
constructor. - Call the
requestSync
method with your payload. It returns a Promise.
const {smarthome} = require('actions-on-google'); const app = smarthome({ jwt: mySecretKeyJson }); // ... // New device is added for user app.requestSync('user-123') .then((res) => { // Request sync was successful }) .catch((res) => { // Request sync failed });
Java
The Actions on Google library for Java supports Request Sync over gRPC.
- Place the downloaded service account JSON in your project directory.
- Read the file location to generate a
GoogleCredentials
object. - Call the
requestSync
method with your payload. It returns a server response.
private void onDeviceAdded() throws IOException { FileInputStream stream = new FileInputStream("service-account-key.json"); GoogleCredentials credentials = GoogleCredentials.fromStream(stream); mySmartHomeApp.setCredentials(credentials); RequestSyncDevicesResponse response = mySmartHomeApp.requestSync("user-123"); }
HTTP POST
- Use the downloaded service account JSON file to create a JSON Web Token (JWT). For more information, see Authenticating Using a Service Account.
- Construct a JWT payload to request an access token with the
https://www.googleapis.com/auth/homegraph
OAuth scope: - Sign the JWT payload with the private key from your service account.
- Use the JWT to request an access token from
https://accounts.google.com/o/oauth2/token
. - Create the JSON request with the
agentUserId
. Here's a sample JSON request for Request Sync: - Combine the Request Sync JSON and the token in your HTTP POST
request to the Google Home Graph endpoint. Here's an example of how
to make the request in the command line using
curl
, as a test:
{ "iss": "<service-account-email>", "scope": "https://www.googleapis.com/auth/homegraph", "aud": "https://accounts.google.com/o/oauth2/token", "iat": <current-time>, "exp": <current-time-plus-one-hour> }
{ "agentUserId": "user-123" }
curl -X POST -H "Authorization: Bearer ACCESS_TOKEN" \ -H "Content-Type: application/json" \ -d @request-body.json \ "https://homegraph.googleapis.com/v1/devices:requestSync"
Error responses
See these possible responses to understand what you may receive back from Google upon making a Request Sync request.