Closed FabioEight closed 2 weeks ago
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!
(message by CodeOwnersMention)
private_ble_device documentation private_ble_device source (message by IssueLinks)
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.
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:
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