Support for Nest Protect

Feature Requests
304

Hi :slight_smile:

I’m struggling with the creds part of this.

my issue token looks the same as the screenshots:
URL Starts with:
‘https://accounts.google.com/o/oauth2/’
URL Ends with:
‘&include_granted_scopes=true&auto=0’

1st question, do I remove ‘&auto=0’ at the end of the URL to match the instructions?

Also, the cookie.
Starts with:
NID=511=sx
Ends with:
OtdWYqc4g

2nd question, I see the instructions start the cookie with ‘_Secure’. I have 2 mentions of the the phrase secure in the cookie text.

I’ve tried numerous alterations of the issueToken and oauth2/iframe and I cannot get it to work.

Running v0.4.0b4 but have tried the others.

Thanks All

305

that workaround seems to be fundamentally broken now - for me at least

306

Anyone that got this to work recently?

307

No. I authenticated using the latest method 2 times, but now I can not re-authenticate using same method anymore

308

The cookie method still works every time for me (I’m running the latest beta 0.4.0b7)

Unfortunately though, every restart/reboot causes it to need a new RequestURL and cookie so I’m now having to do it A LOT.

Others @dazzyp @KablammoNick have reported something similar above. Has anyone been able to find a way to make the authentication persistent despite reboots?

309

Interesting, I’m on 0.4.0b7 and not had any issues with authentication lately.

310

That’s good. Did you do anything particular that you can recall to overcome the lack of persistence at reboot/restart? I have to re-authenticate using the cookie method every time, (but fortunately the cookie method is reliable for me).

311

Not that I’m aware of :rofl:

Have certainly restarted plenty of times too.

312

No need, in my experience

Yes, the cookie does mention _Secure twice. Copy the whole thing.

My experience is with running beta 0.4.0b7