HA Core 2025.1 entities card mod styling broken

Configuration Frontend
1

Hi all,
with update to core 2025.1 all my row related styling in entities cards are gone.
example of earlier working code:

type: entities
card_mod:
  style:
    .: |
      ha-card {
        background: #d2d2d2;
        border-top-right-radius: 0px !important;
        border-color: transparent !important;
      }
entities:
  - type: custom:template-entity-row
    entity: sensor.sjenica_pressure
    card_mod:
      style: |
        * {height: 16px !important; border-bottom: solid 1px rgba(255, 255, 255, 0.5);}
    name: Sjenica

This is how it looks before 2025.1
entities_2024
This is how it looks now:

entities_2025
entities_2025425Ă—650 22.7 KB

This code works for years ago, and now, suddenly, after loading fronted 20250103.0 all entity (row) styling stop working.
Styling of whole card works.
Do anybody know something about?
Best regards and happy new year!

2

Same here. Update today. Card Mod is gone:-(
An one with ideas?
Thanks in advance.

3

Until some kind of solution, I moved back to 2024.12.5, because most of my dashbords are ruined.
Btw, such frontend breakdowns happens to often. Developement is needed, but backwards compatibility is too. In this way, users with customized UI are every couple of months forced to rewrite their site. In my opinion… unacceptable.

4

I understand it’s a PITA, but you can’t really expect HA developers to ensure backward compatibility with 3rd party (hacky) components…

1 Like
5

Again such arguments. My Dear. Because the devs know which components are mostly used, here card mod. Since years and with a lot of efforts. And then they can easily check if not everything is ruined with quick changes which are perhaps possible in a better way as well. But they didn’t react even on questions in beta phase, what and why they changed something. This is ignoring a lot of users.

2 Likes
6

While I was writting, @arganto said exactly what I wanted.
In contrary, I’ll expect that commonly used “third party”, or “hacky” components included in main stream.

7

It’s not an argument, it’s a fact.

You are welcome to dream of a better world, but “unacceptable” is definitively a too strong word in this context.

1 Like
8

Well, I can agree… partially. But, don’t you think that frustrated user will drop whole project, and than, when enough such drops happens, this project will die.
So, main line is: If you can’t help, please, don’t defend the SNAFU situations, just skip the post.
Thank you very much.

9

I can help by pointing you to the related card-mod issue:

The issue was reported before the release, but not acted upon by the card-mod devs.
Actually, the last change to card-mod dates from March.

10

Thank you very much. Even better… the issue was known in beta, and still is rolled out as release. I read release notes carefully before updated, and there was no mention of such breakdown. I don’t kow what to say.

11

Once again, 3rd party integrations are not tested by HA devs, and won’t appear in any way in HA release changelogs. The issue was opened by a user like you, nothing indicates that HA devs were even informed.

1 Like
12

card_mod is a very popular “hacky” 3rd party integration! My gui is not that complex and I use it in several places.

13

I’m dreaming of a more considerate world.

Esp. if there where feedback in beta Discord already, where not even was a real response or where this was taken into account. Without that unnecessarily thousands of user setups are kicked with feet only because of most probably (this way) not needed changes.

14

Welcome to a real world where new backup feature causes a negative reaction even from users who personally you do respect. Defending devs blindly - until personally YOUR interests are affected.

Calling a plugin as “hacky” may be considered as rather insulting since tons of users use it & contribute solutions. You do not use - ok, but many people do.
As for “this plugin was not updated since xxxx” - there are many still working plugins which were not updated for a long time.

3 Likes
15

@Ildar_Gabdullin you are right!
This plugin give us a chance to to customize and enhance UI elements and it is around long time.
Why don’t save some space and show more important informations in form of colors of fonts, borders etc.
This plugin is essential in my opinion.
Last time, when badges on top of page was “upgraded” I was in same situation. Many views was unusable, but then I found alternative and replaced badges with mushroom chips.
Now is situation much worse, because there is no replacement for entities card on which I heavily depend.
Very, very disappointing.

16

Hope we will find a way.
Like we found a way to resurrect old-style badges & card-mod them. (although I am not using badges at all)

1 Like
17

Although I understand card_mod is used by many, I also can understand that a release cannot be held up because a custom card_mod no longer functions on a custom:template-entity-row. The devs have no control over either custom component. Both are not part of core. If they need to wait on all bugs in custom components, they could never ever release. Not could they list every issue with them. It is the risk of using custom components. For integrations there are even warnings telling you so in the logs.

Problems with custom components are the responsibility of the custom component code owner. And even then, it is at their discretion to decide if and when they fix is. You got it for free. They were built in peoples spare time.

18

@Edwin_D , agree to disagree.
So many times, especially frontend is changed mercilessly, without a bit of care of backward compatibility. If i.e. linux kernel is maintaned and developed in this way, there will be no linux at all.

19

This is not the problem here. card_mod is not working because of (no one knows and most probably not necessary (this way)) changed on core row part, which are reused everywhere. I would wonder if the changes (for whatever they were) could be done in a more considerate way, that card_mod is still working.

20

ahh that why. just wait for card mod to update then.