Got an issue whereby i have just installed a new thermostat and its not showing up in NST manager even though i have not changed anything on the developer site since installing my first thermostat . Is there something i need to do to activate new devices in NST manager?
If you go to Manage/View Devices in NST Manager, and click on Tap to modify devices and then click on the Nest thermostats section, does it show there. If yes, select it to add it to ST.
I have the same issue, when I refresh NST Manager screen, following error is displayed:
java.lang.NullPointerException: Cannot invoke method poll() on null object @line 137 (poll)
Any idea? Nest Thermostat, Presence device and Nest Weather are working properly.
1 Like
Anyone able to fix following error when refreshing NST Manager screen in app?
IDE: java.lang.NullPointerException: Cannot invoke method poll() on null object @line 137 (poll)
Hi,
Thanks for this app it’s great.
Does anyone know if the NST manager can also control the hot water schedule? I can’t seem to find any settings pertaining to this.
Kind regards,
Sunny
I don’t think nest has an API for this. If you see there is one let us know
Would it be easy to change wind* to be an integer, with a separate value for MPH/KPH?
My use case is that I’d like a certain webcore piston to only fire if wind < X.
Hi, is anyone using additional thermostat with nest? Is it available for you in NST Manager?
Thanks, Jan
looks like nest have stopped allowing developer access? or am i doing soemthing wrong to get this setup
Click on sign-in and login with your nest account, then simply click on create new Oauth client at the bottom of the screen.
1 Like
Yes, I have two nest thermostats and they both show in NST Manager and the ST app once selected in the manage/view devices section.
1 Like
I seem to have done something wrong here… Thought I followed every step, but I’m the end I can only see the nest presence sensor and nest weather in smartthings. No control of the thermostat at all.
check the IDE “Live logging”
Ensure you copied you id/secret in correctly (no extra spaces)
ensure you use the primary nest account login
I don’t really understand any of what I see in live logging…
The client and secret appear to be correct…
I only have 1 nest account…
[ 3fa05894-bb1b-4f19-914c-2124ae73bfd8 12:46:57 PM: info ||| NST Manager (v5.6.0) | Updating Structure Data (Last Updated: 180 seconds ago) | Updating Device Data (Last Updated: 180 seconds ago) | Updating Meta Data(Last Updated: 14400 seconds ago) (async)
3fa05894-bb1b-4f19-914c-2124ae73bfd8 12:44:02 PM: info ||| NST Manager (v5.6.0) | sendFirebaseData({“guid”:“9e06fa8a-5156-4aec-be51-135edf678cec”,“beta”:false,“versions”:{“apps”:{“manager”:“5.6.0”,“automation”:“Not Installed”,“service”:“Not Installed”},“devices”:{“thermostat”:“Not Installed”,“vthermostat”:“Not Installed”,“protect”:“Not Installed”,“camera”:“Not Installed”,“presence”:“5.4.4”,“weather”:“5.5.1”}},“thermostats”:0,“protects”:0,“vthermostats”:0,“cameras”:0,“appErrorCnt”:0,“devErrorCnt”:0,“installDt”:“Tue Mar 12 18:02:06 EDT 2019”,“updatedDt”:“Tue Mar 12 18:02:35 EDT 2019”,“automations”:{“disabled”:0,“nestMode”:0,“remDiag”:0,“schMot”:{“conWat”:0,“extTmp”:0,“fanCirc”:0,“fanCtrl”:0,“humCtrl”:0,“leakWat”:0,“remSen”:0,“tSched”:0},“storage”:0,“watchDog”:0},“timeZone”:“America/Toronto”,“apiCmdCnt”:0,“apiStrReqCnt”:2777,“apiDevReqCnt”:2777,“apiMetaReqCnt”:36,“appNotifSentCnt”:1,“apiRestStrEvtCnt”:0,“appUseMetCnt”:{“appNotifPrefLoadCnt”:0,“authLoadCnt”:1,“autoGlobPrefLoadCnt”:0,“autoLoadCnt”:0,“camZoneFltLoadCnt”:0,“chgLogLoadCnt”:0,“custWeathLoadCnt”:3,“devCustLoadCnt”:1,“devCustNameLoadCnt”:0,“devLocLoadCnt”:0,“diagLoadCnt”:0,“helpLoadCnt”:0,“infoLoadCnt”:0,“logPrefLoadCnt”:0,“mainLoadCnt”:12,“nestLoginLoadCnt”:0,“notifPrefLoadCnt”:0,“pollPrefLoadCnt”:0,“prefLoadCnt”:0,“protTestLoadCnt”:0,“vRprtPrefLoadCnt”:0,“viewAutoSchedLoadCnt”:0,“viewAutoStatLoadCnt”:0},“devUseMetCnt”:{“weatHtmlLoadCnt”:2,“presHtmlLoadCnt”:0},“stateUsage”:“25%”,“mobileClient”:“android”,“liteAppMode”:false,“datetime”:“Mon Mar 18 12:44:02 EDT 2019”,“optOut”:false}, clients/9e06fa8a-5156-4aec-be51-135edf678cec.json, null, heartbeat
3fa05894-bb1b-4f19-914c-2124ae73bfd8 12:43:57 PM: info ||| NST Manager (v5.6.0) | Updating Structure Data (Last Updated: 142 seconds ago) | Updating Device Data (Last Updated: 154 seconds ago) (async)
3fa05894-bb1b-4f19-914c-2124ae73bfd8 12:41:35 PM: info ||| NST Manager (v5.6.0) | Updating Structure Data (Last Updated: 12 seconds ago) | Updating Device Data (Last Updated: 12 seconds ago) (async)
3fa05894-bb1b-4f19-914c-2124ae73bfd8 12:41:31 PM: trace | NST Manager (v5.6.0) | workQueue │ Run Queue: 0 | (async)
3fa05894-bb1b-4f19-914c-2124ae73bfd8 12:41:27 PM: info ||| NST Manager (v5.6.0) | schedNextWorkQ RUNIN │ queue: 0 │ schedTime: 4 │ recentSendCmd: 3 │ last seconds: 3601 │ cmdDelay: 4 | runInActive: true | command proc: false | Api Limited: null
3fa05894-bb1b-4f19-914c-2124ae73bfd8 12:41:27 PM: info ||| NST Manager (v5.6.0) | Adding Cmd to Queue 0 (qsize: 1): Y_-Oh5R3pLMLoFMYHMylLDdLo7QePtZeilRYBn6j3xeFp7D-DaSt1w, poll, poll, 0, NestPres | Y_-Oh5R3pLMLoFMYHMylLDdLo7QePtZeilRYBn6j3xeFp7D-DaSt1w
3fa05894-bb1b-4f19-914c-2124ae73bfd8 12:41:23 PM: info ||| NST Manager (v5.6.0) | Updating Structure Data (Last Updated: 26 seconds ago) | Updating Device Data (Last Updated: 26 seconds ago) (async)
3fa05894-bb1b-4f19-914c-2124ae73bfd8 12:41:19 PM: trace | NST Manager (v5.6.0) | workQueue │ Run Queue: 0 | (async)
3fa05894-bb1b-4f19-914c-2124ae73bfd8 12:41:15 PM: info ||| NST Manager (v5.6.0) | schedNextWorkQ RUNIN │ queue: 0 │ schedTime: 4 │ recentSendCmd: 3 │ last seconds: 3601 │ cmdDelay: 4 | runInActive: true | command proc: false | Api Limited: null
3fa05894-bb1b-4f19-914c-2124ae73bfd8 12:41:15 PM: info ||| NST Manager (v5.6.0) | Adding Cmd to Queue 0 (qsize: 1): Y_-Oh5R3pLMLoFMYHMylLDdLo7QePtZeilRYBn6j3xeFp7D-DaSt1w, poll, poll, 0, NestPres | Y_-Oh5R3pLMLoFMYHMylLDdLo7QePtZeilRYBn6j3xeFp7D-DaSt1w
3fa05894-bb1b-4f19-914c-2124ae73bfd8 12:40:57 PM: info ||| NST Manager (v5.6.0) | Updating Structure Data (Last Updated: 180 seconds ago) | Updating Device Data (Last Updated: 180 seconds ago) (async)
3fa05894-bb1b-4f19-914c-2124ae73bfd8 12:37:57 PM: info ||| NST Manager (v5.6.0) | Updating Structure Data (Last Updated: 180 seconds ago) | Updating Device Data (Last Updated: 180 seconds ago) (async)
EDIT: I noticed in another post above this was caused by REST streaming. I do not have this service turned on.
Logs from Nest Thermostat not updating or checking in.
This just repeats constantly. Fixed by clicking the play button on the smart app. It was happening one a week, then one a day but now it won’t stay connected for more than half an hour.
|| NST Manager (v5.6.0) | finishPoll: Polling BLOCKED | Reason: (Sending Cmd)
||| NST Manager (v5.6.0) | No Device or Structure poll - Devices Last Updated: 1435 seconds ago | Structures Last Updated 715 seconds ago
||| NST Manager (v5.6.0) | schedNextWorkQ ALREADY PENDING │ queue: 0 │ schedTime: 4 │ recentSendCmd: 3 │ last seconds: 3601 │ cmdDelay: 4 | runInActive: true | command proc: false | Api Limited: null
|| NST Manager (v5.6.0) | finishPoll: Polling BLOCKED | Reason: (Sending Cmd)
||| NST Manager (v5.6.0) | No Device or Structure poll - Devices Last Updated: 1246 seconds ago | Structures Last Updated 526 seconds ago
||| NST Manager (v5.6.0) | schedNextWorkQ ALREADY PENDING │ queue: 0 │ schedTime: 4 │ recentSendCmd: 3 │ last seconds: 3601 │ cmdDelay: 4 | runInActive: true | command proc: false | Api Limited: null
|| NST Manager (v5.6.0) | finishPoll: Polling BLOCKED | Reason: (Sending Cmd)
1 Like
that all looks normal.
In the ST classic mobile app, when you go into Nest Manager, did you select devices to add to ST (thermostats, protects, cameras?)?
Does it list devices you can add?
Just did that now… found it, clicked it, saved it, but still not showing up in my “Things” list
EDIT: closed that classic app and opened the new app and it prompted me to add it to a room, now it’s there. Thanks!
Hi, yes I’ve started having exactly the same problem, noticed it this week and have been trying to work out what is happening. So far I’ve found that (thanks to this thread) the “play” button works to re-start everything and initialising the automations works to start everything again, I’m trying to find a pattern - but what does seem to be consistent is when the thermostat should start heating appears to be the point the updates stop being processed (need to have more evidence). Have you guys found any more info on this at all?
I’ve also raised an issue on GIT https://github.com/tonesto7/nest-manager/issues/639
