0
Discuss

Is Nest Thermostat compatible with ActionTiles?

Steve Little 3 years ago in Things & Capabilities / Non-"Works With SmartThings" devices updated by M2 3 years ago 18

So I currently have a tile for my Nest Thermostat and only have the cooling option set in AT. I am able to change the temp up or down but it is not doing anything on my thermostats end. I did have it working with SmartTiles. I currently use Nest Manager to give me control in SmartThings.

Answer

PINNED

I just noticed that in SmartThings my Nest hasn't communicated with SmartThings since 2/23/17. So I obviously have a different issue that I need to address.

Discuss

We don't officially support Nest because it is not a "Works With SmartThings"­™ SmartThings certified device.


I thought some of our Beta testers had it working, however, so let's leave this Topic open for feedback and research.


When we get a chance, we might be able to example the "Nest Manager" Device Type to see if we can determine the reason for the incompatibility. Please provide a link (or attach a file) of the DTH source code you are running.

Waiting for Customer

Can you please try viewing Live Logging when attempting to set the Cooling setpoint from ActionTiles?

Here is some of the live logging after selecting to turn the temp down 3 times while in ActionTiles


3cee7a1e-0b59-47f3-9882-3acdc3d199ba 10:13:17 PM: info ||| Nest Manager | Replacing in Queue 1 (qsize: 1): 4pba68Pk3xucNMDwmSymrsn7UfMulpEX, devices/thermostats, target_temperature_f, 74, 4pba68Pk3xucNMDwmSymrsn7UfMulpEX

3cee7a1e-0b59-47f3-9882-3acdc3d199ba 10:13:17 PM: warn ||Nest Manager | Command Matches last in queue 1 - Replacing
3cee7a1e-0b59-47f3-9882-3acdc3d199ba 10:13:17 PM: debug Nest Manager | setTargetTemp: 4pba68Pk3xucNMDwmSymrsn7UfMulpEX | (74)F | virtual false
3cee7a1e-0b59-47f3-9882-3acdc3d199ba 10:13:05 PM: info ||| Nest Manager | Replacing in Queue 1 (qsize: 1): 4pba68Pk3xucNMDwmSymrsn7UfMulpEX, devices/thermostats, target_temperature_f, 75, 4pba68Pk3xucNMDwmSymrsn7UfMulpEX
3cee7a1e-0b59-47f3-9882-3acdc3d199ba 10:13:05 PM: warn ||Nest Manager | Command Matches last in queue 1 - Replacing
3cee7a1e-0b59-47f3-9882-3acdc3d199ba 10:13:04 PM: debug Nest Manager | setTargetTemp: 4pba68Pk3xucNMDwmSymrsn7UfMulpEX | (75)F | virtual false
3cee7a1e-0b59-47f3-9882-3acdc3d199ba 10:12:56 PM: info ||| Nest Manager | Replacing in Queue 1 (qsize: 1): 4pba68Pk3xucNMDwmSymrsn7UfMulpEX, devices/thermostats, target_temperature_f, 76, 4pba68Pk3xucNMDwmSymrsn7UfMulpEX
3cee7a1e-0b59-47f3-9882-3acdc3d199ba 10:12:56 PM: warn ||Nest Manager | Command Matches last in queue 1 - Replacing
3cee7a1e-0b59-47f3-9882-3acdc3d199ba 10:12:56 PM: debug Nest Manager | setTargetTemp: 4pba68Pk3xucNMDwmSymrsn7UfMulpEX | (76)F | virtual false
3cee7a1e-0b59-47f3-9882-3acdc3d199ba 10:12:52 PM: warn ||Nest Manager | workQueue: busy processing command
3cee7a1e-0b59-47f3-9882-3acdc3d199ba 10:12:52 PM: trace ||Nest Manager | workQueue Run queue: 0 async
3cee7a1e-0b59-47f3-9882-3acdc3d199ba 10:12:47 PM: info ||| Nest Manager | Replacing in Queue 1 (qsize: 1): 4pba68Pk3xucNMDwmSymrsn7UfMulpEX, devices/thermostats, target_temperature_f, 77, 4pba68Pk3xucNMDwmSymrsn7UfMulpEX
3cee7a1e-0b59-47f3-9882-3acdc3d199ba 10:12:47 PM: warn ||Nest Manager | Command Matches last in queue 1 - Replacing
3cee7a1e-0b59-47f3-9882-3acdc3d199ba 10:12:47 PM: debug Nest Manager | setTargetTemp: 4pba68Pk3xucNMDwmSymrsn7UfMulpEX | (77)F | virtual false
3cee7a1e-0b59-47f3-9882-3acdc3d199ba 10:11:52 PM: warn ||Nest Manager | workQueue: busy processing command
3cee7a1e-0b59-47f3-9882-3acdc3d199ba 10:11:52 PM: trace ||Nest Manager | workQueue Run queue: 0 async
PINNED

I just noticed that in SmartThings my Nest hasn't communicated with SmartThings since 2/23/17. So I obviously have a different issue that I need to address.

I have two Nest Thermostats and I'm able to change setpoints via SmartTiles fine.


I am using Nest Manager in SmartThings.

Do you mean ActionTiles or only "SmartTiles"?

My bad ... I meant ActionTiles. It works fine for me in ActionTiles.

+2

I am currently using Nest Manager for two thermostats and one virtual thermostat and everything appears to be working smoothly. I am using the dual thermostats (thanks for adding those in - much less confusing for my wife!)

I am having a difficult time locating this Smart App. I tried from the ST App on my phone but no luck. Can you please point me in the right direction? Thanks @chrstnMchl

+1

Details on the Nest Manager (now called NST Manager, apparently) are in the Things That Are Smart wiki. This link will take you directly to the instructions on how to access the device handler and the smartapp in github.


http://thingsthataresmart.wiki/index.php?title=NST_Manager#Using_Git_Integration_.28Recommended.29

Always gotta ask just in case...


...Terry.

Yes but I got caught up in that stupid URL thing. I was on the wrong IDE (again). Its now configured in my ST app. Now I have to see if i can get it into AT. :D

So.. .everything is installed now in my ST mobile app and i can see it on the IDE. I am just not sure how to expose it to AT now. Can someone walk me through that?

As long as the DTH includes Capability "Sensor" and Capability "Actuator", then you'll find the new Device available to Authorize by going to (in the ActionTiles App...)

  • My Locations
  • <location name>
  • Menu - Settings
  • Authorize Things

Well dang, I didnt add a DTH, only the app. {grrrr}

Changing the Nest temperature on an action tile - a notification message appears that says the temperature has been changed, and the new temperature appears on the tile - but if the thermostat is in ECO mode, the temperature setting doesn't actually get changed. If you use the Nest web app to change the temperature while it's in ECO mode, it rejects the attempt and pops up a message that you have to switch the thermostat out of ECO mode. ActionTiles should mirror the fact that the temperature really didn't change. And yes, I understand that it's not a "Works with SmartThings" device, I'm posting this in case it's a minor change. Perhaps after sending a temp change to the device, poll the device to see what the setting is on it rather than just incrementing the tile (if that's what's happening).

+1
Discuss

Good discussion, Jim,

Perhaps after sending a temp change to the device, poll the device to see what the setting is on it rather than just incrementing the tile (if that's what's happening).


ActionTiles doesn't poll (that's a big part of earning our WWST™ certification!).


It is up to the devices to tell ActionTiles if any Attribute changes. Perhaps ActionTiles should consider resetting its display to the last known setPoint if it doesn't receive a confirmation Event; but assuming that a command failed is something we avoid doing. It would keep the app pretty busy waiting around for stuff to happen.


May I suggest that you propose the following to the DTH developer?

  • If the Nest device (or any thermostat, actually) receives a "set Heating/Cooling setPoint()" Command that it must reject because it is in a special ECO mode, then it should immediately trigger a "sendEvent(setPoint)" to correct everyone (including ActionTiles) what the current setting actually still is.
  • As a result, ActionTiles would be updated ASAP with the actual Nest value.
  • I believe this would be within compliance of SmartThings's device type handler guidelines.

Make sense?