[Question] Do you have plan for a scheduler implementation?

[rajeevan]

First of all, Thank you for the awesome project.

Do you plan on expanding this to also include a simple scheduler? that will remove the need for Tado's cloud and also implement a proper Auto HVAC mode.

I tried existing few in HomeAssistant! but they are far off and trying to hack things together. Having such functionality in this project makes more sense. Of-cause that would mean this project need GUI (What you have is already comparable to what Tado has!)

Thanks

[rajeevan]

with lots of AI Agent help and debugging.. some sort of working solution
https://github.com/AmpScm/TadoLocal/compare/main...rajeevan:TadoLocal:scheduler?expand=1

I'm going to try this locally and see how it goes

[Nicko33127]

First of all, Thank you for the awesome project.

Do you plan on expanding this to also include a simple scheduler? that will remove the need for Tado's cloud and also implement a proper Auto HVAC mode.

I tried existing few in HomeAssistant! but they are far off and trying to hack things together. Having such functionality in this project makes more sense. Of-cause that would mean this project need GUI (What you have is already comparable to what Tado has!)

Thanks

I am not sure if you found this schedule addon:
https://github.com/nielsfaber/scheduler-card

With the both hacs addon I can control home away using my zone.home as a condition in the scheduler, and I also use windows as a second condition and with the " Re-evaluate when conditions change" option ticked in. As soon as one of the condition changes my thermostats act accordingly. Without this and only using -1 when away.. when back home, the temp would go back to previously know temperature not currently desired temp in schedule.

So with this I get schedules for each 7 rooms plus another one for away.. and everything work as expected for me. Home away temps , and temperature is always what I need. And it's very easy to use.

Boost can be done via an automation

[rhuijben]

Just noting that @rajeevan's work is now in PR #22.