When I select ‘start eco’ on my Nest thermostat it activates the ‘eco’ preset and drops the target temperature to a low set point (9°C in my case). This is reflected in my HA instance via the Google Nest integration: the climate card shows the target at 9° (sometimes 9.1 or so for some reason, but whatever) and the HVAC action changes from Heating to Idle. All good.
The Nest system also supports “Home” and “Away” settings. ‘Away’ has the same effect on thermostats as ‘start eco’. I’m fairly sure that the Nest integration in my HA was responding to this exactly as it does when ‘eco’ is started directly, but now it’s only detecting the HVAC action change from Heating → Idle when it’s triggered by ‘Away’ - the preset in HA doesn’t change to ‘eco’, and the setpoint stays where it was.
This is a real pain for me, I was relying on being able to detect the preset and setpoint. It seems to have been a behaviour change very recently, perhaps in the last few days. As far as I can tell it’s not the result of anything I’ve done. Has anyone else noticed it?