WTH no sections in history graph card

Month of "What the heck?!"
1

Why can’t you add section lines/labels in the history graph card, like you can with entity card?

2

I’m having trouble visualising what you mean by this. Can you post a mock-up screen shot?

3

Here is an example, using the section labels from the standard entity cards mixed with the history graph cards. Separates various motion sensor histories based on which systems are providing the sensor values.

History-Entity-Sections-Example
History-Entity-Sections-Example3196×1450 208 KB

And the associated Lovelace yaml:

type: history-graph
entities:
  - entity: binary_sensor.motion_sensors
    name: All
  - type: section
    label: ADT
  - entity: binary_sensor.adt_motion_sensors
    name: ADT
  - entity: binary_sensor.north_warehouse_motion
    name: XXX
  - entity: binary_sensor.south_warehouse_motion
    name: XXX
  - entity: binary_sensor.south_office_motion
    name: Entry
  - entity: binary_sensor.north_office_motion
    name: Office
  - type: section
    label: Tasmota
  - entity: binary_sensor.tasmota_motion_sensors
    name: Tasmota
  - type: section
    label: Frigate
  - entity: binary_sensor.frigate_motion_sensors
    name: Frigate
  - entity: switch.XXX_dome_motion
    name: Dome
  - entity: binary_sensor.XXX_entry_motion
    name: Entry
  - entity: binary_sensor.XXX_corner_motion
    name: Corner
  - entity: binary_sensor.XXX_dome_motion
    name: XXX Dome
  - entity: binary_sensor.XXX_entry_motion
    name: XXX Entry
hours_to_show: 8
title: Motion
refresh_interval: 60
1 Like
4

If you do this as separate history graph cards the problem is that the timelines do not match up since the width of each bar is dynamically adjusted based on the text length of the name displayed on each sensor line.

5

Yeah I’ve got a similar issue with the history-graph, but on mine I’m displaying an input_select and a sensor value. The timelines don’t align as the input_select line doesn’t start at the same position as the sensor graph, due to the text.