Closed sjtrny closed 3 years ago
Nothing in the logs I assume? The status check function should output errors from the library if any are encountered.
Nothing that I could see. I've switched over to the standard component on the device since it seems more reliable, which is critical since it is in a greenhouse with sensitive plants.
I'll setup a test rig on my bench to see if I can recreate the problem again and catch an error message.
I can't replicate it with a single BME680 on an ESP32. It might be conflicting with the Dallas sensor that is on the board. I'm closing this issue for now. I'm not sure I will have time to do further testing for a while.
I reduced the memory requirements for the component the other day; but it's pretty unlikely that that's the issue here as that only cropped up when loading in font glyphs for a display. As a result of that investigation I've got a test setup running on the desk by me at the moment driving an I2C display at the same time and that seems happy enough but that's fairly anecdotal. I'd perhaps be inclined to just run a single sensor per board but I don't know how silly that might get for your setup!
Anyway; thanks for the update. If you do end up with time for more testing in the future and have any more info please feel free to re-open.
Hi, I've started noticing that when I use this component the sensor seems to get stuck and doesn't send out updates. I switched back to the standard esphome BME680 component and it doesn't happen.
Symptoms: