I did some more testing and found a way to gain insight in the “performance” of detecting BLE advertisement data.
I zoomed in on the data from one of the Tile Mate devices that was on the same location for the last week and did not move around. It is 3 meters away from the location of the Theengs Bridge and the BLED112 device.
BLED112
I don’t know how often the Tile Mate advertises per minute, but the BLED112 device discovers it an average of 4 times per minute. Then I checked the periods where the BLED112 device did not discover the Tile Mate for at least 60 seconds. This happened a couple of time in the past three days:
- 2024-09-12 - 2 times not discovered for a period of 60 seconds
- 2024-09-13 - 5 times not discovered for a period of 60 seconds
- 2024-09-14 - 4 times not discovered for a period of 60 seconds
Theengs Bridge
Then I checked the MQTT broker data to analyze how often the Theengs Bridge did not report the Tile Mate for at least 60 seconds. This happened often during the past three days:
- 2024-09-12 - 564 times not discovered for a period of 60 seconds
- 2024-09-13 - 253 times not discovered for a period of 60 seconds
- 2024-09-14 - 250 times not discovered for a period of 60 seconds
I installed the latest test version on 2024-09-12 in the evening, so that explains the improvement at 2024-09-13. The scanning has been improved a lot by the latest test version, however it still seems to “miss” a lot of BLE advertisements compared to the BLED112 device.
I wonder if the scanning could be further improved such that the Theengs Bridge would come closer to the results shown by the BLED112 device? Should I adjust specific scanning parameters? Please let me know if you want me to do more testing.