from now its running in Power Save mode and Debug level 5.
be my guest 
1 Like
Thanks again for testing! And again no significant difference 
It would have been nice if there was at least one other sensor where this ‘workaround’ would have some effect. One more question: what is the version number of your SDS011 (can be found on the status page, something like 23-06-26(fdff)) ?
this is A
A’s link
this is B
B’s link
both in my balcony, A is working 6 months, B is working 2.
Debug level 5, Power save on.
be my guest
1 Like
And again on both sensors no significant difference. Thanks for testing!
Back to your original question:
After some debugging on my sensor with the consistent ‘failures’ I found out that all errors were caused by what appears to be a failure to correctly start the SDS011. After the start command the loop expects a certain number of bytes. If that number is too low no values will be tried to read.
I added a check so that if that happens an additional start command is given and that, on my sensors, fixes the initial ‘failure to start’. No more missing values, with and without debug level 5 or power save setting.
This potential fix and some others cherry-picked from a few open pull requests are available at Commits · Phaze-III/sensors-software · GitHub .
You can try the builds at fetchSensorSDS(): do a (re)start also when serialSDS.available() < SD… · Phaze-III/sensors-software@c5953e1 · GitHub (the airrohr-firmware-builds artifact on that page can be downloaded when signed in as registered github user).
Please note that if you want to try these builds you must disable auto-update in the config before flashing.