Same Thing
The ST application has limitations with the displaying of HTML content with the Android OS.
After you Force Stop the ST app, the first time you go back into a Nest device, the HTML content will load without an issue (sometimes you still have to swipe down on the screen depending on device). The next time you go into that device, you will see the spinning circle. Known issue with no timetable of a fix.
In fact, I believe that @tonesto7 is going to remove this section from displaying in the device period. The HTML (graphs, etc) are available from inside of NST Manager itself and will open the HTML content in another browser.
I thought I would give you the full details, instead of cryptic answers.
@WB70 Perfect this makes sense, looking forward to that area being removed. Thanks for the information
That same information is available 100% of the time if you open NST Manager and click on View Device Tiles:
@WB70 Yes I have seen that and it does work all the time or at least the times I have been in there with no problems. I’m much rather just go there if needed rather than having it show up on the main screen where it does not work
I personally don’t use the ST mobile app to view, access or control my devices. I use the app really for maintenance, device additions, rules and automation.
For accessing, viewing and controlling devices on a daily basis, I use ActionTiles. If you haven’t gone down that route yet, you should take a look. They have a free two week trial to see if you like it before purchasing it. It’s one of a handful of reasons I am still on the ST platform. 
Trying to create a simple tile in webcore which will let me know if my nest indoor cam is on/off. I usually turn it off when I am home and expect to turn back on when mode changes to Away.
What should I select from following categories which will let me know if camera is streaming/on or notstreaming/off.
I could be wrong, but I believe it is “isStreaming”, values “on” and “off”
EDIT: I tested and confirmed with a Piston that the above is indeed correct.
Maybe I am too impatient. “isStreaming = on” is working for me but “isStreaming = off” is not working.
How long do I have to wait for ST to recognize that camera is off?
Both on and off worked for me. I edited the same Piston for on and then off to turn on a light as shown below:
To test, open your camera in the mobile app and simply press the little camera image, not the Active / Inactive picture
The labels in your device show Streaming and Off, but I validated that the correct values in the DH are on and off and they both work appropriately in webCoRE.
If you test the way I described, your test will be almost instant.
Its working now. My original piston was (forcefully) turning it on since the mode was away. But I paused that piston and started from scratch and it is working now. Trigger is instant as you said. Thank you.
1 Like
Excellent!
And remember, if you turn your camera off/on from the Nest app, there will be a delay. NST Manager has to poll Nest before it will update to off/on in ST.
Yup. I use the same approach as you. Use NST Manager for webcore and automation stuff. Use the Nest app to see the actual event, etc…
1 Like
Quick question. I run my Automation schedules through NST manager, and over the course of the last year have tweaked them occasionally. That said, from time to time it seems like old temp setpoints that I no longer use get sent to the Stat. Is this something that Nest has learned and I need to delete some sort of cache perhaps? It’s not a huge issue, just always looking to make things run as smooth as possible.
Numerically, let’s say for a few months it ran on auto between 70-73 from sunset to sunrise, but now I’ve had it widened to auto 65-75, occasionally I will catch it in the logs as having set the Stat to 70-73 still for some reason. I don’t see any conflicts in my scheduling kind of scratching my head.
Thanks!
If you open the Nest App and select your Thermostat and then click on Schedule, do you have any set schedules in there?
And if you do have any schedules that show up, if you click on the Gear icon, is the Auto-Schedule On/Learning?
Hey folks. I’m struggling to figure out my scenario…
I have a vacation home with a Nest. I have an automation that preheats / cools the house when we get on the road so that it is up to temp when we arrive.
I had the Nest stay in Eco mode when we are not there, but then the automation doesn’t work, because it can’t take the Nest out of Eco.
So I shut off the Eco functionality, and things work now, however, should I be concerned about something here? Is it a “problem” to NOT have the Nest in Eco, or is this just some cost saving feature?
You can’t have both things turned on at the same time:
If you are using ST/NST Manager to do your scheduling and setting thermostat temps up and and down and setting your Nest to Away based on when ST goes into Away Mode, then you can’t have Nest setup to go into ECO Mode when Nest goes into Away.
When Nest goes into ECO Mode from the Nest side when it goes into Away (that’s a locked mode, period), and you cannot now adjust temps from ST, whether it be manually adjusting the thermostat or from a schedule adjustng the temp settings.
Yes - ECO is supposed to represent cost saving (Economically friendly) with a value to represent when it should heat and a value representing when it should cool.
In short, if you are doing your scheduling from NST Manager, do not turn on option in Nest for it to go into ECO when Away. You can do those same schedules within NST Manager if you needed to put it into ECO Mode, but in order to adjust heat/cooling numbers, you must then take the thermostat out of ECO Mode.
I personally don’t use ECO Mode. I set schedules on the Nest side that represent the same temps as what ECO Mode automatically sets those predefined temps to.
You could also bypass doing any schedules in NST Manager and opt for a different control of your thermostat via WebCoRE and Pistons. Different ways to slice and dice depending on your requirements.
Hopefully this clears it up a little but and doesn’t add to even more confusion
The only thing that I really use NST Manager for is setting my Nest environment to Away when ST goes into Away (Mode automation). When Nest goes Away, I then have a bunch of cameras that turn on based on that. Outsde of that, I keep things very simplified for the fact that when ST goes down (a lot of outages this year), my environment doesnt get comprimised or screwed up in any way because of control all of my automation from the ST side. Not reliable or recommended from my perspective. This is no fault of NST Manager, but the platform it sits on.
Is there any setting in Nest environment where if thermostat goes to echo, all nest cam should turn on. Just thinking about the possibility when ST goes down, then nest cameras will not be affected since nest thermostat will automatically go in eco mode based on phone location.
Take SmartThings out of the equation for a minute. Forget that you have NST Manager installed.
In Nest, when set to Away, you have the option of turning cameras on and off and also for your thermostat to be set to ECO when Away and taken out of ECO when Home (Home/Away Assist).
Now in NST Manager, if all you do is setup the Mode Automation so that when ST goes into Away, it automatically puts your Nest environment into Away Mode.
With this, Nest is relying on ST based on the Away mode being set. With what I posted above, everything is controlled from Nest as to what happens with your devices (cameras and thermostat) via Home/Away Assist. The only automation in place from ST is setting Nest to Away with the Mode Automation setup in NST Manager.
With that being said, if you want ST to control what happens in the Nest environment, then you need to turn off those same settings in Nest itself. If you want cameras to be controlled from NST Manager you can. If you want NST Manager to put Nest into ECO Mode you can.
1 Like
How can I use NST Manager to switch the thermostat to Eco when smartthings goes into away mode?