Metadevice already tracked despite not existing yet

[jamesonuk]

Don't think it is a bug but I can't see anywhere that explains what this means.

In the logs I am repeatedly seeing Metadevice already tracked despite not existing yet

Up to 607 instances over a couple of days now...

Is this something I haven't configured properly, a dubious device, something to be expected or something else?

[urosch]

I have similar logs:
`This error originated from a custom integration.

Logger: custom_components.bermuda
Source: custom_components/bermuda/coordinator.py:897
integration: Bermuda BLE Trilateration (documentation, issues)
First occurred: 16:28:21 (1 occurrences)
Last logged: 16:28:21

Metadevice already tracked despite not existing yet.`

[agittins]

Thanks for the report!

It's a bug, in that what is happening is something I didn't expect to happen when I was writing it :-)

I think it's harmless, but I'll dig some more, since the fact it's happening at all implies that I don't know what's going on here as well as I think I do!

@jamesonuk is that iBeacon one that you own or have configured in Bermuda? I'm guessing that this is happening when an iBeacon is detected after it has gone out of range for a while, but I'll need to test more to see what's going on - it might be a hint to a bigger problem in Bermuda, or it might be nothing.

In either case, it's harmless other than the noise in the logs, and doesn't indicate any misconfiguration or anything at your end.

[agittins]

Ah, thought this sounded familiar! 😅 I'll close this one out and track it on the original report:

Duplicate of #405

[agittins]

Duplicate of #405