-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Tasmota (Sensors) stopped working CCS811 in v12.4.0 #18043
Comments
The driver is not in the list?? It is sensor driver number 24
Just checked the source code, see no reason why it should not be in the sensor firmware |
I've since reverted back to 12.3.1 but I will reinstall 12.4 and double check on that tomorrow morning. |
Jason, the numbers around drivers are a bit confusing, thus:
|
I should be able to provide an update possibly later today and tomorrow morning at the latest. Assuming that all previously set values are still the same after the upgrade, I'm not quite sure what has changed. As nothing to the configuration was changed. |
For me, hooking a CCS811 up to Tasmota 12.4.0 worked right away, both on ESP8266 and ESP32. This test includes the same exact binary version as indicated in the |
Thx sfromis. One more time stumbled over this :-) |
For what it's worth, I do have an additional device that exhibits the same behavior that may be useful for testing. I wasn't able to see any correlation between the two. |
@jlclark440 Have you done more testing? We can't reproduce the problem. |
Since CCS811 needs more power than most sensors, like 30-54 mA due to the heater, it may be more susceptible to borderline availability of enough current on 3.3V power input. |
Working on it now, have one device running 12.4.0 and the other still on 12.3.1. 12.4 12.3.1 |
As long as you have Note that in borderline cases, small variations in when how much power is drawn may tip the scale for becoming "too bad" for it to work. |
Please list/describe your hardware and setup. Powers supply, used board and wiring. |
ping @jlclark440 or can we close? |
Closing, as reverting to a previous version does not exhibit this current issue. |
PROBLEM DESCRIPTION
A clear and concise description of what the problem is.
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
:Backlog Rule1; Rule2; Rule3
:Status 0
:weblog
to 4 and then, when you experience your issue, provide the output of the Console log:TO REPRODUCE
Steps to reproduce the behavior:
Upgrade from 12.3.1 to 12.4.0
EXPECTED BEHAVIOUR
A clear and concise description of what you expected to happen.
CCS811 sensor not detected after upgrade, reverting to 12.3.1 with out any other changes restores the sensor .
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
ADDITIONAL CONTEXT
Add any other context about the problem here.
i2cscan on 12.3.1 results in expected response; 12:55:48.893 CMD: i2cscan
12:55:48.916 MQT: stat/Nodemcu1/RESULT = {"I2CScan":"Device(s) found at 0x5a"}
(Please, remember to close the issue when the problem has been addressed)




The text was updated successfully, but these errors were encountered: