Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HomeAssistant Log Warnings #405

Open
cuchipandy opened this issue Dec 4, 2024 · 7 comments
Open

HomeAssistant Log Warnings #405

cuchipandy opened this issue Dec 4, 2024 · 7 comments

Comments

@cuchipandy
Copy link

Describe the bug

Error

Configuration

Config
Globals
Select

Diagnostics

Working on it

@agittins
Copy link
Owner

agittins commented Dec 5, 2024

Thanks for your report - I'm a little puzzled how Bermuda has got to that point to log those warnings, so I'd be very interested to see the diagnostics if you are able to upload them. If you're having trouble getting them to download, the best bet is to "Reload integration" on Bermuda, then after about 30 seconds try the "Download Diagnostics" - it should be pretty quick after a recent reload.

This performance issue with the diagnostics will be fixed in the next version.

@cuchipandy
Copy link
Author

I can get diagnostics that way but maybe the warnings didnt log in the first 30s after reload integration.
is it important to log the warnings?

@cuchipandy
Copy link
Author

I think i catched the warnings in this log...
config_entry-bermuda-01JDQPQ9HNB179M8TKB28WSM1Y.json

@cuchipandy
Copy link
Author

@Wiikendz
Copy link

Wiikendz commented Jan 2, 2025

Any new to this issue? I've also started getting these Log Warnings..

@jamesonuk
Copy link

Following on from the issue reported above.

This is definitely not anything I have configured (in fact I setup Bermuda to test with my phone then I replaced the phone a few weeks ago and have just realised I did not update this....) So I had not actually asked Bermuda to track anything that was going to be in my house given the old phone has gone off for trade in

What is interesting though is that the ID is the same in both reports 1ca92e23f0874df7b9a2fd4b716a4bf6 followed by a bit I presume is not part of the ID.

I do wonder whether this could be something to do with privacy and random MAC type stuff ???

@agittins
Copy link
Owner

Thanks for the extra info. Yes, I think it is related to when iBeacon devices either return into range, or when the MAC address changes in the case of devices using IRK (phones, fancier watches etc). I think it will happen with any iBeacon device whether it's "configured" or not, since Bermuda tracks these things in the background anyway so we can later make the best use of all available data for locating.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants