@brucehvn wrote:
Running hass.io 0.103.6.
I ran into this issue when creating a template sensor to get the current temperature from my nest thermostat. I made a mistake specifying the unit of measurement, but I had a big problem trying to get it correct. When I modified the sensors.yaml to use the proper value, it would never change to reflect that in the state attributes. I removed the sensor completely and restarted ha, then re added the sensor, but it still used the old unit of measurement. I even went into the db and deleted all the state and history data for that sensor, but I could not get it to use my new unit of measurement. I finally had to add it under a different name to get the proper value.
I think I’m seeing the same thing now with the darksky sensor. I’m a US guy, but my wife likes to see temperatures in Celsius, so while I have a weather card in the UI that shows my imperial values (using the darksky integration, not the sensor), I wanted to change the darksky sensor to use metric values and I would setup a custom darksky card I found in the forums here that does use the sensor. I changed the darksky sensor to use
si
as the units of measurement, but it’s not changing in the states list. However, I did add some new monitored_conditions and those show up with the right metric values. It’s just the ones that were already there that won’t change.Is there a way to get HA to completely reset it’s knowledge about a particular sensor so I can re-add it with the right values?
Posts: 4
Participants: 2