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

Site updated at 2017-10-24 07:34:37 UTC

Browse source
This commit is contained in:
Travis CI 2017-10-24 07:34:38 +00:00
parent 79915af7fb
commit 7126740507
166 changed files with 484 additions and 208 deletions
Download patch file Download diff file Expand all files Collapse all files

2
components/binary_sensor.bayesian/index.html
View file

@ -97,7 +97,7 @@
<li><strong>entity_id</strong> (<em>Required</em>): Name of the entity to monitor.</li>
<li><strong>prob_given_true</strong> (<em>Required</em>): The probability of the observation occurring, given the event is <code class="highlighter-rouge">true</code>.</li>
<li><strong>prob_given_false</strong> (<em>Optional</em>): The probability of the observation occurring, given the event is <code class="highlighter-rouge">false</code> can be set as well. If <code class="highlighter-rouge">prob_given_false</code> is not set, it will default to <code class="highlighter-rouge">1 - prob_given_true</code>.</li>
<li><strong>platform</strong> (<em>Required</em>): The only supported observation platforms are <code class="highlighter-rouge">state</code> and <code class="highlighter-rouge">numeric_state</code>, which are modeled after their corresponding triggers for automations, requiring <code class="highlighter-rouge">before</code> and/or <code class="highlighter-rouge">after</code> instead of <code class="highlighter-rouge">to_state</code>.</li>
<li><strong>platform</strong> (<em>Required</em>): The only supported observation platforms are <code class="highlighter-rouge">state</code> and <code class="highlighter-rouge">numeric_state</code>, which are modeled after their corresponding triggers for automations, requiring <code class="highlighter-rouge">below</code> and/or <code class="highlighter-rouge">above</code> instead of <code class="highlighter-rouge">to_state</code>.</li>
<li><strong>to_state</strong> (<em>Required</em>): The target state.</li>
</ul>
</li>

8
components/sensor.min_max/index.html
View file

@ -74,16 +74,16 @@
</h1>
</header>
<hr class="divider">
<p>The <code class="highlighter-rouge">min_max</code> sensor platform is consuming the state from other sensors and determine the minimum, maximum, and the mean of the collected states. The sensor will always show you the highest/lowest value which was received from your all monitored sensors. If you have spikes in your values, it’s recommended filter/equalize your values with a <a href="/components/sensor.statistics/">statistics sensor</a> first.</p>
<p>It’s an alternative to the <a href="/components/sensor.template/">template sensor</a>’s <code class="highlighter-rouge">value_template:</code> to get the average of multiple sensors.</p>
<p>The <code class="highlighter-rouge">min_max</code> sensor platform consumes the state from other sensors to determine the minimum, maximum, and the mean of the collected states. The sensor will always show you the lowest/highest value which was received from all monitored sensors. If you have spikes in your values, it’s recommended to filter/equalize your values with a <a href="/components/sensor.statistics/">statistics sensor</a> first.</p>
<p>This sensor is an alternative to the <a href="/components/sensor.template/">template sensor</a>’s <code class="highlighter-rouge">value_template:</code> to get the average of multiple sensors.</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="pi">{{</span> <span class="nv">((float(states.sensor.kitchen_temperature.state) +</span>
<span class="nv">float(states.sensor.living_room_temperature.state) +</span>
<span class="nv">float(states.sensor.office_temperature.state)) / 3) | round(2)</span>
<span class="pi">}}</span>
</code></pre>
</div>
<p>Sensors with an unknown state will be ignored in the calculation. If the unit of measurement of the sensors differs, the <code class="highlighter-rouge">min_max</code> sensor will go to an error state where the value is <code class="highlighter-rouge">UNKNOWN</code> and the unit of measurement is <code class="highlighter-rouge">ERR</code>.</p>
<p>To enable the minimum/maximum sensor, add the following lines to your <code class="highlighter-rouge">configuration.yaml</code>:</p>
<p>Sensors with an unknown state will be ignored in the calculation. If the unit of measurement of the sensors differs, the <code class="highlighter-rouge">min_max</code> sensor will go to an error state where the value is <code class="highlighter-rouge">UNKNOWN</code> and unit of measurement is <code class="highlighter-rouge">ERR</code>.</p>
<p>To enable the <code class="highlighter-rouge">min_max</code> sensor, add 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">sensor</span><span class="pi">:</span>
<span class="pi">-</span> <span class="s">platform</span><span class="pi">:</span> <span class="s">min_max</span>

2
components/sensor.statistics/index.html
View file

@ -74,7 +74,7 @@
</h1>
</header>
<hr class="divider">
<p>The <code class="highlighter-rouge">statistics</code> sensor platform is consuming the state from other sensors. Beside the maximal and the minimal value also the total, the mean, the median, the variance, and the standard deviation are as attributes available. If it’s a binary sensor then only the state changes are counted.</p>
<p>The <code class="highlighter-rouge">statistics</code> sensor platform consumes the state from other sensors. Besides the maximum and the minimum values, the total, mean, median, variance and the standard deviation are also available as attributes. If it’s a binary sensor then only state changes are counted.</p>
<p>If you are running the <a href="/components/recorder/">recorder</a> component, on startup the data is read from the database. So after a restart of the platform, you will immediately have data available. If you’re using the <a href="/components/history/">history</a> component, this will automatically also start the recoder component on startup.
If you are <em>not</em> running the <code class="highlighter-rouge">recorder</code> component, it can take time till the sensor starts to work because a couple of attributes need more than one value to do the calculation.</p>
<p>To enable the statistics sensor, add the following lines to your <code class="highlighter-rouge">configuration.yaml</code>:</p>