Calling process_advertisement on a metadevices is a bug.

[dapuzz]

Hello
I get this error message in logs:
[custom_components.bermuda] Calling process_advertisement on a metadevices (Luci Albero [54:32:04:5f:65:16]) is a bug. Advert tuple: (('54:32:04:5f:65:16', 'ac:67:b2:3b:ff:14')) (8 previous messages suppressed)

My device "Luci Albero" is a Shelly 1 Mini Gen3 (S3SW-001X8EU)
All others ESP32 devices are working fine.

How could I help you to understand why we are processing advertisement on a metadevice?
I can be wrong, but this has started after latest series of update.

Thank you.

[agittins]

Hi! I think you might be running one of the beta releases, is that right?

This seems to happen when a proxy gets "demoted" from being a scanner due to not providing proxied advertisements any longer, such as when it is rebooting or has otherwise disconnected for some reason.

It's possible that it happens under other circumstances, so if you'd like to dig further into it, I'd need a "diagnostics" download, done at a time when those logging messages are happening. If they have only happened for a short period and stopped, it's almost certainly from the device re-connecting, and can be ignored.

I will be altering the logging settings for this message before the next release, since it isn't properly an error/bug for the specific case where a proxy has disconnected but the backend still reports the old adverts for a time.

[rvanmaanen]

I'm also getting them, but already made the link with devices rebooting, as I noticed it happened a lot then and I have been rebooting my Everything Presence Lites quite a few times so didn't report it.

Using version 0.8.4:

This error originated from a custom integration.

Logger: custom_components.bermuda
Source: custom_components/bermuda/log_spam_less.py:92
integration: Bermuda BLE Trilateration (documentation, issues)
First occurred: June 1, 2025 at 06:05:45 (110 occurrences)
Last logged: 12:32:27

Calling process_advertisement on a metadevices (Presence Sensor Living Room [94:54:c5:f2:aa:6a]) is a bug. Advert tuple: (('94:54:c5:f2:aa:6a', '94:54:c5:f2:a7:46'))
Calling process_advertisement on a metadevices (Presence Sensor Living Room [94:54:c5:f2:aa:6a]) is a bug. Advert tuple: (('94:54:c5:f2:aa:6a', '94:54:c5:a0:cb:a2'))
Calling process_advertisement on a metadevices (Presence Sensor Bedroom [94:54:c5:f2:a7:46]) is a bug. Advert tuple: (('94:54:c5:f2:a7:46', '3c:8a:1f:04:a6:d2')) (2 previous messages suppressed)
Calling process_advertisement on a metadevices (Presence Sensor Bedroom [94:54:c5:f2:a7:46]) is a bug. Advert tuple: (('94:54:c5:f2:a7:46', '94:54:c5:f2:aa:6a')) (2 previous messages suppressed)
Calling process_advertisement on a metadevices (Presence Sensor Bedroom [94:54:c5:f2:a7:46]) is a bug. Advert tuple: (('94:54:c5:f2:a7:46', '94:54:c5:a0:cb:a2')) (2 previous messages suppressed)

[dapuzz]

I am using 0.8.4 and yes, it may be related to disconnections as I can see in the history of shelly I get lot's of unavailable and off back and forth

If you think there is nothing to warry about that's ok for me ^_^

[TripelJ]

Hi There. Super happy with Bermuda. But I now also face an issue..

I have several esp32 devices m5stack-atom and esp32-c3 running as bluetooth proxy and I have no issue using them with Bermuda.
But now I got a Shelly PM mini gen3 that works fine for power monitoring and now I enabled it could be used for a Bluetooth proxy.
I also now started to see these alert in the log, and only for the shelly device. I have no experience with using shelly as bluetooth proxy, but perhaps I should just order some more ESP's to use instead if there is no fix with the shelly's. I use stock firmware on the shelly.

Something to do with this ?