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

Enable more than two and up to four BMP/BME sensors on two I2C buses … #17643

Merged
merged 1 commit into from Jan 8, 2023

Conversation

Maschotta
Copy link
Contributor

…for ESP32 (only two addresses (76, 77) per I2C bus are possible). (enhancement of #10827,#1049, #2707)

It is now possible to use four BMP/BME sensors with one ESP32. It is necessary to use two I2C buses because there are only two possible I2C addresses for BMP/BME.

image

Description:

Related issue (if applicable): fixes #

Checklist:

  • [ x] The pull request is done against the latest development branch
  • [ x] Only relevant files were touched
  • [ x] Only one feature/fix was added per PR and the code change compiles without warnings
  • [ x] The code change is tested and works with Tasmota core ESP8266 V.2.7.4.9
  • [ x] The code change is tested and works with Tasmota core ESP32 V.2.0.6
  • [ x] I accept the CLA.

NOTE: The code change must pass CI tests. Your PR cannot be merged unless tests pass

…for ESP32 (only two addresses (76, 77) per I2C bus are possible). (enhancement of arendst#10827,arendst#1049, arendst#2707)
@arendst arendst merged commit d80b763 into arendst:development Jan 8, 2023
arendst added a commit that referenced this pull request Jan 8, 2023
Add ESP32 support for BMPxxx sensors on two I2C busses (#17643)
Maschotta added a commit to Maschotta/Tasmota that referenced this pull request Jan 9, 2023
@kugelkopf123
Copy link
Contributor

kugelkopf123 commented Jan 14, 2023

It seems that this change causes problems when only one sensor is connected. I flashed an ESP32 with the latest build and with one BME280 sensor, I get this sensor displayed twice.
Bildschirmfoto 2023-01-14 um 23 12 25

@sfromis
Copy link
Contributor

sfromis commented Jan 14, 2023

I'm also seeing that issue. Also looks like a breaking change when the address is included in the sensor name, instead of only when there's more than one address.

Same error in the JSON, which for practical purposes is invalid JSON.

@arendst arendst self-assigned this Jan 15, 2023
@arendst
Copy link
Owner

arendst commented Jan 15, 2023

Let's see if I can spend my sunday afternoon in fixing this....

Maschotta added a commit to Maschotta/Tasmota that referenced this pull request Jan 15, 2023
Maschotta added a commit to Maschotta/Tasmota that referenced this pull request Jan 15, 2023
arendst added a commit that referenced this pull request Jan 15, 2023
Fix BMP support on two busses (#17643)
@arendst
Copy link
Owner

arendst commented Jan 15, 2023

Fixed.

Maschotta added a commit to Maschotta/Tasmota that referenced this pull request Jan 15, 2023
…ensor recognition if one bus is used. I2cSetDevice uses bus 0 as default, even if there is no second I2C bus. Hence, sensors are recognized twice.
Maschotta added a commit to Maschotta/Tasmota that referenced this pull request Jan 15, 2023
Maschotta added a commit to Maschotta/Tasmota that referenced this pull request Jan 15, 2023
…ensor recognition if one bus is used. I2cSetDevice uses bus 0 as default, even if there is no second I2C bus. Hence, sensors are recognized twice.
Maschotta added a commit to Maschotta/Tasmota that referenced this pull request Jan 15, 2023
Maschotta pushed a commit to Maschotta/Tasmota that referenced this pull request Jan 15, 2023
Fix BMP support on two busses (arendst#17643)
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

Successfully merging this pull request may close these issues.

None yet

4 participants