Skip to content
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

How to set max detection range for area #421

Open
skycryer opened this issue Jan 3, 2025 · 1 comment
Open

How to set max detection range for area #421

skycryer opened this issue Jan 3, 2025 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@skycryer
Copy link

skycryer commented Jan 3, 2025

not a bug but an understanding problem. Until now I used espresence, and there I can set the max distance per room.

For example I have configured bluetooth_proxy for devices in my bedroom and my kitchen for testing now, this rooms are on different floors. The place I put my phone every night is so,etching between the tracker for bedroom and kitchen. But kitchen is around 3 meters away and bedroom tracker around 1.5 meter. And I can see it bouncing between this areas.

The dining area also does pick the kitchen signal even it should not. Espresence was set a max distance for the kitchen tracker so outside the kitchen it was not seen.

Is that possible with Bermuda? Maybe I missed the docu for that config.

I saw the setting in config for all areas but I want to change this per area. Some areas are larger than other so it makes no sense to set this globally

@agittins agittins self-assigned this Jan 14, 2025
@agittins agittins added the enhancement New feature or request label Jan 14, 2025
@agittins
Copy link
Owner

Thanks for your question - you are right, Bermuda doesn't currently have a way to specify a max radius per proxy but I can see how it might be quite useful for your situation (and others, I'm sure).

The global setting was intended mostly as a way to tame down situations where signals outside of the home or on adjacent floors etc might be an issue, where a global setting makes sense. But both can be quite useful, I think.

I'll have a think about how best to implement this, it might be as a disabled-by-default entity on the scanner's page, that you enable to override the global setting for that particular scanner.

workaround

In the meantime, you can work around this to some degree by using the per-scanner rssi offset (in calibration 2, in the configure flow). If you use a negative offset for a given scanner, it will report devices as being "further away" than they are, which will make that scanner less likely to "win" the area for a given device, since other scanners will report a closer distance, comparatively. Obviously this isn't perfect since it distorts the calculated distance and working out a good value will be more confusing, but it is an easy way right now to "tame down" a scanner that wins areas too easily.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants