Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More-info dialog is slow and laggy after update to 2025.1.0 #23584

Closed
3 of 4 tasks
drogenlied opened this issue Jan 5, 2025 · 4 comments · Fixed by #23619
Closed
3 of 4 tasks

More-info dialog is slow and laggy after update to 2025.1.0 #23584

drogenlied opened this issue Jan 5, 2025 · 4 comments · Fixed by #23619
Assignees

Comments

@drogenlied
Copy link

Checklist

  • I have updated to the latest available Home Assistant version.
  • I have cleared the cache of my browser.
  • I have tried a different browser to see if it is related to my browser.
  • I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.

Describe the issue you are experiencing

After updating to 2025.1.0, graphs that are opened from an entity on the dashboard, for example a temperature or humidity graph, are an unpleasant experience.
The opened graph lags, flashes and redraws multiple times over 1-2 seconds until it has reached the end of its opening animation and its final size.

Checked in Chromium 131 and Firefox 133 on Thinkpad X1 Yoga Gen7.

Describe the behavior you expected

Graphs should open like before 2025.1.0, no animation and in less than 500ms, or better less than 300ms.

Steps to reproduce the issue

  1. Update to 2025.1.0
  2. (maybe optional) Use laptop with 4k screen and Intel Xe graphics.
  3. Enjoy the laggy web UI after clicking on a temperature entity on your dashboard to see the graph.

What version of Home Assistant Core has the issue?

2025.1.0

What was the last working version of Home Assistant Core?

2024.12.1

In which browser are you experiencing the issue with?

Chromium 131, Firefox 133

Which operating system are you using to run this browser?

Debian Linux Unstable

State of relevant entities

Entities are displayed fine, dashboard is fine, pop-up graph is laggy and slow.
See configuration below for an example where the graph is especially badly lagging.

Problem-relevant frontend configuration

type: entities
entities:
  - entity: sensor.d1_sensors_bme280_temperature
  - entity: sensor.d1_sensors_bme280_dewpoint
  - entity: sensor.d1_sensors_bme280_humidity
  - entity: sensor.d1_sensors_bme280_pressure
title: Dachboden

Javascript errors shown in your browser console/inspector

None

Additional information

It seems that a lot of animations were either introduced in 2025.1 or they are way slower and they make the web frontend less nice to use, it is not snappy anymore but laggy and you have to wait for seconds before elements have stopped moving around, redrawing and lagging.

@bramkragten
Copy link
Member

bramkragten commented Jan 6, 2025

This is probably because of the added animations in graphs @MindFreeze

@MindFreeze
Copy link
Contributor

I haven't been able to reproduce this but it seems to be caused by the dialog animation resizing the chart.
@drogenlied Do you this lagginess in the other charts, like the history page, or just in the more-info dialog?

@drogenlied
Copy link
Author

On the history page, the animation is smooth, although I still find it annoying that the graph is animated when adding a new entity. It is simply another second of my time that is being wasted.

@MindFreeze MindFreeze changed the title Frontend is slow and laggy after update to 2025.1.0 More-info dialog is slow and laggy after update to 2025.1.0 Jan 7, 2025
@drogenlied
Copy link
Author

Found another funny behaviour related to the more-info dialog, resizing on open can interact with the graph tooltip, creating an infinite resize loop:

Bildschirmaufnahme_20250109_164605.webm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants