* add note for asynchronously update of adc
* Move to section; add details; change ID name to match example config
Co-authored-by: Otto Winter <otto@otto-winter.com>
* Add docs for CT Clamp
* Fix title bar
* Fix reference
* 2 many changes
* Update docs for new configuration
* Compress index image
* Update for config changes
- Also remove 3.3V message, because if the user needs to calibrate anyway, then the 3.3V is also part of the calibration process.
- Use calibrate_linear instead of multiply, more user-friendly
- Update SEO image
-
Co-authored-by: Otto Winter <otto@otto-winter.com>
* Add mpr121 docs and images
* add images
* update mpr121 docs
* Title bar same length as text
* wrong size and location
* wrong size and location
* wrong location
* wrong size and location
* wrong size and location
* Added binary_sensor_map
* tabs to spaces
* added to index
* add image
* text changes
* remove linefeed
* image is jpg not png
* preview fail??
* Update binary_sensor_map.rst
- Make use case and function more clear
- Remove options that do not exist yet.
- Fix incorrect sensor link in configuration variables
- Fix required values labeled optional
- Less literal text with backslash. Was hard to read.
- Move config example essential part up.
- Remove disqus
* Update binary_sensor_map.rst
* Fix
Co-authored-by: Otto Winter <otto@otto-winter.com>
* added debounce and threshold
* extended and fixed documentation for thresholds
* line to long
* line to long list end
* no spaces at lin end
* Update mpr121.rst
* default for touch release thresholds
* Lint
Co-authored-by: Otto Winter <otto@otto-winter.com>
* Added documentation for AM2320
* Added new files for AM2320
* Fixed too long row
* Update am2320.rst
Co-authored-by: Mikkonen Teemu <teemu.mikkonen@iki.fi>
Co-authored-by: Otto Winter <otto@otto-winter.com>
Clarify that this component uses voltage range at the chip pin, but voltage range at the board pin can be greater (e.g., for NodeMCU)
## Description:
**Related issue (if applicable):** fixes <link to issue>
**Pull request in [esphome](https://github.com/esphome/esphome) with YAML changes (if applicable):** esphome/esphome#<esphome PR number goes here>
**Pull request in [esphome-core](https://github.com/esphome/esphome-core) with C++ framework changes (if applicable):** esphome/esphome-core#<esphome-core PR number goes here>
## Checklist:
- [ ] Branch: `next` is for changes and new documentation that will go public with the next ESPHome release. Fixes, changes and adjustments for the current release should be created against `current`.
Co-authored-by: Otto Winter <otto@otto-winter.com>
senors => sensors
## Description:
**Related issue (if applicable):** fixes <link to issue>
**Pull request in [esphome](https://github.com/esphome/esphome) with YAML changes (if applicable):** esphome/esphome#<esphome PR number goes here>
**Pull request in [esphome-core](https://github.com/esphome/esphome-core) with C++ framework changes (if applicable):** esphome/esphome-core#<esphome-core PR number goes here>
## Checklist:
- [ ] Branch: `next` is for changes and new documentation that will go public with the next ESPHome release. Fixes, changes and adjustments for the current release should be created against `current`.
## Description:
#222
**Related issue (if applicable):** fixes <link to issue>
**Pull request in [esphome](https://github.com/esphome/esphome) with YAML changes (if applicable):** esphome/esphome#<esphome PR number goes here>
**Pull request in [esphome-core](https://github.com/esphome/esphome-core) with C++ framework changes (if applicable):** esphome/esphome-core#<esphome-core PR number goes here>
## Checklist:
- [x] Branch: `next` is for changes and new documentation that will go public with the next ESPHome release. Fixes, changes and adjustments for the current release should be created against `current`.
Co-authored-by: Otto Winter <otto@otto-winter.com>
