Brandawg93 / homebridge-nest-cam_old

Use your Nest Cam as IP camera in HomeKit.
Apache License 2.0
89 stars 14 forks source link

Google account token #71

Open nvdokh opened 5 years ago

nvdokh commented 5 years ago

I migrated my Nest account over to Google. Now I cannot use the script to get a token. Is there something I am missing?

muzzymate commented 5 years ago

Can you get a token by logging into https://home.nest.com on a desktop browser, and then going to the URL https://home.nest.com/session ? In the text output, I see an "access_token":"b.............." value and put that in my config.json file. But I haven't migrated to a Google Account yet.

PaRkThEcAr commented 5 years ago

@muzzymate, so i had the same issue. when i tried your method, it worked for about an hour before the token expired. and the plug in directions to pull a token from nest does not work with Google accounts.

so we are on the right track, but it seems to not be working at the moment. however, i have to wonder, is this a dead project? not a lot of activity here.

xtianpaiva commented 5 years ago

same here, migrated to a google account and now my token (extracted from home.nest.com/session) expires very shortly, hope we can find a fix soon.

muzzymate commented 5 years ago

Guess I'm glad I didn't migrate it then for both this Nest-Cam and the -Nest Homebridge plugins. .

PaRkThEcAr commented 5 years ago

Well, Homebridge-nest works with the new works with google assistant API migration. Nest-cam however doesnt. I just wonder when this will get updated or better yet, get merged with Homebridge-nest to take advantage of the new API and use less plugins :?

On Sep 17, 2019, at 1:38 PM, muzzymate <notifications@github.com mailto:notifications@github.com> wrote:

Guess I'm glad I didn't migrate it then for both this Nest-Cam and the -Nest Homebridge plugins. .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/KhaosT/homebridge-nest-cam/issues/71?email_source=notifications&email_token=AJJYF4BEV6YWVQTVP57HXGLQKEW3LA5CNFSM4IPEZ2OKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD65VHAI#issuecomment-532370305, or mute the thread https://github.com/notifications/unsubscribe-auth/AJJYF4BKGSW32PDSK4NUJTTQKEW3LANCNFSM4IPEZ2OA.

PaRkThEcAr commented 4 years ago

No I havent! Run me through that. Do you know if that works?

Sent from my iPhone

On Nov 14, 2019, at 8:34 PM, Beni Katznelson notifications@github.com wrote:  @muzzymate have you tried creating an app password in google and using that to login?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

PaRkThEcAr commented 4 years ago

 No I havent! Run me through that. Do you know if that works?

Sent from my iPhone

On Nov 14, 2019, at 8:34 PM, Beni Katznelson notifications@github.com wrote:  @muzzymate have you tried creating an app password in google and using that to login?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

bktz commented 4 years ago

 No I havent! Run me through that. Do you know if that works? Sent from my iPhone

On Nov 14, 2019, at 8:34 PM, Beni Katznelson @.***> wrote:  @muzzymate have you tried creating an app password in google and using that to login? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

So I deleted my comment because I realized afterwards that it wouldn't solve the problem. If you generate an app password for google it will just replace using a username and password to login. But the result of that is a token that will expire and that will need to be refreshed.

I think the only solution to the problem is to add code that will refresh your authentication token.

Brandawg93 commented 4 years ago

I am continuing this project here. Google authentication has been resolved.