-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I-9PSL displays dash/hyphen for PM2.5 intermittently when air quality is good #202
Comments
Hi @hsugene From your log it's look the communication to PM sensor always failed. |
Hi @pnt325, thank you for the reply. I can try to check the connection, but I bought a pre-assembled version and I’m honestly not very comfortable with opening it. I suppose it’s possible that something got knocked loose in transport. With that said, I do not believe it’s a connection issue because, if I open my windows and let some outside air into the room, the PM sensor will report data reliably the entire time (like 12+ hours). The issue only occurs when the PM levels in the room are close to zero. The way I can reproduce it is by shutting my windows and turning on my air purifier for an hour or so. Achim on the AirGradient forum also mentioned that this was not an isolated issue:
Given this information, do you still think it would be worthwhile to replace the sensor? Thank you! |
Hi @hsugene And thank for your information we will procedure to test it |
Hello, I was referred here from the official AirGradient forum (here). I did a little more digging, so I’ll try to rephrase what I wrote there.
The basic issue is that, when the PM sensor on my I-9PSL is seeing all zero values, there is some flaky behavior:
I have been able to reproduce this issue consistently by turning on my air purifier, which is apparently very good at filtering out all the PM in my room. Moreover, when turn off the air purifier and allow the PM levels to rise, the issue does not occur.
I’m attaching a video file that shows the issue. It’s a 15-minute recording (sped up 20x) showing both the display going from 0 to – and the corresponding local API output from
/measures/current
. I took the liberty of drawing a timeline at the bottom so that it’s easy to identify where the issue occurs.To demonstrate normal operation, I opened my windows during the last 2/3 of the video to allow the PM numbers to rise. After doing so, the display and local monitor API provides the expected results reliably.
I can only speculate that, when all PM readings are zero, there’s something that makes the device think “hmm, that can’t be right, so I’m going to reset myself.” But obviously, I’m not the expert here!
Lastly, I’m also attaching the output that is shown in the video.
This isn’t a huge deal, I suppose, since I can just assume that blank values == good air. It just makes the any logs look a bit messy, that’s all.
Thanks!
agbugreport.H.264-x264-35.00.mp4
agoutput.txt
The text was updated successfully, but these errors were encountered: