IR HAVOC + HTU21

[CosmicDuck]

Hello,
is there a buid with IR + Sensors available?

I want to read the values from a htu21 device to control a IR-Remote air conditioner/heater.

I try to use Gitpod to compile my own binary using tasmota.

Without modifying anything the build process runs smoothly.

Now I want to add the htu21 device and then additionally irhvac command features for the electra.

If I add in user_config_override.h simply the htu and ir_hvac the build runs:

#ifndef USE_HTU
#define USE_HTU
#endif

#ifndef USE_IR_HVAC
#define USE_IR_HVAC
#endif

My iresp board has gpio 4 allready used for the ir-tx led so I want to use for i2c sda the unused gpio12.
gpio 5 could still be used for I₂C SCL. I configured the both gpio in the template section.
After flashing my ir-device i added the htu21 to the gpio 12 and 5 the board is possible to send the ir-hvac commands for electra but the htu21 is not found by the esp. I had allready added 120 Ω pull up resistors at SCL and SDA near HTU21 device added so this should no the problem

Is it possible the gpio 12 could not be used for I₂C?

Is it possible to check the raw signals on gpio5 an 12 by using tasmota?

Cheers,

[sfromis]

Using the tool decode-status you can verify what's actually included in the build in use, or check if the sensor index from I2C devices is found in the output of command I2CDriver. Of course also verify that the sensor address appears in the output of command I2CScan.

More generally, you should heed the instructions on https://tasmota.github.io/docs/Compile-your-build/#customize-your-build to not expect to add drivers to the "fine tuned" variants (that includes IR), but instead add your feature selection to the base when you set up to build.

[CosmicDuck]

Using the tool decode-status you can verify what's actually included in the build in use, or check if the sensor index from I2C devices is found in the output of command I2CDriver. Of course also verify that the sensor address appears in the output of command I2CScan.

{"I2CScan":"No devices found"}

More generally, you should heed the instructions on https://tasmota.github.io/docs/Compile-your-build/#customize-your-build to not expect to add drivers to the "fine tuned" variants (that includes IR), but instead add your feature selection to the base when you set up to build.
I'd read that so I used the default tasmota set, I think. That's the reason why I didn't changed anything.
However the compiling does not show any error.

I also checked the HTU21 on another esp32 device with the available allsensor binary successfully.

Another I₂C-Device is also not shown with I2CScan on the iresp-board.

I will remove the HTU21 from the breadboard an check if I can pull down the lines.

[CosmicDuck]

I will remove the HTU21 from the breadboard an check if I can pull down the lines.
Can I use in template the Button menu to show me the status of the gpios?

[sfromis]

It is not relevant what you saw with another build than the one you are using. Do check what I2CDriver says, as I suggested.

But as long as you do not see anything from I2CScan, your sensor is not being seen, likely wiring issues.

[CosmicDuck]

It looks like I cannot pull down the gpio. Both are the whole time at high level although I try to bring it down with a direct wire to gnd:

{"GPIORead":{"GPIO4":0,"GPIO5":1,"GPIO12":1,"GPIO14":1}}

I must check why.