home-assistant[bot]
commented
7 months ago 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)
vdiogo
Ekomak
taxitain
heyitsmed00d3
johnnvp
The problem
I have a Aiyato tag. Home Assistant spotted it as a new device and prompted me to add the iBeacon integration. The ibeacon tracker integration shows no devices or entities... Restarts, reboots, reloads... no difference. Why did it spot something that it seems unable to see ?
What version of Home Assistant Core has the issue?
2024.1.5
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
Link to integration documentation on our website
No response
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