Private BLE Tracker, entities changing name

[FabioEight]

The problem

This is the second time I'm facing an issue with Private BLE Device, following a Core upgrade. Last day, I upgraded to 2024.5.4 from 2024.5.2 and my BLE Device Tracker entities got renamed:

As you can see, the device_tracker entities are renamed to "_2" and the original stop working (red mark on the right). I have performed no actions/changes on Private BLE. MAC addresses of the devices are correct. I had the same issue a couple of months ago, again, following a HA Core upgrade (can't recall the version).

What version of Home Assistant Core has the issue?

2024.5.4

What was the last working version of Home Assistant Core?

2024.5.2

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Private BLE Device

Link to integration documentation on our website

https://www.home-assistant.io/integrations/private_ble_device

Diagnostics information

Syslog did not record any relevant log for private BLE integration.

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @jc2k, mind taking a look at this issue as it has been labeled with an integration (private_ble_device) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `private_ble_device` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign private_ble_device` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

private_ble_device documentation private_ble_device source _{^{(message by IssueLinks)}}

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.