[New feature request] Please keep the card lean

[sigmazetato]

I find this project remarkable and have been using it since the very first versions.
It’s a great and, above all, lightweight tool for controlling your climate based on time and events.
I believe it should stay that way — lean and focused on the essential functions for time‑based control.

It cannot be the card’s job to cover every possible control scenario that anyone could implement in Home Assistant using automations.
Home Assistant already provides all the necessary tools; you just have to build it yourself or use suitable blueprints.
The only thing that would be desirable is the ability to use all card functions from within automations.

By the way, two wishes:

The ability to reorder the temperature colors, just like it works for rooms.

Support for the HA Season Sensor to setting the season automaticly.

Silly question: Where on earth is the season setting? I couldn’t find it anywhere on the card :-/

[github-actions]

Checked version: repo=qlerup/thermostat-pro-timeline, status=missing

Hi! I couldn't find a version number in the issue description.
Please reply with the version you're running in X.Y.Z format (e.g. 3.1.1) or with a v prefix (e.g. v3.1.1).

Thanks 🙏

[sigmazetato]

3.2.0

[github-actions]

Checked version: repo=qlerup/thermostat-pro-timeline, reported=3.2.0, latest=3.2.0, status=latest

Thanks! Your version looks up to date ✅

• You have: 3.2.0 ✅
• Latest release: 3.2.0 — https://github.com/qlerup/thermostat-pro-timeline/releases/tag/v3.2.0

If the issue still happens, please share steps to reproduce and any relevant logs/screenshots. 🙏

[m-emy]

Hi! I completely agree with you that the project should remain simple

However, I think adding additional features (especially if they are optional and disabled by default) wouldn’t burden the experience for those who want simplicity. If someone doesn’t need them, they simply won’t enable them, and the interface will remain as minimalist as it is now

Personally, I requested extra functions precisely because this integration offers a huge advantage: a very simple visual interface, which is missing “by default” in Home Assistant. Yes, you can build automations and use blueprints, but for many users (or for people around me) it’s difficult to create them, understand them, and especially modify them correctly over time. Having a clear UI option that can be easily enabled/disabled would be a huge benefit

It would be useful even for me: at home there are other people who want to adjust values/modes without going into automations and without the risk of breaking something

And by the way, I also agree with your two proposals:
the ability to reorder the temperature colors (like it works for rooms)
support for the HA Season Sensor to automatically set the season

[qlerup]

Thanks for the kind words, both of you! This was my first real card on Home assistent, and I learned alot on the Way, and how Home assistent works (still learning).

Thes card/integration is growing fast, and sometimes, there will be errors on the Way.

It started as a card only with around 1000 lines of code, now it have so many features, that the integration + card has over 35.000 - 40.000 lines of code together. 😅

I Will take a peak into this.

What is the entity name of that? And how do I get it, it will be smart of the winter/summer Can toggle between automatic.

[sigmazetato]

Hi,

credit where credit is due :-)

Regarding the question about the entity:
Just like the well‑known integrations — or according to the new terminology, “apps” — such as:
Sun: https://www.home-assistant.io/integrations/sun/
and
Moon: https://www.home-assistant.io/integrations/moon/

there are also:
Season: https://www.home-assistant.io/integrations/season/
Holiday: https://www.home-assistant.io/integrations/holiday/
(This refers not to vacations but to holidays like Easter, Christmas, or other national holidays — I also use it for the pro‑timeline.)
Workday: https://www.home-assistant.io/integrations/workday/

These three are great for controlling climate hardware.
I hope that was helpful.

[sigmazetato]

Hmmm,

I understand your reasons for your argument, but consider this:
The more features an application has, the more its complexity increases.
That means — and this is pure statistics and experience — with every change, the likelihood of introducing errors rises.
There’s a reason why the principle of “keep it simple” has always been used in engineering, and in IT especially the idea of microservices has proven successful.
Hiding functions in the UI doesn’t help either — the code and the complexity are still there.
So my point is mainly driven by the desire to keep the code complexity as low as possible.

I already find the complexity of the application quite high, including configuration and display options. It’s slowly becoming difficult to navigate all the available settings.
And some features are not implemented consistently, probably because they got lost along the way — for example the automatic backup:
You can enter an interval greater than 1, but only 1 backup is ever stored.
And unfortunately, no automatic backup is performed — at least not for me.
And if an automatic backup is implemented, there should also be a function to limit the number of backups, otherwise the backup file — yes, it’s just one big file — will grow without limits.
I haven’t mentioned this before because I have my own working backup concept, but the issue is still there.

Home Assistant lives from its users. Every new personal solution brings experiences that flow back into the community.
In fact, personal engagement with problems and solutions is one of the fundamental pillars of Home Assistant’s existence.
Of course, not everyone can build integrations or blueprints — I can’t either. But everyone can still share experiences and solutions.
Engaging with the system, searching for solutions, sharing automations or YAML snippets, or giving tips for system operation — that’s what helps all of us.
Not wanting to engage with the system and therefore expecting others to create complex adjustments means shifting work onto others that you could do yourself if you wanted to.
And for simple operation, you build simple dashboards — that’s a basic skill every user should have.
And if you did something wrong: that’s what backup/restore is for.

HA is not a pure consumer product — that’s simply impossible because it’s not a trivial system. It is actually quite a complex system.
I see this again and again in forum posts when the system has issues and pure consumers don’t even understand how HA works or what to do when the system doesn’t start.

I believe a Home Assistant user should make the effort to understand the system, the applications, and the YAML code, because only then can the full potential of Home Assistant be unlocked.
If that’s not possible, I gladly recommend Homey Pro to pure consumer users as a “ready to use” solution. That was my first solution too, but I couldn’t tinker in the engine room as much as I can with Home Assistant.

Please don’t get me wrong — I don’t want to start a debate here. But this issue is discussed frequently in HA forums in one form or another, and in the end it always turns out that statements like:
“It’s difficult to understand something, to change something, or I’m afraid of breaking something”
are not justified at all — because if that’s the case, then Home Assistant is simply the wrong tool.