BME680: IAQ accuracy going from 3 o 1

[micha_pr]

Hello,

using the BME680 as indoor sensor in office room I can see red marked IAQ accuracy

18:57:52.693 -> 164814095, 24.24, 101317.00, 54.56, 731373.00, 38.85, 3, 24.18, 54.75, 32.37, 529.50, 0.56
18:57:55.732 -> 164817096, 24.24, 101321.00, 54.58, 721204.00, 39.58, 3, 24.18, 54.77, 32.77, 531.06, 0.56
18:57:58.729 -> 164820096, 24.25, 101319.00, 54.62, 729001.00, 36.84, 1, 24.19, 54.79, 31.31, 525.23, 0.55
18:58:01.735 -> 164823096, 24.24, 101319.00, 54.63, 721976.00, 37.78, 1, 24.18, 54.84, 31.81, 527.22, 0.55
18:58:04.726 -> 164826095, 24.25, 101317.00, 54.64, 712818.00, 42.12, 1, 24.19, 54.82, 34.12, 536.47, 0.57

There was no reason for changing the accuracy to 1, I think...
I understand that after a while in little changing environmental conditions the accuracy may fall down to value 2 until it can come back to value 3, but why to value 1?

Value 1 will be there for at least 14 hours, as I can see.

(BTW: it was taking 3 days until the IAQ accuracy was set to 3 - in office room. I know... stable environment ...)

And - does it make sense to (auto-)save this config state (with value 1) and overwrite the existing state 3?
Or can it help to save the old config state and reload it if there are no changes in environmental conditions?

Thanks!

Michael

[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.