Absolutely and congrats for your sharp eye,

The units are not all tested together at the same time , but they are tested in batches. So there will be some differences related to the time of the day they were tested, and the units selected for a given batch. They are not tested in order.

The VOC doesn’t have a common baseline. You can read more about those sensors here: https://www.uradmonitor.com/smartcity-debate-iasi-2018/ . This is why we have the AQI VOC algorithm (similar to the Bosch BSEC library) that uses history data to compute a common baseline and provide comparable signals of identical amplitudes based on similar trend raw data. The auto test tool for this will only check that the value is in technically correct interval. The AQI VOC algorithm aligns the data between the various units or sensors (eg. BME680 vs MP503)

The CO2 sensor has an internal auto-calibration mechanism that triggers every 24hours and detects the lowest value to see if it gets close to the ambiental outdoor value of 400ppm. If this is the case, it will adjust an internal offset.

All in one these are the things you see between the various units in the report page.

Let me know if you need any additional details, and thanks for an excellent question.

Do you have more data on this? More correlation sets to other instruments? There is an offset that can be adjusted here, and I’d like to do that for your unit.

Type is the device class as defined in specs v1. Originally the model A was 1, the A2 was 4, the KIT1 was 5 , the D was 6 , the A3 was 8.
It was the first digit of the Device ID. You’re using an A3 so it starts with 8.

The second digit was a code for the Geiger tube used. 1 was SBM20 while the 2 was SI29BG. 4 was LND712. So your device ID starts with 82.

Having the Geiger tube encoded in the device ID started to loose meaning with the recent units that only do Air Quality monitoring and have no radiation sensors. So the device class defined in specs v2 became two digits big. As an example, the device class for an INDUSTRIAL is 14.

HW is the hardware version. Each model was multiple iterations. With the A3, HW103 and HW105 were the most common. You can still see a first HW100 (first iteration) here: https://www.uradmonitor.com/?open=82000001 . This particular unit is not only part of the first production batch, but it is also the very first uRADMonitor A3 unit produced. It is installed on a bus in the city of Cluj Napoca. Its data is linked to an external GPS module so we have the Air Quality measurements mapped to location. Here’s how that looks: http://www.uradmonitor.com/cluj

SW is the firmware version, the actual software running on the devices themselves. This can be updated from time to time, as I push out newer software versions to fix bugs or add new features: https://www.uradmonitor.com/firmware-upgrade-a3-wifi/

VOL is the voltage on the Geiger tube. It is configured to 380V in software, as the Geiger tube needs this High Voltage to run. It is low current, so you cannot electrocute yourself, however touching the internals while the device is running can give you a little shock. So don’t do it.

VOC is the Volatile Organic Compounds sensor. You can read about those here: https://www.uradmonitor.com/products/?sel=4 under the “IMPACT” tab or in the datasheet here: https://www.uradmonitor.com/wordpress/wp-content/uploads/2017/02/datasheet_a3.pdf

WDT is the watchdog, a timer that will reboot the device when it reaches a certain value. Normally this doesn’t happen, as periodically the Watchdog is reset to 0 if all critical operations are successful (mainly reading the sensors and communicating the data to the server). Resetting the watchdog is called “patting the dog”.

INT is the time interval for sending data. It is set to 60seconds on the A3. This means that every minute your A3 will send data. This can be customised.

HTTP is the server’s return code when the A3 send some data. 200 means OK. Anything else means error. There can be various errors codes. These are the standard HTTP Error codes, you can find documentation about them online if interested.

Let me know if you have any additional questions here, and thanks for your interest. This is much appreciated.

Radu

@lumpylumpy There is no Wifi antenna, you got the latest A3 version that comes with an embedded antenna for a more convenient form factor.

@emogenet not quite sure what if the “repeated twice” thing, please post some screen shots with that so I can see. Yes you can call the script directly, the form is:
http://192.168.4.1/s?u=SSID&p=KEY

But please note the SSID and the KEY must be URL ENCODED. There are online tools for that, with a quick google search I found https://meyerweb.com/eric/tools/dencoder/

Timeouts are sometimes possible, due to the Wifi module being stressed a little, being used both as a client (to send data) and a server (to serve local webserver used for config) at the same time, via a 9600bps serial connection. However the configuration must work in all cases and has been tested so on all units shipped.

Please note that there’s a key length limit of 20 characters. Do not use longer passwords on the networks you connect the A3 to.

Hope this helps,

Thanks guys,

@florian_gutzwiller_hb3xpa please confirm you see the right flag now.

He can assign it to his account once he opens the dashboard on a computer within the same network like the A3 unit.

Basically, the computer he uses needs to have the same external IP like the A3 unit (to be in the same LAN). Then your friend will see the A3 in his Dashboard and be able to click the “ADD” button to assign it.

Let me know if you need any help. BTW, I just assigned both units to your account, so your friend might need to re-attach it in case he did previously.

VOC raw values can sometimes for as high as a few millions.

This is why I have developed the AQI VOC scale to bring all VOC readings to a common scale 0 – 500. Please use that instead of the raw data.