I2C component detection

[HelmiBeh]

PROBLEM DESCRIPTION

A clear and concise description of what the problem is.
Having upgrated my Vindriktning device with some additional sensors, I have an issue with the autodetection of an I2C device, the SGP30. Built a special 14.2.0.4 version containing drivers for SHT3x, IAQ, ENS16x, AHT2x, SGP30 and vindriktning. SHT3x, IAQ, vindriktning, ENS160 and AHT21 will be recognized all time. But SGP30 is only detected, if the module with ENS160 and AHT21 is not in the I2C chain.

REQUESTED INFORMATION

Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!

• [x ] Read the Contributing Guide and Policy and the Code of Conduct
• [x ] Searched the problem in issues
• Searched the problem in discussions
• Searched the problem in the docs
• Searched the problem in the chat
• [ x] Device used (e.g., Sonoff Basic): ESP-12___
• Tasmota binary firmware version number used: 14.2.0.4_____
  • Pre-compiled
  • [ x] Self-compiled
• [x ] Flashing tools used: OTA___
• [x ] Provide the output of command: Backlog Template; Module; GPIO 255:

  Configuration output here:
18:36:45.888 MQT: Luft/RESULT = {"NAME":"Generic","GPIO":[1,1,1,1,1,1,1,1,1,1,1,1,1,1],"FLAG":0,"BASE":18}
18:36:46.131 MQT: Luft/RESULT = {"Module":{"18":"Generic"}}
18:36:46.337 MQT: Luft/RESULT = {"GPIO0":{"0":"None"},"GPIO1":{"0":"None"},"GPIO2":{"0":"None"},"GPIO3":{"608":"I2C SCL"},"GPIO4":{"640":"I2C SDA"},"GPIO5":{"7456":"VINDRIKTNING"},"GPIO9":{"0":"None"},"GPIO10":{"0":"None"},"GPIO12":{"0":"None"},"GPIO13":{"0":"None"},"GPIO14":{"0":"None"},"GPIO15":{"0":"None"},"GPIO16":{"0":"None"},"GPIO17":{"0":"None"}}

• If using rules, provide the output of this command: Backlog Rule1; Rule2; Rule3:

  Rules output here:

• Provide the output of this command: Status 0:

  STATUS 0 output here:

• Set weblog to 4 and then, when you experience your issue, provide the output of the Console log:

  Console output here:

TO REPRODUCE

Steps to reproduce the behavior:

EXPECTED BEHAVIOUR

A clear and concise description of what you expected to happen.

Console output without detection of SGP30:
00:00:00.063 Project tasmota - Tasmota Version 14.2.0.4(tasmota)-2_7_7(2024-09-18T18:20:14)
00:00:00.119 I2C: SHT3X found at 0x44
00:00:00.153 I2C: AHT2X found at 0x38
00:00:00.156 I2C: IAQ found at 0x5a
00:00:00.303 I2C: EN16X found at 0x53

Device detected:
00:00:00.063 Project tasmota - Tasmota Version 14.2.0.4(tasmota)-2_7_7(2024-09-18T18:20:14)
00:00:00.119 I2C: SHT3X found at 0x44
00:00:00.154 I2C: SGP30 found at 0x58
00:00:00.157 I2C: IAQ found at 0x5a

SCREENSHOTS

If applicable, add screenshots to help explain your problem.

ADDITIONAL CONTEXT

Add any other context about the problem here.

(Please, remember to close the issue when the problem has been addressed)

[Jason2866]

Most AHT sensors are not following the i2c standard. Not something which can be solved in software.
If you want to use more sensors on the i2c bus do not use any AHT sensor.

[HofeBY]

@HelmiBeh
what´s the command output with connected devices:
I2Cdriver
I2Cscan
a Picture of I2C cabeling type and lenght and the used devices. termination ?
your compiling configuration file.
describe your compilation environment. OS, version of VSC, etc.

[HelmiBeh]

what´s the command output with connected devices:
I2Cdriver

Luft/RESULT = {"I2CDriver":"8,15,18,43,46,84"}

I2Cscan

Luft/RESULT = {"I2CScan":"Device(s) found at 0x38 0x44 0x53 0x58 0x5a"}

a Picture of I2C cabeling type and lenght and the used devices.

abt 15cm 0.08mm² wire. ESP-12 with boards: GY-SGP30 (https://www.ebay.de/itm/164311829709), SHT3x (https://www.ebay.de/itm/334687210686), IAQ-Core (https://de.aliexpress.com/item/1005004161607094), ENS160+AHT21 (https://www.ebay.de/itm/165689572415)

termination ?

4* 10k in parallel = 2k5 @ 3V3

your compiling configuration file.

My_ini.zip

describe your compilation environment. OS, version of VSC, etc.

VSC:
Version: 1.93.1 (user setup)
Commit: 38c31bc77e0dd6ae88a4e9cc93428cc27a56ba40
Date: 2024-09-11T17:20:05.685Z
Electron: 30.4.0
ElectronBuildId: 10073054
Chromium: 124.0.6367.243
Node.js: 20.15.1
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.19045

[sfromis]

If adding the module with the AHT21 breaks I2C, you should read the response from Jason2866. They are not "good citizens" on the bus.

BTW. If CO₂ detection is your reason for getting ENS160, I can't recommend that one either. It has a small glob of corroded tin changing resistance with "something" in the air. While that "something" includes CO₂, it cannot tell what's in the air, as numbers depend on several factors.