Don’t know why we should “lol” at you. You’ve discovered another way how Google forcing their costumers to migrate and that’s imporstant info…
Btw: For those who haven’t noticed it yet. Here we have pretty promissing solution :
Don’t know why we should “lol” at you. You’ve discovered another way how Google forcing their costumers to migrate and that’s imporstant info…
Btw: For those who haven’t noticed it yet. Here we have pretty promissing solution :
Unfortunately this doesn’t work with a Google account. Users like me, who bought the thermostat a short while ago and just got into HA, are still looking for a solution.
that was a sucker buy.
100%. I’d never buy something like that. There was someone here who started a thread promoting a ‘special’ after the end of the API had been announced as well. Hope no one fell for that crap.
Have you checked it? Yes it does work with Google account.
In his topic he explicitly says:
- 2FA accounts won’t work with this, as I’m basically automating a web-based flow for authentication (there’s no way at this point to provide 2FA to the integration, though I’m still looking into this)
- Google accounts won’t work with this, as they use a different authentication mechanism
Since I bought it about 1,5 months ago I was forced to use my Google account, which also uses 2FA. But I have to look into this. Thanks for letting me know!
the post you linked to is 26 days old. HE has since then updated his repo to reflect that it does in fact work with google Auth.
Ah I see. Great news.
They also mention “Device Access for Individuals” program in the same post, which is I believe perfect match for self deployed HA at home.
The Individuals program is explicitly available for smart home enthusiasts and is likely the long-term solution. Unfortunately they say it won’t be available until late 2020…
So how will that get developed for HA if the devs have to sign an NDA to even see the API?
it it possible to use the nest hub max camera as a camera device in hassio , I recently bought the hub max… Is that the same API that was used, is it the issue as in this blog thread?
Just copied the Nest part trom an older core.config_entries to my new HA instance and added a new Nest Protect to my Nest Account. The entity is created in HA, but the sensors do not have any data:
My Nest Account is converted to a Google Account and 2FA is not enabled.
Switching status from Home to Away in the Nest app is also visible in HA, so that is working. Newly added devices will not?
Worked With Nest
It looks like Google has killed off the mobile API referred to by robvanuden. I had been using this as well, leveraging gboudreau’s nest.class. The endpoint suddenly stopped working the other day, returning a very unwelcoming “406 - Not Acceptable” response.
Stay classy, Google.
On another note, I hear that the ecobee has a very robust (and accessible) API. Anyone interested in a slightly used Nest 3d gen?
Have you tried badnest?
Thanks, no I hadn’t considered it. It’s Python though and the rest of my app is PHP. It might be worth a try but then again there’s no telling when Google may kill of this API as well.
Are you using it?
No, just drawing it to your attention.
php? I thought this was the home assistant forum?
Would anyone know why I get nothing in my nest integrations?? Is this due to the Google factor?
I copied my nest data from my old entities file
Have you read the thread?
Yes.
I’ve tried to restore it from previous files but I guess I’m just one of the unlucky ones