Gost entry detected

[chemelli74]

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

At each restart a old and removed device is detected:

Maybe you just list all entries without looking at if still active ?

Reproduction steps

1. Install
2. Configure for device A
3. Remove device A from it's main integration, Shelly for example
4. Remove device A from BatteryNote
5. Restart
6. Verify is still detected

System Health details

Metodo di installazione
Home Assistant Container
Core
2025.11.3
Frontend
20251105.1

Debug logs

Diagnostics dump

No response

[andrew-codechimp]

Discovery scans the device_registry, the main integration should have deleted the entry from that, I wonder if it's setting something I need to filter out rather than deleting.

If you are able to can you find that main device within config/.storage/core.device_registry and post the row of json so I can see if there's anything I'm missing. You should be able to search by name to find it.

It's ok to obfuscate any data that's sensitive.

[chemelli74]

I realized where the problem lies.

I have a Shelly device that is also added as device_tracker from Vodafone.

I then removed the Shelly device from Shelly integration page, but the device is not removed from HA and is now a empty one. Is linked to the way device_tracker handled entities (meaning it create a device only if another integration has one, otherwise create only the entity).

This is the reason of the "ghost" entry in my registry.

Will dig into this with core Team.

[andrew-codechimp]

Ok, that didn't feel quite right as normally the device will be deleted.
If you get any further insight please let me know if I'm missing handling some scenario.
Although a lot has changed in v3 the discovery code hasn't so it's odd this is the first report in 2 years.