Two entities in a lovelace history graph display separately

Configuration Frontend
1

Hi all

I have one history card in my lovelace that is displaying its contents strangely. Generally (and as expected) most of my history cards plot multiple entries on the same axis (within a single card)—like this:
history1

However, I have one card that creates a separate set of axis for each entity—like this:

history2
history2593×551 17.4 KB

I note that the configuration is virtually identical for both cards (and I have tested to see whether using plain sensor string rather than entities makes any difference—it doesn’t).

Truncated config is as follows (its actual part of a vertical stack—and I’m using the Config UI rather than lovelace.yaml, hence the weird order):

  - entities:
      - entity: sensor.daily_power_solar
        name: Solar
      - entity: sensor.daily_power_solcast
        name: SolCast
    hours_to_show: 168
    refresh_interval: 120
    type: history-graph

Does anyone have suggestions as to what might be causing this?

2

You entities have different unit_of_measurements (kw and kwh).

4 Likes
3

Good catch! Much appreciated–it should be same units; I’m check my sensor setup to try to fix it.

4

Is there a fix for this?

There are definitely times where you want to graph two different pieces of data on top of each other, like Lux over temperature, to visualize how ambient daylight affects the temperature of a room, or humidity over temperature, to visualize how the outdoor temperature is affecting the humidity of inside of the house.

Being able to denote two different units and scales on the same singular y-axis seems like a fairly basic feature of creating a graph, to me. It seems kind of silly and inconsistent that you can compare the two when the units are the same, but not when the units are different.

5

Use a custom card which supports two different Y axis.