OpenMarine
BMP388 on I2C Bus - Printable Version

+- OpenMarine (https://forum.openmarine.net)
+-- Forum: MacArthur HAT (https://forum.openmarine.net/forumdisplay.php?fid=29)
+--- Forum: General discussion (https://forum.openmarine.net/forumdisplay.php?fid=30)
+--- Thread: BMP388 on I2C Bus (/showthread.php?tid=6870)



BMP388 on I2C Bus - carango - 2026-04-25

Hello,

I am trying to connect a BMP388 sensor on the I2C bus in OpenPlotter 4 and send its values to Signal K, but I am stuck.
System
  • OpenPlotter 4
  • I2C app version 4.2.0
  • Signal K up to date
  • BMP388 connected on I2C
  • Sensor detected at address 0x77
What I already verified

So the BMP388 seems to be visible on the I2C bus at 0x77.

I2C app configuration

In the OpenPlotter I2C app, I configured the sensor as BMP3XX with:
  • address: 0x77
  • channel: pressure
  • Signal K key: environment.inside.pressure
  • rate: 1.0
and also:
  • address: 0x77
  • channel: temperature
  • Signal K key: environment.inside.temperature
  • rate: 1.0



Problem

In Signal K, I do not get actual values.
The data browser only shows:



No data available. Waiting for data…”


So I am unsure whether:
  1. BMP3XX support is currently broken or incomplete in OpenPlotter 4 / I2C 4.2.0
  2. there is an additional step required to publish the sensor data to Signal K
  3. the BMP388 should be configured differently
  4. the environment.inside.temperature / environment.inside.pressure keys are correct for this use case



Additional background

At one point I had an old i2c-reader package in Signal K that failed with:

Failed to start: Could not locate the bindings file…”

That package has now been removed, so I am trying to use only the native OpenPlotter I2C app path.

My questions
  • Is BMP388 / BMP3XX expected to work in OpenPlotter 4 I2C 4.2.0?
  • Is there a missing step to get the values into Signal K?
  • Is there any known issue with BMP3XX on OpenPlotter 4?
  • Should I test another sensor type or another Signal K key mapping?



Any help would be appreciated. Thanks a lot.
georg
:::