I have this sensor connected to my Hass.io install and all worked well for two days, values in the 6 - 20 range as expected. Using the built-in component:
Without any change, except a reboot, the values jumped up to the 30 to 60 range for the same room.
I then migrated the sensor to a Pi Zero, a Pi 3, and a Pi 3+ with Hassbian - and the situation re-occured.
I can forgive the Pi Zero as its voltages are a little different, but I can’t understand the variance with the other setups.
My configuration is standard, and doesn’t show any errors:
- platform: serial_pm
serial_device: /dev/ttyUSB0
name: Nova
brand: novafitness,sds021
I’ve noticed that if the api runs immediately after start-up / reboot then the same issue occurs, so if you want to run this automatically add a 30 second delay, e.g. in /etc/rc.local
sleep 30 && python ...
This might be what is causing the issue with the component, I’ve an issue logged as:
How do we know that the value which is shown at startup is wrong and value after long time is correct. What I think is that if sds011 is running for long time may be it starts giving the lowest value? Whenever the sensor runs full night its values are dropped to around 5-6 and if i restart in morning they become 23- 30 and stay there until evening.
How do we know which values are actually correct.?