mirrors
/
Tasmota
mirror of https://github.com/arendst/Tasmota.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

typos

Christian 2019-08-07 21:03:52 +02:00
parent 1bf5a8ac06
commit c96696d4c4
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
CHIRP-soil-moisture-sensor.md

@ -1,7 +1,7 @@
Chirp is a plant watering alarm which uses capacitive sensing to measure moisture. It provides ambient and temperature readings. A "sensor mode only" version (without the chirp function) is available and probably the preferred variant fot Tasmota.
Chirp is a plant watering alarm which uses capacitive sensing to measure moisture. It provides ambient and temperature readings. A "sensor mode only" version (without the chirp function) is available and probably the preferred variant for Tasmota.
See [Catnip electronics](https://www.tindie.com/stores/miceuz/) for further information.
### Connecting to an EPS8266
### Connecting to an ESP8266
It uses a standard I2C-connection with 3.3V and GND.
@ -23,7 +23,7 @@ At boot time the driver will scan the I2C bus for CHIRP-sensors and enumerate th
**CHIRPSCAN** will re-scan the I2C bus and re-enumerate the sensors.
**CHIRPSELECT** will select the active sensors, which can receive commands. To select the first sensor use `CHIRPSELECT 0`.
**CHIRPSELECT** will select the active sensor, which can receive commands. To select the first sensor use `CHIRPSELECT 0`.
**CHIRPSET** will set the new I2C address for the selected sensor. Use decimal address.
To change active sensor to 0x1f (=31) use `CHIRPSET 31`.
@ -46,7 +46,7 @@ The sensor is relativly slow and therefore the driver will (tries to) slow down
The problem seems to occure mostly when the sensor shall wake up from sleep. That's why the already implemented auto-sleep-wake-function is currently deactivated in the driver.
Typically when you get readings of 0 for all 3 measurements, then the I2C bus is likely "frozen". The expected result for I2CSCAN on the console is {"I2CScan":"Error 4 at 0x01"}.
A restart (RESTART 1) of TASMOTA should be enough, but maybe you need to do a power cycle.
Different core-SDK may lead to different behaviour.
Different core-SDK's may lead to different behaviour.