Set point change not actioned

[Mayhem]

Hi

Installed the Nest plugin some time ago and all good.
Some time later I noticed that when I changed the set point on the device panel the temp would change but then flip back to the original value on the next status update.
From the nets phone app and device itself all was fine an f it was changed on the device the update came through to the plugin and Indigo.
I took a flyer and regenerated the API key and all was well.

However it has happened again and changing the key and several roads/restarts later no joy.

Any thoughts anyone??
I am running Indigo 6.1.9 and Nest plugin v2.0.32
Thanks in advance.
Neil

Below is log example. The set point was 16.5 to start with you see the change request and then on the next update the temp changes back.

2 Jun 2016, 20:16:46
NEST Home sent "Lounge Thermostat (Downstairs)" decrease heat setpoint to 15.5
NEST Home sent "Lounge Thermostat (Downstairs)" decrease heat setpoint to 14.5
UPS and Battery Monitor Power Status - AC Power
UPS and Battery Monitor UPS Model - -Value800ELCD (id=9895936)
UPS and Battery Monitor Charging Status - True
UPS and Battery Monitor Battery Charge - 100
UPS and Battery Monitor Refreshing in 5 Minutes
NEST Home Lounge Thermostat (Downstairs) target_temperature_c updated to 16.5
NEST Home Lounge Thermostat (Downstairs) ambient_temperature_c updated to 20.0

22 Jun 2016, 20:17:22
NEST Home sent "Lounge Thermostat (Downstairs)" decrease heat setpoint to 15.5
NEST Home sent "Lounge Thermostat (Downstairs)" decrease heat setpoint to 15.5
NEST Home sent "Lounge Thermostat (Downstairs)" decrease heat setpoint to 14.5
Z-Wave received "023 - Lounge Radiator Thermostat (LC-13)" status update battery level 69%
Z-Wave received "Lounge Radiator Thermostat (LC-13)" heat setpoint is 21.00 °C
NEST Home sent "Lounge Thermostat (Downstairs)" decrease heat setpoint to 13.5

22 Jun 2016, 20:18:09
NEST Home Lounge Thermostat (Downstairs) target_temperature_c updated to 16.5
NEST Home Lounge Thermostat (Downstairs) ambient_temperature_c updated to 20.0

[Colorado4Wheeler]

I've also had this problem and from what my somewhat limited testing on this has shown is that it's not the plugin causing it (mostly, sometimes perhaps), it is the Nest auto setting that does it. I was getting pretty frustrated one day when this kept happening to me and found if I went into the Nest website and deleted or moved the auto temp schedule around then the problem worked itself out.

[Mayhem]

Dude, your spot on.

The auto away has never really worked since I started using the plugin anyway and Nest say everything is fine from their end.

I switched off the auto away and the changes stay.....


The mystery gets deeper.

Cheers.

[Colorado4Wheeler]

Yea, the auto away feature is a bit buggy and, in the case of using it with Indigo, fairly unnecessary since you can use Indigo for all that. For me getting the Nest was purely an aesthetic thing and not a functional one, I love the look but knew I would control it 100% through Indigo - and for that reason I waited for the plugin before I got one .

[Mayhem]

Same here.
Loved the looks and the build quality.

So when I saw the plugin that was the clincher.