Battery notes suggest to add a new device, even if it already has a battery notes device added (previously, manually)

[chefkoch]

Checklist

• I have added battery_notes: to my configuration.yaml and restarted.
• I have read the FAQ's.
• 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..

Battery Notes Version

2.10.11

Describe the issue

When adding a device a few weeks ago, it was not immediately published / suggested as a new device by/for battery notes.
So I added battery notes manually to the device.

Now a few days/weeks later (did not monitor recently when it was actually available), battery notes suggests to be added (attached) to a new battery powered device, which is acutally the device I added battery notes a few weeks ago manually to.

I had the same issue with two other devices. There I removed battery notes, which was added manually and followed the suggested popup to add a new device. After this the suggestion was gone and did not came back so far.

Reproduction steps

see description above...

1. add a new battery powered device (zigbee) in my case
2. add batterynotes to the device manually as it was not populated at this moment, yet
3. later there should be a suggestion to add battery notes to the device (from step 1), which is redundant and creates a duplicate battery notes entry, as we already added it in step 2.
   ...

System Health details

System Information

version	core-2025.9.4
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
container_arch	amd64
user	root
virtualenv	false
python_version	3.13.7
os_name	Linux
os_version	6.12.43-haos
arch	x86_64
timezone	Europe/Berlin
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
HACS Data	ok
GitHub API Calls Remaining	5000
Installed Version	2.0.5
Stage	running
Available Repositories	2304
Downloaded Repositories	10

Home Assistant Cloud

logged_in	false
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Home Assistant OS 16.2
update_channel	stable
supervisor_version	supervisor-2025.10.0
agent_version	1.7.2
docker_version	28.3.3
disk_total	30.8 GB
disk_used	17.7 GB
nameservers	10.10.10.1
healthy	true
supported	true
host_connectivity	true
supervisor_connectivity	true
ntp_synchronized	true
virtualization	kvm
board	ova
supervisor_api	ok
version_api	ok
installed_addons	ESPHome Device Builder (2025.10.1), File editor (5.8.0), Mosquitto broker (6.5.2), Node-RED (20.0.0), Piper (1.6.4), SQLite Web (4.4.1), Samba share (12.5.2), Silicon Labs Flasher (0.3.4), Terminal & SSH (9.20.1), Whisper (2.6.0), snapcast-client (0.1.8), Zigbee2MQTT (2.6.2-1), Music Assistant Server (2.6.0), Govee to MQTT Bridge (2025.04.13-17d43d72)

Dashboards

dashboards	4
resources	3
views	15
mode	storage

Network Configuration

adapters	lo (disabled), enp3s0 (enabled, default, auto), hassio (disabled), docker0 (disabled), veth81de6df (disabled), vetha4ee7fc (disabled), vethf6ffc83 (disabled), veth8efa2ec (disabled), vethe08ec9c (disabled), vethcf72b40 (disabled), veth549c944 (disabled), veth9fcb25f (disabled), vethf472f8c (disabled), vethab715e7 (disabled), vethcb8783c (disabled), vethc4ae507 (disabled), vetha140e6a (disabled)
ipv4_addresses	lo (127.0.0.1/8), enp3s0 (10.10.10.6/24), hassio (172.30.32.1/23), docker0 (172.30.232.1/23), veth81de6df (), vetha4ee7fc (), vethf6ffc83 (), veth8efa2ec (), vethe08ec9c (), vethcf72b40 (), veth549c944 (), veth9fcb25f (), vethf472f8c (), vethab715e7 (), vethcb8783c (), vethc4ae507 (), vetha140e6a ()
ipv6_addresses	lo (::1/128), enp3s0 (fe80::e9f:701d:3a62:593/64), hassio (fe80::d0d9:27ff:fea2:1148/64), docker0 (fe80::5c0c:29ff:fe12:bcac/64), veth81de6df (fe80::a4f7:75ff:fefe:d679/64), vetha4ee7fc (fe80::d841:93ff:fe45:a2f/64), vethf6ffc83 (fe80::d463:7ff:fe9a:2ad4/64), veth8efa2ec (fe80::6c53:5ff:feaf:94f0/64), vethe08ec9c (fe80::c010:c7ff:fe17:d4df/64), vethcf72b40 (fe80::58f8:14ff:fee2:c69d/64), veth549c944 (fe80::18c5:5aff:fe4b:8f37/64), veth9fcb25f (fe80::e45c:83ff:fe9b:5017/64), vethf472f8c (fe80::349d:afff:fe50:d1e4/64), vethab715e7 (fe80::2014:6dff:fef1:16b7/64), vethcb8783c (fe80::f08c:57ff:fe9d:2954/64), vethc4ae507 (fe80::f4c2:f2ff:fe81:1b13/64), vetha140e6a (fe80::78dc:b4ff:fe22:469f/64)
announce_addresses	10.10.10.6, fe80::e9f:701d:3a62:593

Recorder

oldest_recorder_run	5. Oktober 2025 um 16:25
current_recorder_run	17. Oktober 2025 um 22:47
estimated_db_size	514.81 MiB
database_engine	sqlite
database_version	3.48.0

Debug logs

Diagnostics dump

home-assistant_2025-10-17T21-02-18.729Z.log

config_entry-battery_notes-01K7SZZNZYANCGCK3GXQV626CE.json
config_entry-battery_notes-01K6P8R0ZT6JA8F9W8V6S8MZAT(1).json
config_entry-battery_notes-01K6P8R0ZT6JA8F9W8V6S8MZAT.json

[andrew-codechimp]

Hi, yes this will happen if you add a manual entity based device, Battery Notes cannot tell if the entity one is the same as the main device.
I have to do this in order for the odd devices with multiple battery entities.