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/octoplus.md
+14-3Lines changed: 14 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,6 +41,9 @@ Binary sensor to indicate if a saving session that the account has joined is act
41
41
42
42
The state of this sensor states when the saving session events were last updated. The attributes of this sensor exposes the joined and available saving sessions.
43
43
44
+
!!! note
45
+
This will only be available if you have enrolled into Octoplus. Once enrolled, reload the integration to gain access to this sensor.
46
+
44
47
| Attribute | Type | Description |
45
48
|-----------|------|-------------|
46
49
|`available_events`|`array`| The collection of saving session events that you haven't joined |
@@ -76,6 +79,9 @@ This will indicate the baseline consumption that you need to be below for the cu
76
79
77
80
You can use the [current period consumption](./electricity.md#current-interval-accumulative-consumption) sensor (if available) to see how on track you are.
78
81
82
+
!!! note
83
+
This will only be available if you have enrolled into Octoplus. Once enrolled, reload the integration to gain access to this sensor.
84
+
79
85
!!! note
80
86
This is [disabled by default](../faq.md#there-are-entities-that-are-disabled-why-are-they-disabled-and-how-do-i-enable-them).
81
87
@@ -119,9 +125,8 @@ Each item within `baselines` consists of the following attributes
119
125
120
126
Binary sensor to indicate if a free electricity session is active.
121
127
122
-
!!! warning
123
-
124
-
This sensor uses public information supplied by https://github.com/BottlecapDave/OctopusEnergyApi. However it is only applicable to your account if you have joined Octoplus and have signed up to [free electricity sessions](https://octopus.energy/free-electricity/). Once enrolled into Octoplus, reload the integration to gain access to this sensor.
128
+
!!! note
129
+
This will only be available if you have enrolled into Octoplus. Once enrolled, reload the integration to gain access to this sensor. This is only applicable if you have signed up to [free electricity sessions](https://octopus.energy/free-electricity/). This sensor uses public information supplied by https://github.com/BottlecapDave/OctopusEnergyApi.
125
130
126
131
!!! note
127
132
This is [disabled by default](../faq.md#there-are-entities-that-are-disabled-why-are-they-disabled-and-how-do-i-enable-them).
@@ -145,6 +150,9 @@ Binary sensor to indicate if a free electricity session is active.
145
150
146
151
The state of this sensor states when the free electricity session events were last updated. The attributes of this sensor exposes the past, present and future free electricity sessions.
147
152
153
+
!!! note
154
+
This will only be available if you have enrolled into Octoplus. Once enrolled, reload the integration to gain access to this sensor. This is only applicable if you have signed up to [free electricity sessions](https://octopus.energy/free-electricity/). This sensor uses public information supplied by https://github.com/BottlecapDave/OctopusEnergyApi.
155
+
148
156
!!! note
149
157
This is [disabled by default](../faq.md#there-are-entities-that-are-disabled-why-are-they-disabled-and-how-do-i-enable-them).
150
158
@@ -169,6 +177,9 @@ This will indicate the baseline consumption that you need to be above for the cu
169
177
170
178
You can use the [current period consumption](./electricity.md#current-interval-accumulative-consumption) sensor (if available) to see how on track you are.
171
179
180
+
!!! note
181
+
This will only be available if you have enrolled into Octoplus. Once enrolled, reload the integration to gain access to this sensor. This is only applicable if you have signed up to [free electricity sessions](https://octopus.energy/free-electricity/). This sensor uses public information supplied by https://github.com/BottlecapDave/OctopusEnergyApi.
182
+
172
183
!!! note
173
184
This is [disabled by default](../faq.md#there-are-entities-that-are-disabled-why-are-they-disabled-and-how-do-i-enable-them).
Copy file name to clipboardExpand all lines: _docs/faq.md
+13Lines changed: 13 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -182,6 +182,19 @@ Cost sensors are calculated by multiplying the consumption by the rate for each
182
182
183
183
Each half hour block has it's consumption rounded to the nearest 0.01kwh before multiplying by the rate, which is rounded to the nearest penny. The rounding method used is rounding half to even, where numbers ending in 5 are rounded up or down, towards the nearest even hundredth decimal place. As a result, 0.015 would be rounded up to 0.02, while 0.025 is rounded down to 0.02. This is based on [Octopus Energy API documentation](https://developer.octopus.energy/rest/guides/endpoints)
184
184
185
+
## I'm having issues with a sensor. Is there any way I can see the attributes for a certain point in time?
186
+
187
+
The majority of attributes for entities are stored in the database for a short amount of time (default is around 10 days). Unfortunately, the only way of obtaining historic attributes is via the database. This can be done via the [SQLite Web Add-On](https://my.home-assistant.io/redirect/supervisor_addon/?addon=a0d7b954_sqlite-web), where the following SQL query can be executed. You'll need to change the target entity id from `binary_sensor.octopus_energy_xxx_intelligent_dispatching` to the one you want to target.
join state_attributes on states.attributes_id = state_attributes.attributes_id
193
+
join states_meta on states_meta.metadata_id = states.metadata_id
194
+
where states_meta.entity_id = 'binary_sensor.octopus_energy_xxx_intelligent_dispatching'
195
+
order by last_updated_ts desc
196
+
```
197
+
185
198
## Do you support older versions of the integration?
186
199
187
200
Due to time constraints, I will only ever support the latest version of the integration. If you have an issue with an older version of the integration, my initial answer will always be to update to the latest version. This might be different to what HACS is reporting if you are not on the minimum supported Home Assistant version (which is highlighted in each release's changelog).
Copy file name to clipboardExpand all lines: _docs/repairs/no_active_tariff.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,8 @@
3
3
If you receive this repair notice it means that no active tariff was found for one or more of your meters. There are a few reasons why this might be the case.
4
4
5
5
1. You are in the middle of switching tariffs. There can sometimes be a gap in your tariff information coming through when your existing tariff ends and your new tariff begins.
6
-
2. You are new to OE and your tariff hasn't begun yet. Once your tariff starts, the integration will pick it up and should start working.
7
-
3. There is a configuration issue with your account. In this scenario, you'll need to contact Octopus Energy support to get this rectified.
6
+
2. You have had a meter swap. When your meter is replaced, it can take time for systems to fully update, leaving a gap in tariff information until this is complete.
7
+
3. You are new to OE and your tariff hasn't begun yet. Once your tariff starts, the integration will pick it up and should start working.
8
+
4. There is a configuration issue with your account. In this scenario, you'll need to contact Octopus Energy support to get this rectified.
8
9
9
-
All of the above scenarios can be confirmed within your [diagnostic data](../faq.md#ive-been-asked-for-my-meter-information-in-a-bug-request-how-do-i-obtain-this). This will contain your account data including your meters. Under each of your meters, you'll have a list of tariff agreements. For each meter, you should have an agreement with a start date in the past and an end date either in the future or with no end date.
10
+
All of the above scenarios can be confirmed within your [diagnostic data](../faq.md#ive-been-asked-for-my-meter-information-in-a-bug-request-how-do-i-obtain-this). This will contain your account data including your meters. Under each of your meters, you'll have a list of tariff agreements. For each meter, you should have an agreement with a start date in the past and an end date either in the future or with no end date.
Copy file name to clipboardExpand all lines: _docs/setup/cost_tracker.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -88,6 +88,7 @@ Each item within the `tracked_changes` and `untracked_changes` have the followin
88
88
|`rate`|`float`| The rate the consumption is charged at. This is in pounds and pence (e.g. 1.01 = £1.01) |
89
89
|`consumption`|`float`| The consumption value of the specified period. This will be in `kwh`. |
90
90
|`cost`|`float`| The cost of the consumption at the specified rate. This is in pounds and pence (e.g. 1.01 = £1.01) |
91
+
|`cost_raw`|`float`| The raw cost of the consumption at the specified rate. This is in pounds and pence, but not rounded. This is to account for low cost devices |
if (consumption_dataisnotNoneandlen(consumption_data) >=minimum_consumption_recordsandrate_dataisnotNoneandlen(rate_data) >0andstanding_chargeisnotNone):
_LOGGER.debug(f'Skipping consumption and cost calculation as last reset has not changed - last_reset: {last_reset}; consumption start: {sorted_consumption_data[0]["start"]}')
238
+
else:
239
+
_LOGGER.debug(f'Skipping consumption and cost calculation due to lack of data; consumption: {len(consumption_data) ifconsumption_dataisnotNoneelse0}; rates: {len(rate_data) ifrate_dataisnotNoneelse0}; standing_charge: {standing_charge}')
0 commit comments