search

Thor77 / Blueproximity

Run a command once a bluetooth device is in/out of a range
GNU General Public License v2.0
66 stars 15 forks source link

Negative distances #34

Open Thor77 opened 7 years ago

Thor77 commented 7 years ago

With two different SonyEricsson K800i, and two different bluetooth dongles, it shows always negative distances:

-12 at 50cm, -7 at 1m, and so on...

The min/max data indicates: min:-31 max:255

This is the Hardy (1.2.4 version). Please, order me any other data you need.

Thanks.

Thor77 commented 7 years ago

I'm also asking for a "distance skew" feature. I'm getting "zero distance" readings through an office wall, and negative readings when I put the device right next to the receiver (a Lenovo R60 notebook in my case).

So in order to set up accurate unlock parameters I would have to be able to either (a) set negative values or (b) normalize the distance values to "my own" zero.

I suggest to introduce a feature similar to the "reset min/max" button, which would not only reset the recorded readings, but also normalize the scale to the lowest received distance value (for example, if the recorded minimum is "-10", clicking that button would set the new zero to "-10", putting a 10 point skew to the value).

Or simply make it configurable with a text input field. (By fluithle)

Thor77 commented 7 years ago

Logged In: YES user_id=522915 Originator: YES

Well, to modify sources is not inside my todo list ;-)

But it would be a good idea to add a correction rate to the configuration settings. 8-) (By coldbeer)

Thor77 commented 7 years ago

Logged In: YES user_id=114903 Originator: NO

This is kind of strange but still possible. On my original setup the rssi value that is measured only leaves negative values. I looked at several other systems and found that to be true on those too. So I decided to make very simple calculation formula, which is distance = -rssi value...

you could change that in the source if you want to... the formula should then read distance = 31 - rssi. I don't believe there could be a general fix for this. Maybe there could be a corrective shift factor in the settings... (By highno)