Closed s-weise closed 1 year ago
FWIW, I'm using SCD40 (not SCD41, but same driver) on Tasmota 12.2, no problems.
Could be a i2c bus problem. Does the sensor work if you remove the other i2c sensors?
Maybe. For testing I desoldered the pull-up resistors from the sensor board and now the sensor works when nothing else is connected. Does Tasmota activates the internal pull-up resistors on the I2C pins? It's strange that it worked on version 12.1.0.0.
i2c is a bus. For a correct bus setup the last device (seen from wiring) should only be terminated with pull up resistors. Lower resistors are more resilent against "noise". The weak pull ups in esp does not count nor do any harm. Having pull ups on e every connected i2c device do most of the time work. But if power supply is weak you may run in trouble here. Imho thats your issue. How do you power the whole stuff? Are decoupling caps installed? On a border line hardware setup even the smallest change can brake a before working setup. How long are the i2c wires? Keep them as short as possible.
PROBLEM DESCRIPTION
A clear and concise description of what the problem is. Hi,
the CO² sensor SCD41 no longer works under the Tasmota 12.2.0.0 (and 12.2.0.6). In the version 12.1.0.0 the sensor works normal. I use the Adafruit QT Py ESP32-C3 board with the SCD40, SGP30 and VINDRIKTNING sensor. A WS2812 LED is also used. I looked into the Tasmota libs for sensor control and i2c control but i can't find a change the explains this behavior.
Hope my informations can help you.
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
Backlog Template; Module; GPIO 255
:Status 0
:TO REPRODUCE
Steps to reproduce the behavior:
Connect SCD41 with QT Py ESP32-C3.
EXPECTED BEHAVIOUR
A clear and concise description of what you expected to happen.
Normal read out from the SCD41 sensor
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)