The iBeacon tracker integration does not restore to the last state after a restart.

[Juriga1]

The problem

When I restart my Hassio device, trackers configured with the iBeacon integration become 'unavailable' until the device is nearby. Thus, devices that only connect once a month are typically 'unavailable' when they should be 'not_home'. In the Passive BLE Monitor integration, there is an option to restore states after a restart. Is it possible to have this option in this integration?

What version of Home Assistant Core has the issue?

core-2024.5.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

iBeacon Tracker

Link to integration documentation on our website

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

Diagnostics information

No response

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 @bdraco, mind taking a look at this issue as it has been labeled with an integration (ibeacon) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `ibeacon` 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 ibeacon` 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)}}

---

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

[Great-Chart]

I've just fathomed out similar and in the short term resort to remembering (sometimes!) to change status in Developer Tools but think this would be a great addition as somewhat pointless if the trackers have ended up off-line through HA restart. Whilst not suggesting such a feature necessarily bears much similarity to the Passive BLE Monitor its included in documentation as below. https://custom-components.github.io/ble_monitor/configuration_params#restore_state

[Juriga1]

Another way to solve the problem would be to set the status of all iBeacon devices to 'not_home' instead of 'unknown' at startup.