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

Statistics graph Card layout bloated after #23576

Closed
3 of 4 tasks
digitalmagick opened this issue Jan 4, 2025 · 3 comments · Fixed by #23910
Closed
3 of 4 tasks

Statistics graph Card layout bloated after #23576

digitalmagick opened this issue Jan 4, 2025 · 3 comments · Fixed by #23910
Assignees

Comments

@digitalmagick
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

All dashboards involving a Statistics graph Card are now several screens long, useless, and the layout option thinks it's a tiny dot. Layout is broken for this card.

Describe the behavior you expected

The ability to have two next to each other, just as before. In previous versions the layout behaved adequately.

Steps to reproduce the issue

...
Use a home assistant dashboard with a Statistics graph Card.
Notice it's now MASSIVE

What version of Home Assistant Core has the issue?

2025.1.0

What was the last working version of Home Assistant Core?

2024.x.x

In which browser are you experiencing the issue with?

Chome, IE, Edge, Fully Kiosk Browser for android devices, browser dev tools, etc... This is not even remotely a browser issue

Which operating system are you using to run this browser?

HASSOS 14.1

State of relevant entities

Not relevant, changing these has no effect nor impact on appearance, nor were these changed.

Problem-relevant frontend configuration

Not relevant, changing these has no effect nor impact on appearance, nor were these changed.  
All attempted YAML configurations lead to the issue.  I cannot avoid the issue.

Javascript errors shown in your browser console/inspector

N/A

Additional information

No response

@ildar170975
Copy link
Contributor

ildar170975 commented Jan 4, 2025

The ability to have two next to each other, just as before. In previous versions the layout behaved adequately.

Here are four next to each other:
image

In 2025.1 some settings for graph cards were added to provide a minimal number of rows & columns to ensure a proper not-clipped & not too squeezed look. Means - you cannot place 10 graph cards into a narrow section.

@MindFreeze
Copy link
Contributor

What exactly is the issue? There is no screenshot and no explanation.

All dashboards involving a Statistics graph Card...

I have several without any issue so be specific, please

@VinceRMP
Copy link

VinceRMP commented Jan 8, 2025

I have the same "issue" and asked this question also during the beta.
https://discord.com/channels/330944238910963714/427516175237382144/1324304384095424522
My problem is that the minimum width is now 9. This breaks my config as shown in the attached image.
I use a section which is two width and when using precision mode this gives 24 steps to set the width of a card. In my setup I place 3 graphs besides eachother and each have a width of 8.
Now it breaks because of the minimum 9 as seen in the image.
image

The PR that added these minimum values was mainly because of the row issue if I understand correctly. So would it be possible to remove the limit of the columns or atleast make it in line width the section width?
A single section has 12 steps and a double 24 so the limit of 9 seems a bit weird?

For now I replaced the statistics card with the history graph one because that still works, but it would be nice if it could be fixed/changed.

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.

4 participants