“history-graph” card is not combining sensors with same unit on the same graph

[slowfellow]

I have a PM2.5 particle sensor (from Ikea) that has a unit µg/m³ and have created a threshold with the same unit to control an automation I have made. When I add these two entities to one history-graph the result is not one combined graph but two separate graphs.

I have tried following things to resolve this matter.

1. Added the following Status-attributes to the threshold-entity: unit_of_measurement: µg/m³ and device_class: pm25
2. Waited 24hours
3. Changed the values of the threshold and waited another 24 hours.
   So far no change.
   Can someone please help me with this issue?
   Thank you very much in advance!
   
   

[karwosts]

There are actually two different micro symbols in unicode that look nearly identical but use different codepoints, so if those two entities are using different micro symbols that might explain this.

Can you copy and paste the attributes here for both entities (not screenshots) to confirm? (Or you can check yourself).

[slowfellow]

all attributes:
sensor.luchtkwaliteitikea1_current_pm2_5

unit_of_measurement: μg/m³
device_class: pm25
icon: ""
friendly_name: LuchtkwaliteitIkea1 Current PM2.5

all attributes:
input_number.ventilation_pm2_5_threshold

initial: null
editable: true
min: 0
max: 200
step: 1
mode: slider
unit_of_measurement: µg/m³
icon: mdi:weather-dust
friendly_name: Ventilation PM2.5 Threshold
device_class: pm25

[karwosts]

Yeah I was correct, you actually have two different units there.

The first one is "μ" U+03BC: Greek Small Letter Mu (Unicode Character) , and the second one is "µ" U+00B5: Micro Sign (Unicode Character)

[slowfellow]

@slowfellow

μg/m³

Wow seems like you’re absolutely right… they look almost identical but are not:

µg/m³ vs μg/m³
\u00b5 vs \u03bc unicode
µ μ ascii

This issue was driving me crazy. thank you so much for solving this!