Skip to content

Commit f0e2f36

Browse files
author
committed
Deployed 5b48985 with MkDocs version: 1.6.1
1 parent 67acb8b commit f0e2f36

File tree

4 files changed

+3
-2
lines changed

4 files changed

+3
-2
lines changed

search/search_index.json

Lines changed: 1 addition & 1 deletion
Large diffs are not rendered by default.

services/index.html

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -857,6 +857,7 @@ <h1 id="services">Services<a class="headerlink" href="#services" title="Permanen
857857
<h2 id="data-sources">Data Sources<a class="headerlink" href="#data-sources" title="Permanent link">#</a></h2>
858858
<h3 id="target_timeframesupdate_target_timeframe_data_source">target_timeframes.update_target_timeframe_data_source<a class="headerlink" href="#target_timeframesupdate_target_timeframe_data_source" title="Permanent link">#</a></h3>
859859
<p>Updates the source data for a given targetframe period. This will replace any existing data for the source.</p>
860+
<p>There are a collection of <a href="../blueprints/#data-sources">blueprints</a> available for loading popular data sources.</p>
860861
<table>
861862
<thead>
862863
<tr>

setup/data_source/index.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -670,7 +670,7 @@
670670

671671
<h1 id="data-source">Data source<a class="headerlink" href="#data-source" title="Permanent link">#</a></h1>
672672
<p>Data sources help group target timeframe sensors together to be fed from a central data source. These data sources take a specific shape, but can represent anything. To start configuring target timeframe sensors, you'll need to create an initial data source. This can be done via the <a href="https://my.home-assistant.io/redirect/config_flow_start/?domain=target_timeframe">integration UI</a>.</p>
673-
<p>Once the data source has been created, you'll have the following entities created. You'll then need to use the <a href="../../services/#target_timeframesupdate_target_timeframe_data_source">available service</a> to configure the underlying data. </p>
673+
<p>Once the data source has been created, you'll have the following entities created. You'll then need to use the <a href="../../services/#target_timeframesupdate_target_timeframe_data_source">available service</a> to configure the underlying data. There are also a collection of <a href="../../blueprints/#data-sources">blueprints</a> available for loading popular data sources.</p>
674674
<h2 id="entities">Entities<a class="headerlink" href="#entities" title="Permanent link">#</a></h2>
675675
<h3 id="data-source-last-updated">Data Source Last Updated<a class="headerlink" href="#data-source-last-updated" title="Permanent link">#</a></h3>
676676
<p><code>sensor.target_timeframes_{{DATA_SOURCE_ID}}_data_source_last_updated</code></p>

sitemap.xml.gz

0 Bytes
Binary file not shown.

0 commit comments

Comments
 (0)