@Felix-Bayer Yes, I'm aware. On the other side, some days ago the timestamps of the last calibration were quite old, 4 values were from mid january, 1 from November, and only 2 from recent dates (mid/end of february).

I use the correction suggestion from sugo. These values seem much more accurate, when comparing them to the values delivered nativly by airq.

If I think that the Zero-line has shifted and thus a new calibration value is required, I put the airq for around 2 hours outside, and check the values of official measurements. Using them for calibration , it seems.accurate. (anybody without a official station nearby could use https://db.eurad.uni-koeln.de/de/vorhersage/eurad-im.php to get a rough impression for any european location).

Jojo

@Felix-Bayer calibrating CO2 manually did the trick. The measured value is changing again now as expected.
I assume that autocalibration is not suitable for all of the conditions here, such as the temperature shocks - i'll try to switch it off, and monitor the behaviour.
If there comes up a option of query the raw value (beside the adjusted value) I'm very interessted, (bonus if this is also available in Homeassistant , maybe through a internal debug switch).
I'm generally happy with the airq, but I see that some "unexplainable" things cannot uncovered by me without knowing what really happens with the numbers.
jojo

@Felix-Bayer Thank you for the.suggested workaround. Not fully the required solution to make a.good system very good, but a step in the right direction. I'll check it out once I've managed to fix the other issue with air-q. :

After several months, the Air-q shows a very high CO2 value of exactly 5000,0 ppm. This is since around 3 days. When opening windows, or even holding the.airq out of the window, the.value gets for a short time a bit lower, but still much over 4000. This cannot be right. The Airq hasn't changed the position, nor has it been touched when it started that behaviour. The CO2 value cannot get calibrated either. The diagnostics page do also show 5000 for CO2. The description of the sensor from your webpage states, that this sensor has no known cross-sensivity. If there is a failure (software, hardware), it,s still curious why the value gets a bit lower when holding the airq out if the window. It.seems like there would be a calibration in the background active, trying to compensate for the temperaturshock.

What could be the reason why CO2 is at 5000 since 3 days? Is 5000 a special value, like a maximum?

Can you also confirm if and how the CO2 sensor value is compensated? And how to obtain the real value?

The Softwareversions are always kept up to date.

Thank you for your help.
jojo

Thank you for the response.
I do have the Air-Q science, and I do use HomeAssistant as SmartHome system. So I'm able to access the mentioned documentation and to create own graphs since several months.
As suggested I've monitored the the values from the airq app, from the diagnostics section, and.from HomeAssistant. Values from HA and app seems equal, the values from the diagnostics seem to differ. Not as much as i thought (often equal), still sometimes different. Per script gained values seem to.match the values shown by the app an HA.
Back to the original request, can you hint me where to find information on how to obtain the unmodified "diagnostic" raw values with a technical system (script, HomeAssistant)? I neither find these values in the HomeAssistant, nor any hint in the documentation. Maybe just a overseen section in the docs.

jojo

@Mario-air-Q
I'd like to support the request for the ability to obtain the raw values. My reasoning behind is that sensor-data are always influenced.

• Some corrections (such as static offset) can be applied in realtime by the device.
• Other correction data is simply not available at that timepoint (just look for "negative values" ) . These derivations are sometimes severe - my SO2-Values change usually daily between -200 and +400 and take several hours to get reasonable again. Corrections for such things as temperature-shocks can - from my viewpoint - only corrected for the past (depending of the change or shock: some minutes or even several hours). But for this I do require the uncorrected values.
• I've worked with many sensor-types in the past years ; nearly none has a absolut linear response. When the value of the air- e.g. for SO2 should be in the range between 0 and 350ug (1 hour limitation for EU) has a calibration-correction value of currently over +1800 , I expect non-linearity in the response. A real change from 0 to 30 may not result in the same output-value as a change from 1800 to 1830.
• Sensors have always cross-sensitivies. As the effects are sometimes massive (H2S is creates a effect of around 6 for SO2), the calibration is even more important.

Long text short, It would be great if there is option to extract the real sensor values- at least to the science version. This would allow me to be able to create own dashboards, reports and corrections.