Please refer to Contributing README for details.
For German Version see: Konfiguration der Sensoren
If a (previously) configured WiFi is not reachable within 20 seconds after power-on,
the firmware flips itself into AP mode and creates a WiFi network in the form airRohr-\[Sensor-ID\]
.
This WiFi network is by default unencrypted. When a client connects to this, it will get
redirected to the sensors web server http://192.168.4.1/
which allows initial configuration.
Configurable is
The unencrypted Access Point for initial configuration will turn itself off after about 10 minutes. In order to reactivate please power cycle the board.
The DHT22 sensor is originally an Indoor sensor. For outdoor use it appears to be rather sensitive to water condensation after 100% rel.Humidity that keep it for very long time (sometimes forever) at 99.9% value. Also it appears to be sensitive to high UV light, which tends to cause the sensor to crash until hard power-loss restarted.
Better experiences have been made with a BME280 or SHT3x sensor, so consider those instead.
Connecting/Powering via a computer USB will provide USB serial with the settings 9600 baud 8N1. By default the sensor will provide human readable debug information of configurable granularity there.
All measurements can also be read as CSV via USB-Serial when using the USB port in the settings 9600 Baud 8N1. In order to avoid interfering of debug options (see earlier section) set debug to None in the configuration.
Please refer to the Pinout of NodeMCU v2 and v3 for much more detailed information about the individual pin functions.
Note: Serial connections are always crossed (RX on one side is connected with TX on other side)
Please check your version (pinout) at [https://datasheets.maximintegrated.com/en/ds/DS18B20.pdf] Uses the same PIN D7 as DHT22, so DHT22 OR DS18B20 can be used.
Pinout: 8 7 6 5 4 3 2 1
Pinout PMS7003: 9 7 5 3 1 10 8 6 4 2
Pinout: 8 7 6 5 4 3 2 1
Pinout: 1 2 3 4 5
VCC and GND can be provided by board board (use 3.3v!)
Note: Serial connections are always crossed (RX on one side is connected with TX on other side)
For use of multiple sensors with Luftdaten.info, you need to specify a virtual API Pin for the use of Luftdaten.info in the Luftdaten.info sensor registration. The firmware uses the following API pins hardcoded. These match what the Luftdaten.info expect and will use by default when selecting the correct sensor model.