Expose attributes as separate entities instead

[andyearnshaw]

Description

Some entities (Fuel %, AdBlue %) have range attributes. It would be better to expose these ranges as separate entities so that the unit of measurement can be customised without having to set up helpers.

[marq24]

Hi Andy,

by default the Integration will use the HA Unit system in order to localize attributes - including these ranges. I assume you have the challenge in the UK, that you want to use °C and miles.

the http://[your-ha]:8123/config/general does not allow (yet) by default to select different default unit's in detail :-/
-> https://github.com/home-assistant/core/blob/dev/homeassistant/util/unit_system.py

[andyearnshaw]

I assume you have the challenge in the UK, that you want to use °C and miles.

This is correct! It's quite frustrating at times. Having separate entities for these values is how most other vehicle integrations work, I'm using Renault, Peugeot (Stellantis), Hyundai/Kia and now Ford.

[marq24]

... sorry but I could not resist

... is how most other vehicle integrations work

Most of the flies love to eat shit - this does not mean, that this is a good option for me...

But to add something more meaningful - HA have a great Infrastructure to convert unit's and localize values - it's just not well known/adopted by many integrations.

One of the possible reasons (which might explain the poor adoption rate) is the fact, that currently in the HA UI there can be only selected between two two... [While in your normal OS like Windows/MacOs etc you have plenty of options to adjust your preferences.

So from my (isolated) perspective the HA UI should allow users to define their own localization (instead of the simple toggle between US / RestOfTheWord)

The option, that you need (manually) to set each sensor to display miles instead of kilometers is IMHO already the wrong approach... The measurement is distance and then all the rest must be handled elsewhere based on the users localization settings.

[andyearnshaw]

I do agree for the most part, this should be solved in HA so that we can more finely tune our localisations. However, who knows when that will happen, so all we have is the option to set entity's units where necessary.

More than that, in the UK we actually tend to use a mix of units for distances. We will use miles for measuring distance between locations, but then it's becoming increasingly common (thanks to modern educational material) to use metric for measuring something like a short distance between two objects. Likewise, we measure our beer in pints and our soft drinks in litres! We are not consistent at all, so the option to manually set each entity is quite useful.

[marq24]

but then it's becoming increasingly common (thanks to modern educational material) to use metric for measuring something like a short distance between two objects

What?! - Why you left the EU 10 years ago ?! :-D

But to get back on topic - the Integration currently make use of attribute localization for:

• 8 x localize_distance
• 7 x localize_temperature

Sure you are just asking for two - but there is no reason, why all the others should be treated different - So I can agree some sort of, that implementing additional 15 new entities is doable... But then the question must be allowed, why this 15 attributes (which would became independent Entities) are different than all the other attributes? Do you have an idea, how many different attributes are supported by this Integration? There are over +120 possible attributes the integration can provide, and for me as the integration developer it's almost impossible to make the right choice, which of the +120 should be exposed as separate entity.

Of course, you are asking for two specific - but other users might have different opinion, which attribute should be available as own entity... At the end of the day that's the main reason, why I I am hesitate with the implementation of your specific request [since there is a local/individual solution via the template sensors].

[pcaouolte]

I'm also in the UK, I use this to output the fuel range in miles:
{{ (state_attr('sensor.fordpass_wf0jxxxxxxxx#####_fuel', 'fuelRange')|float(0) * 0.621371)|round }} miles