-
Notifications
You must be signed in to change notification settings - Fork 803
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
BLE Whitelist. #331
Comments
Do you think an mqtt json payload with the list of whitelist & blacklist devices answer the need? |
I was more thinking of something along the lines of a whitelist hardcode in the firmware. Right now, I am at 1.8k Topics due to my 7 Esp32 spamming every single thing they find. |
Agree, would be great to scan and get mqtt msg only for relevant BLE devices! |
Thats the way ESPHome works. Define MAC for relevant devices. Would be great OMG has this feature too. |
It would be great to get a scan of one or more g-tags (beacons) that you define yourself (whitelist). Perfect would be information that the beacon is in range or not. If it not in range you get the payload "off" or similar |
I'm planning to add this feature to the next release. Nevertheless I'm still thinking about how to set this whitelist. @maxi1134 the drawback with hardcoded list is that users that take directly the binary file will not be able to use this feature. Why would you not be interested in passing the list by mqtt? |
@1technophile I'm not against the idea. MQTT Would be a more elegant solution now that I think about it. |
ok thanks for the feedback I will design it like that |
Hello, where i can set the Whitelist? Greetz |
Hello, the infos were on the commit msg: |
Question, would it be possible to have a separate topic for the Whitelist? This way you can update whitelist for multiple gateways at once. Myself I use 8 to do per room location. |
Did you try to publish to all the gateways like that: |
Hi, |
Hi, since this I have updated the wiki : |
Hey 1Technophile. Just updated my tester to the latest version of OMG. This is the result on the serial monitor.
The problem is that it keeps detecting other BL devices and publishing them to home/home_presence/Bedroom2 (The gateway name is Bedroom2) |
Hey, Could you post an extract of the serial monitor when publishing non expectedBLE devices? |
Of course,
|
thanks for pointing this, just corrected it in the development branch |
Should be better with my last commit |
Hi there! I just tried setting up the whitelist again (Added a bunch of Hues bulbs w/ Bluetooth in my house and now it's really getting spammed 😅) But it doesn't seem to work. I do see this in the logs of the ESP32 when sending the Whitelist command: But then it keeps listing everything it sees. Instead of just E0:11:26:89:84:17 |
Hi, did you followed the topic mentionned in the doc to publish your command? |
Your topic should end by "config" instead of "set" |
Hi, I have managed to make white list work, but is there any way to temp disable the already set white list and enable later? e.g. {"white-list":"off"} or {"white-list":"false"}, thanks ! |
Not for the moment, you can submit a feature request if you want |
Is your feature request related to a problem? Please describe.
A Whitelist for the Bluetooth Scan for MQTT presence location.
Describe the solution you'd like
A whitelist, this would allow to reduce irrelevant data on the MQTT server, Living in an appartment block, I usually get 20 to 30 devices detected per scan.
Describe alternatives you've considered
A black list could also be usefull.
Additional context
Pretty straightforward.
The text was updated successfully, but these errors were encountered: