Tado: smart schedule not working anymore!

[herwarth]

I know changes are made in the climate component but this is very annoying.
Before I could set the operation mode as follows:
To turn off:
climate.set_operation_mode
{
“entity_id”: “climate.bathroom”,
“operation_mode”: “off”
}
To turn on agian but using the smart schedule of Tado:
climate.set_operation_mode
{
“entity_id”: “climate.bathroom”,
“operation_mode”: “smart schedule”
}

Now I have to use turn_on and turn_off but this is the problem.
When turning a zone on again it is forever. No use of smart schedules anymore.
Can you implement the set_preset_mode: smart or whatever to set the Tado zone to enable smart schedule again?

[jeroenjoosse]

If this is the case, the preset mode 'Tado mode' probably isn't working anymore either. Can't test this as I'm holding off updates beyond 0.95 for this very reason.

[herwarth]

hmmm development on this component is not very active i believe.
also goging back to 0.95.4. this is the latest docker image tag of the 0.95 branch.
super easy to roll back using docker.
hoping it will be fixed asap. because it is annoying as f*ck

[eawenden]

Using climate.turn_off to turn the heating off and the set_hvac_mode to turn it back on enables smart schedule for me again on 0.98.2. Not really the behaviour I would expect, but whatever works...
climate.set_hvac_mode
{
"entity_id": "group.climate_all",
"hvac_mode": "auto"
}

[herwarth]

Using climate.turn_off to turn the heating off and the set_hvac_mode to turn it back on enables smart schedule for me again on 0.98.2. Not really the behaviour I would expect, but whatever works...
climate.set_hvac_mode
{
"entity_id": "group.climate_all",
"hvac_mode": "auto"
}

this works! thanks!

[FrankZZ]

@michaelarnauts I am using the tado override "the other way around" as to what you mentioned in your PR #29014
I have a schedule for when I am home, and when I leave home, homeassistant overrides the temperature indefinitely (sets it to 15C).

With your PR this broke my automation and caused my house to heat up (because I have multiple "events" in my schedule over the day with different temps).

Is it possible to support both, "override until smart schedule" and "override forever"?

[michaelarnauts]

Hmm, that's something that I should make configurable then indeed.

[teocannata]

It would be great, because I have the exactly same problem. I used the Manual mode to decrease indefinitely the target temperature until I come back home. Maybe this is achievable setting a fourth hvac mode?

[michaelarnauts]

@teocannata when you turn your climate off, it still behaves like that and will not turn back on on a schedule change. tado will then set the temperature to "frost protection", somewhere around 5 degrees celcius.

[teocannata]

@michaelarnauts Yes, you're right. The point is that I usually set 17 or 18 degrees when I'm out because my son's room (1 year old) is a mansard and setting it to frost protection would be too cold. I usually use frost protection only when it's summer.

[michaelarnauts]

No problem, I will adapt the code to be able to configure a default_overlay.

[michaelarnauts]

I've updated my open merge request (#29246) to include this. You can have an optional fallback: false (default=true) config parameter to indicate if tado should fallback to the schedule or if it should stay in manual mode.

Feel free to comment in that PR.

[teocannata]

I have updated to 0.104.1 version and put fallback: false in my climate yaml file but I'm getting the following error while home assistant is setting up the tado platform.
What am I missing?
Thanks

Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 158, in _async_setup_platform await asyncio.wait_for(asyncio.shield(task), SLOW_SETUP_MAX_WAIT) File "/usr/local/lib/python3.7/asyncio/tasks.py", line 442, in wait_for return fut.result() File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run result = self.fn(*self.args, **self.kwargs) File "/usr/src/homeassistant/homeassistant/components/tado/climate.py", line 78, in setup_platform tado, zone["name"], zone["id"], discovery_info[CONF_FALLBACK] TypeError: 'NoneType' object is not subscriptable

[michaelarnauts]

This part of the code should have nothing to do with fallback...

Can you please open a new issue and provide more information? (More log, config, ...)

[teocannata]

I thought it was related because I read fallback in the log and the feature of fallback is not working. I will open an issue as soon as possible 👍

[teocannata]

@michaelarnauts Issue opened (#30952), it's my first issue so don't hesitate asking me further information.
Thank you!