home-assistant.io/source/_components/sensor.rfxtrx.markdown
Franck Nijhof c464056402
Making our website faster, cleaner and prettier (#9853)
* 🔥 Removes octopress.js

* 🔥 Removes use of root_url var

* 🔥 Removes Octopress generator reference from feed

* 🔥 Removes delicious support

* 🔥 Removes support for Pinboard

* 🔥 Removes support for Disqus

* 🔥 Removes support for Google Plus

* ↩️ Migrate custom after_footer to default template

* ↩️ Migrate custom footer to default template

* ↩️ Migrate custom header to default template

* 🔥 Removes unused template files

* 🚀 Places time to read directly in post template

* 🚀 Removes unneeded capture from archive_post.html template

* 🔥 🚀 Removes unused, but heaving sorting call in component page

* 🚀 Merged javascripts into a single file

* 🔥 Removes more uses of root_url

* 🚀 Removal of unneeded captures from head

* 🔥 🚀 Removal of expensive liquid HTML compressor

* 🔥 Removes unneeded templates

* 🚀 Replaces kramdown with GitHub's CommonMark 🚀

* 💄 Adds Prism code syntax highlighting

*  Adds support for redirect in Netlify

* ↩️ 🔥 Let Netlify handle all developer doc redirects

* ✏️ Fixes typo in redirects file: Netify -> Netlify

* 🔥 Removes unused .themes folder

* 🔥 Removes unused aside.html template

* 🔥 Removes Disqus config leftover

* 🔥 Removes rouge highlighter config

* 🔥 Removes Octopress 🎉

* 💄 Adjust code block font size and adds soft wraps

* 💄 Adds styling for inline code blocks

* 💄 Improve styling of note/warning/info boxes + div support

* 🔨 Rewrites all note/warning/info boxes
2019-07-15 22:17:54 +02:00

2.6 KiB

title, description, logo, ha_category, ha_iot_class, ha_release
title description logo ha_category ha_iot_class ha_release
RFXtrx Sensor Instructions on how to integrate RFXtrx sensors into Home Assistant. rfxtrx.png
Sensor
Local Polling 0.7

The rfxtrx platform support sensors that communicate in the frequency range of 433.92 MHz.

First you have to set up your rfxtrx hub. The easiest way to find your sensors is to add this to your configuration.yaml:

# Example configuration.yaml entry
sensor:
  platform: rfxtrx
  automatic_add: true

Then when the sensor emits a signal it will be automatically added:

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):

# Example configuration.yaml entry
sensor:
  platform: rfxtrx
  devices:
    0a52080000301004d240259:
      name: device_name

If you want to display several data types from one sensor:

# Example configuration.yaml entry
sensor:
  platform: rfxtrx
  devices:
    0a520802060100ff0e0269:
      name: Bath
      data_type:
       - Humidity
       - Temperature

Only these data_type are valid:

  • Temperature
  • Humidity
  • Barometer
  • Wind direction
  • Rain rate
  • Energy usage
  • Total usage
  • Sound
  • Sensor Status
  • Counter value
  • UV

Example configuration:

# Example configuration.yaml entry
sensor:
  platform: rfxtrx
  automatic_add: true
  devices:
    0a52080705020095220269:
      name: Lving
      fire_event: true
    0a520802060100ff0e0269:
      name: Bath
      data_type:
       - Humidity
       - Temperature

{% configuration %} devices: description: A list of devices. required: false type: list keys: name: description: Override the name to use in the frontend. required: false type: string fire_event: description: Fires an event even if the state is the same as before. Can be used for automations. required: false default: false type: boolean data_type: description: Which data type the sensor should show. required: false type: list automatic_add: description: To enable the automatic addition of new lights. required: false default: false type: boolean {% endconfiguration %}

If a device ID consists of only numbers, please make sure to surround it with quotes. This is a known limitation in YAML, because the device ID will be interpreted as a number otherwise.