DHT12 and BMP280 sensor conflict on I2C in ESP32 DevKit V1

Welcome,

I have a problem with I2C communication on the ESP32 DevKit V1 board. Well, I wanted to connect several sensors supporting this standard to one I2C bus. Namely: DHT12 with library <DHT12.h>, BMP280 with library <BMP280_DEV.h> and RTC module with library <RTClib.h>. (I don't physically have the RTC module and the BMP280 yet, but I've already written code to support them). The problem is that the function :

.

causes the DHT12 sensor to malfunction - it shows NaN (Not a Number) values. When this function is removed, the data shown is correct. However, obviously this function is necessary during operation. I have included a code snippet below:

.

Could someone explain to me how to make this connection correctly?
PS. I would prefer not to change the libraries used to other libraries as this would involve changing quite a lot of the program. I can edit the libraries if that helps and someone could tell me what to change.

Thank you in advance for your help!

khoam wrote:

Askabius wrote:

DHT12 with library <DHT12.h>

.
Which specific bilbibliotheca are you referring to? By the name of the header file alone, it will be hard to guess.

How are the bmp280 and dht12 constructors initialised;

.

Here is the link to the library: https://github.com/xreef/DHT12_sensor_library

And the constructors are defined like this:

.

EDIT: I'll add that in the libraries, the DHT has an address of 0x5C and the BMP has 0x77 or 0x76 (you can choose an alternative)

I have done as instructed, but still the same error - when bmp.begin() is plugged in, the value of the sensors from the DHT12 takes the form NaN, and when the bmp.begin() function is commented out, the readings are correct :/.

EDIT: After removing Wire.begin() and adding an address (same or different) also no change

Is this the lib you are using? https://github.com/MartinL1/BMP280_DEV ?
Because if I take a quick look, I think it only supports SPI for ESP32 - the same in the example.

.
EDIT
And not one I missed the builder for I2C .
but maybe you missed it:

Yes, exactly from this one. It has examples of use with I2C: (this is what I relied on)
.

But if you could recommend any reasonably simple library for communicating with this chip that will 100% work then I'll be picky and throw this non-working crap away....

Not my mistake though, I corrected the question at the top if you have the conversion start in the code as in the example. I understand you fired up the example itself? I don't have anything better unfortunately.

n6210 wrote:

.

Code: C / C++

Log in, to see the code

.

Indeed I didn't have that, but after adding unfortunately no change :/.

khoam wrote:

bmp280.begin(0x77);
bmp280.setClock(100000);
dht12.begin();

.

I almost fell off my chair....
It works! I hope it will also work after the physical connection of the BMP and the RTC, but already a big success!
I'm keeping the topic open for now, I'll let you know when the Post Office graciously delivers the sensors to me and have a chance to test them.

is there a problem with 400khz? @khoam class .

Added after 2 [minutes]:

khoam wrote:

BMP280_DEV sets a default speed of 400000 kHz, so you need to change this later

fact I even saw this, but somehow I didn't look into the others

Well, then all that's left for me to do is to make sure that this wretched bus laughs without too many problems, add some sensible support for the Blynk terminal and eliminate one more small bug and I'll be able to consider the project finished!

And, this "little bug" is that at some point during startup, as if between SETUP and LOOP, a few pins change state to HIGH, for no reason at all. Of course, I set pinMode(pin, OUTPUT); and digitalWrite(LOW) in SETUP and there are no more operations on these pins in SETUP, yet they enter the loop with a high state. And the best thing is that when I give pinMode(pin, INPUT) to these pins in SETUP, a voltage of 0.67V appears on them. Anticipating questions - according to the documentation, there should be no voltage on these pins during Loss/Boot or other cases. I'll have a look at it and if I can figure out what I mean, I'll post the code.

Thanks again for your help!

khoam wrote:

What GPIO is this specifically?

GPIOS: 13, 23, 2, 12, 25 and maybe some others I haven't picked out, but these 5 for sure. But first I'll make sure it's not a bug in the program, which to myself may be calling functions that change the state of these pins for some reason.

EDIT: It turned out that the Blynk.run() function is responsible for this change; But interestingly, it runs all the time in a loop, and only sets the pins to high in its first execution.

EDIT2: SOLVED!

It turned out that the Blynk.syncAll(); function makes all the Blynk.write(); events execute; That is, in this case, as if I had pressed all the buttons that can turn something on at startup.