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

[Bug]: BME680 data output no longer works #3956

Closed
memo-567 opened this issue May 22, 2024 · 7 comments
Closed

[Bug]: BME680 data output no longer works #3956

memo-567 opened this issue May 22, 2024 · 7 comments
Labels
bug Something isn't working

Comments

@memo-567
Copy link

Category

Other

Hardware

T-Beam

Firmware Version

2.3.10.d19607b Alpha

Description

After updating to FW 2.3.10, the BME680 data output no longer works.
After downgrading to FW 2.3.9, everything works perfectly again.
Tested twice.

Relevant log output

No response

@memo-567 memo-567 added the bug Something isn't working label May 22, 2024
@Talie5in
Copy link
Contributor

Talie5in commented May 22, 2024

I've tested rolling back #3904 as a test case against RAK4631 variant (only hardware i have a BME680/RAK1906)

Test #1:
changing the BSEC2 package back to 1.5.2400, building and flashing... sensors come back (no IAQ displaying)
Test #2:
changing the BSEC2 package back to 1.6.2400, building and flashing... sensors come back (no IAQ displaying)
Test #3-7
changing BSEC iteratively backwards until #898bc7d where Sensor Data returns (last good working commit against meshtastic/firmware, also changing lib path where it changes to bsec2 appropriately)

Looks like

in platformio.ini

lib_deps =
  https://github.com/boschsensortec/Bosch-BSEC2-Library#v1.6.2400

in variant.h under rak4631

build_flags = ${nrf52840_base.build_flags} -Ivariants/rak4631 -D RAK_4631
  -L "${platformio.libdeps_dir}/${this.__env__}/**BSEC2 Software Library**/src/cortex-m4/fpv4-sp-d16-hard"

@memo-567
Copy link
Author

memo-567 commented May 23, 2024

A small side effect of the update and back:
Before the update to 2.3.10, the temperature displayed was 0.8 °C higher than that of the reference thermometer. This was fine since it was still within the BME680's one degree manufacturing tolerance.
After going back and forth, there is a difference of 2.8 °C!
A reset to factory settings does not lead to any changes, as it is not a real reset. Data will still be preserved somewhere on the device. Maybe also (wrong) data stored by the BME680?

@memo-567
Copy link
Author

I have shut down the node with the sensor for now. The difference was getting bigger and bigger.
At the end the temperature difference to the reference thermometer was almost 6 °C.

@caveman99
Copy link
Member

resolved with 2.3.11

@memo-567
Copy link
Author

memo-567 commented Jun 3, 2024

Works again, but with restrictions only. The air pressure is displayed incorrectly (10.1 hPa) and the line is overwritten on the left side by the new added (V and mA) values.
photo_2024-06-02_14-54-48

@Talie5in
Copy link
Contributor

Talie5in commented Jun 3, 2024

Works again, but with restrictions only. The air pressure is displayed incorrectly (10.1 hPa) and the line is overwritten on the left side by the new added (V and mA) values. photo_2024-06-02_14-54-48

Thats a client side issue - the Android app needs updating to suit from everything I've seen discussed.

@memo-567
Copy link
Author

memo-567 commented Jun 3, 2024

Possibly the voltage and current values, but the incorrect air pressure can probably be traced back to the Bosch library.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants