Deployed 89cb665 with MkDocs version: 1.6.1

faq/index.html

@@ -695,7 +695,8 @@
 
 <h1 id="faq">FAQ<a class="headerlink" href="#faq" title="Permanent link">#</a></h1>
 <h2 id="ive-updated-the-configuration-of-one-of-my-target-timeframe-sensors-but-its-not-updating-is-there-something-wrong">I've updated the configuration of one of my target timeframe sensors but it's not updating. Is there something wrong?<a class="headerlink" href="#ive-updated-the-configuration-of-one-of-my-target-timeframe-sensors-but-its-not-updating-is-there-something-wrong" title="Permanent link">#</a></h2>
-<p>For some reason when you update the configuration via the integration page, the associated entities don't update. You'll need to reload the parent entry to get the configuration to take effect. This is something I'm currently investigating.</p>
+<p>This was an issue before Home Assistant 2025.09. If you update to 2025.09 or later, this should no longer be an issue.</p>
+<p>If you are on a version before Home Assistant 2025.09, then you'll need to reload the parent entry to get the configuration to take effect.</p>
 <h2 id="ive-setup-a-target-timeframe-with-the-default-time-period-0000-0000-or-a-rolling-target-timeframe-looking-ahead-for-24-hours-but-its-not-updating-is-something-broken">I've setup a target timeframe with the default time period (00:00-00:00) or a rolling target timeframe looking ahead for 24 hours but it's not updating. Is something broken?<a class="headerlink" href="#ive-setup-a-target-timeframe-with-the-default-time-period-0000-0000-or-a-rolling-target-timeframe-looking-ahead-for-24-hours-but-its-not-updating-is-something-broken" title="Permanent link">#</a></h2>
 <p>By default, the target timeframe sensors require the supporting data for the specified time periods to be available in order to be calculate. For example if it was <code>00:00</code> on <code>1/12/2025</code>, then the standard target timeframe would require data for <em>at least</em> between <code>2025-12-01T00:00</code> and <code>2025-12-01T00:00</code>. If this is not the case, then the sensor will not be evaluated. This is made clearer by the <code>values_incomplete</code> attributes of the <a href="../setup/target_timeframe/#attributes">target timeframe</a> and <a href="../setup/rolling_target_timeframe/#attributes">rolling target timeframe</a>.</p>
 <p>For some data sources, this might cause issues due to the data available (e.g. When you're on the Agile tariff of <a href="../blueprints/#octopus-energy">Octopus Energy UK</a> where data is available in advanced up to <code>23:00</code>).</p>