I don’t know anything about this stuff, so I can’t use my experience to “translate” it to what I’m actually seeing. That experience is non-existent. I don’t know how to get to whatever screen the documentation is trying to get me to.
Maybe someone can add some screenshots in the documentation, making it easier to validate what people are looking at.
Not sure exactly what you are looking at but you are clearly in the wrong place. Use the hamburger menu at the top left, select APIs & Services, then Oauth consent screen.
So there is a new official Google Drive backup integration. I’ve used a third-party add-on for some time now which never required creating your own API credentials, so much easier to setup.
Use the hamburger menu at the top left, select APIs & Services, then Oauth consent screen.
Thats what I did.
So there is a new official Google Drive backup integration. I’ve used a third-party add-on for some time now which never required creating your own API credentials, so much easier to setup.
I’m using Google > Google Drive from the Add Integration button. I’m assuming that’s the official one that’s been added since a few days ago in the latest Core update.
That instructions link is the documentation I’m trying to use. The instructions listed right there are way too brief, might as well not be there. But this is the integration. What else should I be using?
Press the “Get started” button and follow the setup flow?
I’ve been working on an automation using the Google APIs for some time and Google has been threatening a revamp of the Oauth consent settings for some time now. If I press the button to actively choose their “new experience” it seems I do get the same sidebar you have on your screen, but if I choose the same option from the menu again I end up back in the old UI.
Whomever wrote the HASS documentation probably did so for Google’s previous UI while new users may be forced into the new UI only?
If I click the get started button, I get asked a question that I don’t know the answer to, and the instructions don’t say what to select. Probably because they’re written for an older UI that doesn’t have that option:
I don’t know what the impact of this choice is. I don’t even have an organisation, so I don’t understand what an “internal” user is. But I also don’t want just any rando on the internet able to guess the url to this app-thing, to access it
Not sure why you are even asked this question, as Internal should only be possible with Workspace accounts, not personal Google accounts. The instructions do say that you should select External at some point but the instructions may not be in quite the correct order.
I also struggled with this writing the instructions for my blueprint. Eventually I figured out it was moot anyway, as it would never work quite like I wanted it to. One problem with credentials for projects set to testing is that they expire in a week. I wonder if the HASS devs have gotten around that.
This has been shown on the Oauth consent screen settings for at least a month by now (and probably much much longer). I suppose it is good if it does become easier to use, but that it will eventually make all previously written (and often painstakingly elaborate) instructions outdated is not so good…
Got the new official Google Drive backup integration up and running. Think I was able to follow the instructions as written, though I’ve gone through creating these kinds of developer credentials before so can’t really be sure I didn’t subconsciously fill in any missing information.
Yeah I got it as well in the mean time. Thanks for the help. It’s a real shame Google has a nack for making things confusing. They’re not really employing the “don’t make me think” principle anymore these days.
Anyway, I verified that the backup feature can use it, and presto. Works like a charm
You cannot use any existing API credentials, unless they were already setup with https://my.home-assistant.io/redirect/oauth as one of the Authorized redirect URIs in the Google Developer Console. Which is exactly what the error message says yours are not.
Select the correct project from the button bar at the top. Click the name of your current project to get the project selector.
Creating a new project can take anywhere from just seconds to slightly longer, and for some dumb reason the UI does not simply delay until the project is created and then switch automatically, you have to switch projects manually. (Unless you are creating your very first project, in which case the UI will wait and then enter the project automatically).
top left hamburger menu > APIs & Services > Credentials > OAuth 2.0 Client IDs > whatever you’ve named your credentials > Authorized redirect URIs > ADD URI
