history-graph: do not show a name if only ONE graph is displayed (like it was before 2022.6.1)

[ildar170975]

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.

Describe the issue you are experiencing

If only one sensor is used in history-graph - then do NOT show a sensor's name - like it was before 2022.6.

Starting from 2022.6.1:

Describe the behavior you expected

Was before:

the 2nd picture was taken from Web.

Steps to reproduce the issue

1. Add a history-graph with ONE sensor.

What version of Home Assistant Core has the issue?

20220.6.1

What was the last working version of Home Assistant Core?

2022.6

In which browser are you experiencing the issue with?

Chrome 102.0.5005.63

Which operating system are you using to run this browser?

Win10x64

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

No response

[ildar170975]

Before 2022.6:

In 2022.6:

In 2022.6.1:

As for me the initial design was much better: do NOT display a name if only one sensor is present.
Or make it customizable.

[ildar170975]

Yes, I do know about this:

But there is a useless space on the left.
And I cannot see a specified name in a popup tooltip.

[bdraco]

TLDR: This looks like it is working as originally designed, and was fixed in 2022.6 to do so.

This will restore the the lack of label.

diff --git a/src/panels/lovelace/cards/hui-history-graph-card.ts b/src/panels/lovelace/cards/hui-history-graph-card.ts
index a94a1b521..917002a94 100644
--- a/src/panels/lovelace/cards/hui-history-graph-card.ts
+++ b/src/panels/lovelace/cards/hui-history-graph-card.ts
@@ -144,7 +144,6 @@ export class HuiHistoryGraphCard extends LitElement implements LovelaceCard {
             .historyData=${this._stateHistory}
             .names=${this._names}
             up-to-now
-            no-single
           ></state-history-charts>
         </div>
       </ha-card>

However noSingle has been set since #4882 so this change looks like it was a bugfix and its now working as designed. Its also really confusing when you have multiple graphs if they don't have labels.

I don't think we should change it back but I'll ask other member's for a second opinion in case someone has a different opinion on this one.

[ildar170975]

Its also really confusing when you have multiple graphs if they don't have labels.

For me, the OLD design was perfect:

1. I usually placed a history-graph card with ONE sensor in the places where it was clear what sensor is displayed on the graph.
   There was NO need to display a name for the only sensor.
   Example (on your picture):
   

2. Also, it was useful to have a history-graph card with ONE sensor below a custom:mini-graph (described here):
   
   Surely these graphs may NOT be horizontally aligned in some cases (like between 00:00 & 01:00) but that was OK.

3. I also used a history-graph card with MANY sensors, it is RIGHT that names ARE displayed:
   

The ideal way could be adding an option:
show_name: true/false
whether to display a name or not (also, the name is always displayed in a tooltip).

[bdraco]

The ideal way could be adding an option:
show_name: true/false
whether to display a name or not (also, the name is always displayed in a tooltip).

That's probably the one way to accommodate the use cases here.

I didn't make this change so I don't fully understand the motivation behind it, and the above lands this into feature request territory so I'll wait for other members to comment on this as they haven't had a chance to weigh in.

[ildar170975]

Thank you very much for support!

[parautenbach]

I would give my support for a new setting like that. Like Ildar, I have also such use cases.

[github-actions]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[ildar170975]

Bump

[github-actions]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[ildar170975]

up

[spacegaier]

I agree that adding this option makes sense and is a low risk/effort thing. PR as a proposal is coming in a minute.