sensor data influenced by other sensor?
-
@jojo if you own a air-Q science, you can see
for the documentation (enter serial number). There you can see how to read values from all sensors via HTTPS POST, MQTT or in JSON-format. If you want the raw data values from sensors you will find it in the Android- or iOS-App. Go to the Dashboard and open the device options of the particular device you want to read, then select "Diagnostics" and scroll down to "Diagnostic Sensor Data". I think with the API-Access you are also able to read these RAW-values directly out of the device to use them elsewhere or correct them by your own calculations.
In our automatic calibration algorithm there are some cross-sensivities, that will be corrected via values from other sensors of the device via exclusion or difference method, depending on the concentration value/sensor to be measured and the existing cross-sensivities.
You can also create your own dashboard via IFTTT or open HAB with the API-features. Or you take data from HTTPS POST or MQTT to do this.
-
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
-
@jojo in no way they are going to understand, they are really not interested, they are working on new sensors while in the meantime this one provides completely random data
my contribution on this forum ends here, I will go on on HA forum with my review, because something better can be achieved -
@jojo if you want to use raw values, without any automatic calibration or offsets, you can just reset the user calibration and deactivate the automatic calibration in the device options. Then you will see the raw data output as normal values in the app. But why do you want use raw values instead of automatic calibration ?
With Firmware Update 1.82 and the new App v1.29.0 many bugs have been fixed and also the auto calibration is now working much better . Just Update to the neweset versions and wait 1 or max. 2 weeks for auto calibration. The more VOCs you have, the longer auto calibration will take because high VOC values will disturb it a little bit.
-
@sugo sorry for this. at the moment I'm still learning the ropes, since I'm new. If you have important or time urgent questions, so they write me next time but simply an e-mail. Then I can react faster and respond to specific questions or challenges. Here I am currently still rare, because I have a lot to do at the moment.
-
@Felix-Bayer : no worries, I am happy with my device, it's just sad that you cannot write a better firmware, I just demonstrated that good calibration can be achieved.
Have a look here, device outside with temperature from 0 to 14 °C
https://community.home-assistant.io/t/air-q-device-any-good/512254/12 -
@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 -
@jojo i think there are two possible solutions/reasons for this:
Option 1 (more likely): The temperature shock has shifted the zeroline permanently. Here you can find how to do calibration manually to correct this shift:
English:
https://support.air-q.com/en/support/manual-calibration-how-do-i-perform-a-manual-calibration/Here is more info on that:
https://support.air-q.com/en/support/why-is-the-carbon-dioxide-co₂-level-so-high/If the air-Q is always exposed to those "unusual" conditions like permanently high VOC-value like in a laboratory or medical establishment, it might be useful to deactivate auto calibration like here:
https://support.air-q.com/en/support/how-does-the-automatic-calibration-work/Option 2: If your measured value does not change over long period of time, it seems it might be blocked or relocated. Sometimes the sensors lose contact to the PCB if the air-Q falls on the ground or is shaked. You can open the air-Q and clean it inside from dust (Tx6 screwdriver needed) and also you could reposition the sensor like described here:
https://support.air-q.com/en/support/a-sensor-has-come-loose-or-is-loose-can-i-reattach-it/Option 3 (most unlikely): If you get no or stable value that does not change at all from sensor it could be that it might be broken. You can send us diagnostic data from your smartphone or Web App if you think this the case. The best is to do this twice to compare the two measured values with different timestamps from diagnostic data.
-
@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 -
@jojo yes but be careful, because when deactivating the automatic calibration, please note that it is then deactivated for all sensors and thus the degradation of electrochemical sensors or the zero line shift is not corrected for sensors . It will be best to leave the calibration activated and only calibrate the CO2 value manually from time to time, if the auto calibration fails you will notice this after maximum one week. All other measured values will be corrected upwards and downwards. CO2 is the only sensor where this is technically and physically somewhat different.
![Felix [air-Q]](/assets/uploads/profile/257-profileavatar-1682679561512.jpeg "Felix [air-Q]"){kind=avatar}