jeena/home-assistant.github.io
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Site updated at 2016-10-21 07:01:42 UTC

Browse source
This commit is contained in:
Travis CI 2016-10-21 07:01:42 +00:00
parent 97f7ebb495
commit ca7898fa67
25 changed files with 41 additions and 41 deletions
Download patch file Download diff file Expand all files Collapse all files

6
components/light.mqtt_json/index.html
View file

@ -89,7 +89,7 @@
<hr class="divider">
<p>The <code class="highlighter-rouge">mqtt_json</code> light platform let you control a MQTT-enabled light that can receive <a href="https://en.wikipedia.org/wiki/JSON">JSON</a> messages.</p>
<p>The <code class="highlighter-rouge">mqtt_json</code> light platform lets you control a MQTT-enabled light that can receive <a href="https://en.wikipedia.org/wiki/JSON">JSON</a> messages.</p>
<p>This platform supports on/off, brightness, RGB colors, transitions, and short/long flashing. The messages sent to/from the lights look similar to this, omitting fields when they aren’t needed:</p>
@ -106,9 +106,9 @@
</span></code></pre>
</div>
<p>In an ideal scenario, the MQTT device will have a state topic to publish state changes. If these messages are published with the RETAIN flag, the MQTT light will receive an instant state update after subscription and will start with correct state. Otherwise, the initial state of the light will be off.</p>
<p>In an ideal scenario, the MQTT device will have a state topic to publish state changes. If these messages are published with the RETAIN flag, the MQTT light will receive an instant state update after subscription and will start with the correct state. Otherwise, the initial state of the light will be off.</p>
<p>When a state topic is not available, the light will work in optimistic mode. In this mode, the light will immediately change state after every command. Otherwise, the light will wait for state confirmation from device (message from <code class="highlighter-rouge">state_topic</code>).</p>
<p>When a state topic is not available, the light will work in optimistic mode. In this mode, the light will immediately change state after every command. Otherwise, the light will wait for state confirmation from the device (message from <code class="highlighter-rouge">state_topic</code>).</p>
<p>Optimistic mode can be forced, even if state topic is available. Try enabling it if the light is operating incorrectly.</p>

2
components/light.zigbee/index.html
View file

@ -103,7 +103,7 @@
<p>Configuration variables:</p>
<ul>
<li><strong>name</strong> (<em>Required</em>): The name you’ would like to give the light in Home Assistant.</li>
<li><strong>name</strong> (<em>Required</em>): The name you would like to give the light in Home Assistant.</li>
<li><strong>pin</strong> (<em>Required</em>): The number identifying which pin to use.</li>
<li><strong>address</strong> (<em>Optional</em>): The long 64 bit address of the remote ZigBee device whose digital output pin you wouldd like to switch. Do not include this variable if you want to switch the local ZigBee device’s pins.</li>
<li><strong>on_state</strong> (<em>Optional</em>): Either <code class="highlighter-rouge">high</code> (default) or <code class="highlighter-rouge">low</code>, depicting whether the digital output pin is pulled <code class="highlighter-rouge">high</code> or <code class="highlighter-rouge">low</code> when the light is turned on.</li>