Replies: 1 comment
-
Think I found it - the code which had the ble_tracker module in had a lambda which turned BLE scanning off and on based on the API being connected or not - I've removed it and all devices seem to be reporting properly again. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have a bunch of BLE Proxies - most of them are purpose-made for proxying BLE traffic - they are M5Stack Athom Lite's in almost every room, but as you can see from the screenshot, most of my devices are not sending advertisements. Some of the other devices are obvious and the rest are generic ESP32 devboards.
I appreciate this may not (is not?) anything to do with Bermuda but it's highlighted by Bermuda so starting off here.
All my devices inherit common components in ESPHome (i.e. the devices that are working are using exactly the same BLE config as those which aren't, all that really changes is the device core config (which is unique per make/model of device) and any additional sensors).
My common BLE config is as follows;
Beta Was this translation helpful? Give feedback.
All reactions