docs: Fixed docs

Author: BottlecapDave

_docs/services.md

@@ -10,15 +10,24 @@ Updates the source data for a given targetframe period. This will replace any ex
 
 | Attribute                | Optional | Description                                                                                                           |
 | ------------------------ | -------- | --------------------------------------------------------------------------------------------------------------------- |
-| `target.entity_id`       | `no`     | The name of the [](./setup/data_source.md#last-updated) sensor whose configuration is to be updated.                                                   |
-| `data.target_hours`      | `yes`    | The optional number of hours the target timeframe sensor should come on during a 24 hour period. Must be divisible by 0.5. |
-| `data.target_start_time` | `yes`    | The optional time the evaluation period should start. Must be in the format of `HH:MM`.                               |
-| `data.target_end_time`   | `yes`    | The optional time the evaluation period should end. Must be in the format of `HH:MM`.                                 |
-| `data.target_offset`     | `yes`    | The optional offset to apply to the target timeframe when it starts. Must be in the format `(+/-)HH:MM:SS`.                |
-| `data.target_minimum_value`     | `yes`    | The optional minimum timeframe the selected timeframes should not go below. |
-| `data.target_maximum_value`     | `yes`    | The optional maximum timeframe the selected timeframes should not go above. |
-| `data.target_weighting`     | `yes`    | The optional weighting that should be applied to the selected timeframes. |
-| `data.persist_changes` | `yes` | Determines if the changes should be persisted to the original configuration or should be temporary and reset upon integration reload. If not supplied, then the changes are temporary |
+| `target.entity_id`       | `no`     | The name of the [data source last updated](./setup/data_source.md#data-source-last-updated) sensor whose underlying data is to be updated.                                                   |
+| `data.data`      | `no`    | The collection of data to update the data source with. This will override any previous data. For the target rate sensors to work properly, you should target having data for the whole of yesterday, today and tomorrow (e.g. if today is 2025-01-04, you should aim to have data from 2025-01-03T00:00:00 to 2025-01-06T00:00:00).
+
+The structure of the data should match the following
+
+```
+[
+  {
+    "start": "2025-01-01T00:00:00Z",
+    "end": "2025-01-01T00:30:00Z",
+    "value": 0.1,
+    "metadata": {
+      // Any additional metadata that might describe how the value was created
+    }
+  },
+  ...
+]
+```
 
 #### Automations
 

_docs/setup/rolling_target_timeframe.md

@@ -2,7 +2,7 @@
 
 After you've configured your [data source](./data_source.md), you'll be able to configure rolling target timeframe sensors. These are configured as sub configuration options associated with your data source. Select `Rolling Target timeframe` from the sub menu.
 
-These sensors calculate the lowest continuous or intermittent values within the next available `x` hours, where `x` is configurable via the sensor, and turn on when these periods are active. If you are targeting an export meter, then the sensors will calculate the highest continuous or intermittent values within the next available `x` hours and turn on when these periods are active. If you are wanting to evaluate on a fixed basis (e.g. every 24 hours), you might be interested in the [standard target timeframe sensors](./target_rate.md)
+These sensors calculate the lowest continuous or intermittent values within the next available `x` hours, where `x` is configurable via the sensor, and turn on when these periods are active. If you are targeting an export meter, then the sensors will calculate the highest continuous or intermittent values within the next available `x` hours and turn on when these periods are active. If you are wanting to evaluate on a fixed basis (e.g. every 24 hours), you might be interested in the [standard target timeframe sensors](./target_timeframe.md)
 
 These sensors can then be used in automations to turn on/off devices that save you (and the planet) energy and money. You can go through this flow as many times as you need rolling target timeframe sensors.
 
@@ -42,7 +42,7 @@ This is the number of hours to look ahead for the best time periods. This will i
 
 ### Evaluation mode
 
-Because the time frame that is being evaluated is currently moving, you might want to set how/when the target times are evaluated in order to make the selected times more or less dynamic.
+Because the time frame that is being evaluated could change at different frequencies depending on the source, you might want to set how/when the target times are evaluated in order to make the selected times more or less dynamic.
 
 #### All existing target timeframes are in the past
 
@@ -144,4 +144,4 @@ The following attributes are available on each sensor
 
 ## Services
 
-There are services available associated with target timeframe sensors. Please review them in the [services doc](../services.md#rolling-target-values).
+There are services available associated with target timeframe sensors. Please review them in the [services doc](../services.md#rolling-target-timeframes).

_docs/setup/target_timeframe.md

@@ -2,7 +2,7 @@
 
 After you've configured your [data source](./data_source.md), you'll be able to configure rolling target timeframe sensors. These are configured as sub configuration options associated with your data source. Select `Target timeframe` from the sub menu.
 
-These sensors calculate the lowest continuous or intermittent values **within a 24 hour period** and turn on when these periods are active. If you are targeting an export meter, then the sensors will calculate the highest continuous or intermittent values **within a 24 hour period** and turn on when these periods are active. If you are wanting to evaluate on a rolling basis, you might be interested in the [rolling target value sensors](./rolling_target_value.md)
+These sensors calculate the lowest continuous or intermittent values **within a 24 hour period** and turn on when these periods are active. If you are targeting an export meter, then the sensors will calculate the highest continuous or intermittent values **within a 24 hour period** and turn on when these periods are active. If you are wanting to evaluate on a rolling basis, you might be interested in the [rolling target value sensors](./rolling_target_timeframe.md)
 
 These sensors can then be used in automations to turn on/off devices that save you (and the planet) energy and money. You can go through this flow as many times as you need target value sensors.
 
@@ -52,7 +52,7 @@ For instance if the lowest period is between `2023-01-01T00:30` and `2023-01-01T
 
 ### Evaluation mode
 
-Because the time frame that is being evaluated could have external factors change the underlying data (e.g. if you're using [external value weightings](#external-value-weightings)), you might want to set how/when the target times are evaluated in order to make the selected times more or less dynamic.
+Because the time frame that is being evaluated could change at different frequencies depending on the source, you might want to set how/when the target times are evaluated in order to make the selected times more or less dynamic.
 
 #### All existing target values are in the past
 
@@ -157,7 +157,7 @@ The following attributes are available on each sensor
 
 ## Services
 
-There are services available associated with target value sensors. Please review them in the [services doc](../services.md#target-values).
+There are services available associated with target value sensors. Please review them in the [services doc](../services.md#target-timeframes).
 
 ## Examples