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: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
Target timeframes was a feature that has been extracted out of the [Octopus Energy integration](https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy). The idea is you can configure binary sensors that will find and turn on during the most optimal time periods based on external data sources, targeting either the lowest or highest values. What these values represent can be anything. In the original integration, the values represented cost of energy, and so the cheapest periods were discovered. But it could represent other things like
4
4
5
-
*Temperature to turn on sprinklers during the hottest times of the day
5
+
*Energy prices to turn on devices when cost is the cheapest
6
6
* Carbon emissions to turn on devices when renewables on the grid are at their highest
7
7
* Solar generation to turn on devices when the most energy is being generated.
Copy file name to clipboardExpand all lines: _docs/blueprints/target_timeframes_octopus_energy_carbon_intensity.yaml
+26-19Lines changed: 26 additions & 19 deletions
Original file line number
Diff line number
Diff line change
@@ -14,16 +14,6 @@ blueprint:
14
14
- sensor
15
15
integration: target_timeframes
16
16
multiple: false
17
-
octopus_energy_previous_day_rates:
18
-
name: Previous day rates
19
-
description: The previous day rates event sensor supplied by Octopus Energy. More information can be found at https://bottlecapdave.github.io/HomeAssistant-OctopusEnergy/entities/electricity/#previous-day-rates.
20
-
selector:
21
-
entity:
22
-
filter:
23
-
- domain:
24
-
- event
25
-
integration: octopus_energy
26
-
multiple: false
27
17
octopus_energy_current_day_rates:
28
18
name: Current day rates
29
19
description: The current day rates event sensor supplied by Octopus Energy. More information can be found at https://bottlecapdave.github.io/HomeAssistant-OctopusEnergy/entities/electricity/#current-day-rates.
@@ -61,6 +51,13 @@ blueprint:
61
51
selector:
62
52
number:
63
53
mode: box
54
+
octopus_energy_weighting:
55
+
name: Octopus Energy rate weighting
56
+
description: The weighting to apply to the Octopus Energy rates when calculating the final value for the period.
57
+
default: 0.7
58
+
selector:
59
+
number:
60
+
mode: box
64
61
carbon_intensity_current_day_rates:
65
62
name: Current day rates
66
63
description: The current day rates event sensor supplied by Carbon Intensity. More information can be found at https://bottlecapdave.github.io/HomeAssistant-CarbonIntensity/entities/#current-day-rates.
@@ -81,20 +78,26 @@ blueprint:
81
78
- event
82
79
integration: carbon_intensity
83
80
multiple: false
81
+
carbon_intensity_weighting:
82
+
name: Carbon Intensity forecast weighting
83
+
description: The weighting to apply to the Carbon Intensity forecast when calculating the final value for the period.
Copy file name to clipboardExpand all lines: _docs/index.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
Target timeframes was a feature that has been extracted out of the [Octopus Energy integration](https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy). The idea is you can configure binary sensors that will find and turn on during the most optimal time periods based on external data sources, targeting either the lowest or highest values. What these values represent can be anything. In the original integration, the values represented cost of energy, and so the cheapest periods were discovered. But it could represent other things like
4
4
5
-
*Temperature to turn on sprinklers during the hottest times of the day
5
+
*Energy prices to turn on devices when cost is the cheapest
6
6
* Carbon emissions to turn on devices when renewables on the grid are at their highest
7
7
* Solar generation to turn on devices when the most energy is being generated.
Copy file name to clipboardExpand all lines: _docs/services.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,6 +54,10 @@ The following services are available if you have set up at least one [target tim
54
54
55
55
For updating a given [target timeframe's](./setup/target_timeframe.md) config. This allows you to change target timeframes sensors dynamically based on other outside criteria (e.g. you need to adjust the target hours to top up home batteries).
56
56
57
+
!!! warning
58
+
59
+
This will cause the sensor to re-evaluate the target times, which may result in different times being picked.
|`target.entity_id`|`no`| The name of the target sensor whose configuration is to be updated. |
@@ -126,6 +130,10 @@ The following services are available if you have set up at least one [rolling ta
126
130
127
131
For updating a given [rolling target timeframe's](./setup/rolling_target_timeframe.md) config. This allows you to change rolling target timeframes sensors dynamically based on other outside criteria (e.g. you need to adjust the target hours to top up home batteries).
128
132
133
+
!!! warning
134
+
135
+
This will cause the sensor to re-evaluate the target times, which may result in different times being picked.
0 commit comments