-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
Suggestion to be able to select Bluetooth radios to use #164
Comments
Hmmm good point. I have an issue to implement independently calibrating both proxies and beacons at #45 that will let you effectively define the receiver sensitivity by proxy - so you'd offset the bluetooth adaptor so that it reported accurate distances. This would solve the particular problem you are having, but I think the ability to disable a scanner completely from calculations is a good idea - we'll need it if/when we support scanners that are not fixed in location (like mounted on a robot vacuum etc). Right now I'm tossing up where to put the configuration - whether to put it on the device page as an entity or whether to put it into the options_flow when you click the "Configure" button for Bermuda. The latter is starting to get a bit crowded, but it might be the better place for it. I'll make a decision on that soon, and get a fix sorted. My bt dongle also gets a stronger signal than the esp32's, so yeah I get warped into the garage more often than I should, too! 😅 |
This is exactly my issue. I have mainly two types of ESP32 boards that would require independent calibration of RSSI strength/sensitivity to achieve accurate localization. Looking forward to the independent calibration. |
While you're adding individual base station calibration, I would wonder if the area of each room could be specified as well. Some rooms are small and others are large. Shrinking area radius of the smaller rooms would be even more important when the adjoining room does not have an ESP32 base station. |
Hello, I'd like to express my gratitude for the great project. It's working better for me than other projects of this type that I've tried. I suggest placing it on the device page as an entity, as putting it on the configuration page might make it easy to miss. As someone who has other integrations with multi-page configurations, it's hard to remember what's on each page and where it is. |
Duplicate of #45 |
I'm going to close this one out and track progress on the original issue #45 which will include both per-proxy offset for |
Just deployed yesterday and It is working great!
Just one challenge:
I have four ESP32 proxys around my house, plus the Pi4 Bluetooth radio. The issue that I am facing is that the Pi4 captures most of the activity from the BLE devices nearby.
For example, while my smart watch is 1-2 meters from the Kitchen ESP32, the Pi4 (8-10 meters away) picks up a stronger signal and provides a false location.
It would be helpful to be to select which radios to utilize.
Thank you
The text was updated successfully, but these errors were encountered: