cancel
Showing results for 
Search instead for 
Did you mean: 

The Report State Dashboard has been deprecated but still needed for an Agent-id ?

debugging
Community Member

Attempting to add report state, bumped into the following 

debugging_0-1755955981708.png

Refer to this page:

https://cloud.google.com/endpoints/docs/openapi/service-account-authentication?authuser=0

isn't this confusing, first it states the dashboard is deprecated , though to use report state the agent ID is required which can only be retrieved using the dashboard ?

 

 

1 Recommended Answer

arm_dpe
Solutions Expert
Solutions Expert

That is correct, Report State dashboard was deprecated some time ago. To check the current state of your device, you can now use Home Graph Viewer tool.
As for the agentUserId , this is the unique user ID from your own system that is passed to Google during the OAuth account linking process. It's an opaque string to Google, meaning Google doesn't know its internal meaning, but it uses it to associate a user's devices with your service. This ID is essential for calls like Report State and Request Sync. Since the agentUserId originates from your system, you are responsible for retrieving and storing it.

To get the agentUserId, you need to:

  1. Implement OAuth account linking in your service.

  2. When a user links their account, your OAuth server will receive a request from Google that includes a unique ID for the user from your system. This is the agentUserId.

  3. You must then store this agentUserId so you can use it for subsequent Report State and Request Sync calls.

View Recommended Answer in original post

1 REPLY 1

arm_dpe
Solutions Expert
Solutions Expert

That is correct, Report State dashboard was deprecated some time ago. To check the current state of your device, you can now use Home Graph Viewer tool.
As for the agentUserId , this is the unique user ID from your own system that is passed to Google during the OAuth account linking process. It's an opaque string to Google, meaning Google doesn't know its internal meaning, but it uses it to associate a user's devices with your service. This ID is essential for calls like Report State and Request Sync. Since the agentUserId originates from your system, you are responsible for retrieving and storing it.

To get the agentUserId, you need to:

  1. Implement OAuth account linking in your service.

  2. When a user links their account, your OAuth server will receive a request from Google that includes a unique ID for the user from your system. This is the agentUserId.

  3. You must then store this agentUserId so you can use it for subsequent Report State and Request Sync calls.