-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
improve "duration" sensor #73
Comments
Thank you for this hint. I will check this and provide a new version in the next days :) |
Got it fixed, going to release a new version tomorrow. |
should be fixed/added in v.1.2.4 |
thanks, I will give it a test |
Hi, |
Okay. Can you tell me/provide a screenshot and show how to convert a other entity? That would be great :) |
Hi, In the case of duration, you would have the option to change the unit of measurements to other time formats: For Power, you can select different Power Units And the same applies for Energy, and so on (would also apply for the usagecounter of this integration) I think, this is acheived by using "native_unit_of_measurement" instead of "unit_of_measurement", as well as "native_value" - and probably "suggested_unit_of_measurement" |
Got it fixed with your link https://developers.home-assistant.io/docs/core/entity/sensor/ |
With home-assistant/frontend#23017 and home-assistant/frontend#23025 HomeAssistant did some improvements on the Sensors that are using "duration" as value of measurement.
You can now define the default measurement of a duration sensor (days, hours, min, seconds, etc.)
These changes are not reflected by the Integration OilFox.
OilFox Sensor:

Other Duration Sensors:

The text was updated successfully, but these errors were encountered: