Feature to generate a report of all battery-powered devices, including device name, device type, battery type, and last battery replaced date.

[42Network]

Checklist

• I have filled out the template to the best of my ability.
• This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
• This issue is not a duplicate feature request of previous feature requests.

Is your feature request related to a problem? Please describe.

Thank you for this awesome contribution to the HA ecosystem. I hope to see it included in the main branch eventually!

I would like to know my entire inventory of battery-powered devices and group by battery type to know how many spare batteries I should have on hand in the worst case. E.g. How many 2032, 2045, AA, AAA, etc. should I have on hand as spares, based on how long the batteries last while in service versus the shelf-life of new, unused batteries?

Describe the solution you'd like

I would like to generate a report of all battery-powered devices, including device name, device type, battery type, and last battery replaced date.

Describe alternatives you've considered

The Device list will show all the "Battery Notes" devices with name, type, and battery level (see screenshot below), but I would also like to see the battery type and install date.

Additional context

[andrew-codechimp]

Thanks for the feedback, I'm not sure this will ever make it into core as code quality and time commitments wouldn't allow me to maintain the standards required for an official integration.

I like the idea of a "report" but as you're probably aware the Devices screen can't be customised so it would have to be a completely new Frontend component, a bit like Calendar and Alarmo amongst other add. This is a very different development skill from integration development (HTML, TypeScript etc) rather than Python so it would be a whole new area for me to learn.

In the meantime myself and others are using autoentities to create custom dashboard items, not as feature rich but shows what batteries we need soon. There's a good example here https://community.home-assistant.io/t/custom-component-battery-notes/613821/24

I'm closing this issue and moving it to the discussion/ideas area so it's not lost.

[ThomDietrich]

Hey guys,
I think this can be achieved via a custom Lovelace configuration.

I didn't have the time to dig much deeper so far. Currently I have a good overview of battery levels ONLY but it's technically feasible to add the battery type information. I didn't come up with the logic to link the two entities yet. Any ideas?

https://community.home-assistant.io/t/low-battery-level-detection-notification-for-all-battery-sensors/258664/345?u=thomdietrich

[andrew-codechimp]

There is an interesting custom card yaml config over on the HA forums that merges both battery level & type that may be useful

https://community.home-assistant.io/t/custom-component-battery-notes/613821/24?u=codechimp

[ThomDietrich]

You know what, I would absolutely love that!!

Not too sure whether it is needed or a good idea to hide the original battery. I would avoid touching what isn't my business :) But I agree, the following sounds good to me:
An entity like sensor.button_battery_status (status, info, extended, plus, ...) with the state and all attributes of the original sensor.button_battery, plus battery_type and battery_quantity. The entity updates with every battery level change, also resolving your forced_update idea from above. Agree, battery_level_entity_id would not be needed anymore. I'm really looking forward to this!

Bonus thought: See my screenshot from above. Common question I have when a device is unavailable is: "Was the battery low before it went offline", versus any other reason for a device to be offline. Do you have a thought how we could use the supercharged battery entity to provide such an info?

[andrew-codechimp]

I will think more about the hiding idea, maybe an optional flag in configuration.yaml but I like the way the switch as x does that.

I'll also add the attribute for last_replaced to the super battery entity, one place to query everything.

For another feature I am going to be looking at reading history to determine past battery levels so this could be used for a "last known level" once I get round to working out how to do it.

[andrew-codechimp]

A sneak peak of what this will look like here #570

[ThomDietrich]

Btw, I just added a new device via ZHA and entity_id are german'ized: For example button.eckstehlampe_identifizieren instead of button.eckstehlampe_identify

[andrew-codechimp]

The more I look at ZHA the more I'll be sticking with z2m. It will make sharing of automations, blueprints or yaml cards a nightmare.
Entity ids shouldn't be localised, there's a dismissed feature request here for it.

https://community.home-assistant.io/t/multi-language-entity-id-how-aliases/31339