1

When using the API to communicate with a Nest Learning Thermostat (in this case using the nest home assistant integration), when a request is made to change the nest thermostat to the "OFF" mode, I can see the mode show as "OFF" on the home.nest.com website, however the thermostat doesn't register it at all and just stays in whatever mode it was already in. Curiously, when I select "OFF" on the home.nest.com site the OFF mode that's displayed on the site has a leaf icon under it, while when I do it via the API it does not. When selecting it on the site the thermostat does switch to "OFF" with a leaf icon displayed under that on the thermostat as well. It seems like the API is sending an "OFF" state that the home.nest.com site can see but that the thermostat itself just doesn't respond to at all for whatever reason. It's like there are two different off commands here and only one of them (whatever the nest.home.com site is using) is working, and whatever the API is using is not. Seems like a bug but I wasn't sure if I'm just doing something wrong here or what. Just wanted to mention it here so that it will hopefully have some visibility from the devs. Thanks.

Ryan Matte
  • 13
  • 2
  • Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. – Community Oct 23 '21 at 06:11
  • Same issue: issuing a command to turn off the Thermostat with the API gives a 200 response and home.nest.com shows the thermostat is off, but in reality the thermostat is still running. {'command': 'sdm.devices.commands.ThermostatMode.SetMode', 'params': {'mode': 'OFF'}} – Collier Oct 25 '21 at 22:24
  • This is a bug that's getting fixed. – Ethan Jan 07 '22 at 22:14

2 Answers2

0

If you see the leaf icon on the home.nest.com site, then the thermostat is in Eco, and the ThermostatMode.SetMode command doesn't work when the thermostat is in Eco: https://developers.google.com/nest/device-access/traits/device/thermostat-mode#setmode. You have to use the ThermostatEco trait instead.

Gothic
  • 322
  • 3
  • 12
0

API bug confirmed, seems to be fixed here: https://github.com/home-assistant/core/issues/60941

pdespres
  • 16
  • Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Jan 25 '22 at 05:14