Thanks to your findings, I was able to identify a bug in the temperature encoding scheme:

uint16_t double2int(double val) {
	int8_t sintp = (int8_t)val;				//signed integer part
	int8_t sdecp = (val - sintp ) * 100;	//signed decimal part
	uint8_t udecp = sdecp>0?sdecp:-1*sdecp; //removed decimal sign
	uint8_t uintp = sintp + 127;			//convert to unsigned
	uint16_t res = (udecp << 8) | (uint16_t)uintp;		//pack it together
	return res;
}

The sign is lost when the integer part is 0, exactly all values between 0 and -1. The fix is added to the firmware as we speak, unless it can be solved on the server side.

For CO2, let’s continue herE: https://www.uradmonitor.com/topic/co2-sensor/

The PM2.5 data is originally generated by the A3, which is then used to extrapolate the PM1.0 / PM10.0 via a linear model, which you probably saw already due to the common chart shapes. There’s a lot of literature covering this topic, and more transformation models. So we might see changes to these calculations in the future.

Sounds good, let me know when you get the usbAsp , I will assist you further.

Done! Thanks, Radu

Solved, the LoRaWAN callback is not configured: https://uradmonitor.com/tools/dashboard-04/?open=14000011

Hi Pat, newer iterations have a sound/noise sensor, but it is still in testing, so I would call it experimental. Your unit is HW103 and doesn’t have it, this is why you are seeing zeros.

Hi Pat,

You will need to send authentication data via the headers. Please see the instructions in the Dashboard, under API tab.

Let me know if this helps.

Thanks!