I have installed the plugin and followed the instructions for the Client ID, Client Secret, etc.  Paid the $5.00.  When I try to authenticate, I get API error.  Evidently, my topic has not been enabled, and I can't seen to do that, so perhaps the plugin does not have access to the api?  Attached is log and some screenshots.

Also tried to update version 1.05 but nothing happens.

NestSDM_3-10-2025_93938_PM.zip

There could be a number of errors here - it's a big log file with lots of restarts. Let's address the missing events subscription first. As mentioned in the installation instructions, the steps need to be performed exactly as described in the very specific order described or it just doesn't work. I think this is because the Device Access project for the NEST SDM API is not truly integrated into Google Cloud Console but is still a red-headed step child. Believe me, it took a lot of work to come up with a description of steps that worked on a repeatable basis.

What appears to have happened here is that you didn't enable "Events" during creation of the Device Access project. From step 7 (yes, 7) of the installation instructions found here:

Quote

Step 7 - Create a Device Access Project (Device Access Console)

Finally (really?!?) you create a Device Access project. This is done in a wizard in the Google Device Access console. You will need to the Client ID of the OAuth client created above in Step 5 for this step:

Access the Device Access Console here: Device Access Console. Click on the "Create project" tile.

Enter a project name of "Nest SDM Plugin" and click the "Next" button.

Enter the OAuth client ID copied from the Google Cloud Console in Step 5 above and click the "Next" button.

Select "Enable" for the Events and click the "Create project" button.

While the interface of the Device Access Console makes you think you can go back and enable  "Events" for your Device Access project after creation, in my experience it doesn't work when you do it this way. My suggestion is to delete your Device Access project from the Device Access Console, give it a day or so to actually get cleaned up, then create a new Device Access project in the Device Access console using the step 7 procedure above exactly as described. 

Then, after an hour or so, restart the plugin and generate a new log file.

Edited March 11Mar 11 by Goose66

OK, will try that.  When I first tried step 7, the enable button was greyed out and, as you mention, I was unable to enable it later.