Add option to pause battery tracking for single devices

[RalphPungaKronbergs]

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.

It would be very helpful if battery tracking could be paused for individual devices.

This would allow the batteries to be removed from the devices during winter storage without triggering a notification from the integration. In the spring, when the devices are put back into operation, the pause would be disabled and the devices would be included in tracking again.

It would be nice if you could see on the entity overview page (e.g., via background color or symbol) which devices are paused in order to have a good overview and be able to quickly access the paused devices..

Describe the solution you'd like

• Each device should be given the option to pause tracking for that device or to resume tracking.
• Any device that has been paused should be excluded from battery tracking.
• Any device that has been paused should be clearly identifiable as paused in the overview.

Describe alternatives you've considered

One could customize the template of a device so that it always returns “false” as the result. However, this would require a lot of manual effort and you would not have an overview of which devices are currently paused.

Additional context

New Option:

Overview variant 1:

Overview variant 2:

[andrew-codechimp]

Hi, thanks for the suggestion.

If it was just stopping the events firing (and therefore your notifications triggering) this would be easy to do today, but it would still show in the battery dashboards as being low/unknown.

I know that the HA Core team are looking at adding an option to disable sub-entries (what the individual battery notes are) and this would then disable events and also the entities which might be more useful to everyone.

I'll add this as an enhancement but I think I'll wait to see what action is being taken on the core front before adding my own switch here.

[RalphPungaKronbergs]

Hi Andrew,

Thank you very much for considering my suggestion.
I completely understand your decision to wait and see first.

[rekatab]

is there an update with that in the meanwhile?

[andrew-codechimp]

There isn't, I'm still waiting on Core to introduce disabling sub config entries, it was discussed on core arch a while back but doesn't seem a priority.