Did you put it in one line? Because if the line breaks are in it won’t work.
1 Like
Hi,
I’ve tried both, but with two different error messages 
Nice neat approach, thanks! It works well for me too.
Cheers
Mark
They discontinued one cloud-based API and a year later replaced it with another cloud-based API. I recall there was talk of a local API but I guess that either didn’t make it into the initial release or was just … talk.
1 Like
Try this:
curl -X POST 'https://www.googleapis.com/oauth2/v4/token?client_id=XXXXCX&client_secret=XXXXXX&code=XXXXXXX&grant_type=authorization_code&redirect_uri=https://www.google.com' -d "{}"
Just saw that the Google Nest API for developers is opened now. I’m not by any means a developer but thought the Home Assistant developers might want to know. Here’s a link to the info:
4 Likes
This command returns the following response:
curl: (3) Failed to convert ‘https to ACE; string contains a disallowed character
Maybe you can do the authorization part again, I’ve had trouble the first time as well, but after getting a new authorization code it did work.
1 Like
after 3 rounds on the authorization part, it is now working 
Thank you all for great help!
1 Like
Try again - somehow I did not save it as a text block and a “2” ended up at the end of the curl command.
FFPlay (ffmpeg player) will play RTSPS streams. I tested it out with my Nest doorbell camera. The new device access console access/api is not too dissimilar to the previous one, so it shouldn’t take too much refactoring to get the nest integration up and running.
Has anyone managed to get the “Home/Away” status of the structure at all? I’ve not been able to find this in the documentation of the various APIs
Cheers
Mark
1 Like
If the token is stored in the secrets file. Can we create an automation that automatically generates the new token every hour ?
yep. doesnt make you broke right?
Is there already someone who’s creating a custom integration for HA?
i hope so, or maybe they will update the official one
11 Likes