Tado fallback: false doesn't works!

[energywave]

The problem

Tado integration introduced the fallback parameter about one year ago. Doc says the default is true so I set it to false as I wants that manual overrides of zones temperature should be until a different setting is issued and doesn't return to automatic schedule on the next scheduled period.
But it doesn't works, when scheduled time is coming the manual temperature that I've set will be returned to auto and the schedule is returning active.
If I see in the Tado app I can see that all the manual temperatures I set with HA are "until next schedule" (translated from italian...)
Is there a way to let fallback: false to work?

Environment

• Home Assistant Core release with the issue: 0.117.5
• Last working Home Assistant Core release (if known):
• Operating environment (OS/Container/Supervised/Core): HassOS on Raspberry Pi 4 / 4GB
• Integration causing this issue: Tado
• Link to integration documentation on our website: https://www.home-assistant.io/integrations/tado/

Problem-relevant configuration.yaml

tado:
  username: !secret tado_username
  password: !secret tado_password
  fallback: false

Traceback/Error logs

Additional information

[probot-home-assistant]

Hey there @michaelarnauts, @bdraco, mind taking a look at this issue as its been labeled with an integration (tado) you are listed as a codeowner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[Savjee]

Can confirm. I'm having the same issue. I checked out the Home Assistant component and I believe it's due to a change of Tado's API.

I've documented my findings and opened an issue on the underlying library: wmalgadey/PyTado#41

[energywave]

Furthermore as I hope that a dev will handle this (let's hope...) it would be very useful to specify fallback with a parameter to the service, not globally in the configuration! Or better, specify a global value like now in configuration but the possibility to specify it even as a parameter in the service. Some automation could so use it, some not, depending on the usage context.

[Savjee]

Small update on the actual issue. I've published a pull request for the Tado library: wmalgadey/PyTado#44

It's a very simple fix. As soon as this one gets merged in, I can submit a fix for Home Assistant.