Czy wolisz polską wersję strony elektroda?
Nie, dziękuję Przekieruj mnie tam
// startDriver BMPI2C 8 14 1 2 3 0
// startDriver BMPI2C [CLK] [DATA] [ChannelForTemp] [ChannelForPressure] [ChannelForHumidity] [Addr]
// Adr8bit 0 for 0x77, 1 for 0x76Info:MAIN:Starting BMPI2C.
Warn:SENSOR:No sensor detected on selected address!
Warn:SENSOR:No sensor detected on alternative address, check wiring!
Error:SENSOR:BMPI2C failed!
Info:MAIN:Started BMPI2C.
Info:CMD:[WebApp Cmd 'startDriver BMPI2C 1 2 1 2 3 0' Result] OK
TL;DR: If you have a 4-pin BMP280 and want it working fast, use BMPI2C, not the BMP280 driver. One expert reply said, "SCL goes first, then SDA." For openESP32 users, this solves custom-build confusion, pin-order mistakes, and address-selection issues when bringing BMP280 data online over MQTT. [#21884401]
Why it matters: This thread shows that most BMP280 setup failures came from using the wrong driver, the wrong pin order, or the wrong I2C address.
| Option | Status in thread | Best use | Main risk |
|---|---|---|---|
| BMP280 driver | Reported as problematic on ESP devices | Only if you specifically rebuild for it | Driver issues on ESPs |
| BMPI2C | Already enabled on openESP32 | BMP280 over I2C | Wrong pins or wrong address |
| AS3935 | Not supported | Use another method | No planned support |
Key insight: The thread’s main fix was simple: replace
ENABLE_DRIVER_BMP280withENABLE_DRIVER_BMPI2C, then start BMPI2C with the correct SCL-first pin order and the matching 0x76/0x77 address setting. [#21884401]
startDriver BMPI2C [CLK] [DATA] [TempChannel] [PressureChannel] [HumidityChannel] [Addr]. [#21884346]0 means 0x77, and 1 means 0x76 for the BMP280-compatible BMPI2C setup. [#21884346]22 21, not 21 22. [#21884388]ENABLE_DRIVER_BMP280 with ENABLE_DRIVER_BMPI2C in the PR, because BMPI2C supports BMP280 and was the working path discussed for openESP32. That means you do not keep chasing the older BMP280 driver if your goal is simply to read a BMP280 sensor. [#21884401]startDriver BMPI2C [CLK] [DATA] [Temp] [Pressure] [Humidity] [Addr]. 1. Put SCL first and SDA second. 2. Assign channel numbers for temperature, pressure, and humidity. 3. Set the last value to 0 for 0x77 or 1 for 0x76. The example shown was startDriver BMPI2C 8 14 1 2 3 0. [#21884346]IO14 on an ESP32-C3, and that pin was identified as one of the flash pins. The reply said the crash was expected in that case, so the reset was tied to invalid pin choice, not proof that BMPI2C itself was unusable on ESP32-C3 hardware. [#21884363]IO14 on the ESP32-C3 in this setup. The thread explicitly says IO14 is one of the flash pins, and using the default or example 8 14 pair on a C3 caused the reboot behavior the user saw. Use other pins instead of copying the example blindly. [#21884363]ESP_RST_INT_WDT was the reboot reason shown immediately after a bad BMPI2C pin setup on an ESP32-C3-Mini. Practically, it marked a watchdog-triggered reset during startup, and the discussion tied it to using IO14, which was said to be a flash pin on that board. [#21884351]startDriver BMPI2C 22 21 1 2 3 0 if you are testing address flag 0. The thread corrected 21 22 to 22 21 explicitly. [#21884388]Detected sensor on alt address, id: 0x58, edit conf!, and switching the final address parameter from 0 to 1 was the next step that moved the setup forward. [#21884391]0 for 0x77 and 1 for 0x76. That mapping was stated directly in the command example, so address selection is not guessed from the pinout alone. You change only the last value when testing the alternate address. [#21884346]1 2 3, so temperature went to channel 1, pressure to channel 2, and humidity to channel 3. For a BMP280, that still follows the driver’s command format even though the sensor focus is temperature and pressure. [#21884346]ENABLE_DRIVER_BMPI2C instead of ENABLE_DRIVER_BMP280. The reply also says DHT had already been enabled in that same PR, so the requested change was only the driver-name swap. That keeps BMP280 support on the BMPI2C path while leaving DHT enabled. [#21884401]