From 0429b5e38e7bab8acc149faae49102ce6ac155d3 Mon Sep 17 00:00:00 2001 From: hokagegano Date: Tue, 20 Dec 2016 17:45:40 +0100 Subject: [PATCH] Update sensor.rfxtrx.markdown --- source/_components/sensor.rfxtrx.markdown | 17 +++++++++++++++-- 1 file changed, 15 insertions(+), 2 deletions(-) diff --git a/source/_components/sensor.rfxtrx.markdown b/source/_components/sensor.rfxtrx.markdown index dabffea8e95..3c8aa88b952 100644 --- a/source/_components/sensor.rfxtrx.markdown +++ b/source/_components/sensor.rfxtrx.markdown @@ -29,8 +29,8 @@ Then when the sensor emits a signal it will be automatically added:

-Here the name is `0a52080000301004d240259` and you can verify that it works from the frontend. -Then you should update your configuration to: +Here the name is `0a52080000301004d240259` or `0a52080000301004d240259_temperature` and you can verify that it works from the frontend. +Then you should update your configuration to (_temperature is not needed): ```yaml # Example configuration.yaml entry @@ -54,6 +54,17 @@ sensor: - Humidity - Temperature ``` +Only these data_type are valid : +- *Temperature* +- *Humidity* +- *Barometer* +- *Wind direction* +- *Rain rate* +- *Energy usage* +- *Total usage* +- *Sound* +- *Sensor Status* +- *Counter value* Example configuration: @@ -79,3 +90,5 @@ Configuration variables: - **automatic_add** (*Optional*): To enable the automatic addition of new lights. - **data_type** (*Optional*): Which data type the sensor should show - **fire_event** (*Optional*): Fires an event even if the state is the same as before. Can be used for automations. + +