Our supported theme variables are documented here:
https://www.home-assistant.io/integrations/frontend/#supported-theme-variables
Anything else you customize is not supported and isn’t considered (we do try to minimize, but it isn’t a priority). Building a custom card is the way to go if you want a different look and feel. That way, you decide.
The cards provided by Home Assistant will always aim at providing the best experience for the larger part of users.
…/Frenck
I am not capable of building a custom card, Frenck.
I just want the choice of using a tile like thermostat card or the old one, surely that’s not a big ask.
You can, that has been introduced a few release back.
That one has been replaced, as per above.
Right, but there are more choices available out there, that might be a better fit for your specific use case in that case. Maybe someone wants to make a custom card out of the old card? 
There speaks a politician who chooses sound bites out of context.
but thanks for you responses - but they do not answer my question as to why there isn’t a choice of the old card in the standard cards. As I said it shouldn’t be a big ask.
It is actually, many mis that part. There are many considerations for keeping that around. For example, support, maintenance, keeping it working, fixing bugs and many more things.
In this case, we decided not to take that burden and upgrade the existing card to a level that is functional the same, but uses the new and much requested, styling (and even has more features available).
Jup, checked but it not physically possible to add Features in the current state/afterwards. Editing does not show the Add Features, only when creating a new card…
The old card has been removed. The new design is much nicer IMO.
You have two choices to get what you want:
Use the new card and enable the features you want, like HVAC modes (from the UI, very easy).
Use the tile thermostat card.
Thanks, I’ll look into your suggestion of using the tile thermostat card. But IMHO i don’t like the pastel colours and it would mean a big redesign of all my dashboards to accommodate just one dictated change!
The new functions from the UI are irrelevant when comparing the cards. And the labels don’t show the same info. So they are not equivalent functionally as far as i can see.
Add this to a theme:
state-climate-auto-color: '#ff8000' # orange
state-climate-cool-color: '#039be5' # blue
state-climate-dry-color: '#e0b400' # yellow
state-climate-fan_only-color: '#0da035' # green
state-climate-heat-color: '#e45e65' # red
state-climate-heat-cool-color: '#b200ff' # purple
state-climate-idle-color: '#395274' # dark blue-grey
Change the colours to what you like.
Very easy update for me BTW. Slightly faster restart too.
Just one backend change - delete the ping yaml and restart.
And one frontend change - add the climate features to my climate cards.
Thanks devs and beta testing team.
Is there a way to disable the new login page? I have HASS behind a load balancer, and now it’s showing that login page even when I’m logging in externally and am not on my internal network.
When will the energy dashboard issue be addressed. Energy dashboard is not calculating the consumed solar if the solar battery is charged from the grid.
This issue is known for more than 3 years and it still not been addressed.
This statement IS confusing for people.
LTS only keeps data which are defined as “keep me in LTS”.
Many data are not stored in LTS (either by its nature - or because a user decided no to keep them in LTS) - and a user will never see them in the new “augmented History view” for long past periods.
So, if a user does need a REAL data (i.e. not interpolated etc; not to mention non-numerical values) for a LONG period (> than default “10 days”) - he would definitely change that “purge_keep_days” Recorder setting to a higher value.
The initial idea “let’s show LTS on History view” has nothing about “no need to revise purge_keep_days”. The new augmented History view (as you said yourself) is only a UI feature to see data in a more convenient way.
It turns out that my load balancer wasn’t adding the x-forwarded-for header properly. I’ve fixed that, and now I’m getting the external login page as expected.
I noticed that the internal view of the new login page is also shown on my external endpoint. I have currently a layer 4 load balancer in front of my external access so Home Assistant does not know the external IP. I would say that it should be possible to disable the tile based login screen entirely, but I could not find any information on this yet. To prevent any privacy problems I had to turn off external access in order to gain some time to find out what to with this.
From a process standpoint I’m not too happy on how this new feature is pushed in this release. I would be better to warn users that the external view will not work in some cases and that there is an option to disable this new page (as stated before).
All my sensor using BLE, and I mean ALL of them changed entity names with the release. Did I miss something, is that intentional?
Same goes for my shelly devices. Dashboard, automations, all need to be reconfigured…
Please tell me that this automatic login is optional and can be switched off? There is no such thing as a Trusted Network since 1980.
On the margin of the new thermostat card:
We have seen some great variants in the release party, but it is not documented anywhere. (Especially, not here)
My problem is that I’ve lost my dual target temperature (low / high) according to the mqtt hvac (climate) integration. As of now (/by default?), only the low (first) value is visible. Is there any guide how to bring it back? is it possible as of now?
I think I’ll freeze my HA version at 2023/11.
My issue is with the new login screen. Look, I understand why Amazon wants to persist your login. They don’t want anything to be in between you and the buy now button.
But HA has access to unlock my front door, open my garage door, and watch my camera feeds. I would like that level of access to be somewhat more protected, than buying someting on Amazon.
I think more effort needs to be put on adding the biometrics, and 2FA. It’s good to see that such effort is under way, even though you didn’t mention Android being part of that effort.
But I had hoped, that this effort was given priority over beautifying the login screen. Especially the passkey feature that Frank mentioned.
My banking app asks for authentication when I open it. So does my password manager. There are good reasons for why they do that.
I hope that on the scale between the convenience and security, that HA will lean a bit more to the security side.
No automatic login was added. If you don’t have trusted networks set up you still need to log in.
You still need to tick the “Keep me logged in” box if you want the login to persist if you don’t have trusted networks set up.