mirror of
https://github.com/esphome/esphome-docs.git
synced 2024-07-06 12:16:28 +02:00
185 lines
7.1 KiB
ReStructuredText
185 lines
7.1 KiB
ReStructuredText
Sensor Component
|
||
================
|
||
|
||
esphomelib has support for many different sensors. Each of them is a
|
||
platform of the ``sensor`` domain and each sensor has several base
|
||
configuration options.
|
||
|
||
Currently supported sensor platforms:
|
||
|
||
====================== ====================== ======================
|
||
|ADC|_ |ADS1115|_ |BMP085|_
|
||
---------------------- ---------------------- ----------------------
|
||
`ADC`_ `ADS1115`_ `BMP085`_
|
||
---------------------- ---------------------- ----------------------
|
||
|Dallas|_ |DHT|_ |HDC1080|_
|
||
---------------------- ---------------------- ----------------------
|
||
`Dallas`_ `DHT`_ `HDC1080`_
|
||
---------------------- ---------------------- ----------------------
|
||
|HTU21D|_ |MPU6050|_ |Pulse Counter|_
|
||
---------------------- ---------------------- ----------------------
|
||
`HTU21D`_ `MPU6050`_ `Pulse Counter`_
|
||
---------------------- ---------------------- ----------------------
|
||
|Ultrasonic Sensor|_
|
||
---------------------- ---------------------- ----------------------
|
||
`Ultrasonic Sensor`_
|
||
====================== ====================== ======================
|
||
|
||
.. |ADC| image:: /esphomeyaml/images/flash.svg
|
||
:class: component-image
|
||
.. _ADC: /esphomeyaml/components/sensor/adc.html
|
||
|
||
.. |ADS1115| image:: /esphomeyaml/images/ads1115.jpg
|
||
:class: component-image
|
||
.. _ADS1115: /esphomeyaml/components/sensor/ads1115.html
|
||
|
||
.. |BMP085| image:: /esphomeyaml/images/bmp180.jpg
|
||
:class: component-image
|
||
.. _BMP085: /esphomeyaml/components/sensor/bmp085.html
|
||
|
||
.. |Dallas| image:: /esphomeyaml/images/ds18b20.jpg
|
||
:class: component-image
|
||
.. _Dallas: /esphomeyaml/components/sensor/dallas.html
|
||
|
||
.. |DHT| image:: /esphomeyaml/images/dht22.jpg
|
||
:class: component-image
|
||
.. _DHT: /esphomeyaml/components/sensor/dht.html
|
||
|
||
.. |HDC1080| image:: /esphomeyaml/images/HDC1080.jpg
|
||
:class: component-image
|
||
.. _HDC1080: /esphomeyaml/components/sensor/hdc1080.html
|
||
|
||
.. |HTU21D| image:: /esphomeyaml/images/htu21d.jpg
|
||
:class: component-image
|
||
.. _HTU21D: /esphomeyaml/components/sensor/htu21d.html
|
||
|
||
.. |MPU6050| image:: /esphomeyaml/images/mpu6050.jpg
|
||
:class: component-image
|
||
.. _MPU6050: /esphomeyaml/components/sensor/mpu6050.html
|
||
|
||
.. |Pulse Counter| image:: /esphomeyaml/images/pulse.svg
|
||
:class: component-image
|
||
.. _Pulse Counter: /esphomeyaml/components/sensor/pulse_counter.html
|
||
|
||
.. |Ultrasonic Sensor| image:: /esphomeyaml/images/hc-sr04.png
|
||
:class: component-image
|
||
.. _Ultrasonic Sensor: /esphomeyaml/components/sensor/ultrasonic.html
|
||
|
||
|
||
Base Sensor Configuration
|
||
~~~~~~~~~~~~~~~~~~~~~~~~~
|
||
|
||
All sensors in esphomeyaml/esphomelib have a name and some other
|
||
optional configuration options. By default, the sensor platform will
|
||
chose appropriate values for all of these by default, but you can always
|
||
override them if you want to.
|
||
|
||
.. code:: yaml
|
||
|
||
# Example sensor configuration
|
||
name: Livingroom Temperature
|
||
|
||
# Optional variables:
|
||
unit_of_measurement: "°C"
|
||
icon: "mdi:water-percent"
|
||
accuracy_decimals: 1
|
||
expire_after: 30s
|
||
filters:
|
||
- sliding_window_moving_average:
|
||
window_size: 15
|
||
send_every: 15
|
||
|
||
Configuration variables:
|
||
|
||
- **name** (**Required**, string): The name for the sensor.
|
||
- **unit_of_measurement** (*Optional*, string): Manually set the unit
|
||
of measurement the sensor should advertise its values with. This does
|
||
not actually do any maths (conversion between units).
|
||
- **icon** (*Optional*, icon): Manually set the icon to use for the
|
||
sensor in the frontend.
|
||
- **accuracy_decimals** (*Optional*, int): Manually set the accuracy of
|
||
decimals to use when reporting values.
|
||
- **expire_after** (*Optional*, `time </esphomeyaml/configuration-types.html#time>`__): Manually set the time in which
|
||
the sensor values should be marked as “expired”/“unknown”. Not
|
||
providing any value means no expiry.
|
||
- **filters** (*Optional*): Specify filters to use for some basic
|
||
transforming of values. Defaults to a basic sliding window moving
|
||
average over the last few values. See `Sensor
|
||
Filters <#sensor-filters>`__ for more information.
|
||
- All other options from `MQTT
|
||
Component </esphomeyaml/components/mqtt.html#mqtt-component-base-configuration>`__.
|
||
|
||
Sensor Filters
|
||
~~~~~~~~~~~~~~
|
||
|
||
esphomeyaml/esphomelib allow you to do some basic preprocessing of
|
||
sensor values before they’re sent to Home Assistant. This is for example
|
||
useful if you want to apply some average over the last few values to
|
||
relief Home Assistant’s state machine and keep the history graphs in the
|
||
front-end a bit more clean. More sophisticated filters should be done
|
||
with Home Assistant `filter
|
||
sensor <https://www.home-assistant.io/components/sensor.filter/>`__.
|
||
|
||
.. code:: yaml
|
||
|
||
# Example filters:
|
||
filters:
|
||
- offset: 2.0
|
||
- multiply: 1.2
|
||
- filter_out: 42.0
|
||
- filter_nan:
|
||
- sliding_window_moving_average:
|
||
window_size: 15
|
||
send_every: 15
|
||
- exponential_moving_average:
|
||
alpha: 0.1
|
||
send_every: 15
|
||
- lambda: x * (9.0/5.0) + 32.0
|
||
|
||
Above example configuration entry is probably a bit useless, but shows
|
||
every filter there is currently:
|
||
|
||
- **offset**: Add an offset to every sensor value.
|
||
- **multiply**: Multiply each sensor value by this number.
|
||
- **filter_out**: Remove every sensor value that equals this number.
|
||
- **filter_nan**: Remove every value that is considered ``NAN`` (not a
|
||
number) in C.
|
||
- **sliding_window_moving_average**: A `simple moving
|
||
average <https://en.wikipedia.org/wiki/Moving_average#Simple_moving_average>`__
|
||
over the last few values.
|
||
|
||
- **window_size**: The number of values over which to perform an
|
||
average when pushing out a value.
|
||
- **send_every**: How often a sensor value should be pushed out. For
|
||
example, in above configuration the weighted average is only
|
||
pushed out on every 15th received sensor value.
|
||
|
||
- **exponential_moving_average**: A simple `exponential moving
|
||
average <https://en.wikipedia.org/wiki/Moving_average#Exponential_moving_average>`__
|
||
over the last few values.
|
||
|
||
- **alpha**: The forget factor/alpha value of the filter.
|
||
- **send_every**: How often a sensor value should be pushed out.
|
||
|
||
- **lambda**: Perform a simple mathematical operation over the sensor
|
||
values. The input value is ``x`` and the result of the lambda is used
|
||
as output. Each floating point operation should have ``.0`` attached
|
||
as in above configuration. This will be copied over to the C++ code
|
||
as a raw string.
|
||
|
||
Example: Converting Celsius to Fahrenheit
|
||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||
|
||
While I personally don’t like the Fahrenheit temperature scale, I do
|
||
understand that having temperature values appear in the fahrenheit unit
|
||
is quite useful to some users. esphomelib uses the celsius temperature
|
||
unit internally, and I’m not planning on making converting between the
|
||
two simple (😉), but you can use this filter to convert celsius values to
|
||
fahrenheit.
|
||
|
||
.. code:: yaml
|
||
|
||
filters:
|
||
- lambda: x * (9.0/5.0) + 32.0
|
||
unit_of_measurement: "°F"
|