gon
March 7, 2022, 11:44am
1
hi
i have a vindriktning with an esp32-pico (m5stamp) and it worked great over the last half a year.
the fan power is always-on with 3.3v
uptime today was 38 days.
it is in a room where people smoke.
after a good ventilation, sensor shows green again.
but over the last 6 weeks the clean/base-value rose from 12 to 53, yellow
then i rebooted today.
the value then fell down to 12 again, green.
and i have a second one, identically, but in a non-smoking room.
and it behaved the same, rebooted it, now it’s green again
anybody else have similar experiences (a rising baseline) ?
gon
March 8, 2022, 6:04am
2
should have researched first
opened 04:32PM - 20 Feb 22 UTC
Not sure how to fix incorrect display values? He's been showing me 200-260 for … some time. And it will never go down. I also tried to vacuum and it didn't help.
opened 06:49PM - 05 Dec 21 UTC
Situation: vindriktning with small self-made esp8266 board that sends the values… to my IOT system. Readout function based on this git repo.
Over the last 2 months the pm2.5 values have been (on average) nearly linearly increasing, up to the point where it was 140 ppm average, and red all the time. I opened up the box, found that the small filter on the sensor was all clogged up. Gave it a gentle blowout with the air compressor (yes, I protected the fan). Started all up again. The first 4-5 hours it did not seem to make any difference. But then suddenly there was a 100 ppm drop, followed by a drop of 30 more 1 hours later. Both drops were while we were out, nothing happened in the house, the device did not reboot.
It reacts to our presence, so it is not dead, and now it is back to levels where it was when I just bought it.
So either I damaged it, or the sensor really sensitive to dust accumulation on the sensor. I tend to believe the latter.
Maybe others also see that nearly linear increase over time? That could confirm my suspicion.
![Screenshot 2021-12-05 at 19 48 17](https://user-images.githubusercontent.com/12572422/144759487-6393d1fb-bd04-49bd-9c3c-91a9a62f4db5.png)
![Screenshot 2021-12-05 at 19 50 59](https://user-images.githubusercontent.com/12572422/144759567-5206d0bb-15a1-4668-80c9-19f869ebf119.png)
gon
March 27, 2022, 12:16pm
3
i made now an auto-reboot based on the uptime:
reboot next midnight after being up longer than 14 days