For me, this is resolved in the 2024.8.1 release. Thank you 
That’s weird because 2024.8.1 breaks the integration for just about everyone else.
There’s another update coming in 2024.8.2 that will hopefully fix it.
I get this too. If I try to slowly scroll, it does the looping you describe. If I scroll quickly, I can get out of the loop.
Thanks for the reply and for all the other ones. Actually there are about 5 issues with the same content on Github regarding this for the past 2 months since the new design was released.
Some issues also highlight accessibility issues with the new design by a user who has visual impairment and cannot adjust text size as he would like.
Of course, none of these issues has any input on them or acknowledgement that they are being worked on it.
Open source or not, but the website is the first thing what a new comer would look at before installing HA.
Same issue with old Daikin AC (with firmware 1.14.84)
The fix will be released with 2024.8.2 on the 16th.
2 Likes
New badges don’t work correctly for color control in some cases. I have garage door open/close sensor. I created two badges one for open and one for closed. I set the open icon to garage open, and garage closed to closed icon. Similarly, it set the color to yellow for open and green for closed. Then I set the visiblity for each badge based on open or closed . When the garage is open the open badge appears and color is yellow and the icon is open. When the garage is closed then icon is closed but the color is gray, not green. I have other sensors (3 states) for air quality sensor that work correctly for color control.
Doesn’t work
type: entity
entity: binary_sensor.garage_door_sensor_opening
icon: mdi:garage
display_type: complete
name: Garage
color: green ## <--- icon color is grey (Dark Theme)
visibility:
- condition: state
entity: binary_sensor.garage_door_sensor_opening
state: 'off'
Works
type: entity
entity: binary_sensor.garage_door_sensor_opening
icon: mdi:garage-open
display_type: complete
name: Garage
color: yellow
visibility:
- condition: state
entity: binary_sensor.garage_door_sensor_opening
state: 'on'
Also works
type: entity
entity: sensor.air_quality_result
display_type: complete
visibility:
- condition: state
entity: sensor.air_quality_result
state: Good
color: green
It would be better (not kludgey) not to have to use multiple badges and visibility control for different states of the same sensor for icon and color control
you should write that up as a Github issue in the Frontend repo. so the devs can have a look
(as you were asked to do by a Mod before your wrote this post…)
1 Like
OK did that. This post may get others to try to reproduce
After updating to v2024.8.0 I lost all my Xiaomi ZigBee devices (battery)
I run HA in a docker on my NAS and map my Zigbee USB stick (HUSBZB-1) into the container.
After the update alle devices of the following types are not available:
- XIAOMI mi Aqara doorsensors (13)
- XIAOMI mi Aqara climate sensor(1)
Other (power connected) zigbee devices are still operational:
- IKEA Tradfri zigbee repeaters
- IKEA Tradfri zigbee outlet switches
- PHILIPS Zigbee light strip
So in principle my zigbee stick is still working.
I tried to reconnect one of the door sensors again to my setup but get a different type of device:
seems to be a switch and not a door sensor any more. The sensor entity is not working either. Update to 2024.8.1 did not change anything.
Any suggestions what went wrong?
After the update, my Daikin integration stopped working.
My Daikin WiFi module is BRP069B41.
I did a rollback to 2024.7 and it worked again.
I see that there has been a change in the integration.
So I suppose something went wrong with this upgrade, can you check please, with this warm weather, this integration is certainly interesting to have.
It’s been mentioned and reported multiple times in this thread. A few posts up from yours, there’s even an expected date for the fix.
Thanks,
good thing that the backup/restore mechanism is working so good, just the energy dashboard stats going bad.
PSA: Users of custom front-end components BEWARE of this update. Especially if you’re using templating to express states / adapt your UI in some conditions.
I spent my entire weekend trying to fix what this broke, and ultimately rolled back to 2024.7.1 because of how bad of a state this put me in.
There are reports of this same issue popping up across this and other forums, but they all follow a similar pattern: If you’re using a Raspberry PI 3 or 4 with an external SSD, and have some HACS components for your dashboard (especially using templating) your host will become unresponsive randomly. You’ll have to manually pull the power and reboot it to bring it back online. It could be minutes, or hours, but once it starts it will not stop.
If you’re getting the dreaded “Connection lost” toast for seemingly no reason, and after reboot you’re seeing “The last session didn’t shut down cleanly” (or similar) save yourself some time and roll back to 2024.7.x.
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