Can I only display the date/day without the hours for daily graphs that use group by date?

[thewan056]

For my daily graphs, such as a daily power consumption graph, can I hide the time shown for each point? For example if I hover over the first point I would like it to only say 1 Mon, instead of 1 Mon, 12.00AM - 1 Mon, 11.59PM. Or maybe if its on the same day, do not show the day and date twice, like 1 Mon, 12.00AM - 11.59PM. I'm trying to reduce clutter. This would also apply to extrema if possible. Since I do not really care what time that data point was collected as long as it was on that day.

[ildar170975]

If you are asking about a new functionality - suggest to prepare a more detailed description of logic (technical assignment for a developer).

[thewan056]

If you are asking about a new functionality - suggest to prepare a more detailed description of logic (technical assignment for a developer).

As there is no guideline on what do you exactly mean by a "more detailed description of logic", I'm afraid I can't prepare one.
I would gladly attempt to prepare one if there was some guidance or template given to me as I am not a very technical person.
There was no template provided during the issue submission like what some other repos do.

The reason why my post is simple is that I do not know whether or not does my question require a new feature implemented, or it is something that can be worked around with card mod for example, or maybe someone already implemented it through a fork. I did a search through issues and didn't find any similar questions.

[ildar170975]

Guidelines are not provided here since a technical assignment is a matter supposed to be learned as a part of technical education. Since people have a very different level of it - we may observe a situation “we asked for XYZ, got ABC”.
In short, assignment should contain a complete description of functionality; a developer should understand it clearly. Ofc some discussion between an “asked” and a “maker” is required; but initially the task should be defined as clear as possible on the 1st step - to reduce amount of time for implementation and reduce a probability of a wrong implementation. And ofc a developer should ask questions , should not be too self-confident.
This is a very short explanation.

[thewan056]

Ah I see. Thanks for the explanation.
I apologize. Because my previous experiences when it comes to feature requests or reporting issues in general is that if I pretend to be too technical or smart, when I am actually not, by posting too much information, people seem to just brush me off or ignore my post.
So I am trying to fix my habit of putting in too much, maybe unnecessary information, by following guidelines or templates strictly if there is one, or if there is not, try to keep my post as simple as possible and only post more specific information when requested, provided the request was clear what is needed. Like requests for a screenshot, logs, code, flow chart, etc.

I have created some screenshots showing what i want to achieve and i hope it is enough:

Before:

After:

After Alternative:

I chose a single graph to make it easier to see what I want. The real issue with clutter is when 2 or 3 graph are side by side when it gets really hard to read and also it doesn't look nice.
example:

By just showing the day/date only would greatly make the graphs more readable in a compact situation.

[ildar170975]

@thewan056
What do you think?

1. When displaying a time interval for selected point:
   if left & right bounds are from the same date - display a date only once:
   currently:
   19 Fri, 20:14 - 19 Fri, 22:13
   proposed:
   19 Fri, 20:14 - 22:13

type: custom:mini-graph-card
entities:
  - entity: sensor.xiaomi_cg_1_co2
hours_to_show: 48
hour24: true

2. Regarding extrema. What you suggested was "do not show time, only date".
   The easiest which may be proposed is:
   add an option like omit_time_for_extrema (default false): if true - then show only a date, w/o time.
   But imho in a perfect world for both kind of labels - for extrema, for selected points - a kind of format_datetime options should be provided. For instance, someone may not like 19 Fri in labels, he prefers 19.01.24.