In my home automation system I use CO2 sensors from Netatmo and some MH-Z14A based arduino nodes.
I really like, that the Netatmo sensors work for about a year on battery. But they can only be integrated with a cloud api into my home automation. This has led to one interruption of several hours in the past, when the service was down. As I regulate my heating with the measured data of these sensors, this was problematic. 🙂
What I am missing with the battery powered Netatmo sensors, is a led indicating air quality.
To remove the dependency of the cloud api, I decided to build my own sensors. But before I order more MH-Z14A sensors, I want to make an evaluation.
Caution: This article is about the experiences I made in my setup with the sensors I have and with the (maybe buggy) code I wrote. It may be, that you can not reproduce my findings. 🙂
evaluate CO2 sensors for Netatmo replacement
- I don’t want to be dependent on cloud
- I wan’t a led indicating air quality with every sensor
- prototype with every sensor
- graphs of measurements made with different sensors
- decision for one sensor
- buy samples of different sensors
- build a prototype with all sensors
- make measurements, store them in influxdb and make graphs with grafana
- evaluate the measurements
- Prototype built with MH-Z14A and CCS811
- API Endpoint with node-red configured to store data in influxdb
- first dashboard in grafana implemented
- other sensors ordered
- Progress 20190424
- MH-Z19b arrived
The CCS811 seems to reset sometimes (no values for several minutes and then starts with 400ppm). I will add a pull up resistor on the I2C bus.
CCS811 is quite complex to handle. It has a MCU and you can make firmware updates. The library from adafruit is incomplete, it doesn’t support baseline-functions, which you have to use. I changed to the sparkfun library.
CCS811 didn’t show usable results in mode 3 (measurement every 60s). Now trying mode 1 (every 1s) with a moving average over one minute.