Describe the bug
I am experiencing an issue where a specific tracking entity keeps coming back as a "ghost entity" after every Home Assistant restart, despite being deleted multiple times and having the auto-delete feature enabled.
Here is the exact behavior:
- After a Home Assistant restart, the tracking entity reappears and shows a "normal" state.
- If I manually reload the integration from the Devices & Services page, the entity state changes to "unavailable" (nicht bereitgestellt).
- I have tried deleting the entity permanently using the
aliexpress_package_tracker.remove_tracking service in the Developer Tools, as well as deleting it directly from the integration's device overview.
- Despite deleting it, and despite having configured the integration to automatically remove tracking numbers 7 days after delivery, the entity always survives a complete HA restart and comes back.
It seems the tracking number is not being properly purged from the underlying storage file, causing the initialization process to pull it back in on every reboot.
Steps to reproduce
- Enable the setting to auto-delete packages 7 days after delivery.
- Attempt to delete an existing tracking entity via UI or the
remove_tracking service.
- Restart Home Assistant completely.
- Notice that the deleted tracking entity is back and fully present again.
- Reload the integration to see it become "unavailable".
Expected behavior
When a tracking entity is deleted (either manually via the service/UI or through the 7-day auto-purge feature), it should be permanently removed from the configuration storage and must not reappear after a Home Assistant restart.
Environment details
- Home Assistant Core Version: 2026.4.1
- Home Assistant Operating System Version: 17.2
- Home Assistant Supervisor Version: 2026.03.3
- AliExpress Package Tracker Version: 2.9.1
Additional Context
No response
Describe the bug
I am experiencing an issue where a specific tracking entity keeps coming back as a "ghost entity" after every Home Assistant restart, despite being deleted multiple times and having the auto-delete feature enabled.
Here is the exact behavior:
aliexpress_package_tracker.remove_trackingservice in the Developer Tools, as well as deleting it directly from the integration's device overview.It seems the tracking number is not being properly purged from the underlying storage file, causing the initialization process to pull it back in on every reboot.
Steps to reproduce
remove_trackingservice.Expected behavior
When a tracking entity is deleted (either manually via the service/UI or through the 7-day auto-purge feature), it should be permanently removed from the configuration storage and must not reappear after a Home Assistant restart.
Environment details
Additional Context
No response