I use protects, with the Nest Streaming service (part of nest mgr). It works well for me. few seconds delay (of course both ST cloud and Nest cloud and your internet need to be working).
Good news is protects do their job even when cloud is down.
1 Like
Hi, This question may have been asked before but does NST Manager handle the nest hello doorbell? Im looking for a smartthings and webCore way of identifying faces in the doorbell triggering an action. I have seen some people mention using android alternatives but wanted to try and keep it as contained as possible.
Thanks in advance
Yes but It picks it up as a camera rather than a doorbell as they haven’t updated their API yet.
Great thanks. As its a camera, is that able to report the facial recognition side of it, or is all of that awaiting the API update from them?
This is just after I got a notification and updated to 5.5.3 (looks like there was a Nest Cam DTH update as well). Is there any info on this?
Long shot… but any chance you guys could add an extra attribute on the vThermostat that shows the average of the remote temp sensors for the active schedule?
You are already calculating this value in code today (see screenshot below)
I know that the rounded whole number value is exposed in [vThermostat device:Temperature] but I really need the more precise value for graphing purposes.
My current work around is to create a separate virtual temp sensor in ST and use another app to average together the temps sensors but I have 2 thermostats with 5 schedules each that all use different alt. temp sensors combinations. My current workaround only simulates one of those combinations. To simulate all of them I would have to duplicate the schedule logic that already exists in NST mgr. Would be great if I could just pull the average value for the active schedule from the vThermostat device.
thx for considering… happy to hear any other ideas to achieve this as well.
NST manager overall is working great to integrate my Nest Protects into Smartthings.
I am currently trying to have webCore monitor whether the power has gone out in my home by using the nest protect (I have my hub and internet on a UPS).
I am not a programmer, but from looking at the groovy soure code (https://github.com/tonesto7/nest-manager/blob/master/devicetypes/tonesto7/nest-protect.src/nest-protect.groovy), it appears that I would want to be monitoring a specific protect for the value of “powerSource” for “mains” or “battery”
However, I can’t get webCore to work, and interestingly, in nest manager diagnostics device data both “powerSource” and “powerSourceNest” have value of null. Is this function not currently working, or am I somehow doing this wrong?
Thanks for any help or insight that anyone has.
Hello all, I’m fairly new at this but was able to install the nest manager. The issue I’m running into is creating a developer account to obtain a client ID. The nest developer website current shows this message “Thank you for your interest in the Works with Nest program. We’re upgrading our systems and will not accept new client reviews during this time. Please check back in a few weeks. If you have an urgent issue, please message us through the developer console.”
Can anyone please help me get started? Is there a client ID I can use?
Awesome app thanks so much for putting this together! Was working perfectly with my Android device. I’m now on Apple and bridging my SmartThings hub through a pi. All works well but I notice that when I change the temp in the Apple Home app (also using an app called Eve), nothing changes on the thermostat. The apps show the change but the nest doesn’t change. What am I doing wrong?
If the change shows up to nest, nst manager will get it.
If you use the stream module, it should be near instant. If you are not using it, you are going to wait for the next poll to occur.
Hi, I added wundergound PWS station, but it seems the temperature is rounded off with no decimal. How can I get the number behind decimal? For example, 98.3F instead of just 98F.
Thanks
There is a word document called Nest Developer - Nest Product.pdf (scroll up to Sept 24th) It walks you through each step and what is expected on each line.
That message got me as well. If you follow the steps, at the very end a client ID and client secret will be assigned to you. That’s strictly for you DO NOT SHARE IT. Enter that info in your IDE Nest Manager and make sure OA Auth is enabled. OA only on the NST Manager and not the NST Automations. Then re-run the nest manager and it will import all your devices. ( Also make sure you add the devices in your device handler before you run the APP ) Once everything gets pulled in come back here and try and make a donation. These guys work really hard on this stuff. It’s only right to donate for their time. IDK what I would do without this boards. I just redid my nest manager from scratch yesterday after it not working for months. With a little bit of reading and testing… I got everything installed and working. Even the Nest Doorbells work! These guys are great!! in case I didn’t say that enough. Good luck
Any word if the Nest x Yale lock will be supported? I want my lights to turn on when I unlock the door 
1 Like
I’d like my door to lock and the porch lights to come on when someone unknown approaches my door. I may put a speaker and a tts message, “Say cheese, you are on camera!”
(I think locking the door when unknown faces are detected by Nest doorbell is a neat feature).
Yesterday I started to see the following message on the NST Manager Status page on my phone:
“Your Manager State Usage is Greater than 80% full. This is not normal and you should notifiy the developer.”
The only option on the page is to go to the NST Diagnostic Web Page, which does not seem to provide any clues on how to fix this. How can I clear this error?
many times hitting “done” / “save” on your way out may clear some of this. If it continues to happen we may need to move to a private message to see your diagnostic page.
Are you running the latest release?
I got the error cleared by running the Run StateClean() and Run SendInstallData() functions on the diagnostics page, but I had to do it a few times before the State Usage on the diagnostics page went down to 37%
Not sure which of those functions actually solved the problem though.
Any idea what the cause might be, and how I can prevent it from happening again?
I wish I had an answer for you. The platform has been a fickle mistress lately and i’m seeing weirdness across the board
1 Like
Any insight as to whether NEST will actually allow better integration between it and SmartThings/Webcore etc.?
While the current system does provide all of the functionality I need and works well when it is stable, it is very complex for non-programmer types such as myself to maintain, and as you pointed out, tends to go flaky on occasion, making it the weak point in my entire automated system.
For the most part the nest side of the api is very stable.
The code of NM (and other device handlers) runs in SmartThings cloud, and when they have platform issues, life gets exciting.
1 Like