Closed loopy321 closed 9 months ago
The attributes of the sensor are metric. But if you create a new sensor {{ day2rain }} for example and set the type 'precipitation' it will present as imperial on the sensor.
I am assuming you have the rainfactor calculation it probably should not be set to the device class of precipitation as it is only a factor, % to apply.
Thanks for the suggestion. I tried that, but the "type" does not set - I tried re-editing it and saving as precipitation, but does not work (keeps making it blank):
Try adding a new sensor, rather than editing the existing one, I will check what is happening on the modify.
As a side note - the "add ons" disappeared from my "settings" home assistant menu with the most recent v2.08. Not sure why.
I haven't experienced that. I just updated two devices rpi's to the version with no impact on the settings. Maybe a restart is required?
I am unable to get results to show in imperial either.
Hi @josephny ,
I hope this helps:
All data is captured in metric measurements.
To see the information in your local unit of measure:
WARNING (Recorder) [homeassistant.components.sensor.recorder] The unit of sensor.current_temp (°C) cannot be converted ...
Go to https://my.home-assistant.io/redirect/developer_statistics to fix this
Note Unit of measure is not applied to attributes, it is applied only to the sensor state. Attribute values are supplied as metric values. HA recommends that rapidly changing attributes are not used on sensors as this impact the history capture, instead create multiple sensors.
Hi, I'm after opinions/requests for the next release of this. No promises on a timeline though. This is just a requirements, wish list exercise at the moment.
This is what I am proposing:
Are there any request that I can add to the backlog, happy to consider, but can't promise on delivery 😄
Again, thanks for the work on this. In an effort to help troubleshoot, I have noticed that the units are not correct. See below with sensor set to "in" but apparently reporting "mm" (this is on v.2.08):