OK, I see where my test was wrong
it was using an existing data file
the local IP data is currently used for all the data
the sensor ID method (from the cloud data) is used to get the channel 2 PM2.5 data (in case the channel 1 data from the local IP data is out of range)
do you not have the local IP data working correctly maybe?
what I can do is set the cloud data (via the sensor number) to get the 1.0 and 10.0 data if that is not available via the local IP data
yes?
Correct–I don’t have the IP method working. I get an error message when I enter the IP and press the Test button. (See the message attached.) Only the sensor ID method is working for me. Sure, you can get the 1.0 and 10.0 data using the could method if you can. However, I only see the 2.5 data in the cloud data but maybe I overlooked it.
Refreshing the topic. I had installed a home-made air quality sensor using the sensor from Sharp (GP2Y1010AU0F/GP2Y1010AU0F posted in this forum) and a MQ131 sensor (for ozone). I’ve been logging for a while now but don’t get any exciting result. I do readouts either every 1 second or do a 10-sec average and log to a file.
I’ve noticed a difference between two sensors: GP2Y1010AU0F has an offset of about 0.4-0.5 V which is what the specifications say. The GP2Y1010AU0F has no offset (or 0.04-0.05 V).
I’ve attached a log for one day from both sensors that are installed side by side.
Either our air is that clean or something does not work OK. Can someone post a log for one day from the PurpleAir sensor? I wonder if the dynamics is more interesting there.
PS: I made a smoke from a candle and both sensors reacted immediately. So they should be connected alright. ??
Smoke is a good test. You may want to check the sensitivity specifications for those sensors to calibrate your expectations for general air quality sensing.
With the Napa wildfires, I have to say that the Purple Air sensor was a good investment. The air quality around here has really sucked the last several days.