SmartThings Community

[RELEASE] NST Manager v5.0

Ah ok. Next time I’ll go into nest manager and hit done to see what happens.
Is there a way I can get a notification when it goes down? Is this possible in core? It’s just a pain to having to keep checking it’s done what the routine has asked it to do…

there are notification settings in not manager you should look at. These can warn if unable to check with nest.

Tony has posted an update that is more conservative on sending command to nest.
Please ensure your nst manager, automations and device handers are up to date

1 Like

Can the nest manager change the display and farsight settings? This would really help me out. Thanks!

I’m not aware these are in their API.

If you find parameters you want in their published API (developers.nest.com), that is what we have available.

OK. Thanks!

Does anybody know the correct syntax for the ‘setNestEta’ command? I want to get the travel time when I leave work, from google API’s and use that for the 'setNestEta. However, I’m not sure exactly the formatting Nest requires.

the command is

setNestEta(tripId, begin, end)

and cancelNestEta (tripid)

Tripid is a string you make up

begin and end are string times, in iso 8601 format

begin must be > now, and end must be > begin (in time)

https://developers.nest.com/guides/api/away-guide

Thank you. I’m new to webcore and smartthings. Is there a quick way to format a webcore date to iso8601?

I expect in webcore you would use formatDateTime

https://wiki.webcore.co/Functions#formatDateTime

I expect the format string looks something like: “yyyy-MM-dd’T’HH:mm:ssZ” or “yyyy-MM-dd’T’HH:mm:ssXXX”

You might have luck asking some of this in the webcore forum

Thank you again for everything!

The documentation seems to suggest that the begin and end are just arrival window times and not the begin and end of the tip (which is what I would think). In other words, if you leave work at 5:00PM and are expected to get home 5:30PM,
I would think:
begin is 5:00PM
end is 5:30PM
but the documentation seems to suggest:
begin is 5:25PM
end is 5:35PM

Can you help enlighten me on this?

Thanks!

My reading of this is

  • if you are leaving at 5:00 and expect to be home at 5:30

you would set arrival window for 5:25 - 5:45 (and you would have done this around or before your 5:00 PM

Thanks again for your wonderful help.

1 Like

Did you ever get an answer to your query? I am having the same problem. It is very difficult to key on people if motionperson is never active.

I am having the same problem as Flyize. I have a Nest Doorbell and two Nest Cam IQ Outdoor. I am using the NST Manager with the real time solution on my Raspberry Pi. Everything is up to date and appears to be operating normally. The motionperson trigger for the cameras is periodically triggered, but is always inactive. It is never active. Even when the Nest App states that there is a person in the camera’s view, motionperson declares that it is inactive. What is going on?

does the nest doorbell finally work with smartthings and NST manager

I don’t recall what I was trying to do, but no. I did not find a solution.

I’m not sure how long it has been the case but it appears that for some time my schedule isn’t actually executing.

it also appears that the thermostat isn’t communicating the correct state inside the SmartThings Classic App.

I’m currently running v5.6.2 of the NST Manager.

My installation is via the classic Github method as installed it before the transition to the community beta installer.

I’m sure there is something going wrong but am not entirely sure what could be causing the disconnect any help is appreciated.

Honestly it’s hard to be 100% but Nest seems to be making a lot of adjustments on their side and it’s having a big effect on lots of us users.

1 Like