Closed RezzZ closed 4 years ago
diving further in the code I saw that I was using the following set_temperature service:
- service: climate.set_temperature
data:
entity_id: climate.atag_one_thermostat
operation_mode: 'Manual'
temperature: '22.5'
It seems the operation_mode is not part of your set_temperature function so it stays on auto mode but still sets the temperature and it starts heating. I'm switching back to setting two services, one to manual, the other for temp. Lets see if that works
Hi René,
In my perception you can still set the temperature in Auto mode if looking at the Atag One App. In Manual mode it no longer follows your schedule. In Auto mode it does.
I will have a look at the code to see if I can make the operation modes case insensitive.
Thanks for your analysis.
Regards, Wim
true, setting temp with auto still enabled works but than how to revert back to the original scheduled temp? Up side is that the schedule will resume when a new time/temp setting is scheduled but I'd rather set it to manual to keep control
not relevant any more after the alignment with the general climate.component
Hi, I recently installed this great component for my new atag one but I'm facing difficulties setting the one back to mode 'auto'.
I receive the following error:
I found a similar issue with the nest thermostat pointing to a location where the bug might be:
It shouldn't error even so though, that's a bug in the nest set_operation_mode method.
https://github.com/home-assistant/home-assistant/issues/10172
edit: hmm, problem might be my automation setting it to 'auto' instead of 'Auto'. Need to test it still, but setting it to 'manual' (not 'Manual') with temperature does work so it still shouldn't give this error.