Open Koen00 opened 1 year ago
Baseline is not fixed forever, it is being updated whenever the sensor gets exposed to fresh air (or fresher than it was at the time when previous baseline was logged). It also depends a lot on current env/temp/humidity. Actually I’m not sure if there is much sense to specify it in config, as you have to update it periodically to reflect current environment, or just keep it running for a day and let it figure out the baseline on its own.
okay. Is there a way to speed up the startup process? After a restart of the ESP, the CCS811 also needs lots of time to generate measurements. But it's not disconnected from the power supply. Ideally, I want to use a deep sleep and take an air quality measurement every 1-5 minutes. But with this speed, I don't think it's viable.
Saving the latest baseline to the flash, not an option?
Have you tried deep sleep? Is baseline being reset after waking up (with or without baseline specified in config)? I believe CCS811 should still keep it in memory, as the sensor is still powered in deep sleep mode. In fact it has 4 different modes of operation 0-3, each having different power consumption. If the sensor is powered on or after being idle (mode 0) for long time it has to be conditioned for at least 20 min according to the specification before accurate readings even if you restore the baseline. So I don’t think completely powering off or putting the sensor in idle mode 0 is a good idea. Instead probably I would use low power mode 3, in which measurements are taken each 60 seconds (and ESPHome sets this mode if update_interval >= 60s)
Storing in flash could be an option I think, however I’m not sure if it is required for deep sleep. But if you want to restore it after reset/power off, you could try storing it in flash.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
The problem
Configured baseline as mentioned in the docs is not used or looks like it is not used in the deployed operation.
The start log gives the output where the baseline is correctly given. But at a measurement, another value for baseline is given in the log output. After 'startup' of the sensor/esp there is also some time of no measurement, because of the self calibration/initialisation which will be avoided if there is a set baseline (like which is mentioned in the documentation).
Which version of ESPHome has the issue?
2023.2.0
What type of installation are you using?
Home Assistant Add-on
Which version of Home Assistant has the issue?
2023.01.1
What platform are you using?
ESP32
Board
featheresp32
Component causing the issue
CCS811
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response