Site updated at 2018-01-28 22:02:31 UTC
This commit is contained in:
parent
57a21e9eb0
commit
01b474f87c
268 changed files with 412 additions and 412 deletions
|
@ -79,7 +79,7 @@
|
|||
<p>There is currently support for the following device types within Home Assistant:</p>
|
||||
<ul>
|
||||
<li><a href="/components/binary_sensor.alarmdecoder/">Binary Sensor</a>: Reports on zone status</li>
|
||||
<li><a href="/components/sensor.alarmdecoder/">Sensor</a>: Emulates an keypad display</li>
|
||||
<li><a href="/components/sensor.alarmdecoder/">Sensor</a>: Emulates a keypad display</li>
|
||||
<li><a href="/components/alarm_control_panel.alarmdecoder/">Alarm Control Panel</a>: Reports on alarm status, and can be used to arm/disarm the system</li>
|
||||
</ul>
|
||||
<p>This is a fully event-based component. Any event sent by the AlarmDecoder device will be immediately reflected within Home Assistant.</p>
|
||||
|
|
|
@ -165,7 +165,7 @@ A word of caution: The Arduino boards are not storing states. This means that wi
|
|||
<a href='/components/rpi_pfio/'>PiFace Digital I/O</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/rpi_gpio/'>Raspberry PI GPIO</a>
|
||||
<a href='/components/rpi_gpio/'>Raspberry Pi GPIO</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/raspihats/'>Raspihats</a>
|
||||
|
|
|
@ -135,7 +135,7 @@
|
|||
<a href='/components/rpi_pfio/'>PiFace Digital I/O</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/rpi_gpio/'>Raspberry PI GPIO</a>
|
||||
<a href='/components/rpi_gpio/'>Raspberry Pi GPIO</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/raspihats/'>Raspihats</a>
|
||||
|
|
|
@ -260,7 +260,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -270,7 +270,7 @@ file:</p>
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -244,7 +244,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -256,7 +256,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -74,7 +74,7 @@
|
|||
</h1>
|
||||
</header>
|
||||
<hr class="divider">
|
||||
<p>The <code class="highlighter-rouge">arest</code> binary sensor platform allows you to get all data from your devices (like Arduinos with a ethernet/wifi connection, the ESP8266, and the Raspberry Pi) running the <a href="http://arest.io/">aREST</a> RESTful framework.</p>
|
||||
<p>The <code class="highlighter-rouge">arest</code> binary sensor platform allows you to get all data from your devices (like Arduinos with an ethernet/wifi connection, the ESP8266, and the Raspberry Pi) running the <a href="http://arest.io/">aREST</a> RESTful framework.</p>
|
||||
<p>To use your aREST binary sensor in your installation, add the following to your <code class="highlighter-rouge">configuration.yaml</code> file:</p>
|
||||
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span>
|
||||
<span class="s">binary_sensor</span><span class="pi">:</span>
|
||||
|
@ -270,7 +270,7 @@ This sensor is not suitable for fast state changes because there is a high possi
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -243,7 +243,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -249,7 +249,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -298,7 +298,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -266,7 +266,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -241,7 +241,7 @@ To get your Blink binary sensors working with Home Assistant, follow the instruc
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -261,7 +261,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -298,7 +298,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -244,7 +244,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -267,7 +267,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -248,7 +248,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -240,7 +240,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -281,7 +281,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -244,7 +244,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -260,7 +260,7 @@ If the <code class="highlighter-rouge">ffmpeg</code> process is broken, the sens
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -251,7 +251,7 @@ If the <code class="highlighter-rouge">ffmpeg</code> process is broken, the sens
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -272,7 +272,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
|
||||
<title>gc100 Binary Sensor - Home Assistant</title>
|
||||
<meta name="author" content="Home Assistant">
|
||||
<meta name="description" content="Instructions on how to set up an gc100 binary sensor within Home Assistant.">
|
||||
<meta name="description" content="Instructions on how to set up a gc100 binary sensor within Home Assistant.">
|
||||
<meta name="viewport" content="width=device-width">
|
||||
<link rel="canonical" href="https://home-assistant.io/components/binary_sensor.gc100/">
|
||||
<meta property="fb:app_id" content="338291289691179">
|
||||
|
@ -16,12 +16,12 @@
|
|||
<meta property="og:site_name" content="Home Assistant">
|
||||
<meta property="og:url" content="https://home-assistant.io/components/binary_sensor.gc100/">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:description" content="Instructions on how to set up an gc100 binary sensor within Home Assistant.">
|
||||
<meta property="og:description" content="Instructions on how to set up a gc100 binary sensor within Home Assistant.">
|
||||
<meta property="og:image" content="https://home-assistant.io/images/default-social.png">
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:site" content="@home_assistant">
|
||||
<meta name="twitter:title" content="gc100 Binary Sensor">
|
||||
<meta name="twitter:description" content="Instructions on how to set up an gc100 binary sensor within Home Assistant.">
|
||||
<meta name="twitter:description" content="Instructions on how to set up a gc100 binary sensor within Home Assistant.">
|
||||
<meta name="twitter:image" content="https://home-assistant.io/images/default-social.png">
|
||||
<link href="/stylesheets/screen.css" media="screen, projection, print" rel="stylesheet">
|
||||
<link href="/atom.xml" rel="alternate" title="Home Assistant" type="application/atom+xml">
|
||||
|
@ -250,7 +250,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -321,7 +321,7 @@ binary_sensor.home_line_crossing_2
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -256,7 +256,7 @@ Full configuration details can be found on the main <a href="/components/hive/">
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -252,7 +252,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -288,7 +288,7 @@ You should choose a unique device name (DEVICE_NAME) to avoid clashes with other
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -299,7 +299,7 @@ For more information about IHC resource ids see <a href="/components/ihc/#manual
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -242,7 +242,7 @@ component.</p>
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -255,7 +255,7 @@ If you set <code class="highlighter-rouge">show_on_map</code> <code class="highl
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -255,7 +255,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -299,7 +299,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -280,7 +280,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -373,7 +373,7 @@ home/bathroom/switch/button 1
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -359,7 +359,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -285,7 +285,7 @@ The firmware version 2.26 doesn’t support TLS/SSL. This means that you are onl
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -287,7 +287,7 @@ You must have the <a href="/components/nest/">Nest component</a> configured to u
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -290,7 +290,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -266,7 +266,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -260,7 +260,7 @@ You must have the <a href="/components/octoprint/">OctoPrint component</a> confi
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -272,7 +272,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -265,7 +265,7 @@ When run on Windows systems, the round trip time attributes are rounded to the n
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -257,7 +257,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
|
||||
<title>Raspihats Binary Sensor - Home Assistant</title>
|
||||
<meta name="author" content="Home Assistant">
|
||||
<meta name="description" content="Instructions how to integrate Raspihats add-on boards for Raspberry PI into Home Assistant as a binary_sensor.">
|
||||
<meta name="description" content="Instructions how to integrate Raspihats add-on boards for Raspberry Pi into Home Assistant as a binary_sensor.">
|
||||
<meta name="viewport" content="width=device-width">
|
||||
<link rel="canonical" href="https://home-assistant.io/components/binary_sensor.raspihats/">
|
||||
<meta property="fb:app_id" content="338291289691179">
|
||||
|
@ -16,12 +16,12 @@
|
|||
<meta property="og:site_name" content="Home Assistant">
|
||||
<meta property="og:url" content="https://home-assistant.io/components/binary_sensor.raspihats/">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:description" content="Instructions how to integrate Raspihats add-on boards for Raspberry PI into Home Assistant as a binary_sensor.">
|
||||
<meta property="og:description" content="Instructions how to integrate Raspihats add-on boards for Raspberry Pi into Home Assistant as a binary_sensor.">
|
||||
<meta property="og:image" content="https://home-assistant.io/images/default-social.png">
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:site" content="@home_assistant">
|
||||
<meta name="twitter:title" content="Raspihats Binary Sensor">
|
||||
<meta name="twitter:description" content="Instructions how to integrate Raspihats add-on boards for Raspberry PI into Home Assistant as a binary_sensor.">
|
||||
<meta name="twitter:description" content="Instructions how to integrate Raspihats add-on boards for Raspberry Pi into Home Assistant as a binary_sensor.">
|
||||
<meta name="twitter:image" content="https://home-assistant.io/images/default-social.png">
|
||||
<link href="/stylesheets/screen.css" media="screen, projection, print" rel="stylesheet">
|
||||
<link href="/atom.xml" rel="alternate" title="Home Assistant" type="application/atom+xml">
|
||||
|
@ -143,7 +143,7 @@
|
|||
70: -- -- -- -- -- -- -- 77
|
||||
</code></pre>
|
||||
</div>
|
||||
<p>For more details about the <code class="highlighter-rouge">raspihats</code> add-on boards for Raspberry PI, visit <a href="http://www.raspihats.com/">raspihats.com</a>.</p>
|
||||
<p>For more details about the <code class="highlighter-rouge">raspihats</code> add-on boards for Raspberry Pi, visit <a href="http://www.raspihats.com/">raspihats.com</a>.</p>
|
||||
</article>
|
||||
</div>
|
||||
<aside id="sidebar" class="grid__item one-third lap-one-whole palm-one-whole">
|
||||
|
@ -308,7 +308,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
Raspihats Binary Sensor
|
||||
|
|
|
@ -358,7 +358,7 @@ User-Agent: Home Assistant
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -346,7 +346,7 @@ to configure your new devices and leave it off otherwise.</p>
|
|||
RFXtrx Binary Sensor
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -258,7 +258,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -6,22 +6,22 @@
|
|||
<head>
|
||||
<meta charset="utf-8">
|
||||
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
|
||||
<title>Raspberry PI GPIO Binary Sensor - Home Assistant</title>
|
||||
<title>Raspberry Pi GPIO Binary Sensor - Home Assistant</title>
|
||||
<meta name="author" content="Home Assistant">
|
||||
<meta name="description" content="Instructions how to integrate the GPIO sensor capability of a Raspberry PI into Home Assistant.">
|
||||
<meta name="description" content="Instructions how to integrate the GPIO sensor capability of a Raspberry Pi into Home Assistant.">
|
||||
<meta name="viewport" content="width=device-width">
|
||||
<link rel="canonical" href="https://home-assistant.io/components/binary_sensor.rpi_gpio/">
|
||||
<meta property="fb:app_id" content="338291289691179">
|
||||
<meta property="og:title" content="Raspberry PI GPIO Binary Sensor">
|
||||
<meta property="og:title" content="Raspberry Pi GPIO Binary Sensor">
|
||||
<meta property="og:site_name" content="Home Assistant">
|
||||
<meta property="og:url" content="https://home-assistant.io/components/binary_sensor.rpi_gpio/">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:description" content="Instructions how to integrate the GPIO sensor capability of a Raspberry PI into Home Assistant.">
|
||||
<meta property="og:description" content="Instructions how to integrate the GPIO sensor capability of a Raspberry Pi into Home Assistant.">
|
||||
<meta property="og:image" content="https://home-assistant.io/images/default-social.png">
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:site" content="@home_assistant">
|
||||
<meta name="twitter:title" content="Raspberry PI GPIO Binary Sensor">
|
||||
<meta name="twitter:description" content="Instructions how to integrate the GPIO sensor capability of a Raspberry PI into Home Assistant.">
|
||||
<meta name="twitter:title" content="Raspberry Pi GPIO Binary Sensor">
|
||||
<meta name="twitter:description" content="Instructions how to integrate the GPIO sensor capability of a Raspberry Pi into Home Assistant.">
|
||||
<meta name="twitter:image" content="https://home-assistant.io/images/default-social.png">
|
||||
<link href="/stylesheets/screen.css" media="screen, projection, print" rel="stylesheet">
|
||||
<link href="/atom.xml" rel="alternate" title="Home Assistant" type="application/atom+xml">
|
||||
|
@ -70,7 +70,7 @@
|
|||
<article class="page">
|
||||
<header>
|
||||
<h1 class="title indent">
|
||||
Raspberry PI GPIO Binary Sensor
|
||||
Raspberry Pi GPIO Binary Sensor
|
||||
</h1>
|
||||
</header>
|
||||
<hr class="divider">
|
||||
|
@ -122,15 +122,15 @@
|
|||
<div class='section'>
|
||||
<h1 class='title delta'>Related components</h1>
|
||||
<ul class='divided'>
|
||||
<li><a href='/components/rpi_gpio/'>
|
||||
Raspberry PI GPIO
|
||||
</a></li>
|
||||
<li><a href='/components/switch.rpi_gpio/'>
|
||||
Raspberry PI GPIO Switch
|
||||
</a></li>
|
||||
<li><a href='/components/cover.rpi_gpio/'>
|
||||
Raspberry Pi Cover
|
||||
</a></li>
|
||||
<li><a href='/components/rpi_gpio/'>
|
||||
Raspberry Pi GPIO
|
||||
</a></li>
|
||||
<li><a href='/components/switch.rpi_gpio/'>
|
||||
Raspberry Pi GPIO Switch
|
||||
</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class='section'>
|
||||
|
@ -263,7 +263,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
Raspberry PI GPIO Binary Sensor
|
||||
Raspberry Pi GPIO Binary Sensor
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -266,7 +266,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -241,7 +241,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -266,7 +266,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -239,7 +239,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -241,7 +241,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -256,7 +256,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -236,7 +236,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -396,7 +396,7 @@ device tracking and Z-Wave multisensor presence sensors.</p>
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -253,7 +253,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -268,7 +268,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -284,7 +284,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -272,7 +272,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -258,7 +258,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -250,7 +250,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -281,7 +281,7 @@ The above devices are confirmed to work, but others may work as well.
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -265,7 +265,7 @@ If you use the sensor for Canada (<code class="highlighter-rouge">CA</code>) wit
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -628,7 +628,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -242,7 +242,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -260,7 +260,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -257,7 +257,7 @@
|
|||
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a>
|
||||
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>
|
||||
|
|
|
@ -248,7 +248,7 @@
|
|||
Random Binary Sensor
|
||||
</a></li>
|
||||
<li><a href='/components/binary_sensor.rpi_gpio/'>
|
||||
Raspberry PI GPIO Binary Sensor
|
||||
Raspberry Pi GPIO Binary Sensor
|
||||
</a></li>
|
||||
<li><a href='/components/binary_sensor.raspihats/'>
|
||||
Raspihats Binary Sensor
|
||||
|
|
|
@ -110,7 +110,7 @@
|
|||
</code></pre>
|
||||
</div>
|
||||
<h3><a class="title-link" name="local-image-with-hassio" href="#local-image-with-hassio"></a> Local image with Hass.io</h3>
|
||||
<p>You can show an static image with this platform. Just place the image here: <code class="highlighter-rouge">/config/www/your_image.png</code></p>
|
||||
<p>You can show a static image with this platform. Just place the image here: <code class="highlighter-rouge">/config/www/your_image.png</code></p>
|
||||
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">camera</span><span class="pi">:</span>
|
||||
<span class="pi">-</span> <span class="s">platform</span><span class="pi">:</span> <span class="s">generic</span>
|
||||
<span class="s">name</span><span class="pi">:</span> <span class="s">Some Image</span>
|
||||
|
|
|
@ -252,7 +252,7 @@
|
|||
<span class="s">mode_state_template</span><span class="pi">:</span> <span class="s2">"</span><span class="s">{{</span><span class="nv"> </span><span class="s">value_json</span><span class="nv"> </span><span class="s">}}"</span>
|
||||
</code></pre>
|
||||
</div>
|
||||
<p>This will parse the incoming <code class="highlighter-rouge">"auto"</code> as JSON, resulting in <code class="highlighter-rouge">auto</code>. Obvisouly, in this case you could also just set <code class="highlighter-rouge">value_template: "{{ value_json }}"</code>.</p>
|
||||
<p>This will parse the incoming <code class="highlighter-rouge">"auto"</code> as JSON, resulting in <code class="highlighter-rouge">auto</code>. Obviously, in this case you could also just set <code class="highlighter-rouge">value_template: "{{ value_json }}"</code>.</p>
|
||||
<h3><a class="title-link" name="example" href="#example"></a> Example</h3>
|
||||
<p>A full configuration example looks like the one below.</p>
|
||||
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Full example configuration.yaml entry</span>
|
||||
|
|
|
@ -75,7 +75,7 @@
|
|||
</header>
|
||||
<hr class="divider">
|
||||
<p>This platform supports the ESP82666 based “WiFi MQTT Relay / Thermostat” sold by <a href="https://shop.openenergymonitor.com/wifi-mqtt-relay-thermostat/">OpenEnergyMonitor</a>. The underlying <a href="http://oemthermostat.readthedocs.io/">library</a> only supports this single relay variant of the <a href="https://harizanov.com/2014/12/wifi-iot-3-channel-relay-board-with-mqtt-and-http-api-using-esp8266/">original device</a>.</p>
|
||||
<p>This platform controls the setpoint of the thermostat in it’s “manual” mode, therefore there is a configuration option the away setpoint.</p>
|
||||
<p>This platform controls the setpoint of the thermostat in its “manual” mode, therefore there is a configuration option the away setpoint.</p>
|
||||
<p>To set it up, add the following information to your <code class="highlighter-rouge">configuration.yaml</code> file:</p>
|
||||
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span>
|
||||
<span class="s">climate oem</span><span class="pi">:</span>
|
||||
|
|
|
@ -190,7 +190,7 @@
|
|||
</dd>
|
||||
<dt><a class="title-link" name="tilt_closed_value" href="#tilt_closed_value"></a> tilt_closed_value</dt>
|
||||
<dd>
|
||||
<p class="desc"><span class="type">(<span class="integer">integer</span>)</span><span class="required">(Optional)</span><span class="description">The value that will be sent on an <code class="highlighter-rouge">close_cover_tilt</code> command.</span></p>
|
||||
<p class="desc"><span class="type">(<span class="integer">integer</span>)</span><span class="required">(Optional)</span><span class="description">The value that will be sent on a <code class="highlighter-rouge">close_cover_tilt</code> command.</span></p>
|
||||
<p class="default">Default value: 0</p>
|
||||
</dd>
|
||||
<dt><a class="title-link" name="tilt_opened_value" href="#tilt_opened_value"></a> tilt_opened_value</dt>
|
||||
|
|
|
@ -135,7 +135,7 @@ RTS Record: 15 Address: FFFFFF RC: FFFF
|
|||
<ul>
|
||||
<li><strong>name</strong> (<em>Optional</em>): Name for the device, defaults to Rflink ID.</li>
|
||||
<li><strong>aliases</strong> (<em>Optional</em>): Alternative Rflink ID’s this device is known by.</li>
|
||||
<li><strong>fire_event</strong> (<em>Optional</em>): Fire an <code class="highlighter-rouge">button_pressed</code> event if this device is turned on or off (default: False).</li>
|
||||
<li><strong>fire_event</strong> (<em>Optional</em>): Fire a <code class="highlighter-rouge">button_pressed</code> event if this device is turned on or off (default: False).</li>
|
||||
<li><strong>signal_repetitions</strong> (<em>Optional</em>): Repeat every Rflink command this number of times (default: 1).</li>
|
||||
<li><strong>fire_event_</strong> (<em>Optional</em>): Set default <code class="highlighter-rouge">fire_event</code> for RFLink switch devices (see below).</li>
|
||||
<li><strong>signal_repetitions</strong> (<em>Optional</em>): Set default <code class="highlighter-rouge">signal_repetitions</code> for RFLink switch devices (see below).</li>
|
||||
|
|
|
@ -149,13 +149,13 @@
|
|||
<h1 class='title delta'>Related components</h1>
|
||||
<ul class='divided'>
|
||||
<li><a href='/components/rpi_gpio/'>
|
||||
Raspberry PI GPIO
|
||||
Raspberry Pi GPIO
|
||||
</a></li>
|
||||
<li><a href='/components/binary_sensor.rpi_gpio/'>
|
||||
Raspberry PI GPIO Binary Sensor
|
||||
Raspberry Pi GPIO Binary Sensor
|
||||
</a></li>
|
||||
<li><a href='/components/switch.rpi_gpio/'>
|
||||
Raspberry PI GPIO Switch
|
||||
Raspberry Pi GPIO Switch
|
||||
</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
|
|
|
@ -104,7 +104,7 @@ You may receive an email from Apple stating that someone has logged into your ac
|
|||
<ul>
|
||||
<li><strong>icloud_update</strong>: This service can be used to ask for an update of a certain iDevice. The <code class="highlighter-rouge">account_name</code> and <code class="highlighter-rouge">device_name</code> are optional.</li>
|
||||
<li><strong>icloud_lost_iphone</strong>: This service will play the Lost iPhone sound on a certain iDevice. The <code class="highlighter-rouge">account_name</code> and <code class="highlighter-rouge">device_name</code> are optional.</li>
|
||||
<li><strong>icloud_set_interval</strong>: This service will change the dynamic interval of an iDevice. The <code class="highlighter-rouge">account_name</code> and <code class="highlighter-rouge">device_name</code> are optional. If <code class="highlighter-rouge">interval</code> is used in the service_data, the iDevice will be updated with that new interval. That interval will be fixed until the iDevice changes zone or if this service is called again. If <code class="highlighter-rouge">interval</code> isn’t used in the service_data, the interval for that iDevice will revert back to it’s default dynamic interval based on it’s current zone, it’s distance towards home and it’s battery level.</li>
|
||||
<li><strong>icloud_set_interval</strong>: This service will change the dynamic interval of an iDevice. The <code class="highlighter-rouge">account_name</code> and <code class="highlighter-rouge">device_name</code> are optional. If <code class="highlighter-rouge">interval</code> is used in the service_data, the iDevice will be updated with that new interval. That interval will be fixed until the iDevice changes zone or if this service is called again. If <code class="highlighter-rouge">interval</code> isn’t used in the service_data, the interval for that iDevice will revert back to its default dynamic interval based on its current zone, its distance towards home and its battery level.</li>
|
||||
<li><strong>icloud_reset_account</strong>: This service can be used to reset an iCloud account. This is helpful when not all devices are being found by the component or if you have added a new iDevice to your account. The <code class="highlighter-rouge">account_name</code> is optional.</li>
|
||||
</ul>
|
||||
</article>
|
||||
|
|
|
@ -136,7 +136,7 @@ The Android app for OwnTracks is no longer developed or supported, Zanzito is a
|
|||
<h3><a class="title-link" name="using-owntracks-ibeacons-to-track-devices" href="#using-owntracks-ibeacons-to-track-devices"></a> Using Owntracks iBeacons to track devices</h3>
|
||||
<p>iBeacons don’t need to be stationary. You could put one on your key ring, or in your car.</p>
|
||||
<p>When your phone sees a mobile iBeacon that it knows about, it will tell HA the location of that iBeacon. If your phone moves while you are connected to the iBeacon, HA will update the location of the iBeacon. But when your phone loses the connection, HA will stop updating the iBeacon location.</p>
|
||||
<p>To use mobile iBeacons with HA, you just set up a region that doesn’t match your Zone names. If HA sees an entry event for a iBeacon region that doesn’t match a Zone name (say <code class="highlighter-rouge">keys</code>) - it will start tracking it, calling the device <code class="highlighter-rouge">device_tracker.beacon_keys</code>).</p>
|
||||
<p>To use mobile iBeacons with HA, you just set up a region that doesn’t match your Zone names. If HA sees an entry event for an iBeacon region that doesn’t match a Zone name (say <code class="highlighter-rouge">keys</code>) - it will start tracking it, calling the device <code class="highlighter-rouge">device_tracker.beacon_keys</code>).</p>
|
||||
<p>This allows you to write zone automations for devices that can’t track themselves (for example <em>alert me if I leave the house and my keys are still at home</em>). Another example would be <em>open the gates if my car arrives home</em>.</p>
|
||||
<h3><a class="title-link" name="using-mobile-and-fixed-ibeacons-together" href="#using-mobile-and-fixed-ibeacons-together"></a> Using mobile and fixed iBeacons together</h3>
|
||||
<p>You can use iBeacons of both types together, so if you have a Zone <code class="highlighter-rouge">drive</code> with an iBeacon region called <code class="highlighter-rouge">-drive</code> and you arrive home with a mobile iBeacon called <code class="highlighter-rouge">-car</code>, then <code class="highlighter-rouge">device_tracker.beacon_car</code> will be set to a state of <code class="highlighter-rouge">drive</code>.</p>
|
||||
|
|
|
@ -74,7 +74,7 @@
|
|||
</h1>
|
||||
</header>
|
||||
<hr class="divider">
|
||||
<p>The <code class="highlighter-rouge">tado</code> device tracker is using the <a href="https://www.tado.com/">Tado Smart Thermostat</a> and it’s support for person presence detection based on smartphone location by geofencing.</p>
|
||||
<p>The <code class="highlighter-rouge">tado</code> device tracker is using the <a href="https://www.tado.com/">Tado Smart Thermostat</a> and its support for person presence detection based on smartphone location by geofencing.</p>
|
||||
<p>This tracker uses the Tado API to determine if a mobile device is at home. It tracks all devices in your home that Tado knows about.</p>
|
||||
<p>To use the Tado platform in your installation, add the following to your <code class="highlighter-rouge">configuration.yaml</code> file:</p>
|
||||
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry for Tado</span>
|
||||
|
|
|
@ -74,7 +74,7 @@
|
|||
</h1>
|
||||
</header>
|
||||
<hr class="divider">
|
||||
<p>The <code class="highlighter-rouge">envisalink</code> component will allow Home Assistant users who own either a DSC or Honeywell alarm panel to leverage their alarm system and it’s sensors to provide Home Assistant with rich information about their homes. Connectivity between Home Assistant and the alarm panel is accomplished through a device produced by Eyez On, known as the Envisalink. The Envisalink evl3 and evl4 boards provide a TCP/IP interface to the alarm panel, where it emulates an alarm keypad. This board also exposes a raw TCP/IP based API, upon which this component is built. Currently, the Envisalink version 4 is the latest model. This component supports both the evl3 and the evl4.</p>
|
||||
<p>The <code class="highlighter-rouge">envisalink</code> component will allow Home Assistant users who own either a DSC or Honeywell alarm panel to leverage their alarm system and its sensors to provide Home Assistant with rich information about their homes. Connectivity between Home Assistant and the alarm panel is accomplished through a device produced by Eyez On, known as the Envisalink. The Envisalink evl3 and evl4 boards provide a TCP/IP interface to the alarm panel, where it emulates an alarm keypad. This board also exposes a raw TCP/IP based API, upon which this component is built. Currently, the Envisalink version 4 is the latest model. This component supports both the evl3 and the evl4.</p>
|
||||
<p>Please visit the <a href="http://www.eyezon.com/">eyezon website</a> for further information about the evl3 and evl4 boards.</p>
|
||||
<p>There is currently support for the following device types within Home Assistant:</p>
|
||||
<ul>
|
||||
|
|
|
@ -134,7 +134,7 @@
|
|||
</p>
|
||||
<p>More information can be found on the <a href="https://www.developers.meethue.com/documentation/groups-api#22_create_group">Philips Hue API documentation</a> website.</p>
|
||||
<h3><a class="title-link" name="using-hue-scenes-in-home-assistant" href="#using-hue-scenes-in-home-assistant"></a> Using Hue Scenes in Home Assistant</h3>
|
||||
<p>The Hue platform has it’s own concept of scenes for setting the colors of a group of lights at once. Hue Scenes are very cheap, get created by all kinds of apps (as it is the only way to have 2 or more lights change at the same time), and are rarely deleted. A typical Hue hub might have hundreds of scenes stored in them, many that you’ve never used, almost all very poorly named.</p>
|
||||
<p>The Hue platform has its own concept of scenes for setting the colors of a group of lights at once. Hue Scenes are very cheap, get created by all kinds of apps (as it is the only way to have 2 or more lights change at the same time), and are rarely deleted. A typical Hue hub might have hundreds of scenes stored in them, many that you’ve never used, almost all very poorly named.</p>
|
||||
<p>To avoid user interface overload we don’t expose scenes directly. Instead there is a hue.hue_activate_scene service which can be used by <code class="highlighter-rouge">automation</code> or <code class="highlighter-rouge">script</code> components.
|
||||
This will have all the bulbs transitioned at once, instead of one at a time using standard scenes in Home Assistant.</p>
|
||||
<p>For instance:</p>
|
||||
|
|
|
@ -74,7 +74,7 @@
|
|||
</h1>
|
||||
</header>
|
||||
<hr class="divider">
|
||||
<p>The <code class="highlighter-rouge">microsoft_face_detect</code> image processing platform allows you to use the <a href="https://www.microsoft.com/cognitive-services/en-us/">Microsoft Face Identify</a> API through Home Assistant. This platform enables you do detect face on camera and fire a event with attributes.</p>
|
||||
<p>The <code class="highlighter-rouge">microsoft_face_detect</code> image processing platform allows you to use the <a href="https://www.microsoft.com/cognitive-services/en-us/">Microsoft Face Identify</a> API through Home Assistant. This platform enables you do detect face on camera and fire an event with attributes.</p>
|
||||
<p>Please refer to the <a href="/components/microsoft_face/">component</a> configuration on how to setup the API key.</p>
|
||||
<p>For using the result inside an automation rule, take a look at the <a href="/components/image_processing/">component</a> page.</p>
|
||||
<h3><a class="title-link" name="configuration-home-assistant" href="#configuration-home-assistant"></a> Configuration Home Assistant</h3>
|
||||
|
|
|
@ -74,7 +74,7 @@
|
|||
</h1>
|
||||
</header>
|
||||
<hr class="divider">
|
||||
<p>The <code class="highlighter-rouge">microsoft_face_identify</code> image processing platform lets you use <a href="https://www.microsoft.com/cognitive-services/en-us/">Microsoft Face identify</a> API through Home Assistant. This platform allow you do identify persons on camera and fire a event with identify persons.</p>
|
||||
<p>The <code class="highlighter-rouge">microsoft_face_identify</code> image processing platform lets you use <a href="https://www.microsoft.com/cognitive-services/en-us/">Microsoft Face identify</a> API through Home Assistant. This platform allow you do identify persons on camera and fire an event with attributes.</p>
|
||||
<p>Please refer to the <a href="/components/microsoft_face/">component</a> configuration on how to setup the API key.</p>
|
||||
<p>For using the result inside an automation rule, take a look at the <a href="/components/image_processing/">component</a> page.</p>
|
||||
<h3><a class="title-link" name="configuration-home-assistant" href="#configuration-home-assistant"></a> Configuration Home Assistant</h3>
|
||||
|
|
|
@ -777,11 +777,11 @@ var allComponents = [
|
|||
{url:"/components/switch.rainmachine/", title:"RainMachine Switch", cat:"switch", featured: false, v: "0.51", logo: "rainmachine.png"},
|
||||
{url:"/components/binary_sensor.random/", title:"Random Binary Sensor", cat:"sensor", featured: false, v: "0.57", logo: "home-assistant.png"},
|
||||
{url:"/components/sensor.random/", title:"Random Sensor", cat:"sensor", featured: false, v: "0.32", logo: "home-assistant.png"},
|
||||
{url:"/components/rpi_gpio/", title:"Raspberry PI GPIO", cat:"diy", featured: false, v: "0.7", logo: "raspberry-pi.png"},
|
||||
{url:"/components/binary_sensor.rpi_gpio/", title:"Raspberry PI GPIO Binary Sensor", cat:"binary-sensor", featured: false, v: "0.7", logo: "raspberry-pi.png"},
|
||||
{url:"/components/switch.rpi_gpio/", title:"Raspberry PI GPIO Switch", cat:"switch", featured: false, v: "0.7", logo: "raspberry-pi.png"},
|
||||
{url:"/components/camera.rpi_camera/", title:"Raspberry Pi Camera", cat:"camera", featured: false, v: "0.17", logo: "raspberry-pi.png"},
|
||||
{url:"/components/cover.rpi_gpio/", title:"Raspberry Pi Cover", cat:"cover", featured: false, v: "0.23", logo: "raspberry-pi.png"},
|
||||
{url:"/components/rpi_gpio/", title:"Raspberry Pi GPIO", cat:"diy", featured: false, v: "0.7", logo: "raspberry-pi.png"},
|
||||
{url:"/components/binary_sensor.rpi_gpio/", title:"Raspberry Pi GPIO Binary Sensor", cat:"binary-sensor", featured: false, v: "0.7", logo: "raspberry-pi.png"},
|
||||
{url:"/components/switch.rpi_gpio/", title:"Raspberry Pi GPIO Switch", cat:"switch", featured: false, v: "0.7", logo: "raspberry-pi.png"},
|
||||
{url:"/components/switch.rpi_rf/", title:"Raspberry Pi RF Switch", cat:"switch", featured: false, v: "0.19", logo: "raspberry-pi.png"},
|
||||
{url:"/components/raspihats/", title:"Raspihats", cat:"diy", featured: false, v: "0.45", logo: "raspihats.png"},
|
||||
{url:"/components/binary_sensor.raspihats/", title:"Raspihats Binary Sensor", cat:"binary-sensor", featured: false, v: "0.44", logo: "raspihats.png"},
|
||||
|
@ -1872,11 +1872,11 @@ allComponents.pop(); // remove placeholder element at the end
|
|||
<li><a href='/components/switch.rainmachine/'>RainMachine Switch</a></li>
|
||||
<li><a href='/components/binary_sensor.random/'>Random Binary Sensor</a></li>
|
||||
<li><a href='/components/sensor.random/'>Random Sensor</a></li>
|
||||
<li><a href='/components/rpi_gpio/'>Raspberry PI GPIO</a></li>
|
||||
<li><a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a></li>
|
||||
<li><a href='/components/switch.rpi_gpio/'>Raspberry PI GPIO Switch</a></li>
|
||||
<li><a href='/components/camera.rpi_camera/'>Raspberry Pi Camera</a></li>
|
||||
<li><a href='/components/cover.rpi_gpio/'>Raspberry Pi Cover</a></li>
|
||||
<li><a href='/components/rpi_gpio/'>Raspberry Pi GPIO</a></li>
|
||||
<li><a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a></li>
|
||||
<li><a href='/components/switch.rpi_gpio/'>Raspberry Pi GPIO Switch</a></li>
|
||||
<li><a href='/components/switch.rpi_rf/'>Raspberry Pi RF Switch</a></li>
|
||||
<li><a href='/components/raspihats/'>Raspihats</a></li>
|
||||
<li><a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a></li>
|
||||
|
|
|
@ -124,7 +124,7 @@
|
|||
</dl>
|
||||
</div>
|
||||
<p>In the example above 12345 is ihc resource id and “tablelight” is the name.
|
||||
The IHC resource id can be a light level for dimmers or an boolean output of a relay.
|
||||
The IHC resource id can be a light level for dimmers or a boolean output of a relay.
|
||||
For more information about IHC resource ids see <a href="/components/ihc/#manual-setup">Manual Setup</a></p>
|
||||
</article>
|
||||
</div>
|
||||
|
|
|
@ -107,7 +107,7 @@
|
|||
<li><strong>name</strong> (<em>Optional</em>): Name for the device, defaults to Rflink ID.</li>
|
||||
<li><strong>type</strong> (<em>Optional</em>): Override automatically detected type of the light device, can be: switchable, dimmable, hybrid or toggle. See ‘Light Types’ below. (default: Switchable)</li>
|
||||
<li><strong>aliases</strong> (<em>Optional</em>): Alternative Rflink ID’s this device is known by.</li>
|
||||
<li><strong>fire_event</strong> (<em>Optional</em>): Fire an <code class="highlighter-rouge">button_pressed</code> event if this device is turned on or off (default: False).</li>
|
||||
<li><strong>fire_event</strong> (<em>Optional</em>): Fire a <code class="highlighter-rouge">button_pressed</code> event if this device is turned on or off (default: False).</li>
|
||||
<li><strong>signal_repetitions</strong> (<em>Optional</em>): Repeat every Rflink command this number of times (default: 1).</li>
|
||||
<li><strong>fire_event_</strong> (<em>Optional</em>): Set default <code class="highlighter-rouge">fire_event</code> for RFLink switch devices (see below).</li>
|
||||
<li><strong>signal_repetitions</strong> (<em>Optional</em>): Set default <code class="highlighter-rouge">signal_repetitions</code> for RFLink switch devices (see below).</li>
|
||||
|
@ -137,7 +137,7 @@
|
|||
<h3><a class="title-link" name="light-types" href="#light-types"></a> Light types</h3>
|
||||
<p>Light devices can come in different forms. Some only switch on and off, other support dimming. Dimmable devices might not always respond nicely to repeated <code class="highlighter-rouge">on</code> command as they turn into a pulsating state until <code class="highlighter-rouge">on</code> is pressed again (for example KlikAanKlikUit). The RFLink component support three types of lights to make things work in every situation:</p>
|
||||
<ul>
|
||||
<li><em>Hybrid</em>: This type sends a <code class="highlighter-rouge">dim</code> followed by an a <code class="highlighter-rouge">on</code> command; and <code class="highlighter-rouge">off</code> commands. This will make dimmable devices turn on at the requested dim level and on/off devices on. One caveat is this type is not compatible with signal repetition as multiple <code class="highlighter-rouge">on</code> signals will cause dimmers to go into disco mode.</li>
|
||||
<li><em>Hybrid</em>: This type sends a <code class="highlighter-rouge">dim</code> followed by an an <code class="highlighter-rouge">on</code> command; and <code class="highlighter-rouge">off</code> commands. This will make dimmable devices turn on at the requested dim level and on/off devices on. One caveat is this type is not compatible with signal repetition as multiple <code class="highlighter-rouge">on</code> signals will cause dimmers to go into disco mode.</li>
|
||||
<li><em>Switchable</em>: Device type that sends only <code class="highlighter-rouge">on</code> and <code class="highlighter-rouge">off</code> commands. It work for both on/off and dimmable type switches. However dimmables might have issues with signal repetition (see above).</li>
|
||||
<li><em>Dimmable</em>: Sends only <code class="highlighter-rouge">dim</code> and <code class="highlighter-rouge">off</code> commands. This does not work on on/off type devices as they don’t understand the <code class="highlighter-rouge">dim</code> command. For dimmers this does not cause issues with signal repetitions.</li>
|
||||
<li><em>Toggle</em>: Device type that sends only <code class="highlighter-rouge">on</code> commands to turn on or off the device. Some switches like for example Livolo light switches use the same ‘on’ command to switch on and switch off the lights. If the light is on and ‘on’ gets sent, the light will turn off and if the light is off and ‘on’ gets sent, the light will turn on. If the device has an unknown state, it will assume it is off by default.</li>
|
||||
|
|
|
@ -132,7 +132,7 @@
|
|||
</code></pre>
|
||||
</div>
|
||||
<h3><a class="title-link" name="exclude-events" href="#exclude-events"></a> Exclude Events</h3>
|
||||
<p>Entities customized as hidden are excluded from the logbook by default, but sometimes you want to show the entity in the UI and not in the logbook. For instance you use the <code class="highlighter-rouge">sensor.date</code>to show the current date in the UI, but you do not want an logbook entry for that sensor every day.
|
||||
<p>Entities customized as hidden are excluded from the logbook by default, but sometimes you want to show the entity in the UI and not in the logbook. For instance you use the <code class="highlighter-rouge">sensor.date</code>to show the current date in the UI, but you do not want a logbook entry for that sensor every day.
|
||||
To exclude these entities just add them to the <code class="highlighter-rouge">exclude</code> > <code class="highlighter-rouge">entities</code> list in the configuration of the logbook.</p>
|
||||
<p>To exclude all events from a whole domain add it to the <code class="highlighter-rouge">exclude</code> > <code class="highlighter-rouge">domain</code> list. For instance you use the <code class="highlighter-rouge">sun</code> domain only to trigger automations on the `azimuth attribute, then you possible are not interested in the logbook entries for sun rise and sun set.</p>
|
||||
<h3><a class="title-link" name="custom-entries" href="#custom-entries"></a> Custom Entries</h3>
|
||||
|
|
|
@ -74,7 +74,7 @@
|
|||
</h1>
|
||||
</header>
|
||||
<hr class="divider">
|
||||
<p>Mailboxes provide an list of messages with short information about each. Mailbox messages appear on a separate panel in the frontend.</p>
|
||||
<p>Mailboxes provide a list of messages with short information about each. Mailbox messages appear on a separate panel in the frontend.</p>
|
||||
<p>Home Assistant currently supports only the <a href="/component/mailbox.asterisk_mbox">Asterisk Voicemail</a> mailbox.</p>
|
||||
<p>Each mailbox also provides an entity to indicate the number of messages available on the main page.</p>
|
||||
</article>
|
||||
|
|
|
@ -74,7 +74,7 @@
|
|||
</h1>
|
||||
</header>
|
||||
<hr class="divider">
|
||||
<p>Google Cast devices like Android TVs and Chromecasts will be automatically discovered if you enable <a href="/components/discovery/">the discovery component</a>. There is a issue where Chromecasts can only be discovered if your device is connected to the same subnet as your Chromecast.</p>
|
||||
<p>Google Cast devices like Android TVs and Chromecasts will be automatically discovered if you enable <a href="/components/discovery/">the discovery component</a>. There is an issue where Chromecasts can only be discovered if your device is connected to the same subnet as your Chromecast.</p>
|
||||
<p>The Chromecast platform can also be forced to load by adding the following lines to your <code class="highlighter-rouge">configuration.yaml</code>:</p>
|
||||
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span>
|
||||
<span class="s">media_player</span><span class="pi">:</span>
|
||||
|
|
|
@ -106,13 +106,13 @@
|
|||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code>ln -s /path/to/your/installation/of/gi /path/to/your/venv/lib/python3.4/site-packages
|
||||
</code></pre>
|
||||
</div>
|
||||
<p>On a Raspberry PI, you may need to add the Home Assistant user to the <code class="highlighter-rouge">audio</code> group:</p>
|
||||
<p>On a Raspberry Pi, you may need to add the Home Assistant user to the <code class="highlighter-rouge">audio</code> group:</p>
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code>sudo usermod -a -G audio <ha_user>
|
||||
</code></pre>
|
||||
</div>
|
||||
<h2><a class="title-link" name="example-usage" href="#example-usage"></a> Example Usage</h2>
|
||||
<h3><a class="title-link" name="using-with-tts" href="#using-with-tts"></a> Using with TTS</h3>
|
||||
<p>To play TTS on your local computer (for example, if you have speakers attached to your Raspberry PI:</p>
|
||||
<p>To play TTS on your local computer (for example, if you have speakers attached to your Raspberry Pi:</p>
|
||||
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">media_player</span><span class="pi">:</span>
|
||||
<span class="pi">-</span> <span class="s">platform</span><span class="pi">:</span> <span class="s">gstreamer</span>
|
||||
|
||||
|
|
|
@ -112,7 +112,7 @@ on your receiver, or else startup of Home Assistant will hang if you
|
|||
have your receiver switched off.</li>
|
||||
<li>In some cases, auto-discovery fails due to a known bug in the
|
||||
receiver’s firmware. It is possible to manually specify the
|
||||
receiver’s IP address or via it’s hostname (if it is discoverable by
|
||||
receiver’s IP address or via its hostname (if it is discoverable by
|
||||
your DNS) then.</li>
|
||||
</ul>
|
||||
<h3><a class="title-link" name="supported-operations" href="#supported-operations"></a> Supported operations</h3>
|
||||
|
|
|
@ -74,7 +74,7 @@
|
|||
</h1>
|
||||
</header>
|
||||
<hr class="divider">
|
||||
<p><a href="https://mycroft.ai">Mycroft</a> is a open source voice assistant that allows you to send notifications and more to Mycroft from Home Assistant.</p>
|
||||
<p><a href="https://mycroft.ai">Mycroft</a> is an open source voice assistant that allows you to send notifications and more to Mycroft from Home Assistant.</p>
|
||||
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span>
|
||||
<span class="s">mycroft</span><span class="pi">:</span>
|
||||
<span class="s">host</span><span class="pi">:</span> <span class="s">0.0.0.0</span>
|
||||
|
|
|
@ -76,7 +76,7 @@
|
|||
<hr class="divider">
|
||||
<p>The <code class="highlighter-rouge">clickatell</code> platform uses <a href="https://clickatell.com">Clickatell</a> to deliver SMS notifications from Home Assistant.</p>
|
||||
<h3>Get your Clickatell API Credentials</h3>
|
||||
<p>Go to your <a href="https://portal.clickatell.com/#/">Clickatell SMS Platform Portal</a> section and create a new SMS integration. There are three screens of information required to creater an integration. Please ensure the following:</p>
|
||||
<p>Go to your <a href="https://portal.clickatell.com/#/">Clickatell SMS Platform Portal</a> section and create a new SMS integration. There are three screens of information required to create an integration. Please ensure the following:</p>
|
||||
<ol>
|
||||
<li>Give the new Integration an identification name.</li>
|
||||
<li>Ensure it is set for ‘production’ use.</li>
|
||||
|
|
|
@ -286,7 +286,7 @@
|
|||
</code></pre>
|
||||
</div>
|
||||
<h3><a class="title-link" name="making-notifications-work-with-nginx-proxy" href="#making-notifications-work-with-nginx-proxy"></a> Making notifications work with NGINX proxy</h3>
|
||||
<p>If you use <a href="/ecosystem/nginx/">NGINX</a> as an proxy with authentication in front of your Home Assistant instance, you may have trouble with receiving events back to Home Assistant. It’s because of authentication token that cannot be passed through the proxy.</p>
|
||||
<p>If you use <a href="/ecosystem/nginx/">NGINX</a> as a proxy with authentication in front of your Home Assistant instance, you may have trouble with receiving events back to Home Assistant. It’s because of authentication token that cannot be passed through the proxy.</p>
|
||||
<p>To solve the issue put additional location into your nginx site’s configuration:</p>
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code>location /api/notify.html5/callback <span class="o">{</span>
|
||||
<span class="k">if</span> <span class="o">(</span><span class="nv">$http_authorization</span> <span class="o">=</span> <span class="s2">""</span><span class="o">)</span> <span class="o">{</span> <span class="k">return </span>403; <span class="o">}</span>
|
||||
|
|
|
@ -75,7 +75,7 @@
|
|||
</header>
|
||||
<hr class="divider">
|
||||
<p>The <a href="https://www.pushsafer.com/">Pushsafer service</a> is a platform for the notify component. This allows you to send messages to the user using Pushsafer.</p>
|
||||
<p>In order to get an private or alias key you need to go to the <a href="https://www.pushsafer.com">Pushsafer website</a> and register.</p>
|
||||
<p>In order to get a private or alias key you need to go to the <a href="https://www.pushsafer.com">Pushsafer website</a> and register.</p>
|
||||
<p>To use Pushsafer notifications, add the following to your <code class="highlighter-rouge">configuration.yaml</code> file:</p>
|
||||
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span>
|
||||
<span class="s">notify</span><span class="pi">:</span>
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
|
||||
<title>Raspihats - Home Assistant</title>
|
||||
<meta name="author" content="Home Assistant">
|
||||
<meta name="description" content="Instructions how to integrate Raspihats add-on boards for Raspberry PI into Home Assistant.">
|
||||
<meta name="description" content="Instructions how to integrate Raspihats add-on boards for Raspberry Pi into Home Assistant.">
|
||||
<meta name="viewport" content="width=device-width">
|
||||
<link rel="canonical" href="https://home-assistant.io/components/raspihats/">
|
||||
<meta property="fb:app_id" content="338291289691179">
|
||||
|
@ -16,12 +16,12 @@
|
|||
<meta property="og:site_name" content="Home Assistant">
|
||||
<meta property="og:url" content="https://home-assistant.io/components/raspihats/">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:description" content="Instructions how to integrate Raspihats add-on boards for Raspberry PI into Home Assistant.">
|
||||
<meta property="og:description" content="Instructions how to integrate Raspihats add-on boards for Raspberry Pi into Home Assistant.">
|
||||
<meta property="og:image" content="https://home-assistant.io/images/default-social.png">
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:site" content="@home_assistant">
|
||||
<meta name="twitter:title" content="Raspihats">
|
||||
<meta name="twitter:description" content="Instructions how to integrate Raspihats add-on boards for Raspberry PI into Home Assistant.">
|
||||
<meta name="twitter:description" content="Instructions how to integrate Raspihats add-on boards for Raspberry Pi into Home Assistant.">
|
||||
<meta name="twitter:image" content="https://home-assistant.io/images/default-social.png">
|
||||
<link href="/stylesheets/screen.css" media="screen, projection, print" rel="stylesheet">
|
||||
<link href="/atom.xml" rel="alternate" title="Home Assistant" type="application/atom+xml">
|
||||
|
@ -135,7 +135,7 @@
|
|||
<a href='/components/rpi_pfio/'>PiFace Digital I/O</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/rpi_gpio/'>Raspberry PI GPIO</a>
|
||||
<a href='/components/rpi_gpio/'>Raspberry Pi GPIO</a>
|
||||
</li>
|
||||
<li>
|
||||
Raspihats
|
||||
|
|
|
@ -166,7 +166,7 @@ Wildcards only work at the end of the ID, not in the middle or front!
|
|||
<p>If you find a device is recognized differently, with different protocols or the ON OFF is swapped or detected as two ON commands, it can be overcome with the RFLink ‘RF Signal Learning’ mechanism from RFLink Rev 46 (11 March 2017). <a href="http://www.rflink.nl/blog2/faq#RFFind">Link to further detail.</a></p>
|
||||
<h3><a class="title-link" name="technical-overview" href="#technical-overview"></a> Technical Overview</h3>
|
||||
<ul>
|
||||
<li>The<code class="highlighter-rouge">rflink</code> Python module is a asyncio transport/protocol which is setup to fire a callback for every (valid/supported) packet received by the RFLink gateway.</li>
|
||||
<li>The<code class="highlighter-rouge">rflink</code> Python module is an asyncio transport/protocol which is setup to fire a callback for every (valid/supported) packet received by the RFLink gateway.</li>
|
||||
<li>This component uses this callback to distribute ‘rflink packet events’ over <a href="https://home-assistant.io/docs/configuration/events/">Home Assistant’s event bus</a> which can be subscribed to by entities/platform implementations.</li>
|
||||
<li>The platform implementation takes care of creating new devices (if enabled) for unseen incoming packet ID’s.</li>
|
||||
<li>Device entities take care of matching to the packet ID, interpreting and performing actions based on the packet contents. Common entity logic is maintained in this main component.</li>
|
||||
|
|
|
@ -6,22 +6,22 @@
|
|||
<head>
|
||||
<meta charset="utf-8">
|
||||
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
|
||||
<title>Raspberry PI GPIO - Home Assistant</title>
|
||||
<title>Raspberry Pi GPIO - Home Assistant</title>
|
||||
<meta name="author" content="Home Assistant">
|
||||
<meta name="description" content="Instructions how to integrate the GPIO capability of a Raspberry PI into Home Assistant.">
|
||||
<meta name="description" content="Instructions how to integrate the GPIO capability of a Raspberry Pi into Home Assistant.">
|
||||
<meta name="viewport" content="width=device-width">
|
||||
<link rel="canonical" href="https://home-assistant.io/components/rpi_gpio/">
|
||||
<meta property="fb:app_id" content="338291289691179">
|
||||
<meta property="og:title" content="Raspberry PI GPIO">
|
||||
<meta property="og:title" content="Raspberry Pi GPIO">
|
||||
<meta property="og:site_name" content="Home Assistant">
|
||||
<meta property="og:url" content="https://home-assistant.io/components/rpi_gpio/">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:description" content="Instructions how to integrate the GPIO capability of a Raspberry PI into Home Assistant.">
|
||||
<meta property="og:description" content="Instructions how to integrate the GPIO capability of a Raspberry Pi into Home Assistant.">
|
||||
<meta property="og:image" content="https://home-assistant.io/images/default-social.png">
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:site" content="@home_assistant">
|
||||
<meta name="twitter:title" content="Raspberry PI GPIO">
|
||||
<meta name="twitter:description" content="Instructions how to integrate the GPIO capability of a Raspberry PI into Home Assistant.">
|
||||
<meta name="twitter:title" content="Raspberry Pi GPIO">
|
||||
<meta name="twitter:description" content="Instructions how to integrate the GPIO capability of a Raspberry Pi into Home Assistant.">
|
||||
<meta name="twitter:image" content="https://home-assistant.io/images/default-social.png">
|
||||
<link href="/stylesheets/screen.css" media="screen, projection, print" rel="stylesheet">
|
||||
<link href="/atom.xml" rel="alternate" title="Home Assistant" type="application/atom+xml">
|
||||
|
@ -70,7 +70,7 @@
|
|||
<article class="page">
|
||||
<header>
|
||||
<h1 class="title indent">
|
||||
Raspberry PI GPIO
|
||||
Raspberry Pi GPIO
|
||||
</h1>
|
||||
</header>
|
||||
<hr class="divider">
|
||||
|
@ -93,15 +93,15 @@
|
|||
<div class='section'>
|
||||
<h1 class='title delta'>Related components</h1>
|
||||
<ul class='divided'>
|
||||
<li><a href='/components/binary_sensor.rpi_gpio/'>
|
||||
Raspberry PI GPIO Binary Sensor
|
||||
</a></li>
|
||||
<li><a href='/components/switch.rpi_gpio/'>
|
||||
Raspberry PI GPIO Switch
|
||||
</a></li>
|
||||
<li><a href='/components/cover.rpi_gpio/'>
|
||||
Raspberry Pi Cover
|
||||
</a></li>
|
||||
<li><a href='/components/binary_sensor.rpi_gpio/'>
|
||||
Raspberry Pi GPIO Binary Sensor
|
||||
</a></li>
|
||||
<li><a href='/components/switch.rpi_gpio/'>
|
||||
Raspberry Pi GPIO Switch
|
||||
</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class='section'>
|
||||
|
@ -138,7 +138,7 @@
|
|||
<a href='/components/rpi_pfio/'>PiFace Digital I/O</a>
|
||||
</li>
|
||||
<li>
|
||||
Raspberry PI GPIO
|
||||
Raspberry Pi GPIO
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/raspihats/'>Raspihats</a>
|
||||
|
|
|
@ -136,7 +136,7 @@
|
|||
PiFace Digital I/O
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/rpi_gpio/'>Raspberry PI GPIO</a>
|
||||
<a href='/components/rpi_gpio/'>Raspberry Pi GPIO</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/raspihats/'>Raspihats</a>
|
||||
|
|
Some files were not shown because too many files have changed in this diff Show more
Loading…
Add table
Add a link
Reference in a new issue