Device sends %CO2% instead of the actual value

[admin]

This is a known bug, that i will fix in a couple of days.
Basically it happens right after power on, while the CO2 sensor has not yet warm up
For the CM1102 this takes ~2 minutes
For CDM7160 - ~1 minute
So you would get 1 or 2 such readings.

Due to the nature of the FW it was a bit hard to fix it in a clean manner initially, this is why i left it for a later time when i get better ideas.

[Ed Davies]

It doesn't just happen on start up. I've got the refresh interval set low (12 seconds instead of 120) though it seems to actually use 20 seconds (I'm guessing there's a minimum for the CO₂ detector to operate or something). Sometimes there are short runs of %CO2% in the data:

Code:

2016-09-25T09:46:32+01:00 22.85&58.99&1268.00
2016-09-25T09:46:52+01:00 22.76&58.98&1270.00
2016-09-25T09:47:11+01:00 22.86&58.96&%CO2%
2016-09-25T09:47:31+01:00 22.49&58.91&%CO2%
2016-09-25T09:47:50+01:00 22.86&58.95&%CO2%
2016-09-25T09:48:10+01:00 22.45&58.90&1263.00
2016-09-25T09:48:29+01:00 22.80&58.93&1263.00

This is logging HTTP requests (temperature, humidity, CO₂) to my laptop using netcat -l and a little shell script to extract the appropriate part of the URL from the GET line and add the timestamp. I have an MQQT server (mosquitto) installed but need to have another look at it before setting that up.

Sometimes there are other combinations:

Code:

2016-09-24T22:11:46+01:00 23.26&58.03&1080.00
2016-09-24T22:12:05+01:00 23.27&58.03&1081.00
2016-09-24T22:12:25+01:00 %TEMP%&%HUM%&%CO2%
2016-09-24T22:12:44+01:00 %TEMP%&%HUM%&1085.00
2016-09-24T22:13:04+01:00 23.30&57.97&1079.00
2016-09-24T22:13:23+01:00 23.30&57.98&1079.00

Code:

2016-09-24T23:16:23+01:00 23.16&57.72&1089.00
2016-09-24T23:16:43+01:00 23.16&57.82&1091.00
2016-09-24T23:17:02+01:00 23.04&57.73&%CO2%
2016-09-24T23:17:22+01:00 23.16&57.76&%CO2%
2016-09-24T23:17:41+01:00 23.16&57.75&%CO2%
2016-09-24T23:18:01+01:00 23.15&57.75&1100.00
2016-09-24T23:18:20+01:00 %TEMP%&%HUM%&%CO2%
2016-09-24T23:18:40+01:00 %TEMP%&%HUM%&1089.00
2016-09-24T23:18:59+01:00 23.16&57.72&1090.00
2016-09-24T23:19:19+01:00 23.16&57.73&1093.00

[admin]

yeah.. i tested now a sensor as well for a longer time and indeed did notice those hickups. apparently there are some communications failures occasionaly

i will fix this

[stephane]

yeh, I have the same problem sometime with the %PM25% and %PM10% values.

[admin]

i think i managed to fix it, at least the device was running for 1 hour sending each 10 seconds and there was not a single hickup

I won't push this as a general update for now, so you can update to the latest version by sending a command
otah

[freakstar]

(09-27-2016, 03:52 AM)admin Wrote: i think i managed to fix it, at least the device was running for 1 hour sending each 10 seconds and there was not a single hickup

I won't push this as a general update for now, so you can update to the latest version by sending a command
otah

Got my device yesterday, configured it and everyting was working fine. Placed it in the living room and noticed that since then CO2 wasn't updating. 

Now connected to my computer I see %CO2% is sent instead of the value. In the output I see "Raw CO2: -2]".

I sent command otah but it did not matter.

---

(09-29-2016, 06:12 PM)freakstar Wrote:

(09-27-2016, 03:52 AM)admin Wrote: i think i managed to fix it, at least the device was running for 1 hour sending each 10 seconds and there was not a single hickup

I won't push this as a general update for now, so you can update to the latest version by sending a command
otah

Got my device yesterday, configured it and everyting was working fine. Placed it in the living room and noticed that since then CO2 wasn't updating. 

Now connected to my computer I see %CO2% is sent instead of the value. In the output I see "Raw CO2: -2]".

I sent command otah but it did not matter.

Powered the device off for a couple of minutes, now it looks like it is working again!

[admin]

"Raw CO2: -2]" - this is the cryptic way of saying that the sensor is still warming up.
Usually this lasts only the first 1-2 minutes, so after two minutes being powered on it should send correct values.

Though, there may be still some bugs that result in restarting the sensor after the device has worked for some time, and then it will again need a minute to warm up.
If this issue still reappears you can enable debug logs by sending a command
debug
and then send it to me.

Thanks and sorry in advance if this happens

[freakstar]

Strange, after I posted yesterday it was working I disconnected the sensor from my computer and connected it elsewhere to a normal USB power supply. Then the CO2 value stops working again...? Even when I power it of for a while, looks like it isn't working when not connected to my computer?

[admin]

(09-30-2016, 07:29 AM)freakstar Wrote: Strange, after I posted yesterday it was working I disconnected the sensor from my computer and connected it elsewhere to a normal USB power supply. Then the CO2 value stops working again...? Even when I power it of for a while, looks like it isn't working when not connected to my computer?

Hmm does the Led light violet for some time after you connect it to the USB Power?
And if you connect it to the computer and then check the output from the Chrome app - is it working ?

hmmm .. and actually what means it is not working - sending %CO2% or not sending anything

[freakstar]

(09-30-2016, 07:44 AM)admin Wrote:

(09-30-2016, 07:29 AM)freakstar Wrote: Strange, after I posted yesterday it was working I disconnected the sensor from my computer and connected it elsewhere to a normal USB power supply. Then the CO2 value stops working again...? Even when I power it of for a while, looks like it isn't working when not connected to my computer?

Hmm does the Led light violet for some time after you connect it to the USB Power?
And if you connect it to the computer and then check the output from the Chrome app - is it working ?

hmmm .. and actually what means it is not working - sending %CO2% or not sending anything

Connected to the computer it is working fine.

I think the issue is my power supply. What are the minimum requirements? For now I have connected it to an other USB power supply and it looks like that fixed it.

---

Power supply was the issue. Switched from one which said it has 2000 mA output to 1200 mA and now it is working fine!