andrew-codechimp / ha-battery-notes Goto Github PK

Manufacturer

Xiaomi

Model

WSDCGQ01LM

Battery Type

CR2032

Battery Quantity

1

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.

na

Describe the solution you'd like

{
    "manufacturer": "Visonic",
    "model": "MCT-340 E",
    "battery_type": "CR2032",
    "battery_quantity": 1
},

Describe alternatives you've considered

na

Additional context

na

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.

I have multiple Aeotec Multisensors that have the capability to be powered by battery or 5vdc adapter. All my Aeotec sensors are currently under 5vdc adapter power but they continue to be shown in discovered devices, understandably. There is no option to ignore.

Describe the solution you'd like

Please add an option to ignore devices.

Describe alternatives you've considered

No alternative.

Additional context

None

System Health details

N/A

Checklist

• I have enabled debug logging for my installation.
• I have filled out the issue template to the best of my ability.
• This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
• This issue is not a duplicate issue of any previous issues..

Describe the issue

Have installed via HACS and added to configuration .yaml the battery_notes: and did the restart. It's not being up the SmartThings sensors that I think are already in the database. So I have something off just asking for ideas

Reproduction steps

1. N/A

...

Debug logs

n/a

Diagnostics dump

N/A

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.

When a battery note is added for a device, the device's icon changes to the HA Battery Notes icon automatically. There's currently option to change this behaviour.

Describe the solution you'd like

Having a global(?) setting related to the integration that allows the user to choose to retain the original device icon.

Describe alternatives you've considered

Accepting this can't be changed :-)

Additional context

Top entry shows the HA Battery Notes icon, bottom entry shows the original device's icon.

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.

No

Describe the solution you'd like

        "manufacturer": "Orbit BHyve",
        "model": "HT25-0000",
        "battery_type": "AA",
        "battery_quantity": 2

Describe alternatives you've considered

n/a

Additional context

n/a

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.

This is an interesting project, but for now it requires to manually fill every sensor you have with battery type.

Describe the solution you'd like

It would be much more useful if it had a base like powercalc where different users can add a note, then it will search for the same entities in your configuration, and autopopulate them.

Describe alternatives you've considered

Didn't see any integrations like yours tbh

Additional context

I am willing to populate this database with 30-50 sensor types or even more, just so it would be filled at the start

Manufacturer

Philips

Model

Hue motion outdoor sensor (9290019758)

Battery Type

AA

Battery Quantity

2

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.

I was about to add an entry for Amazon Blink Cameras, but noticed that the model shows up as "unknown" in the device list, and is missing in the device page, in HomeAssistant. How can we add battery notes to such devices?

Will adding the following into library.json work?:

        {
            "manufacturer": "Blink",
            "battery_type": "AA",
            "battery_quantity": 2
        }

Describe the solution you'd like

Any, as long as I can add battery notes to Blink XT2 cameras.

Describe alternatives you've considered

na

Additional context

na

Manufacturer

Xiaomi

Model

GZCGQ01LM

Battery Type

CR2450

Battery Quantity

1

Manufacturer

Lidl

Model

HG06336

Battery Type

AAA

Battery Quantity

2

Manufacturer

Xiaomi

Model

MCCGQ01LM

Battery Type

CR1632

Battery Quantity

1

Manufacturer

Xiaomi

Model

RTCGQ01LM

Battery Type

CR2450

Battery Quantity

1

System Health details

System Information

Checklist

• I have enabled debug logging for my installation.
• I have filled out the issue template to the best of my ability.
• This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
• This issue is not a duplicate issue of any previous issues..

Describe the issue

After fresh install with HACS i cant add any deice. And no devices are discovered.

Reproduction steps

1. Install with HACS
2. Reboot Home Assistant (Whole HA)
3. Try add device with add integration

Debug logs

Dont have any log from integration

Diagnostics dump

No response

System Health details

System Information

Checklist

• I have added battery_notes: to my configuration.yaml and restarted.
• I have enabled debug logging for my installation.
• I have filled out the issue template to the best of my ability.
• This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
• This issue is not a duplicate issue of any previous issues..

Describe the issue

Google Nest Protect Smoke Alarms are being auto-detected.
What it is not accounting for is that there are 2 models - hardwired (i.e. to household 120V/240V) and battery operated.

Mine are the hard-wired variety and so I have 2 discovered devices wanting to be configured.

Does this need some sort of tweak to the library.json to differentiate (if possible)?
Or just an option to exclude these devices from auto-detection?
Or do I just configure them as though they are battery operated, and then delete them?
Or do I configure them as "Irreplaceable"?

This is the relevant existing library entry:

        {
            "manufacturer": "Google",
            "model": "Topaz-2.7",
            "battery_type": "AA",
            "battery_quantity": 3
        },

Here's my wired model device:

Reproduction steps

1. Install integration and reboot

...

Debug logs

n/a

Diagnostics dump

No response

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.

Some people don't want this functionality and confuses when devices have had the button pressed x years ago

Describe the solution you'd like

Add a config option to disable showing of battery replaced, enabled by default

Describe alternatives you've considered

None

Additional context

None

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.

na

Describe the solution you'd like

{
    "manufacturer": "Vision Security",
    "model": "ZP3111-5",
    "battery_type": "AAA",
    "battery_quantity": 2
}

Describe alternatives you've considered

na

Additional context

na

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.

Changed some batteries a few days ago, but unable to set the replacement date to anything but now().

Describe the solution you'd like

If possible, change the service set_battery_replaced to take an optional date to set the replacement date of a battery.

Describe alternatives you've considered

Maybe manually modifying the .storage info?

Additional context

None really.

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.

Depending on the type of device and their power usage, in my testing sometimes the operation duration highly depends on the manufacturer and/or specific variants of the same type of batteries.

I tend to play around and test different battery series to see how they behave and my findings are, that some are lasting way longer than others. Even from the same brand, the different series can vary a lot. So, for example, the industrial AA from Varta do indeed last longer in some scenarios than their ultra power sisters.

Describe the solution you'd like

The ultimative end goal for a feature I have in mind is a database of batteries (in general/ and specific to decides) and their actual usage.

To be more accurate I even consider looking at usage metrics, so I think a contact sensor could actually measure „contact changes“ while motion sensors could measure motion triggers. A TRV could measure valve reports and regular sensors updates to their measured values. As fallback a generic count of updates could also help to better knowledge about the efficiency of batteries and devices.

Describe alternatives you've considered

Long time ago i started a spreadsheet but this was abandoned really fast because the time this took. And because with the former system (not HASS) it was not easy to implement (for me)

Additional context

I am open to feedback on this, as it could be, that I am the only one that is annoyed by the variance of efficiency of the devices on the market and the claims from the brands are mostly just garbage.

I think also only the simplest type of usage information could already help for beginners and all users that try to find a good sensor or battery powered device.

For example i am currently replacing all Aeotec sensors because they just suck batteries (CR123) like no others while the Philips sensors are the most efficient sensors I've tested so far. And they are using simple AAAs, which is also a factor in terms of maintenance costs.

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.

No

Describe the solution you'd like

  "manufacturer": "Allegion",
  "model": "BE469",
  "battery_type": "AA",
  "battery_quantity": 4

Describe alternatives you've considered

n/a

Additional context

n/a

Manufacturer

TuYa

Model

TS0203

Battery Type

CR2032

Battery Quantity

1

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.

Local changes to the library are overwritten by an update.

Describe the solution you'd like

The HA Integration Switch Manager uses blueprints and individual files per device. https://github.com/Sian-Lee-SA/Home-Assistant-Switch-Manager#blueprints

This means that the self-created devices are not overwritten during an update and the devices would be easier to maintain.

Perhaps this feature could also be implemented with feature #88

Describe alternatives you've considered

Without using the HA Blueprint folder, individual files per device would be a big improvement.

Additional context

no additional context

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.

The config flow contains a label to "optionally" enter the number of batteries a device takes. It's possible to enter this in a format that doesn't like up with that used by the sensor when completed via the library. This creates an inconsistent view in the UI.

Describe the solution you'd like

A textbox in the config flow to allow entry of the quantity (defaulting to 1). This would allow processing and for atting the same way as those populated by the library.

Describe alternatives you've considered

Defining the format of entry in the label stating that it is optional.

Additional context

The entry screen in the config flow.

Badly formatted battery type with quantity.

Correctly formatted battery type from library.

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.

na

Describe the solution you'd like

{
    "manufacturer": "Ecolink",
    "model": "TILTZWAVE1",
    "battery_type": "CR123A",
    "battery_quantity": 1
},

Describe alternatives you've considered

na

Additional context

na

Manufacturer

TuYa

Model

IH012-RT01

Battery Type

CR2450

Battery Quantity

1

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.

na

Describe the solution you'd like

{
    "manufacturer": "ISW-ZPR1-WP13",
    "model": "Bosch",
    "battery_type": "AA",
    "battery_quantity": 4
}

Describe alternatives you've considered

na

Additional context

na

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.

I have battery powered two Bluetooth sensors.
I would like to have them auto configured, but I don't know what data to enter to the database.

Describe the solution you'd like

I would like to be able to add data for Bluetooth devices to the database and have them auto recognised.

Describe alternatives you've considered

What other data can I add to support my case?

Additional context

https://kb.shelly.cloud/knowledge-base/shellyblu-door-window

https://kb.shelly.cloud/knowledge-base/shellyblu-motion

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.

Having many battery-powered devices and adding the last ones, the already configured devices are not relevant here and do 'hide' the not-configured ones.

Describe the solution you'd like

See title

Describe alternatives you've considered

NA

Additional context

NA

Manufacturer

TuYa

Model

TS0601_smoke_1

Battery Type

AAA

Battery Quantity

2

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.

No

Describe the solution you'd like

{
	"manufacturer": "eQ-3",
	"model": "HM-CC-RT-DN",
	"battery_type": "AA",
	"battery_quantity": 2
},
{
	"manufacturer": "eQ-3",
	"model": "HM-Dis-EP-WM55",
	"battery_type": "AAA",
	"battery_quantity": 2
},
{
	"manufacturer": "eQ-3",
	"model": "HM-Sec-RHS",
	"battery_type": "LR44",
	"battery_quantity": 2
},
{
	"manufacturer": "eQ-3",
	"model": "HM-TC-IT-WM-W-EU",
	"battery_type": "AAA",
	"battery_quantity": 2
},
{
	"manufacturer": "eQ-3",
	"model": "HMIP-WRC2",
	"battery_type": "AAA",
	"battery_quantity": 2
},
{
	"manufacturer": "eQ-3",
	"model": "HmIP-DLD",
	"battery_type": "AA",
	"battery_quantity": 4
},
{
	"manufacturer": "eQ-3",
	"model": "HmIP-KRCK",
	"battery_type": "AAA",
	"battery_quantity": 1
},
{
	"manufacturer": "eQ-3",
	"model": "HmIP-STH",
	"battery_type": "AAA",
	"battery_quantity": 2
},
{
	"manufacturer": "eQ-3",
	"model": "HmIP-WRCD",
	"battery_type": "AAA",
	"battery_quantity": 2
},
{
	"manufacturer": "eQ-3",
	"model": "HmIP-eTRV-CL",
	"battery_type": "AA",
	"battery_quantity": 4
}

Describe alternatives you've considered

n/a

Additional context

Merged and sorted:

{
	"manufacturer": "eQ-3",
	"model": "HM-CC-RT-DN",
	"battery_type": "AA",
	"battery_quantity": 2
},
{
	"manufacturer": "eQ-3",
	"model": "HM-Dis-EP-WM55",
	"battery_type": "AAA",
	"battery_quantity": 2
},
{
	"manufacturer": "eQ-3",
	"model": "HM-ES-TX-WM",
	"battery_type": "AA",
	"battery_quantity": 4
},
{
	"manufacturer": "eQ-3",
	"model": "HM-Sec-RHS",
	"battery_type": "LR44",
	"battery_quantity": 2
},
{
	"manufacturer": "eQ-3",
	"model": "HM-TC-IT-WM-W-EU",
	"battery_type": "AAA",
	"battery_quantity": 2
},
{
	"manufacturer": "eQ-3",
	"model": "HMIP-SWDO",
	"battery_type": "AAA"
},
{
	"manufacturer": "eQ-3",
	"model": "HMIP-SWDO-I",
	"battery_type": "AAA",
	"battery_quantity": 2
},
{
	"manufacturer": "eQ-3",
	"model": "HMIP-SWDO-PL",
	"battery_type": "AAA",
	"battery_quantity": 2
},
{
	"manufacturer": "eQ-3",
	"model": "HMIP-WRC2",
	"battery_type": "AAA",
	"battery_quantity": 2
},
{
	"manufacturer": "eQ-3",
	"model": "HMIP-eTRV",
	"battery_type": "AA",
	"battery_quantity": 2
},
{
	"manufacturer": "eQ-3",
	"model": "HMIP-eTRV-2",
	"battery_type": "AA",
	"battery_quantity": 2
},
{
	"manufacturer": "eQ-3",
	"model": "HMIP-eTRV-B",
	"battery_type": "AA",
	"battery_quantity": 2
},
{
	"manufacturer": "eQ-3",
	"model": "HMIP-eTRV-C",
	"battery_type": "AA",
	"battery_quantity": 2
},
{
	"manufacturer": "eQ-3",
	"model": "HMIP-eTRV-E",
	"battery_type": "AA",
	"battery_quantity": 2
},
{
	"manufacturer": "eQ-3",
	"model": "HmIP-DLD",
	"battery_type": "AA",
	"battery_quantity": 4
},
{
	"manufacturer": "eQ-3",
	"model": "HmIP-KRCK",
	"battery_type": "AAA",
	"battery_quantity": 1
},
{
	"manufacturer": "eQ-3",
	"model": "HmIP-SCI",
	"battery_type": "AAA",
	"battery_quantity": 2
},
{
	"manufacturer": "eQ-3",
	"model": "HmIP-SLO",
	"battery_type": "AA",
	"battery_quantity": 2
},
{
	"manufacturer": "eQ-3",
	"model": "HmIP-SMI",
	"battery_type": "AA",
	"battery_quantity": 2
},
{
	"manufacturer": "eQ-3",
	"model": "HmIP-SMI55",
	"battery_type": "AAA",
	"battery_quantity": 2
},
{
	"manufacturer": "eQ-3",
	"model": "HmIP-SMO",
	"battery_type": "AA",
	"battery_quantity": 2
},
{
	"manufacturer": "eQ-3",
	"model": "HmIP-SRH",
	"battery_type": "AAA"
},
{
	"manufacturer": "eQ-3",
	"model": "HmIP-STH",
	"battery_type": "AAA",
	"battery_quantity": 2
},
{
	"manufacturer": "eQ-3",
	"model": "HmIP-SWDM",
	"battery_type": "AAA",
	"battery_quantity": 2
},
{
	"manufacturer": "eQ-3",
	"model": "HmIP-WRC6",
	"battery_type": "AAA",
	"battery_quantity": 2
},
{
	"manufacturer": "eQ-3",
	"model": "HmIP-WRCD",
	"battery_type": "AAA",
	"battery_quantity": 2
},
{
	"manufacturer": "eQ-3",
	"model": "HmIP-WTH-2",
	"battery_type": "AAA",
	"battery_quantity": 2
},
{
	"manufacturer": "eQ-3",
	"model": "HmIP-eTRV-CL",
	"battery_type": "AA",
	"battery_quantity": 4
}

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.

From Ikea and Ring

Describe the solution you'd like

    {
        "manufacturer": "IKEA",
        "model": "FYRTUR roller blind (E1757)",
        "battery_type": "Rechargeable"
    },	        
    {
        "manufacturer": "Ring",
        "model": "Contact Sensor",
        "battery_type": "CR2032",
        "battery_quantity": 2
    },
{
        "manufacturer": "Ring",
        "model": "Motion Sensor",
        "battery_type": "AA",
        "battery_quantity": 2
    },
{
        "manufacturer": "Ring",
        "model": "Security Keypad",
        "battery_type": "Rechargeable"
    },

Describe alternatives you've considered

Additional context

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.

No way to keep track of when a battery is replaced against the device in HA

Describe the solution you'd like

Suggestion: Optionally add a second entity to go alongside the battery type, where the user can define the date of the last time the battery was replaced as a date selector field (similar to the date helper).

Describe alternatives you've considered

I tried setting up helpers, but not having the helper entity added to the device made it difficult to keep track of everything.

I also tried setting the 'Battery type' entity from this integration to the battery type followed by the last change date, but doing this don't get the history of the changes you would get from a date entity.

Additional context

Keeping track of when batteries are changed can be a bit of a nightmare when you have a lot of devices, being able to record the last time a battery was changed helps identify devices that are draining battery's too fast and how many replacement batteries needed per year etc.

System Health details

System Information

Checklist

• I have enabled debug logging for my installation.
• I have filled out the issue template to the best of my ability.
• This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
• This issue is not a duplicate issue of any previous issues..

Describe the issue

I have added you integration using HACS
When I add
battery_notes: enable_autodiscovery: true
in my configuration.yaml and reboot HA I get an error that the integration does nocht support yaml.

Reproduction steps

1. Add integration using HACS
2. add configuration.yaml
3. Reboot HA
   ...

Debug logs

No log needed

Diagnostics dump

No response

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.

na

Describe the solution you'd like

{
    "manufacturer": "AEON Labs",
    "model": "DSB05",
    "battery_type": "AAA",
    "battery_quantity": 4
},

Describe alternatives you've considered

na

Additional context

na

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.

na

Describe the solution you'd like

{
    "manufacturer": "_TZ3000_xr3htd96",
    "model": "TS0201",
    "battery_type": "AAA",
    "battery_quantity": 2
},
{
    "manufacturer": "_TZ3000_dowj6gyi",
    "model": "TS0201",
    "battery_type": "CR2450",
    "battery_quantity": 1
},
{
    "manufacturer": "_TZE200_locansqn",
    "model": "TS0601",
    "battery_type": "AAA",
    "battery_quantity": 3
},

Describe alternatives you've considered

na

Additional context

na

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.

Actually I am quite happy with battery notes since I use it. It will even become more useful as I add more devices

Describe the solution you'd like

Having date of preoviding new full battery alltogether with the type of the battery and the device will help understand how long a battery for a device lasted and/or prognose whow long it will last before need to replace it.

Describe alternatives you've considered

Additional context

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.

The definitions library of batteries is blowing out in size. I observed that some of my devices are already in that file but were not auto-detected simply due to differences in how different integrations, i.e. ZHA vs. Zigbee2MQTT, present models and manufacturers.

Describe the solution you'd like

Allow for one, or more, models and manufacturers against each key in the libraries definition file, e.g.

{
	"manufacturer": [
		"Xiaomi",
		"Aqara"
	],
	"model": [
		"Aqara human body movement and illuminance sensor (RTCGQ11LM)",
		"RTCGQ11LM"
	],
	"battery_type": "CR2450"
}

Or some similar format.

Describe alternatives you've considered

We could simply keep adding to the database but it's going to grow larger and more unmanageable over time, especially so if there were to say be a dropdown selection of models in the future to maybe choose from.

Additional context

.

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.

na

Describe the solution you'd like

{
    "manufacturer": "Vision Security",
    "model": "ZS5101",
    "battery_type": "CR123A",
    "battery_quantity": 1
},

Describe alternatives you've considered

na

Additional context

na

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.

no

Describe the solution you'd like

Right now, the library devices are stored in a list, which means specific devices can only be accessed by iterating through the library until a match is found.
If it were a keyed dictionary instead, particular entries can be navigated to directly.

Describe alternatives you've considered

iterating sequentially is always possible

Additional context

I'm working on a github actions workflow for you that will allow people to create library entries automatically from a github issue form.

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.

I use a mix of rechargeable and disposable batteries, and although I can usually tell which one I'm using by the instantaneous voltage, it would be handy if this could be included in the integration.

Describe the solution you'd like

There could be an attribute in the integration item that could be checked to indicate that the device currently has a battery that can be charged (e.g. CR2450/LIR2450, CR2032/ML2032 etc.)

Describe alternatives you've considered

I can also imagine a way to have multiple optional batteries associated with a given type of device, but that would probably require a more labour-intensive or more sofisticated solution at the moment.

Additional context

I may be the only one in the world who has a problem with using disposable (albeit less self-discharging) batteries, so I'd be happy to have someone to partner with me on the idea (:

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.

Data base of devices (library.json) grows very fast so releases comes often and every time HA need to be restarted.

Describe the solution you'd like

Wonder if will be possible to reload library.json somehow, without need to restart HA.

Describe alternatives you've considered

Maybee some kind of service which will load library.json directly from github?

Additional context

no

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.

You seem to have based your integration on devices, which may not be created by yaml integrations. Wouldn't it be more logical to base it on sensors?

In my case the integration is for Wireless Sensor Tags, which is set up in configuration.yaml. The integration creates battery sensors (data from the cloud) but there are no associated devices, so they do not appear in your configuration drop-down list.

Describe the solution you'd like

The configuration drop-down list should contain all battery sensors.

Describe alternatives you've considered

Can't see that there are any.

Additional context

None.

System Health details

I can't seem to find this data in my installation

Checklist

• I have enabled debug logging for my installation.
• I have filled out the issue template to the best of my ability.
• This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
• This issue is not a duplicate issue of any previous issues..

Describe the issue

I've installed the integration through HACS, and see the Battery Notes card.
I have restarted my Home Assistant instance.
When I open a device with a battery (i.e. front door lock), I am unable to see anywhere to add the battery type.

Reproduction steps

1. restarted HA
2. Navigate to HACS > Integrations > Battery Notes
3. Unable to see any option to add battery types
4. Navigate to a device with known batteries (4xAA)
5. Review diagnostic sensors, unable to see a sensor for battery type.
   ...

Debug logs

no logs found for this integration.

Diagnostics dump

No response

Manufacturer

Lidl

Model

HG06335/HG07310

Battery Type

CR123A

Battery Quantity

1

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.

If Hue devices are integrated into HA using ZHA (e.g without the Hue Bridge) the model name is reported differently than with Hue. The current device database contains model names for Hue, e.g for a Wall Switch Module its Hue wall switch module (RDM001) but ZHA reports only RDM001.

Describe the solution you'd like

It would be great if an alternative model name could be specified.

Describe alternatives you've considered

Add separate entries for ZHA devices (e.g model name RDM001). I don't like this solution as it would add bloat and redundancy to the device library

Additional context

Thanks for the great work anyway 👍

Manufacturer

Xiaomi

Model

MCCGQ01LM

Battery Type

CR1632

Battery Quantity

1

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.

The list of devices the dropdown for devices when creating a new battery-note contains all available devices. This is/can be a very long list. Most many devices do not have a battery and are unnecessary in the list.

Describe the solution you'd like

Fill the devices list with a filter that only includes devices which has a battery

Describe alternatives you've considered

NA

Additional context

NA

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.

For consistency add standard battery types for non-standard battery rechargeable devices like Ring doorbell and non-standard irreplaceable batteries like smoke detectors to allow all battery devices to auto discover battery notes.

Functionality is already there it is more a question on defining a "standard" battery type label for these types. This to add them in a consistent way to the library.

Describe the solution you'd like

new labels:

• Non-standard rechargeable battery
• Irreplaceable battery

Describe alternatives you've considered

Manual entry without auto discovery

Additional context

I like all my battery devices linked where possible as that provides a way to create a singe list of batteries and near future replacements

System Health details

Hi,
I own a frient A/S heat detector with Siren - Model: HESZB-120
I would like to add this device to the library.json file - but I noticed the following:

        {
            "manufacturer": "Develco",
            "model": "Smoke detector with siren (SMSZB-120)",
            "battery_type": "CR123"
        },
        {
            "manufacturer": "Develco Products A/S",
            "model": "AQSZB-110",
            "battery_type": "AA",
            "battery_quantity": 2
        },
        {
            "manufacturer": "frient",
            "model": "MOSZB-140",
            "battery_type": "AA",
            "battery_quantity": 2
        },

I know, that the frient A/S is in fact a device manufactured by Develco - but labeld as frient.
And I am pretty sure, that this is similar to the other frient device already available in the json - if you compare the model information.

Should I add the device as frient / frient A/S - or as Develco / Develco Products A/S ?
Or should I use the Manufacturer as it is shown in the Device Information of HA?

Checklist

• I have enabled debug logging for my installation.
• I have filled out the issue template to the best of my ability.
• This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
• This issue is not a duplicate issue of any previous issues..

Describe the issue

Reproduction steps

...

Debug logs

---

Diagnostics dump

No response

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.

No

Describe the solution you'd like

        "manufacturer": "Kwikset",
        "model": "Kevo",
        "battery_type": "AA",
        "battery_quantity": 4

Describe alternatives you've considered

n/a

Additional context

n/a