your using type: entity here, so that is not the old/legacy badge
Card-mod may be definitely broken since a “new badge” is a DIFFERENT element.
Not an issue, just a matter of adapting a user’s config to the new reality.
1 Like
I know, I posted the original code, the changed code already includes
type: custom:hui-state-badge-element
Changed the original post also :).
2 Likes
well its as Ildar says, move to card-mod thread, and let’s find the correct Dom path to the property you want to modify. Its a new (legacy) kid on the block, we need some new examples in the Main thread probably
or start experimenting with the new badges, as that is the real new shiny kid on the block, you might even start liking it 
3 Likes
So, is there any solution for styling?
Can you post code of one of yours custom:hui-state-badge-element badge?
About this:
Sort data tables by created or last modified
I find this feature very very useful.
My old WTH.
Since I have not installed .8 yet - I wonder are these new fields “created” & “modified” became accessible as attributes? (for entities & devices)
I’m experiencing issues with the Reolink integration where my doorbell and camera’s have de-authenticated.
The issue seems to be the lacking support for special characters in the passwords for specific device logins. (specifically ^, % and & characters as far as I can tell) All special characters are supported on the devices themselves.
1 Like
Just updated to 2024.8.0 and it broke my Alexa Media Player integration. Does anyone else have problems with this?
2 Likes
I like the new badges very much, but from functional point of view I really need the colors of them to be customised based on conditions. If the new badges would offer this functionality out of the box, I would gladly use them 
.
1 Like
Someone wrote that in the livechat of the releaseparty too. I haven’t upgraded yet because of this.
No dragons, uh? 
I am afraid this has worsened the existing issues on the Entities and Helper pages.
They have become so feature rich, and all of these details are stored in the browser. And reevaluated upon state changes.
It’s no longer as lightweight as it was before, and in my case, I cant even load Entities anymore.
Adding the Yaml template entities to the Helpers seems great.
Whether the constant state changes of these templates dont hurt the /config/helpers, I am not yet convinced…
But the idea is great indeed, very useful.
2 Likes
No dragons 
1 Like
I posted the code (which is not working) above in my question, as I’m also looking for a solution - none found one yet, unfortunately.
they probably wont support templating out of the box, but ofc you can use the state-colors in themes.
Im sure that anytime soon, people will start to try and card-mod them like you wish, so give it some time.
1 Like
I do not think that a change of a state should be considered as a CHANGE.
And I never desired this.
For me, the CHANGES are like “user changed smth in more-info”, “user chaged yaml → caused a change of icon, template etc”.
Having a table of 5000 entities sorted by “changed” & redrawn on every change of “states” object is nonsense.
3 Likes
If it didn’t update based on state changes the UI would never show new values…
we are not sure, but please read what Karwosts wrote about the inner workings of the Frontend on those pages. Its in the link I posted on Entities
1 Like
exactly, and since the template entities are now added, this might very well be weighing in extra
seems to be a known issue…check the custom component’s GitHub page for details
(it’s not a Core issue)
see here config_flow.py line 815: `hass_url` undefined · Issue #2408 · alandtse/alexa_media_player · GitHub
1 Like