$nest->setAway(TRUE); doesn't stay away

[FrdPrefct]

When running $nest->setAway(TRUE);, it will set my thermostats to away and eco mode, but after a few minutes (if that) the thermostats will come out of eco. Most of the time the house is still reading "away".

Any idea how to actually manually set AWAY from the API, and keep it that way?

[bauzer714]

This most likely isn't the root cause of the problem, but.....setAway is for the most part, deprecated. Use "setEcoMode" instead with parameter (ECO_MODE_MANUAL / ECO_MODE_AUTO). Although setAway is calling setEcoMode on it's own - away is basically only there for legacy when Nest didn't have Eco mode.

How many thermostats do you have? Theoretically this shouldn't matter since ECO is system level rather than 'per device'. If you manually set it in eco via the app will it pull itself back out? Has it done this for more than today? What does it say in the 'history' of who pulled it out of eco?

[FrdPrefct]

I have 2.
So, what would be the proper way to use "setEchoMode"?

[bauzer714]

Eco, not Echo. Here are the implementations you can use.

//Go into eco mode.
$nest->setEcoMode(ECO_MODE_MANUAL);

/Resume previous mode
//So if it was in cool before eco started .. it'll go back to cool.
$nest->setEcoMode(ECO_MODE_AUTO);

[FrdPrefct]

Hello,
Unfortunately, that had the same result. It will take the thermostats off Eco after some time...

[gboudreau]

Away/present is not deprecated; it's the away mode of the thermostat that is.
setAway() will change you presence/away value for the location.
The 3rd parameter of that method is a BOOL that defines if you want to use ECO temps on the thermostat, when setting the location's presence indicator to away. It defaults to TRUE, which means Eco mode will be enabled when you call setAway(AWAY_MODE_ON).

There is also a setting on the thermostat that defines if the ECO temps should be used automatically, when you're away:

As for your actual problem, did you try to do tests with the web (or mobile) app, see if ECO mode sticks, or it reacts the same?
Maybe try to execute getDeviceInfo() every minute until ECO mode gets disabled, and use diff to compare the device info when the device is in ECO mode, and when it is not anymore, see if any of the values could explain why it happens.
Maybe the thermostat detects noise or movement, and decides to disable ECO mode? (I doubt; never did that for my Nest v1, but maybe other versions work differently.)

[FrdPrefct]

Away/Eco seems to stick when I use the Web or App, without an issue.
I've disabled sensors too, thinking maybe it was picking up something fictitious moving in my house.

[FrdPrefct]

Okay, here's the differences I see from when I use the app, as opposed to using the api.

"mode": "range,manual-eco,away" (Downstairs Thermo)
"eco_mode": "manual-eco" (Downstairs Thermo)
"mode": "range,manual-eco,away" (Upstairs Thermo)
"eco_mode": "manual-eco" (Upstairs Thermo)

"mode": "range,auto-eco,away" (Downstairs Thermo)
"eco_mode": "auto-eco" (Downstairs Thermo)
"mode": "range,auto-eco,away" (Upstairs Thermo)
"eco_mode": "auto-eco" (Upstairs Thermo)

[FrdPrefct]

Okay, now it's doing it regardless if i use the API or if i use the app...
When using the app, it was working properly, no issue previously.

[DrDoneSomething]

I had that problem - I logged into the nest website and turned off auto away, seems to work.