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

RSSI Values on API for Known BT Classic and BLE Devices #177

Closed
paulrbeers opened this issue Apr 22, 2020 · 2 comments
Closed

RSSI Values on API for Known BT Classic and BLE Devices #177

paulrbeers opened this issue Apr 22, 2020 · 2 comments

Comments

@paulrbeers
Copy link

Is your feature request related to a problem? Please describe.
It's somewhat difficult/time consuming to dial in RSSI values for both BLE and BT Classic since every device is different

Describe the solution you'd like
Now that I am aware of the API, could we get the measured RSSI value? Currently there is the distance calculated, but I'd love to be able to see the RSSI values so I can tweak the settings

Describe alternatives you've considered
Manually logging into each node (I have 10? now), stopping the room-assistant service and using HCITool for BT Classic and manually starting/stopping room-assistant to get the BLE values

Additional context
No I don't want to know all devices out there, just the ones I've spelled out in my local.yml file.

@mKeRix
Copy link
Owner

mKeRix commented Apr 22, 2020

Great idea, that would certainly help for tuning the values! :)

mKeRix added a commit that referenced this issue May 31, 2020
Tuning BLE values is tricky if the measured RSSI and the measuredPower
used for calculation are not visible anywhere. Putting them into the
attributes would cause a lot of data to be constantly updated in the
other integrations, so now they are just available in the API as an
additional field of the entity.

Closes #140, #177 and #203
mKeRix added a commit that referenced this issue May 31, 2020
Tuning BLE values is tricky if the measured RSSI and the measuredPower
used for calculation are not visible anywhere. Putting them into the
attributes would cause a lot of data to be constantly updated in the
other integrations, so now they are just available in the API as an
additional field of the entity.

Closes #140, #177 and #203
github-actions bot pushed a commit that referenced this issue May 31, 2020
# [2.8.0](v2.7.1...v2.8.0) (2020-05-31)

### Features

* **bluetooth-low-energy:** add RSSI and measuredPower to entity ([ec48507](ec48507)), closes [#140](#140) [#177](#177) [#203](#203)
* document API with OpenAPI ([4d6d4de](4d6d4de))
* draw temperature values on heatmaps ([d2ad9bf](d2ad9bf))
* **grid-eye:** add heatmap camera entity ([ac52e76](ac52e76))
* **home-assistant:** add support for camera entities ([bc941ad](bc941ad))
* **omron-d6t:** add heatmap camera entity ([aee7f09](aee7f09)), closes [#199](#199)
@mKeRix
Copy link
Owner

mKeRix commented May 31, 2020

This has been added in 2.8.0! 🎉

@mKeRix mKeRix closed this as completed May 31, 2020
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

2 participants