Issue w/ Nest recently?

I'm currently using the built-in Nest integration. I created the custom commands "Away ()" and "Present ()" to put my thermostat into Away or Home based on the mode of the hub. This has worked perfectly until a few days ago. I first noticed that the thermostat didn't appear to be returning to Home mode when it was supposed to. I went in and tested the commands to see what was happenings, and they don't seem to be doing what they originally did. Instead of actually changing the mode of the thermostat, it looked like the "Away ()" command was putting the thermostat into Eco mode without actually changing the Home/Away mode of the thermostat.

Has there been a change recently either with the Nest developer program or the way Hubitat sends the commands that would account for this seemingly random change?

I do the same exact thing but my custom commands are setAway() and setHome()

They've been working for the past few weeks.

How did you create those commands? When I go to make a new command in RM, neither of those are on the list of available ones for my thermostat. Maybe I'm not completely understanding how custom commands work. See the attached screenshot for what I see when trying to make one.

15%20AM

Mine was created in relation to the Nest Presence Device.
Not a Thermostat.

Ahh, ok. That makes sense. I'm not sure if I set up a presence device for my Nest. I'll go check now.

1 Like

I went back and added the Nest Presence sensor, and then I created the custom commands you mentioned. I still seem to be seeing the same issue though. When I came home from work today, the command took the thermostat out of Eco mode, but it stayed in “Away”. Not sure if this is an underlying Nest issue, or if I’m doing something wrong somewhere.

I have a Nest and presence detection on my phone, but if I'm working from Home the Nest will go in to away mode until I go back downstairs and walk past the thermostat..

I was hoping to trigger presence based on my PIR in my office, but have a similar issue to you.. Hitting "Present" in the thermostat doesn't seem to trigger a presence event as you would expect? And seems to cause issues in the API status?

Perhaps something has changed and Nest needs some additional data at the same time? Hopefully one of the Devs can confirm what's going on here?

[dev:289] 2019-02-07 02:53:13.878 pm [debug] API Status is: (Sporadic Issues) | Previous State: (Good)

[dev:289] 2019-02-07 02:53:06.929 pm [debug] ST | Nest Presence: Present | Previous State: Not present | State Variable: false

[dev:289] 2019-02-07 02:53:06.823 pm [trace] setHome()...

[dev:289] 2019-02-07 02:53:06.820 pm [trace] present()... 

The equivalent in state history:

lastUpdatedDt Thu Feb 07 14:53:13 GMT 2019 DEVICE 2019-02-07 02:53:13.950 PM GMT
thermostatSetpointMin 9.0 C Thermostat SetpointMin is 9.0°C DEVICE 2019-02-07 02:53:13.924 PM GMT
thermostatSetpointMax 32.0 C Thermostat SetpointMax is 32.0°C DEVICE 2019-02-07 02:53:13.924 PM GMT
heatingSetpointMax 32.0 C Heat SetpointMax is 32.0°C DEVICE 2019-02-07 02:53:13.917 PM GMT
heatingSetpointMin 9.0 C Heat SetpointMin is 9.0°C DEVICE 2019-02-07 02:53:13.908 PM GMT
apiStatus Sporadic Issues API Status is: Sporadic Issues DEVICE 2019-02-07 02:53:13.878 PM GMT
presence present Device is: present DEVICE 2019-02-07 02:53:06.929 PM GMT
nestPresence home Nest Presence is: home DEVICE 2019-02-07 02:53:06.929 PM GMT

I only have a NestCam on the account. Is it possible to set Away/Home?

That's all I really have.

It works.

Hopefully you've connected Nest already.

Can you please share info on your config (i.e screenshot)? Not sure how to configure this in rule machine

Here's the setAway() rule.

Thanks! Just did the setup. Will check in the AM to see if it works.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.