Energy dashboard display issue for solar production since 2025.2.0

[jmcruvellier]

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

When comparing data, "holes" appear (maybe related to the display animation?):

Describe the behavior you expected

Expected correct display as in previous releases

Steps to reproduce the issue

1. Open energy dashboard
2. Tick "Compare" in menu

What version of Home Assistant Core has the issue?

2025.2.0

What was the last working version of Home Assistant Core?

2025.1.4

In which browser are you experiencing the issue?

Google Chrome Version 133.0.6943.54 (Build officiel) (64 bits)

Which operating system are you using to run this browser?

Windows 11

State of relevant entities

Problem-relevant frontend configuration

Javascript errors shown in your browser console/inspector

Additional information

No response

[nacree]

A bit similar issue with rendering the different consumptions, but instead having holes there, the "unfollowed consumption" is rendered on the top of the other.

[hmmbob]

Are you by any chance using a custom theme?

[jmcruvellier]

Are you by any chance using a custom theme?

Yes, but same issue when using default HA theme

[hmmbob]

ok.

I was asking because during beta we've seen that setting --disabled-text-color (and to lesser extend, --state-unavailable-color) seemed to mess up the graphs. The normal HA theme did not have this issue though.

[karwosts]

Possible duplicate of #24091, not sure.

[jmcruvellier]

Possible duplicate of #24091, not sure.

Yes but it was for the beta and was closed. I'm having the issue on the release version.

[karwosts]

Yes but it was for the beta and was closed. I'm having the issue on the release version.

It wasn't fixed during the beta, it was fixed just yesterday and the fix isn't released yet. So it's possible that will fix this once it gets released.

[jmcruvellier]

Yes but it was for the beta and was closed. I'm having the issue on the release version.

It wasn't fixed during the beta, it was fixed just yesterday and the fix isn't released yet. So it's possible that will fix this once it gets released.

That's correct 😉