Suggest this is linked to https://tado.vanillacommunities.com/en-gb/discussion/850/support-multiple-schedule-configurations-such-as-spring-summer-autumn-winter-etc which has some more ideas in the same model. My addon would be to be to allow multiple profiles which can then be triggered by month/date or other triggers (including IFTTT).
My comments from that topic were:
Really would like this --- and potentially also have this all integrated with an optional external thermometer feed (see https://tado.vanillacommunities.com/en-gb/discussion/5387/outdoor-thermometer). This is the one major shortcoming with Tado at present.
I would go a little further to suggest the ability to have MULTIPLE profiles (ideally up to 10), which can then be attached to dates, to events from IFTTT and other home automation systems, and/or to external temperature sensing. This could also be tied into another request I've seen about individual geofencing.
I would also want to see the "open window sensing" process configured in each of these - during the summer, then often the temperature indoors will drop simply because the doors are open - you therefore would want to have a different "open window sensing" behaviour during these times. Especially good if the option of an external thermostat was there, so you could have logic such as "outside temp more than inside target temp never switches heating on, even if open window has been sensed".
At work I run a couple of bespoke commercial building management systems. Tado actually mimics a lot of the functions from the systems I'm used to using but this is an area that Tado is lacking.
I suggest summer/winter changeover thresholds. One to cut off the heating in spring if the external temperature exceeds X, and another to begin heating in autumn if the external temperature falls below Y. These need to be set at different levels in my view to account for acclimatised comfort perception (spring cutoff at 18, and autumn start at 13 are what I find works). On the days that are borderline, the system will run (or not) to feather the heating through the changing season depending on external temperature.
This could either reference the predicted weather or run off an external thermostat.
Just my thoughts...
I like this idea, especially when programming the smart A/C controllers in order to be used in both summer and winter.
Tado needs save-able seasonal settings so bad.
Ideally all four - spring summer autumn winter. Ideally this would be done with a simple 'save current schedule as a preset' option. We've got copy and paste schedule, it should not be desperately difficult to add a save & name option, and we should be able to have at least 4 saved schedules per room/zone.
After careful monitoring of my system since installing it late summer, it seems obvious to me that there are a few transition weeks between "no heating at all" to "some heating if things dip below a certain level" through to "brr, heating on more than it's not".
But once through those weeks, the heating pattern changes for the better part of the whole season. Having to go through room by room tweaking during the transition weeks essentially wrecks the stable configuration I had found for the previous season. This requires me to write down the optimal settings for each room once I have identified them for a given season, then when we hit that season this year, labouriously reprogram each room.
Ideally, I would be able to save a bunch of presets for each room or zone. As February turns to March I can 'step down' the various rooms as the temperature rises into spring without messing with the winter preset, then flip the switch to "spring" in April. Then as it starts to leave summer in September I can 'step up' the coldest rooms a bit until say, early November, when I could just activate the winter preset I put in place the year before, and then sit on those settings until Feb/march again.
This would be a huge time saver as each season turns.