I2C BMP280 does not show in Signal K

[Rosea]

Hi all, I can't get any readings from my BMP280 sensor in Signal K. It's wired to the right GPIOs und it shows up in I2C correctly. However Signal K doesn't get those data. 
Any ideas how to solve that problem? 
cheers Dominik

[baltika_no_9]

Have you got a screenshot of the I2C panel showing the device?

[TwistedAnkles]

I've got the same issue.  Macarther Hat on a Pi5.  It is added, with address 0x76 on OpenPlotter's I2C--a BMP280--and showing "Signal K Keys" for pressure and temperature.  I'm just not seeing them as paths on the SK instrument panel.

[saltwaterone]

Hi all, I can't get any readings from my BMP280 sensor in Signal K. It's wired to the right GPIOs und it shows up in I2C correctly. However Signal K doesn't get those data. 
Any ideas how to solve that problem? 
cheers Dominik

I am new to this forum so sorry if this has been covered already, but I saw your I2C question, and many other I2C connection questions (related to I2c connections to signalK) and I wanted share my solution to dozens of annoying I2C (and UART) issues I've experienced with signalk, and just generally getting I2C sensors working on the boat.   I've basically stopped all my efforts to connect them to RPi and instead have standardized on CAN and USB for all device connections to the RPi by using ESP32s to terminate I2C and then convert the data into NMEA syntax (after applying whatever logic I need at the sensor level), then only sending NMEA to the Pi/signalK.  I did this because it was just getting super messy, wire-wise, at the Pi server, and I also found it allowed me to apply lots of granular logic at the sensor/ESP level so that signalK can just report and alert.  The logic part may not be particularly useful for the BMP280 sensor, but for water level or temp sensors, I can code pretty granular logic related to what is sense, when, how it's changed, thresholds of concern, etc., and all signalk has to do is surface the data.  There are some great esp32 nmea libraries so it's not super difficult to do, and for me, it has saved a ton of headaches.  Just a thought, i hope it is helpful.

[PaddyB]

Hi all, I can't get any readings from my BMP280 sensor in Signal K. It's wired to the right GPIOs und it shows up in I2C correctly. However Signal K doesn't get those data. 
Any ideas how to solve that problem? 
cheers Dominik

I am new to this forum so sorry if this has been covered already, but I saw your I2C question, and many other I2C connection questions (related to I2c connections to signalK) and I wanted share my solution to dozens of annoying I2C (and UART) issues I've experienced with signalk, and just generally getting I2C sensors working on the boat.   I've basically stopped all my efforts to connect them to RPi and instead have standardized on CAN and USB for all device connections to the RPi by using ESP32s to terminate I2C and then convert the data into NMEA syntax (after applying whatever logic I need at the sensor level), then only sending NMEA to the Pi/signalK.  I did this because it was just getting super messy, wire-wise, at the Pi server, and I also found it allowed me to apply lots of granular logic at the sensor/ESP level so that signalK can just report and alert.  The logic part may not be particularly useful for the BMP280 sensor, but for water level or temp sensors, I can code pretty granular logic related to what is sense, when, how it's changed, thresholds of concern, etc., and all signalk has to do is surface the data.  There are some great esp32 nmea libraries so it's not super difficult to do, and for me, it has saved a ton of headaches.  Just a thought, i hope it is helpful.

I do similar, though send the data as signalk deltas over udp. Played with BLE for a little while but haven't got that working properly yet.

[saltwaterone]

Hi all, I can't get any readings from my BMP280 sensor in Signal K. It's wired to the right GPIOs und it shows up in I2C correctly. However Signal K doesn't get those data. 
Any ideas how to solve that problem? 
cheers Dominik

I am new to this forum so sorry if this has been covered already, but I saw your I2C question, and many other I2C connection questions (related to I2c connections to signalK) and I wanted share my solution to dozens of annoying I2C (and UART) issues I've experienced with signalk, and just generally getting I2C sensors working on the boat.   I've basically stopped all my efforts to connect them to RPi and instead have standardized on CAN and USB for all device connections to the RPi by using ESP32s to terminate I2C and then convert the data into NMEA syntax (after applying whatever logic I need at the sensor level), then only sending NMEA to the Pi/signalK.  I did this because it was just getting super messy, wire-wise, at the Pi server, and I also found it allowed me to apply lots of granular logic at the sensor/ESP level so that signalK can just report and alert.  The logic part may not be particularly useful for the BMP280 sensor, but for water level or temp sensors, I can code pretty granular logic related to what is sense, when, how it's changed, thresholds of concern, etc., and all signalk has to do is surface the data.  There are some great esp32 nmea libraries so it's not super difficult to do, and for me, it has saved a ton of headaches.  Just a thought, i hope it is helpful.

I do similar, though send the data as signalk deltas over udp. Played with BLE for a little while but haven't got that working properly yet.

Cool, I have not considered sending via UDP, it's an interesting idea, especially if WiFi is used.  I ended up combining a three axis compass, a gps (I love the little GPS i'm using - a ublox M10, super fast acquisition and crazy accurate/sensitive), a BME680 temp sensor (which also includes a carbon dioxide/VOC sensor as a bonus!) and a 9-axis IMU on the same I2C bus (except the compass, which is UART) of a single ESP32, and I think I have them shielded well enough that I can mount in a single hockey puck like enclosure below the dodger in the companion way, and call it a day for those data sources, all on the single USB cable.   I was wrong that libraries exist for some of this, I had to write the conversion to NMEA0813 myself, but it works great, checksum and all.  SignalK is just incredible, I had to do almost no tweaking of that other than establishing the paths for the environmentals and IMU data.  The only tricky part will be exposing the temp sensor to air while the rest of the sensors are sealed in a waterproof enclosure.  I am working through 3D printed designs and I think I'm getting close.  It's just crazy how much high integrity data sensors can be combined like this in such a small form factor these days.  I think all in it cost around  $120, if that.  Man I love the open boating stuff!

[PaddyB]

You can get some great boards made up as well with high quality sensors really cheap by jlcpcb. This has not been turned off for about 6 years now.

https://github.com/boatybits/boatymonpy

Micropython but just paid for claude pro so it will likely do a great job rewriting the code far better than I could ever hope to do.
Even my fridge talks signalk

[saltwaterone]

You can get some great boards made up as well with high quality sensors really cheap by jlcpcb. This has not been turned off for about 6 years now.

https://github.com/boatybits/boatymonpy

Micropython but just paid for claude pro so it will likely do a great job rewriting the code far better than I could ever hope to do.
Even my fridge talks signalk

So cool...  Is that your board design?   If so did you use a company like PCBWay to build it?   I dont have the hardware chops to get the RF, EMI stuff good enough to commit to a bespoke board, but more of this kind of thing, with simple plug and play interfaces, woukd go lomg way toward making open boating more broadly available.

[PaddyB]

You can get some great boards made up as well with high quality sensors really cheap by jlcpcb. This has not been turned off for about 6 years now.

https://github.com/boatybits/boatymonpy

Micropython but just paid for claude pro so it will likely do a great job rewriting the code far better than I could ever hope to do.
Even my fridge talks signalk

So cool...  Is that your board design?   If so did you use a company like PCBWay to build it?   I dont have the hardware chops to get the RF, EMI stuff good enough to commit to a bespoke board, but more of this kind of thing, with simple plug and play interfaces, woukd go lomg way toward making open boating more broadly available.

drawn up here - https://easyeda.com/editor
then these guys build them - https://jlcpcb.com/
Really handy, even just for little NMEA break out boards or whatever.