NST is not offering an api to guard sensors that I'm aware of. That is what would be needed to integrate with hubitat
Thank you.
2 Likes
We have posted an update to the weather driver to use asynchttp
2 Likes
First off, thank you for this app and drivers. I've been using it for a few months, and I greatly appreciate it!
Today, around 12:22p CT I started getting messages in the logs that I've never seen before. Is anyone else getting anything similar? Since this started, I can no longer control any of my Nest devices via Hubitat. (edit: I'm aware that Google is threatening pulling support on August 1, I'm just curious if others are impacted today, 5 weeks early)
Here is a sample. I haven't changed anything in my configuration, Nest userID, password, etc. My account is up to date and I am able to log into, and operate, devices via the Nest app.
app:1952019-06-23 02:35:29.493 pm [info](http://192.168.0.169/installedI can log into, and operate, devices via the Nest appapp/configure/195) schedNextWorkQ COMMAND RUNNING │ queue: 0 │ schedTime: 3 │ recentSendCmd: 2 │ last seconds: 7752 │ cmdDelay: 3 | runInActive: false | command proc: true | Api Limited: null
app:1952019-06-23 02:35:29.279 pm tracePolling BLOCKED | Reason: (Sending Cmd)
app:1952019-06-23 02:33:57.316 pm info schedNextWorkQ COMMAND RUNNING │ queue: 0 │ schedTime: 3 │ recentSendCmd: 2 │ last seconds: 7660 │ cmdDelay: 3 | runInActive: false | command proc: true | Api Limited: null
app:1952019-06-23 02:33:57.135 pm tracePolling BLOCKED | Reason: (Sending Cmd)
app:1952019-06-23 02:33:55.671 pm info schedNextWorkQ COMMAND RUNNING │ queue: 0 │ schedTime: 3 │ recentSendCmd: 2 │ last seconds: 7658 │ cmdDelay: 3 | runInActive: false | command proc: true | Api Limited: null
app:1952019-06-23 02:33:55.437 pm tracePolling BLOCKED | Reason: (Sending Cmd)
app:1952019-06-23 02:33:47.794 pm info schedNextWorkQ COMMAND RUNNING │ queue: 0 │ schedTime: 3 │ recentSendCmd: 2 │ last seconds: 7650 │ cmdDelay: 3 | runInActive: false | command proc: true | Api Limited: null
app:1952019-06-23 02:33:47.604 pm tracePolling BLOCKED | Reason: (Sending Cmd)
app:1952019-06-23 02:33:09.315 pm info schedNextWorkQ COMMAND RUNNING │ queue: 0 │ schedTime: 3 │ recentSendCmd: 2 │ last seconds: 7612 │ cmdDelay: 3 | runInActive: false | command proc: true | Api Limited: null
app:1952019-06-23 02:33:09.110 pm tracePolling BLOCKED | Reason: (Sending Cmd)
app:1952019-06-23 02:33:06.740 pm info schedNextWorkQ COMMAND RUNNING │ queue: 0 │ schedTime: 3 │ recentSendCmd: 2 │ last seconds: 7609 │ cmdDelay: 3 | runInActive: false | command proc: true | Api Limited: null
app:1952019-06-23 02:33:06.546 pm tracePolling BLOCKED | Reason: (Sending Cmd)
app:1952019-06-23 02:32:50.500 pm info schedNextWorkQ COMMAND RUNNING │ queue: 0 │ schedTime: 3 │ recentSendCmd: 2 │ last seconds: 7593 │ cmdDelay: 3 | runInActive: false | command proc: true | Api Limited: null
app:1952019-06-23 02:32:50.321 pm tracePolling BLOCKED | Reason: (Sending Cmd)
app:1952019-06-23 02:32:48.059 pm info schedNextWorkQ COMMAND RUNNING │ queue: 0 │ schedTime: 3 │ recentSendCmd: 2 │ last seconds: 7590 │ cmdDelay: 3 | runInActive: false | command proc: true | Api Limited: null
app:1952019-06-23 02:32:47.872 pm tracePolling BLOCKED | Reason: (Sending Cmd)
app:1952019-06-23 02:32:03.104 pm info schedNextWorkQ COMMAND RUNNING │ queue: 0 │ schedTime: 3 │ recentSendCmd: 2 │ last seconds: 7546 │ cmdDelay: 3 | runInActive: false | command proc: true | Api Limited: null
app:1952019-06-23 02:32:02.887 pm tracePolling BLOCKED | Reason: (Sending Cmd)
app:1952019-06-23 02:31:41.486 pm info schedNextWorkQ COMMAND RUNNING │ queue: 0 │ schedTime: 3 │ recentSendCmd: 2 │ last seconds: 7524 │ cmdDelay: 3 | runInActive: false | command proc: true | Api Limited: null
app:1952019-06-23 02:31:41.360 pm tracePolling BLOCKED | Reason: (Sending Cmd)
Thanks!
Probably just an outage
1 Like
trying going into the nst manager app, and hit done, and see if the logs clear up.
1 Like
It looks like it stopped on it’s own around 4:22p CT. I’m not looking forward to Aug. 1. 
I also just went into the app and hit Done as you suggested just to be safe. Thank you!
@tonesto7 Apologies if this has been asked before:
I have this integration working in ST at the moment - as we all know, there is no way to sign up to the works with nest program anymore.. but is there a way that I can move over the authentication from the ST app to this Hubitat app?
Keep all your information from Smartthings and use that same information for Hubitat. I moved this from Smartthings to Hubitat and I don't remember it being super hard but I remember it not going flawlessly. I wish I could remember the details but it was too long ago. I don't remember the troubleshooting being difficult though.
NST Manager, NST Automations and device handlers have been updated.
See post 1 in this thread for details.
2 Likes
I am getting the following error in the thermostat driver after updating:
Here are my current states:
And here are my State Variables:
I've updated each of the apps.
Any ideas?
Scott
I also updated all NST Manager and I too and experiencing extra chatty log messages from NST Manager devices and apps now.
these should turn off after 30 mins automatically , or can be turned off in the event stream device
HE console -> Devices -> Nest event stream -> Under preferences turn off "enable debug logging" then hit "save preferences"
They should turn off automatically in 30 mins.
Thank you! I'll try going into preferences to try to turn off debug logging.
Note: I updated over 24 hours ago, and the screenshot above was just 2 hours ago. My log file is completely full of messages like that.
I would also suggest go into NST manager and hit done
HE console -> Apps -> NST Manager and hit done
The oddest thing is happening. I did exactly this and turned off 'enable debug logging'. I saved preferences. After 5 minutes or so, I noticed my log did not settle down so I opened the Nest Event Stream device again and "enable debug logging" was back on somehow? I turned it off again... saved preferences again... and 5 minutes later it turned itself back on. I don't get how that is happening?
Regardless, I'll try your other suggestion of hitting done in the NST Manager app. I had done that before I left my message earlier, but I am happy to try whatever you suggest so I will do this again now. Thank you, again!
I tried this 15 minutes ago and my log file is still repeatedly filling with NST info per the screenshot above.
Also, Nest event stream keeps turning 'enable debug logging' back on, no matter how many times I turn it off and hit save preferences, or save device. After 2-3 minutes it turns back on. Do you have any other suggestions for me to try, please?
If you look in the Event stream (or NST manager) after hitting done
you should see: (which will turn off logging)
I'm not seeing that in NST Manager - here's what I am seeing (and I promise I have hit done in NST Manager app page - several times 
)
Here's Nest Event Stream, which has the 'logsOff'
The logs are still filling at the same rate - it's as if that "logsOff" job is being ignored maybe? Please compare the timestamp between when the logsOff job was scheduled in Nest Event Stream with this screenshot below of my logs just now.
EDIT: If you notice in the log files above, it keeps saying "Forced Null sent Event #1 /1"
Just a moment ago, the log said "Forced Null sent Event #1 /2" and then "Sent Event Data Event #2 / 2" which wasn't happening in the earlier logs. After this, things have quieted down a bit.
My logs only go back as far as 2 hours due to all of the NST related logs right now, but it looks like there's maybe a pattern here:
- NST Manager wakes up and restarts the stream
- It does a "Sent Event Data Event #1 / 1"
- Then it does a "Forced Null sent Event #1 / 1" and it seems to loop between these two events with 1 /1.
- After sometime - sometimes 30 minutes, sometimes less, or more, it will finally say "Sent Event Data 2 / 2" and then the logs will settle down for 10 minutes until the next poll where things start to fill the log in a loop again.
(Example: Starts at 8:22p CT)
(Example: Log file fills up with repeated NST information in a loop for 17 minutes until 8:39p CT when it finally says "Sent Event Data Event #2 / 2". Then it goes quiet for 10 minutes)
