I’ve been having issues with my NEST working properly with SmartThings this morning. I noticed I wasn’t getting any updates, so I removed and reinstalled the NEST custom device (based on https://gist.github.com/Dianoga/6055918 code) and I don’t appear to be receiving any updates. I can log into my NEST account from home.nest.com just fine.
Is anyone else seeing this issue or is it just me?
I have seen for many days now that nest does not update automatically in ST app. if i do manual refresh, then it gets current data.
I’ve had the same issue. I think there have been some API changes to SmartThings. I’ve had to update a few SmartApps. I was going to look into this last evening but didn’t have time. Will try tonight and report back if I find anything to change.
Note: the most recent code is actually here - https://github.com/smartthings-users/device-type.nest/blob/master/nest.devicetype.groovy
There’s occasionally an issue where login will expire and isn’t renewed. It’s hard to troubleshoot since as soon as you update, it isn’t expired anymore and it works fine for weeks.
@dianoga Ever since the new Android app came out my nest doesn’t show a temperature on the icon. It does report it, as you can see it in the logs…but none of the numbers show up in the widgets. Any idea what may be going on?
I’m actually doing some work on the device type now.
Hmmm…apparently whatever is broken is causing bad login requests on the Nest API side. I just received a nicely word e-mail from Nest asking if I think my Nest account was hacked and to disable any third party integrations.
@ben really? Can you forward that to support if it doesn’t contain any personal info? Or pick parts out of it.
@Urman - Sure. I’ll forward that on to support. They were nice about it - it wasn’t demanding at all. I was just immediately horrified since I thought integrating Nest with a third party service was against the Nest TOS at this point.
In my response to them I asked if they had an update on the release date of their API, since that would make things play nice together more easily. I haven’t received a reply yet.
Perhaps my difficulties are unrelated to the above, I’ve just starting playing around with smartthings this week.
However, I just created a Nest device using Dianoga’s newest code and instructions this morning and I get an “unable to send command” error within the smartthings app (iOS 7.1) and no information is being received from the Nest. As with others, I can log onto the nest web site and my nest app is working as well.
Add me to the list. Just like Ben, I reinstalled after experiencing the same issues. I am no longer getting updates and am getting “unable to send command” errors like Geoff is.
Scratch that. I added the missing metadata and am now connected and able to send commands.
definition (name: "Nest Thermostat", author: "dianoga7@3dgo.net") {
capability "Polling"
capability "Relative Humidity Measurement"
capability "Thermostat"
attribute "presence", "string"
command "away"
command "present"
command "setPresence"
}
I am currently using @Dianoga 's custom devicetype with the new SmartThings iOS app and noticed a few nuances with usage under things:
Are these known issues, current limitations, or items that are being fixed?
Thanks for all the hard work thus far for getting this to work being Nest/Google are dragging their feet immensely on fully publishing an API!
I’ve noticed at times the temp was about 1 degree off as well. I made a small change to the devicetype that has appeared to correct this - it looked like it was cutting off the decimal portion instead of rounding.
I changed lines 236-242 (in my copy) in the poll() method to the following:
sendEvent(name: 'humidity', value: data.device.current_humidity)
sendEvent(name: 'temperature', value: Math.round(cToF(data.shared.current_temperature)) as Integer, state: data.device.target_temperature_type)
sendEvent(name: 'thermostatFanMode', value: data.device.fan_mode)
sendEvent(name: 'thermostatMode', value: data.shared.target_temperature_type)
sendEvent(name: 'coolingSetpoint', value: Math.round(cToF(data.shared.target_temperature)) as Integer)
sendEvent(name: 'heatingSetpoint', value: Math.round(cToF(data.shared.target_temperature)) as Integer)
sendEvent(name: 'presence', value: data.structure.away)
I haven’t really played with the presence, so I’m not sure if it’s always worked that way or if it’s something new.
As for the Nest in the iOS SmartThings app - other than looking at the temp/humidity, I really don’t use it. I prefer the Nest iOS to adjust it and I know the Nest app is in direct communication with my thermostat. I mainly use the Nest integration with SmartThings to control other devices based on temperature and humidity.
@ben1 That worked! Thanks. 2 Issue downs, 2 to go. 
RESOLUTION to item 1: Modify following section of code ~lines 236-242 ; basically using Math.round function to resolve as @ben1 pointed out.
sendEvent(name: 'humidity', value: data.device.current_humidity)
sendEvent(name: 'temperature', value: Math.round(cToF(data.shared.current_temperature)) as Integer, state: data.device.target_temperature_type)
sendEvent(name: 'thermostatFanMode', value: data.device.fan_mode)
sendEvent(name: 'thermostatMode', value: data.shared.target_temperature_type)
sendEvent(name: 'coolingSetpoint', value: Math.round(cToF(data.shared.target_temperature)) as Integer)
sendEvent(name: 'heatingSetpoint', value: Math.round(cToF(data.shared.target_temperature)) as Integer)
sendEvent(name: 'presence', value: data.structure.away)
PENDING (Comments or Resolution):
2.Presence does not appear to work fully. I can put it into away mode via Nest Device in things view, but it will not come out of away mode.
3.Preferences under nest device in things view on iOS app crashes SmartThings iOS app
I am planning on using the Nest app to still adjust temp, but my goal is to ensure presence works correctly, so that I can use Goodbye/Away mode to set the Nest to away to reduce energy cost, then when I return home the I’m Back/Home to turn away mode off.
Items 3 & 4 are strictly cosmetic and to keep the Girlfriend happy! As we all know no one wants to listen to their significant other nag and those less tech savvy just love to complain about cosmetic issues like this and say the entire solution does not work, when we all know its not the end of the world being we are on the bleeding edge and implementing solutions that are not fully vetted. But they will make our lives not as comfortable until they are fixed! 