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

BT Classic distance measurements change too slowly #775

Closed
mKeRix opened this issue Jun 23, 2021 · 7 comments
Closed

BT Classic distance measurements change too slowly #775

mKeRix opened this issue Jun 23, 2021 · 7 comments

Comments

@mKeRix
Copy link
Owner

mKeRix commented Jun 23, 2021

The current Kalman filter configuration for BT Classic acts too slow when moving large distances. This appeared after the filter values were tuned in a recent version.

More info: #774

@bobonthenet
Copy link

Does this same issue impact Bluetooth Low Energy? I'm experiencing extremely slow changes over long distances. Going from say 20 meters to 1 meter can take several minutes. I'm only using the BLE integration though.

@miczlo
Copy link

miczlo commented Dec 8, 2021

I was just looking at the data coming from 4 different nodes and they seem to be slowly drifting when the device is moved and it can take the nodes a couple minutes even to stabilise on the correct value.

@bobonthenet
Copy link

@w4rthog is that for classic or BLE?

@miczlo
Copy link

miczlo commented Dec 8, 2021

@bobonthenet Sorry, that's BT Classic as per the issue. Having said that BLE also has Kalman filter applied so I'd expect same behaviour?
I had a quick look and yeah it looks like the Kalman filter is just causing said drift.
I moved my phone from one room to another.
RSSI used to be around -6 now it's 4 when read directly.
My distance is falling slowly but steadily and it takes like 5 minutes to stabilize
image
@mKeRix Any chance we could get some parameters to configure the filter ourselves or at least option disable it? Or maybe just expose the raw RSSI over the API as well?

@stevencoutts
Copy link

Same issue here, any ideas on a fix for this?

@mKeRix mKeRix closed this as completed in 6325937 Mar 20, 2022
mKeRix added a commit that referenced this issue Mar 20, 2022
Should allow users to fine-tune the noise reduction mechanism for their
use case.

Refs #775
github-actions bot pushed a commit that referenced this issue Mar 20, 2022
# [2.20.0](v2.19.1...v2.20.0) (2022-03-20)

### Bug Fixes

* **bluetooth-classic:** increase change detection speed ([6325937](6325937)), closes [#775](#775)
* **docker:** include heatmap dependencies in image ([7cf5de1](7cf5de1)), closes [#826](#826)

### Features

* **bluetooth:** add configuration options for noise filter ([85981ee](85981ee)), closes [#775](#775)
* expose some config options as env variables ([#1099](#1099)) ([3ae8e9a](3ae8e9a)), closes [#1094](#1094)
@github-actions
Copy link

🎉 This issue has been resolved in version 2.20.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

github-actions bot pushed a commit that referenced this issue Mar 20, 2022
# [3.0.0-beta.5](v3.0.0-beta.4...v3.0.0-beta.5) (2022-03-20)

### Bug Fixes

* **bluetooth-classic:** increase change detection speed ([6325937](6325937)), closes [#775](#775)
* **docker:** include heatmap dependencies in image ([7cf5de1](7cf5de1)), closes [#826](#826)

### Features

* **bluetooth:** add configuration options for noise filter ([85981ee](85981ee)), closes [#775](#775)
* expose some config options as env variables ([#1099](#1099)) ([3ae8e9a](3ae8e9a)), closes [#1094](#1094)
@github-actions
Copy link

🎉 This issue has been resolved in version 3.0.0-beta.5 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants