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

313

in case you missed itā€¦ google just announced discontinuation of nest protect.

314

Sort of. The current generation is being discontinued, and a ā€œnext generationā€ is being made by First Alert, though it has far less features, and makes it even more ridiculously overpriced.

315

To tap into this. I am struggling to find a viable alternative. I have unifi cameras so can easily detect smoke alarms from via HA. I have 9 nest protected, Four of them hardwired.

And five of them (battery) are expiring this month.

Can anyone recommend solid alternatives that are interconnected?

I love that nest protects donā€™t beep when battery low. You get lots of notice in app etc. This is my main requirement (plus to be as solid / reliable as nest protect )

Thanks

316

There is, allegedly, a smoke detector coming for Ubiquitiā€™s new SuperLink:

Only the gateway is actually available at the moment, and personally, having been burnt by Ubiquiti twice on IoT related devicesā€¦ never again, especially when itā€™s insane to release the gateway with no actual sensors for it, only more ā€œpromisesā€.

317

This is driving me crazy.
I just LOVE the Nest protect despite itā€™s crazy price. After searching for days I was unable to find a reasonbly priced smoke sensors that:

  • are linked
  • are hardwired
  • has a pathlight
  • motion sensor
  • HA integration

Having this in just one single device that integrates with HA wasnā€™t that bad after all and if available I may actually consider buying more :slight_smile:

Any idea which device would come closest to matching these requirements?