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/setup/data_source.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,12 +10,16 @@ The name of the data source. This is for informative purposes.
10
10
11
11
### Id
12
12
13
-
The unique identifier of the data source. This is used by internal events to ensure sensors use the correct data as well as part of the entity name of all related entities. For example, if you were using data provided by Octopus Energy, then this might be `octopus_energy`.
13
+
The unique identifier of the data source. This is used by internal events to ensure sensors use the correct data as well as part of the entity name of all related entities.
14
14
15
-
Once the data source has been created, you'll have the following entities created. You'll then need to use the [available service](../services.md#target_timeframesupdate_target_timeframe_data_source) to configure the underlying data. There are also a collection of [blueprints](../blueprints.md#data-sources) available for loading popular data sources.
15
+
The data source will listen for the [update data source event](../events.md#update-data-source) where the `data source id` matches this id. This event might be raised by other integrations. If this data source is being used for this purpose, then the id will need to be set to a certain value which should be highlighted in that integrations guide.
16
+
17
+
Alternatively, you can use the [available service](../services.md#target_timeframesupdate_target_timeframe_data_source) to configure the underlying data. There is a collection of [blueprints](../blueprints.md#data-sources) available for loading data from popular data sources.
16
18
17
19
## Entities
18
20
21
+
Once the data source has been created, you'll have the following entities created.
Copy file name to clipboardExpand all lines: _docs/setup/rolling_target_timeframe.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
@@ -100,7 +100,7 @@ There may be times that you want the target timeframe sensors to not take into a
100
100
101
101
!!! info
102
102
103
-
This is only available for **continuous** target value sensors in **exact** hours mode.
103
+
This is only available for **continuous** target value sensors.
104
104
105
105
There may be times when the device you're wanting the target value sensor to turn on doesn't have a consistent power draw. You can specify a weighting/multiplier which can be applied to the value of each discovered 30 minute slot. This can be specified in a few different ways. Take the following example weighting/multiplier for a required 2 hours.
Copy file name to clipboardExpand all lines: _docs/setup/target_timeframe.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
@@ -128,7 +128,7 @@ There may be times that you want the target timeframe sensors to not take into a
128
128
129
129
!!! info
130
130
131
-
This is only available for **continuous** target value sensors in **exact** hours mode.
131
+
This is only available for **continuous** target value sensors.
132
132
133
133
There may be times when the device you're wanting the target value sensor to turn on doesn't have a consistent power draw. You can specify a weighting/multiplier which can be applied to the value of each discovered 30 minute slot. This can be specified in a few different ways. Take the following example weighting/multiplier for a required 2 hours.
if (CONFIG_TARGET_MIN_VALUEnotindataordata[CONFIG_TARGET_MIN_VALUE] isNone) and (CONFIG_TARGET_MAX_VALUEnotindataordata[CONFIG_TARGET_MAX_VALUE] isNone):
if (CONFIG_TARGET_MIN_VALUEnotindataordata[CONFIG_TARGET_MIN_VALUE] isNone) and (CONFIG_TARGET_MAX_VALUEnotindataordata[CONFIG_TARGET_MAX_VALUE] isNone):
_LOGGER.debug(f'{context} - New best block discovered {continuous_rates_total} ({continuous_time_periods[0]["start"] iflen(continuous_time_periods) >0elseNone} - {continuous_time_periods[-1]["end"] iflen(continuous_time_periods) >0elseNone})')
213
-
else:
214
-
_LOGGER.debug(f'{context} - Total rates for current block {continuous_rates_total} ({continuous_time_periods[0]["start"] iflen(continuous_time_periods) >0elseNone} - {continuous_time_periods[-1]["end"] iflen(continuous_time_periods) >0elseNone}). Total rates for best block {best_continuous_time_periods_total}')
_LOGGER.debug(f'{context} - New best block discovered {continuous_rates_total} ({continuous_time_periods[0]["start"] iflen(continuous_time_periods) >0elseNone} - {continuous_time_periods[-1]["end"] iflen(continuous_time_periods) >0elseNone})')
213
+
else:
214
+
_LOGGER.debug(f'{context} - Total rates for current block {continuous_rates_total} ({continuous_time_periods[0]["start"] iflen(continuous_time_periods) >0elseNone} - {continuous_time_periods[-1]["end"] iflen(continuous_time_periods) >0elseNone}). Total rates for best block {best_continuous_time_periods_total}')
215
215
216
216
ifbest_continuous_time_periodsisnotNone:
217
217
# Make sure our rates are in ascending order before returning
0 commit comments