I just pre-ordered 3 for my home and hope there will be a plug-in to tie them into Vera similar to Nest.
Anyone else get this linky?
[quote=“chuck1026, post:1, topic:177263”]I just pre-ordered 3 for my home and hope there will be a plug-in to tie them into Vera similar to Nest.
Anyone else get this linky?
I plan on getting one and extending the Nest plugin to support it. I would assume that the upcoming official API will support it, but I hope to integrate it into the plugin (creating new sensor and security child devices) one way or another!
watou
same here
ordered hardwired model
if i understand correctly it will comunicate directly with nest tstat as well as the web component
so we should only need an updated nest app for mcv that can read that data from the tstat
the additional heat/humidity/motion/light sensors as well as of course smoke/co would be great
as these things will double as all in one multi sensors
excelent
you just “hopefully” confirmed what i was hoping for
we of course wont know for sure until we receive the hardware
but good to know i was thinking in the right direction
[quote=“charettepa, post:4, topic:177263”]@watou
excelent
you just “hopefully” confirmed what i was hoping for
we of course wont know for sure until we receive the hardware
but good to know i was thinking in the right direction[/quote]
Good! I am proceeding with the uncertain assumption that it uses the same web services infrastructure as the thermostat, which ought to mean that it will present sensor information in a similar way so I can just add new device types. There is another thread about trying to standardise how Vera sees various kinds of sensor input (like barometric pressure, air quality, etc.) and that work would likely apply to extending the Nest plugin.
The Nest Protect seems like a very well thought-out gadget and I’m looking forward to getting one! It will even shut down your gas furnace through your Nest thermostat if the Protect senses carbon monoxide. Very clever, and might even save lives.
watou
So very happy to hear this
if you should start a new thread or post about this elsewhere
could you please link from here
as i will be monitoring this thread
[quote=“watou, post:5, topic:177263”][quote=“charettepa, post:4, topic:177263”]@watou
excelent
you just “hopefully” confirmed what i was hoping for
we of course wont know for sure until we receive the hardware
but good to know i was thinking in the right direction[/quote]
Good! I am proceeding with the uncertain assumption that it uses the same web services infrastructure as the thermostat, which ought to mean that it will present sensor information in a similar way so I can just add new device types. There is another thread about trying to standardise how Vera sees various kinds of sensor input (like barometric pressure, air quality, etc.) and that work would likely apply to extending the Nest plugin.
The Nest Protect seems like a very well thought-out gadget and I’m looking forward to getting one! It will even shut down your gas furnace through your Nest thermostat if the Protect senses carbon monoxide. Very clever, and might even save lives.
watou[/quote]
AWESOME!!! I hope this works out. My existing detectors are beyond dusty old so Nest Protect is a long overdue upgrade.
Hey watou!!! I bet you are signed up but just in case… go to this linky Nest Developers
If you look at the other discussion about the developer sign up, you would have seen that he is signed up. 
- Garrett
what discussion?
can you give us a link to that thread
if you do that, please make sure it works for those of us who don’t have the Nest thermostat 
[quote=“garrettwp, post:9, topic:177263”]If you look at the other discussion about the developer sign up, you would have seen that he is signed up.
- Garrett[/quote]
Wow, missed that one! I did figure watou was on top of it. Regardless this is great news
[quote=“watou, post:5, topic:177263”][quote=“charettepa, post:4, topic:177263”]@watou
excelent
you just “hopefully” confirmed what i was hoping for
we of course wont know for sure until we receive the hardware
but good to know i was thinking in the right direction[/quote]
Good! I am proceeding with the uncertain assumption that it uses the same web services infrastructure as the thermostat, which ought to mean that it will present sensor information in a similar way so I can just add new device types. There is another thread about trying to standardise how Vera sees various kinds of sensor input (like barometric pressure, air quality, etc.) and that work would likely apply to extending the Nest plugin.
The Nest Protect seems like a very well thought-out gadget and I’m looking forward to getting one! It will even shut down your gas furnace through your Nest thermostat if the Protect senses carbon monoxide. Very clever, and might even save lives.
watou[/quote]
Got a home depot gift card for the holidays and just picked up a Nest Protect. Pretty nifty so far, but definitely needs vera integration. If the motion sensor is exposed through the API, that would be awesome. I volunteer to test if the opportunity comes up
wink wink
Got my Nest Protect today. It’s very elegant in its design, and well thought out similar to the Nest Thermostat.
One thing that I find odd is that it will not connect to a wifi network if the SSID is hidden. This appears to be by design as the setup instructions include this as a caveat. Hopefully they change this in a future update.
I’m happy with it so far, and looking forward to testing out future Vera integration.
I plan on getting one and extending the Nest plugin to support it. I would assume that the upcoming official API will support it, but I hope to integrate it into the plugin (creating new sensor and security child devices) one way or another!watou
Firstly, excellent job on the Nest plugin as it is - use it every day. Not sure if you have thought any more about Protect but happy to help test it whenever you are ready. I have them installed and ready to go. And really hoping the motion detector is exposed via the API so it can be used to trigger other stuff.
Let me know if I can help in any way.
API access hasn’t been opened yet sadly.
I’m considering these. Any updates on the API release? Could it have been stalled due to the sale to Google?
I have one installed and I like it very much. It gives good feedback that it’s doing its job and it looks good, too.
I’ve not heard any update on the API. I supposed it’s possible that the API release was stalled due to the Google acquisition, but I have nothing to base that conjecture on. I think if we continue much longer without the public API, I will dig into the JSON payload and try to create/maintain new device type(s) based on the data there for the Protect. It would of course be much better to have a documented API rather than guesswork.
watou
Do you know if there’s a limit on how often the Nest servers can be queried? Polling the server every couple minutes is a reasonable workaround for a thermostat, but when it comes to smoke detectors, the sooner you can react, the better.