About micha_pr

@Minhwan wrote: ....Hope you understand our system better than before.  If you solve the your question, .....  I think I understand the system since a very long time - but really do not understand why the accuracy will go down on both sensors to "1"... If smart recalibration required - should go after some time to "2" again (per definition "ongoing" - right?), sensor was already calibrated before. The needed calibration is even not logical for the user if he use it in normal living room as sample. So the software should not look at this value if the uptime of the sensor is high and the accuracy was before for a long time at "3". The main "misunderstanding" is the naming "accuracy" and the given value "1" for such a long time (multiple days) after sensor was working some days before with "3". I think here will not be a "solution" per definition of the accuracy and the the behavior of the library regarding the required calibration. ... View more

@ BSTRobin : yes, of course have tested. With floor soap and Wine - after it was going down to minimal values - it came back to previous values again (with accuracy =1). Yesterday the sensor came back to "2" and then "3" ... without additional stimulations... Really I'm not sure about this lines in sample code:   /* Update every STATE_SAVE_PERIOD milliseconds */ if ((stateUpdateCounter * STATE_SAVE_PERIOD) < millis()) { update = true; stateUpdateCounter++; }   Here the sate will be saved - even if accuracy is low (as sample "1") - so maybe a not optimal state for reboot could be saved? I will change it in my code (add  iaqAccuracy >= 3 )  - maybe it can help.   if ((iaqSensor1.iaqAccuracy >= 3) || (iaqSensor2.iaqAccuracy >= 3)) { update = true; stateUpdateCounter++; }   Additional - the first update will be done (in your code) even if one sensor have accuracy "0"  - I have changed it too, it is working (save then some later only) @ Minhwan : The sample code was at very first begin the same as your code - with these described problems. Only after that it was modified (see above) - and I think the delay(3000+x) should not be a problem, because I still wait for the ready sensor. And I think I *must* not request every value, right? BTW: after modification the accuracy seems to be more stable - for longer time... but maybe not because of this, of course. I think the values are still valid, even if accuracy was falling down to "1" - but it is of course misleading or unsettling for users... Thanks! Michael ... View more

Hi, as you can see the final values are not very smooth over long time. The window is open multiple times every day - it is an office room. In chart you see different sensors - a real CO2 sensor, SGP30 (Eurotronic) and 2 sensors BME680. The two BME 680 all the time have nearly same values - so there are no problems with this. Becasue of different MOx sensors here are different values, but tendency is ok. But the BME sensors now not going back to other accuracy - even not after long time. I have seen it already before and think that this maybe because of the stored values. After reboot will be taken the old config state - and that's why does not come back to "2" or "3". The only way is (was last time) to delete the old config from sensor (reboot without reading old config), then all will be ok. again after short time. What is "strange" for me - the values seems to be ok (eCO2/VOC) only the accuracy is down. Maybe you could check the config_state values (attached)? Something wrong here? Will wait with reboot (without config file) until next reply 😉 Thanks! ... View more

Hi, no, not solved,... see attached log. After some time the sensor is going "for ever" (at least for >24 hours) to accuracy = 1 and will not come back. Before all is normal, it is working at accuracy "3" and sometimes is going o "2" and coming back to "3". Header of the syslog data:   "Sensor, Timestamp [ms], raw temperature [°C], pressure [hPa], raw relative humidity [%], gas [Ohm], IAQ, IAQ accuracy, temperature [°C], relative humidity [%]"   Code used basically Github:   const uint8_t bsec_config_iaq[] = { #include "config/generic_33v_3s_4d/bsec_iaq.txt" }; void setup(void) {... iaqSensor1.setConfig(bsec_config_iaq); iaqSensor2.setConfig(bsec_config_iaq); checkIaqSensorStatus(); loadState(); ... iaqSensor1.updateSubscription(sensorList, 10, BSEC_SAMPLE_RATE_LP); iaqSensor2.updateSubscription(sensorList, 10, BSEC_SAMPLE_RATE_LP); checkIaqSensorStatus(); ... } void loop(void) { ... if (iaqSensor1.run()) { delay(50); // If new data is available output = "1, " + String(millis()); output += ", " + String(iaqSensor1.rawTemperature); output += ", " + String(iaqSensor1.pressure); output += ", " + String(iaqSensor1.rawHumidity); output += ", " + String(iaqSensor1.gasResistance); output += ", " + String(iaqSensor1.iaq); output += ", " + String(iaqSensor1.iaqAccuracy); output += ", " + String(iaqSensor1.temperature); output += ", " + String(iaqSensor1.humidity); output += ", " + String(iaqSensor1.staticIaq); output += ", " + String(iaqSensor1.co2Equivalent); output += ", " + String(iaqSensor1.breathVocEquivalent); Serial.println(output); syslog.log(LOG_INFO, output); updateState(); } else { checkIaqSensorStatus(); } if (iaqSensor2.run()) { delay(50);// If new data is available output = "2, " + String(millis()); output += ", " + String(iaqSensor2.rawTemperature); output += ", " + String(iaqSensor2.pressure); output += ", " + String(iaqSensor2.rawHumidity); output += ", " + String(iaqSensor2.gasResistance); output += ", " + String(iaqSensor2.iaq); output += ", " + String(iaqSensor2.iaqAccuracy); output += ", " + String(iaqSensor2.temperature); output += ", " + String(iaqSensor2.humidity); output += ", " + String(iaqSensor2.staticIaq); output += ", " + String(iaqSensor2.co2Equivalent); output += ", " + String(iaqSensor2.breathVocEquivalent); Serial.println(output); syslog.log(LOG_INFO, output); updateState(); } else { checkIaqSensorStatus(); } delay(3000); }     Maybe you have any idea? In this time I restart the ESP32, if a very long time the accuracy is "1", then it is going back after some time to "3" (reading before the config state) Thanks! Michael ... View more

Hello, thanks, I know these definitions, already working with the sensors since a very long time. In these older logs was a wide range of IAQ and VOC values. Later the range was normal for a working room, IAQ between 25 and 90. In any case the described accuracy change was seen. I have changed not the code and request the values after some more than 3 seconds using a delay in the loop. After 2 days I see the normal recalibration if the IAQ is going down to 25.00, so that a calibration could be needed. The values are stable. Will tell you after next days the results and can provide the logs then. Thanks! ... View more