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

BME280 Pressure unit bug #83

Open
jdavid opened this issue Aug 20, 2021 · 2 comments
Open

BME280 Pressure unit bug #83

jdavid opened this issue Aug 20, 2021 · 2 comments

Comments

@jdavid
Copy link
Member

jdavid commented Aug 20, 2021

Data from BME280 is stored in Pa, because that's what returns the getPressure function from the Waspmote API.
e.g. see bme_pres in https://wsn.latice.eu/admin/wsn/frame/22948999 /change/

Except when we use the SDI-12 slave board (QT Py). Then the data is in hPa (hPa is what the sensor actually sends I think).
e.g see bme_pres in https://wsn.latice.eu/admin/wsn/frame/38139406/change/

The bug: The pressure values are in Pa or hPa depending on whether it's directly attached to the waspmote, or it goes through SDI-12.
Should this be fixed so we have always the same unit in the database?

Which unit should be used: Pa or hPa?
Even if we decide not to fix it in the Waspmote, I need to know what unit to use for the future RIOT based motes. @ArcticSnow

Personally I prefer Pa because: then we can use integers (more efficient than floats), and because most of the data today is in Pa. But maybe from a scientific point of view hPa makes more sense?

@ArcticSnow
Copy link
Member

Pa is fine and is the SI unit. hPa is a meteorological convention. The most important is to be aware in which unit the data is.

@jdavid
Copy link
Member Author

jdavid commented Aug 23, 2021

Ok, done for the Riot application, sends Pa.

But what to do with existing data, and the deployed motes that use Qt Py? Should I handle this an convert hPa to Pa in the server, so we use the same unit for every mote?

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

No branches or pull requests

2 participants