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

Data Format Mismatch #199

Closed
eyes-for-computers opened this issue Oct 8, 2022 · 2 comments
Closed

Data Format Mismatch #199

eyes-for-computers opened this issue Oct 8, 2022 · 2 comments
Labels

Comments

@eyes-for-computers
Copy link

When running the "Get sensor data synchronously with callback" sample, I receive a dictionary defined as:

'XX:XX:XX:XX:XX:XX', {'data_format': 5, 'humidity': 63.87, 'temperature': 20.68, 'pressure': 986.1, 'acceleration': 989.5534346360483, 'acceleration_x': -104, 'acceleration_y': -12, 'acceleration_z': 984, 'tx_power': 4, 'battery': 2249, 'movement_counter': 59, 'measurement_sequence_number': 57716, 'mac': 'xxxxxxxxxxxx'}

The github main defines v5 as:

'CB:B8:33:4C:88:4F': { 'data_format': 5, 'battery': 2.995, 'pressure': 1000.43, 'mac': 'cbb8334c884f', 'measurement_sequence_number': 2467, 'acceleration_z': 1028, 'acceleration': 1028.0389097694697, 'temperature': 22.14, 'acceleration_y': -8, 'acceleration_x': 4, 'humidity': 53.97, 'tx_power': 4, 'movement_counter': 70, 'rssi': -65 }

The key issue for me is the lack of 'rssi'. Am I missing something?

  • OS: Raspbian Stretch
  • RuuviTag firmware version: 3.31.1
  • Data format: 5
@terop
Copy link
Contributor

terop commented Oct 9, 2022

Kind of, RSSI reporting is not yet release, please check the changelog. If you want the RSSI information you must install the development version, please check the instructions at https://github.com/ttu/ruuvitag-sensor#installation.

The situation with information about unreleased features shown in documentation is sub-optimal but I don't know what would be the best way to avoid it.

@ttu
Copy link
Owner

ttu commented Oct 9, 2022

The situation with information about unreleased features shown in documentation is sub-optimal but I don't know what would be the best way to avoid it.

There are few common ways to handle documentation.

  • Dedicated documentation page, where it is easy to select version.
  • Version specific documentation is in PyPi/npm/etc.
  • GitHub's main-branch is the latest released version and then there would be a separate development-branch.

This repo has version-specific documentation in PyPi and main-branch has the latest development version. Works often well enough, especially if releases are pretty frequent, so then there is less chance for confusion.

This time I haven't made a new release as there has been project setup file changes, and I haven't had time to test installations thoroughly.

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

No branches or pull requests

3 participants