"Orphaned" Battery Note

[rugbyopera]

Checklist

• I have restarted Home Assistant after the HACS or manual install.
• 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

3.0.4

Describe the issue

I have a pending Repair from Battery Notes that I cannot deal with in a satisfactory way. The repair message reads, "The associated device or entity no longer exists for the Battery Note entry [redacted device name], the Battery Note should be deleted. Select Submit to delete this Battery Note."

The device went offline temporarily. It's now back online, and Battery Notes is tracking the battery state, but this repair issue persists, even after multiple HA restarts. My only option is to delete the battery note, lose all of the state history, and then recreate the battery note.

What I expected: (1) An option to Ignore the repair issue during the time when the device was offline, before it came back online. (2) The repair issue to self-dismiss once the device came back online.

Reproduction steps

1. Set up a device with Battery Notes.
2. Have the device become unavailable. I don't know if it needs to be unavailable at a particular time (ie HA startup) or not.

System Health details

Version | core-2025.11.3 -- | -- Installation type | Home Assistant OS Development | false Supervisor | true Docker | true Container architecture | amd64 User | root Virtual environment | false Python version | 3.13.9 Operating system family | Linux Operating system version | 6.12.51-haos CPU architecture | x86_64 Timezone | America/New_York Configuration directory | /config

Debug logs

Diagnostics dump

No response

[andrew-codechimp]

Hi, that's unusual as most devices don't raise orphan issues when they become unavailable.
What integration are you using? If it's a custom/HACS one can you give me the link.

[patienttruth]

I have a similar issue. Ive had to remove and re-include two zwave devices (z-wave js ui) recently due to some debugging and testing. They're not being recognized as the same device by Battery Notes and I'd prefer to retain the history, especially since the batteries did not get changed.

Is there anything I can manually change to get Battery Notes to recognize the new config record?

[andrew-codechimp]

Is there anything I can manually change to get Battery Notes to recognize the new config record?
If you manually remove and re-add a device then no there's no easy way to move the data, it's all associated by device-id's and it's very error prone to edit by hand.
You can set the battery replaced date manually using the action though.

[patienttruth]

Copy that. Thanks Andrew.