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: _docs/entities/intelligent.md
+9-1Lines changed: 9 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,6 +30,7 @@ This sensor is used to determine if you're currently in a planned dispatch perio
30
30
|-----------|------|-------------|
31
31
|`planned_dispatches`|`array`| An array of the dispatches that are currently planned by Octopus Energy. |
32
32
|`completed_dispatches`|`array`| An array of the dispatches that have been completed by Octopus Energy. This will only store up to the last 3 days worth of completed dispatches. |
33
+
|`started_dispatches`|`array`| An array of the dispatches that have been planned by Octopus Energy and upon API refresh are still planned when the current 30 minute period started and is not in a boosting state. A planned dispatch will be added one 30 minute period at a time. This will only store up to the last 3 days worth of started dispatches. This is used to determine historic off peak rates. For example if you have a planned dispatch of `2025-04-01T10:00:00`-`2025-04-01T11:00:00`, at `2025-04-01T10:01:00` if the planned dispatch is still available the period of `2025-04-01T10:00:00`-`2025-04-01T10:30:00` will be added. |
33
34
|`provider`|`string`| The provider of the intelligent features |
34
35
|`vehicle_battery_size_in_kwh`|`float`| The size of the target vehicle battery in kWh. |
35
36
|`charge_point_power_in_kw`|`float`| The power of the charge point battery in kW. |
@@ -45,9 +46,16 @@ Each item in `planned_dispatch` or `completed_dispatches` have the following att
45
46
|`start`|`datetime`| The start date/time of the dispatch |
46
47
|`end`|`datetime`| The end date/time of the dispatch |
47
48
|`charge_in_kwh`|`float`| The amount to be charged within the dispatch period. |
48
-
|`source`|`string`| Determines what has caused the dispatch to be generated. Will be `smart-charge` or `bump-charge`. |
49
+
|`source`|`string`| Determines what has caused the dispatch to be generated. Will be `smart-charge`, `bump-charge` or None. |
49
50
|`location`|`string`| The location of the smart charge |
50
51
52
+
Each item in `started_dispatch` have the following attributes
53
+
54
+
| Attribute | Type | Description |
55
+
|-----------|------|-------------|
56
+
|`start`|`datetime`| The start date/time of the dispatch |
57
+
|`end`|`datetime`| The end date/time of the dispatch |
58
+
51
59
!!! info
52
60
53
61
You can use the [data_last_retrieved sensor](./diagnostics.md#intelligent-dispatches-data-last-retrieved) to determine when the underlying data was last retrieved from the OE servers.
Copy file name to clipboardExpand all lines: _docs/services.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -339,6 +339,10 @@ This service is only available for the following sensors
339
339
340
340
Due to limitations with Home Assistant entities, this service will only refresh data for the associated statistic ids used for the recommended approach in the [energy dashboard](./setup/energy_dashboard.md#previous-day-consumption). This will not update the history of the entities themselves.
341
341
342
+
!!! warn
343
+
344
+
If you are on intelligent, the cost data will not be correct for charges outside of the normal off peak times. This is because this data isn't available.
345
+
342
346
### octopus_energy.register_rate_weightings
343
347
344
348
Allows you to configure weightings against rates at given times using factors external to the integration. These are applied when calculating [target rates](./setup/target_rate.md#external-rate-weightings) or [rolling target rates](./setup/rolling_target_rate.md#external-rate-weightings).
Copy file name to clipboardExpand all lines: _docs/setup/account.md
+7-9Lines changed: 7 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,25 +53,23 @@ By default, intelligent dispatches are retrieved [periodically](../faq.md#how-of
53
53
54
54
## Intelligent rates mode
55
55
56
-
If you are on an intelligent tariff then it's possible for you to get cheaper rates outside of your normal off peak periods if Octopus Energy schedules the charges and your car accepts the charges. The rate information provides by Octopus Energy doesn't take these periods into account, so the integration has to use the pending/completed dispatch information to adjust the rates appropriately. Due to the quality of the available data, this _can_ be off sometimes. This feature allows how the rate information is adjusted in these scenarios.
56
+
If you are on an intelligent tariff then it's possible for you to get cheaper rates outside of your normal off peak periods if Octopus Energy schedules the charges and your car accepts the charges. The rate information provides by Octopus Energy doesn't take these periods into account, so the integration has to use the planned/completed dispatch information to adjust the rates appropriately. Due to the quality of the available data, this _can_ be off sometimes. This feature allows how the rate information is adjusted in these scenarios.
57
57
58
-
### Pending and completed dispatches will turn into off peak rates
58
+
### Planned and started dispatches will turn into off peak rates
59
59
60
-
This is the default behaviour. In this scenario, all pending dispatches will be assumed to be converted into successful off peak charges by the car and therefore all rates during these periods will be converted into the off peak rate. This will be indicated by the `is_intelligent_adjusted` property. This is useful when planning other devices to turn on in the future during these cheap periods (e.g. by using a [target rate sensor](./target_rate.md)).
60
+
This is the default behaviour. In this scenario, all planned dispatches will be assumed to be converted into successful off peak charges by the car and therefore all rates during these periods will be converted into the off peak rate. This will be indicated by the `is_intelligent_adjusted` property. This is useful when planning other devices to turn on in the future during these cheap periods (e.g. by using a [target rate sensor](./target_rate.md)).
61
61
62
62
!!! warning
63
63
64
-
One side effect of this is around cost sensors, where if a pending dispatch does not turn into a completed dispatch, the cost sensor can increase in value when the pending dispatch is removed.
64
+
One side effect of this is around cost sensors, where if a planned dispatch does not turn into a started dispatch, the cost sensor can increase in value when the planned dispatch is removed.
65
65
66
-
### Only completed dispatches will turn into off peak rates
66
+
### Only started dispatches will turn into off peak rates
67
67
68
-
In this scenario only completed dispatches will be taken into account for adjustments meaning all rates during only completed dispatch periods will be converted into the off peak rate. This will be indicated by the `is_intelligent_adjusted` property. This means no future planning can be made to take advantage of these cheap periods by rates alone.
68
+
In this scenario only started dispatches will be taken into account for adjustments meaning all rates during only started dispatch periods will be converted into the off peak rate. This will be indicated by the `is_intelligent_adjusted` property. This means no future planning can be made to take advantage of these cheap periods by rates alone.
69
69
70
70
!!! warning
71
71
72
-
One side effect of this is around cost sensors, where when a completed dispatch arrives the cost sensor will decrease in value.
73
-
74
-
There have also been reports of some successful charges not resolving into completed dispatches.
72
+
One side effect of this is around cost sensors, where when a started dispatch arrives the cost sensor will decrease in value.
selector.SelectOptionDict(value=CONFIG_MAIN_INTELLIGENT_RATE_MODE_PENDING_AND_COMPLETED_DISPATCHES, label="Pending and completed dispatches will turn into off peak rates"),
844
-
selector.SelectOptionDict(value=CONFIG_MAIN_INTELLIGENT_RATE_MODE_COMPLETED_DISPATCHES_ONLY, label="Only completed dispatches will turn into off peak rates"),
843
+
selector.SelectOptionDict(value=CONFIG_MAIN_INTELLIGENT_RATE_MODE_PENDING_AND_STARTED_DISPATCHES, label="Planned and started dispatches will turn into off peak rates"),
844
+
selector.SelectOptionDict(value=CONFIG_MAIN_INTELLIGENT_RATE_MODE_STARTED_DISPATCHES_ONLY, label="Only stared dispatches will turn into off peak rates"),
selector.SelectOptionDict(value=CONFIG_MAIN_INTELLIGENT_RATE_MODE_PENDING_AND_COMPLETED_DISPATCHES, label="Pending and completed dispatches will turn into off peak rates"),
206
-
selector.SelectOptionDict(value=CONFIG_MAIN_INTELLIGENT_RATE_MODE_COMPLETED_DISPATCHES_ONLY, label="Only completed dispatches will turn into off peak rates"),
205
+
selector.SelectOptionDict(value=CONFIG_MAIN_INTELLIGENT_RATE_MODE_PENDING_AND_STARTED_DISPATCHES, label="Planned and started dispatches will turn into off peak rates"),
206
+
selector.SelectOptionDict(value=CONFIG_MAIN_INTELLIGENT_RATE_MODE_STARTED_DISPATCHES_ONLY, label="Only started dispatches will turn into off peak rates"),
0 commit comments