You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: components/history/index.html
+40-42
Original file line number
Diff line number
Diff line change
@@ -127,54 +127,52 @@ <h1 class="title indent">
127
127
128
128
<p>Without any <codeclass="highlighter-rouge">include</code> or <codeclass="highlighter-rouge">exclude</code> configuration the history displays graphs for every entity (well that’s not exactly true - for instance <codeclass="highlighter-rouge">hidden</code> entities or <codeclass="highlighter-rouge">scenes</code> are never shown) on a given date. If you are only interested in some of the entities you several options:</p>
129
129
130
-
<ul>
131
-
<li>Define domains and entities to <codeclass="highlighter-rouge">exclude</code> (aka. blacklist). This is convenient when you are basically happy with the information displayed, but just want to remove some entities or domains. Usually these are entities/domains which do not change (like <codeclass="highlighter-rouge">weblink</code>) or rarely change (<codeclass="highlighter-rouge">updater</code> or <codeclass="highlighter-rouge">automation</code>).
132
-
<divclass="language-yaml highlighter-rouge"><preclass="highlight"><code><spanclass="c1"># Example configuration.yaml entry with exclude</span>
130
+
<p>Define domains and entities to <codeclass="highlighter-rouge">exclude</code> (aka. blacklist). This is convenient when you are basically happy with the information displayed, but just want to remove some entities or domains. Usually these are entities/domains which do not change (like <codeclass="highlighter-rouge">weblink</code>) or rarely change (<codeclass="highlighter-rouge">updater</code> or <codeclass="highlighter-rouge">automation</code>).</p>
131
+
132
+
<divclass="language-yaml highlighter-rouge"><preclass="highlight"><code><spanclass="c1"># Example configuration.yaml entry with exclude</span>
<li>Define domains and entities to display by using the <codeclass="highlighter-rouge">include</code> configuration (aka. whitelist). If you have a lot of entities in your system and your <codeclass="highlighter-rouge">exclude</code> lists possibly get very large, it might be better just to define the entities or domains to display.
146
-
<divclass="language-yaml highlighter-rouge"><preclass="highlight"><code><spanclass="c1"># Example configuration.yaml entry with include</span>
143
+
</div>
144
+
145
+
<p>Define domains and entities to display by using the <codeclass="highlighter-rouge">include</code> configuration (aka. whitelist). If you have a lot of entities in your system and your <codeclass="highlighter-rouge">exclude</code> lists possibly get very large, it might be better just to define the entities or domains to display.</p>
146
+
147
+
<divclass="language-yaml highlighter-rouge"><preclass="highlight"><code><spanclass="c1"># Example configuration.yaml entry with include</span>
<li>Use the <codeclass="highlighter-rouge">include</code> list to define the domains/entities to display, and exclude some of them with in the <codeclass="highlighter-rouge">exclude</code> list. This makes sense if you for instance include the <codeclass="highlighter-rouge">sensor</code> domain, but want to exclude some specific sensors. Instead of adding every sensor entity to the <codeclass="highlighter-rouge">include</code><codeclass="highlighter-rouge">entities</code> list just include the <codeclass="highlighter-rouge">sensor</code> domain and exclude the sensor entities you are not interested in.
157
-
```yaml
158
-
<h1>Example configuration.yaml entry with include and exclude</h1>
159
-
<p>history:
160
-
include:
161
-
domains:
162
-
- sensor
163
-
- switch
164
-
- media_player
165
-
exclude:
166
-
entities:</p>
167
-
<ul>
168
-
<li>sensor.last_boot</li>
169
-
<li>sensor.date
170
-
```</li>
171
-
</ul>
172
-
</li>
173
-
</ul>
155
+
</div>
156
+
157
+
<p>Use the <codeclass="highlighter-rouge">include</code> list to define the domains/entities to display, and exclude some of them with in the <codeclass="highlighter-rouge">exclude</code> list. This makes sense if you for instance include the <codeclass="highlighter-rouge">sensor</code> domain, but want to exclude some specific sensors. Instead of adding every sensor entity to the <codeclass="highlighter-rouge">include</code><codeclass="highlighter-rouge">entities</code> list just include the <codeclass="highlighter-rouge">sensor</code> domain and exclude the sensor entities you are not interested in.</p>
158
+
159
+
<divclass="language-yaml highlighter-rouge"><preclass="highlight"><code><spanclass="c1"># Example configuration.yaml entry with include and exclude</span>
<p>When the history component queries the states table it only selects states where the state has changed: <codeclass="highlighter-rouge">WHERE last_changed=last_updated</code></p>
192
+
<p>When the <codeclass="highlighter-rouge">history</code> component queries the states table it only selects states where the state has changed: <codeclass="highlighter-rouge">WHERE last_changed=last_updated</code></p>
195
193
196
194
<h4><aclass="title-link" name="on-dates" href="#on-dates"></a> On dates</h4>
0 commit comments