Site updated at 2017-10-27 06:57:22 UTC
This commit is contained in:
parent
8cf2c82e8f
commit
9a525ce04e
26 changed files with 65 additions and 66 deletions
|
@ -74,8 +74,7 @@
|
|||
</h1>
|
||||
</header>
|
||||
<hr class="divider">
|
||||
<p>Binary sensors gather information about state of switches, contacts, pins, and alike. The return value of those sensors is usually digital (1/0). This means that those sensors knows only two states: <strong>0/off/low/closed/false</strong> and <strong>1/on/high/open/true</strong>.</p>
|
||||
<p>Knowing that there are only two states allows Home Assistant to represent these sensors in a better way in the frontend according to their functionality.</p>
|
||||
<p>Binary sensors gather information about the state of devices which have a “digital” return value (either 1 or 0). These can be switches, contacts, pins, etc. These sensors only have two states: <strong>0/off/low/closed/false</strong> and <strong>1/on/high/open/true</strong>. Knowing that there are only two states allows Home Assistant to represent these sensors in a better way in the frontend according to their functionality.</p>
|
||||
<p>The way these sensors are displayed in the frontend can be modified in the <a href="/getting-started/customizing-devices/">customize section</a>. The following device classes are supported for binary sensors:</p>
|
||||
<ul>
|
||||
<li><strong>None</strong>: Generic on/off. This is the default and doesn’t need to be set.</li>
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue