Add mAh, Ah as a new BATTERY_CAPACITY device class

[knyghtryda]

This seems to be a pretty important missing unit. Currently we have support for energy capacity, but not battery capacity, which is useful for a lot of battery based devices (in my case the Ecoflow batteries) which report this value.

[parautenbach]

Ah is actually quite a poor indicator of battery capacity since it's unit isn't Joule, the measure of energy (you thus need the voltage with Ah to get to that).

Wouldn't this value be mostly a constant anyway? Or are you actually talking about remaining capacity here?

[knyghtryda]

Both actually. The Ecoflow delta pro reports full capacity, remaining capacity, and factory spec capacity.

[MartinHjelmare]

Please list the integrations that could leverage the new device class. Integrations that can leverage anything, like template and MQTT aren't interesting.

[frenck]

If there are a handful of integrations in our core codebase that need it, we are definitely open to add it.

At this point, it seems that isn't the case.

[Just-Zuul]

I haven't been using HA for very long, maybe half a year - I'm generally enthusiastic and have decided to use HA instead of IO Broker.

I really don't understand what the problem is with introducing mAh as a unit. MWh (and I think GWh too - of course, if you're a power plant operator) is also possible and I'll say - nobody needs it - normal users probably all use kWh.

Considering that over 1 million people use Ecoflow, most of them don't (yet) know anything about the possibilities with HA, don't know or find this article and all in all it would already make life easier for several thousand people....

But if you think so... OK - HA is your thing - but is that the right decision...?

[frenck]

Home Assistant provides a common interface over multiple devices; it does so by creating an abstraction across things that are common for multiple integrations.

Right now, we do not have multiple integrations in our code codebase that can benefit from these abstractions. If there would be a handful (as pointed out multiple times now), we can reconsider. If we would add it right now, it would be basically dead code or code specifically for a single integration; which is not what we want in our architecture.

../Frenck

[ChristophCaina]

Hi, common to the Statement about MWh:

As already mentioned, Iam using a Rest API to get Sonne information from our Energy supplier about how much renewable Energy is available.
This information comes in MWh.

Beides of that:
My solar Installation does produce 13.000 kWh per year.
At sind Point, it would just good to have the opportunity to Switch to this unit.
That would also apply for the Energy Dashboard, where people already complaining that the large kWh Numbers so not fit into the circles in certain cases.

It's of course not a must have - Just a few usecases where it could already be considered ;)

[frenck]

@ChristophCaina Your comment does not seem to be related to this architectural discussion.

[tiimsvk]

I also use this integration with a device for RPI where the battery capacity is defined in mAh
https://github.com/odya/hass-ina219-ups-hat

[frenck]

Custom integrations are not a factor for us in deciding what we support in Core.

[ChristophCaina]

In my opinion, HA should be capable of handling at least some Standard Units - and Ah / mAh is one.
Regardless of the amount of Integrations that currently exist - or maybe will exist later.

There are other examples of Units that could be integrated - even If they are not that common... MW (Mega Watt) etc. that could be easily added without causing issues If they are not beeing used immediately.

You can Just Setup a Rest API Sensor or create a template that would utilize such a measurement value...
In my opinion, HA should be more flexible for such Units

[frenck]

If there are a handful of integrations in our core codebase that need it, we are definitely open to add it.

At this point, it seems that isn't the case.