Temp Conversion not consistent across cards

[jeeftor (Jeef)]

I’m w wondering about auto C->F temp conversion. I added a Aquara temp sensor and I’m showing it in two different cards.

In one card (left) its converting into F whereas on the other card (history) its coming across as C.

I’m happy to write a patch for the history card - if somebody can point me to where I need to look for that.

I renamed it AQUARA on the left card - its LUMI xxxx on the right.

Thanks!

[koying (Chris B)]

The label, you mean?
Because the data seems consistently °F

[jeeftor (Jeef)]

I mean why is it on a separate graph. It’s a f value listed as c

[koying (Chris B)]

Seems like a DB issue

History-graph shows old unit of measurement

If I add a new sensor, in this case a Zigbee Visonic door/temperature sensor, it gets detected and starts recording data. But it starts recording in degrees C. So, even though I’ve configured it now to F, the history-graph card thinks it’s still in C. As I learned from a similar problem (History-graph shows different styles), my other thermometers show up on one graph, and, in the same card, the new one shows up on a separate graph, because it still thinks it’s in a different unit of measuremen…

Likely, the issue will disappear when the values with wrong unit will be purged.

[jeeftor (Jeef)]

@koying

If I add a new sensor, in this case a Zigbee Visonic door/temperature sensor, it gets detected and starts recording data. But it starts recording in degrees C. So, even though I’ve configured it now to F, the history-graph card thinks it’s still in C. As I learned from a similar problem (History-graph shows different styles), my other thermometers show up on one graph, and, in the same card, the new one shows up on a separate graph, because it still thinks it’s in a different unit of measuremen…

I ended up purging the 1st entry (in c) from the sqlite db and it all worked out