2024.8: Beautiful badges!

Hi, I see in your snapshot that the the “Current garden temperature” shows “30.3”. Is that defined as a temperature in °C? Didn’t it show “30.3 °C” instead of “30.3” in release 2024.7? is this issue affecting only me?
In my case all the states of the entities are shown as raw data in the cards of the dashboard, for example date/time is shown in ISO Format, not in human readable local time.
Thanks for your attention

Can anyone else confirm this is true? And if so, have you looked at CPU utilization? Mine jumped from about 50% to 75-80% a few releases ago. If that were to happen again it would probably cause this symptom. It would be good to know the actual cause.

cant confirm what DT states above, probably fake news coming from Donald, but there have been increasing issues in the /config/entities and /config/helpers page, and a very noticeable lag increase in the Frontend altogether.

Not sure what the reason is for the latter, but the first 2 we have been debugging with the team, and this PR is pending Adds throttler to config pages for state entity updates by silamon · Pull Request #21646 · home-assistant/frontend · GitHub

please read the reasoning behind it, and the issues that reported it, it seems the front-end couldn’t keep up with the constant re-evaluation of state changes.
The fact the yaml configs, templates mainly in my setup, were added to the helpers (the ofc already were in entities) cant have helped… although that has not been acknowledged officially.

4 Likes

@Redpizza @corby the display precision only affects the display precision of the temperature in the UI, it does not affect attributes which is what you’ve highlighted in the screenshots.

1 Like

I meant that the 2024.8 broke all my entity display, not only the numeric precision.
But I understand that it happened only to me.
I don’t know why. For now I rolled back to 2024.7.
Thanks for your replay

Pretty sure someone had this issue a little while back and it was browser refresh/cache, did you try that ?

Great… but… Daikin AC are not working after update to 2024.8.1 · Issue #123550 · home-assistant/core (github.com)

Yes, this has been mentioned multiple times in the thread. It’s also been mentioned that a fix will be out August 16th.

2 Likes

Unless you are running something quite intensive or doing something like video processing thats likely an indication that something is wrong.

Is it possible to animate the Custom: Mushroom Template Badge icon?

Nevermind I figured it out (Use the manual option!)

Oh I looked under every rock that I’m technically qualified to explore. Unfortunately there wasn’t a clear root cause or fix that I can suggest. My CPU would spike right after the host became unresponsive (fan would really start going) but prior to that my utilizaton rested around 8% and RAM sat around 1.5gb (out of 4).

Don’t take my word for it, check out this thread: PSA: 2024.7 recorder problems

OP in that thread cites 2 issues. The second of which remains unresolved and I strongly suspect is what caused my shit to grind to a halt. I have a lot of front end customization and use templating to express states in components like custom button card. I’m becoming convinced that 2028.8 is just going nuts and constantly re-evaluating templates, locking the system up and causing it to crash.

That suspicion comes from digging in that thread after exhausting other options to the best of my ability. I found that my host would stay online for hours, but would always shit the bed within minutes of tapping something on one of my wall mounted dashboards.

Thats all I can share. I wish I had more, but that thread is echoed in a few places and kept me sane this weekend. I never had issues like this before the update and rolling back clearly fixed then, system has been online flawlessly since.

I want to add that I have had problems since 2024.8, and I never have problems. I have a very stable system, strong hardware, I’ve been very satisfied and have not needed to tinker much. I do not do the extensive templating that you do, but I’ve also had strange things happening that NEVER happened before. Lights remaining on after they were switched off. Tablet freezing up, lots of fully kiosk errors. Views on tablet that when selected, fail to draw on the screen. Lots of disconnect errors for no apparent reason. Launch the companion app, and just a blank screen. Right now since my last reboot of router, tablet and NUC, it’s perfect, responsive and stable. But after a few days, it glitches. I’m just hoping someone finds there is a widespread problem so it can be addressed.

3 Likes

Simpler? Means there is a way?
Can you share how? Thank you

Change icon and color.

EDITED: sorry… I forgot to say I have mushroom card installed

image image

type: custom:mushroom-template-badge
entity: light.esquina
content: Esquina
icon: |-
  {% if is_state('light.esquina','on') %}
    mdi:lightbulb
  {% else %}
    mdi:lightbulb-outline
  {% endif %}
color: |-
  {% if is_state('light.esquina','on') %}
    rgb(0,255,0)
  {% else %}
    rgb(100,100,100)
  {% endif %}
tap_action:
  action: toggle

Update keeps rolling back with no issues in logs.

Reattempt to update fails, reverts after twenty minutes, and shows update available.

Any context or fix expected?

(Edit: No I am not using recorder. I am using the default SQLite)

Yet no logs.

For me it’s not the case. I’m using Raspberry Pi 4 (supervised install on Raspbian) with SSD and HACS and a bunch of customisations and templates in frontend, but everything works as before (I only lost my precious heavy customised old-style badges :smiley: ). Also CPU runs under 10% most of the time with occasional spikes up to 44%.

1 Like

@corby I can confirm that the degrees centigrade symbol has re-appeared, and the display precision is now working correctly, after a reboot.

Thanks all.

Yes, I confirm! I’ve just re-updated with 2024.8.1. All entities show the unit of measure and date/time is correctly displayed. It was probably a metter of browser cache, as suggested by Holdestmade. I don’t have any entity with more than one digit precision but they are shown according the display precision set (like 30.2 °C; 224 V; 34.70% )
Thanks you all guys for your advice and support.