I am new to this forum and new to the measurement cummunity.
I bought a Ai-Thinker ESP8266 NodeMCU V2 and Nova SDS011 to measure the PM concentration in my neighborhood. I managed to get everything connected and installed, but when i look at the device statistics, I notice that almost 1 in 4 measurements leads to an error. The temperature and humidity measurements go well, but the measurements of PM2,5 en PM10 go wrong for approximately 25% of the cases. In that case, there is no measurement ( ‘-’ as value for the measurement) and also my sensor does not appear on maps.sensor.community anymore. The measurements take place every 300 seconds and there is always a good wifi-connection with the device (i can always access it, even when the measurements go wrong).
Unfortunately, I have no rights yet to post images in the forum to clarify the problem.
Could you send me the IDs of the sensor: API ID (the one from the map) and board ID.
As @air-ais told, it is probably a power supply issue: use a USB charger with more than 1500 mA. The specs should be written on it.
Have you changed something in the firmware ? It should be 145 s.
Actually I don’t really understand where you see this:
In the web interface ? In devices.sensor.community?
If the sending frequency is changed to 300 s. it is normal that the sensor regularly disappears from the map. The map is optimized for the 145 s. rhythm.
Another possibility would be bad cable connections. Sometimes the Dupont cables are not tight enough.Try to make them tighter or find some KONTAKT 60 fluid.
However, we are now a full day later, and the number of errors has dropped significantely. It is now less than 10%. It looks likes the sensor needed some time 'to run properly???
I changed the sending frequency to 300 seconds, because I read on a forum, that it increases the lifespan of the sensor. I changed it in the configuration part of the web interface under more settings (“Measuring interval (sec)”).