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
feat(octopus): broaden saving/free session entity regex to match Power Down/Up rename
Octopus Energy integration v19.0.0 renamed the saving-session and
free-electricity event entities to Power Down and Power Up
(event.octopus_energy_ACCOUNT_ID_octoplus_power_down_events /
..._power_up_events). Both old and new entities remain registered
until January 2027 (ADR-0004), and resolve_arg_re()'s regex
matching against HA state keys is a one-off startup resolution, so
broadening the 're:' alternation to match either name is enough -
no runtime try-new-then-old logic is needed here, unlike the join
service rename in point 3.
Updates the octopus_saving_session/octopus_free_session regex in
apps.yaml (default, coverage test fixture, and all 23 inverter
templates that configure them), plus docs/energy-rates.md to
mention the rename, the entity_registry_enabled_default=False
gotcha, and the January 2027 cutoff.
Part of #4548 (point 2).
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
("octopus_saving_session", saving_pattern, ["event.octopus_energy_a4dd6c5ee_octoplus_power_down_events"], "event.octopus_energy_a4dd6c5ee_octoplus_power_down_events", "new Power Down entity"),
868
+
("octopus_saving_session", saving_pattern, ["event.octopus_energy_a4dd6c5ee_octoplus_power_up_events"], None, "Power Up entity must not match the saving-session/Power Down pattern"),
("octopus_free_session", free_pattern, ["event.octopus_energy_a4dd6c5ee_octoplus_power_up_events"], "event.octopus_energy_a4dd6c5ee_octoplus_power_up_events", "new Power Up entity"),
871
+
("octopus_free_session", free_pattern, ["event.octopus_energy_a4dd6c5ee_octoplus_power_down_events"], None, "Power Down entity must not match the free-session/Power Up pattern"),
("saving_session_join_service_fallback", test_saving_session_join_service_fallback, "Saving session join service fallback test (issue #4548 point 3)", False),
448
449
("saving_session_auto_join_toggle", test_saving_session_auto_join_toggle, "Saving session auto-join toggle test (issue #4120)", False),
449
450
("saving_session_custom_entity_no_rewrite_match", test_saving_session_custom_entity_no_rewrite_match, "Saving session custom entity no rewrite match test (issue #4573)", False),
451
+
("saving_session_entity_regex_power_rename", test_saving_session_entity_regex_power_rename, "Saving/free session entity regex Power Down/Up rename test (issue #4548 point 2)", False),
Copy file name to clipboardExpand all lines: docs/energy-rates.md
+20-8Lines changed: 20 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -143,16 +143,24 @@ if you don't want the standing charge (and only have consumption usage) to be in
143
143
Note that this configuration option to suppress the standing charge only applies if you are using the Octopus Integration from Predbat.
144
144
If you are using the Octopus Energy direct method of Predbat directly connecting to Octopus then the standing charge will always be included in the plan and charts.
145
145
146
-
### Octopus Saving sessions
146
+
### Octopus Saving sessions (Power Down events)
147
147
148
-
Predbat can automatically join you to Octopus saving sessions and plan battery activity for the saving session period to maximise your income.
148
+
Predbat can automatically join you to Octopus saving sessions - now called Power Down events - and plan battery activity for the session period to maximise your income.
149
149
150
-
Note: **You must have signed up to both the Octopus Octoplus and then the Saving Session schemes to benefit from these events**
150
+
Note: **You must have signed up to both the Octopus Octoplus and then the Saving Session/Power Down schemes to benefit from these events**
151
151
152
152
For Predbat to automatically manage Octopus saving sessions the following additional configuration item in `apps.yaml` is used.
153
153
Like the electricity rates, this is set in the `apps.yaml` template to a regular expression that should auto-discover the Octopus Energy integration.
154
154
155
-
- **octopus_saving_session** - Indicates if a saving session is active, should point to the sensor 'event.octopus_energy_ACCOUNT_ID_saving_session_event'.
155
+
- **octopus_saving_session** - Indicates if a saving session/Power Down event is active, should point to the sensor 'event.octopus_energy_ACCOUNT_ID_octoplus_power_down_events'.
Octopus Energy integration v19.0.0 renamed this sensor from `..._octoplus_saving_session_events` to `..._octoplus_power_down_events`. The above pattern matches either name, so existing configurations keep working unchanged.
162
+
The old sensor is retained by the integration until **January 2027**, after which only the Power Down naming will exist. The new sensor ships disabled by default in Home Assistant
163
+
(`entity_registry_enabled_default: False`) - if Predbat's Octopus entity list does not show a Power Down sensor, [enable it in the entity registry first](https://bottlecapdave.github.io/HomeAssistant-OctopusEnergy/faq/#there-are-entities-that-are-disabled-why-are-they-disabled-and-how-do-i-enable-them), otherwise Predbat will keep silently using the old sensor with no visible warning.
156
164
157
165
When a saving session is available it will be automatically joined by Predbat and should then appear as a joined session within the next 30 minutes.
158
166
@@ -180,9 +188,9 @@ If you do not have an export tariff then forced export will not apply and Predba
180
188
If you do not want Predbat to automatically join Octopus saving sessions and manage your battery activity for the session,
181
189
simply delete or comment out the **octopus_saving_session** entry in `apps.yaml`.
182
190
183
-
### Octopus free (power up) events
191
+
### Octopus free (Power Up) events
184
192
185
-
Predbat can automatically detect Octopus free events and adjust your battery plan according. Note that this is derived from external sources, which do not verify your eligibility for free sessions.
193
+
Predbat can automatically detect Octopus free events - now called Power Up events - and adjust your battery plan accordingly. Note that this is derived from external sources, which do not verify your eligibility for free sessions.
186
194
187
195
For Predbat to automatically manage Octopus free sessions the following additional configuration item in apps.yaml is used.
188
196
@@ -194,10 +202,14 @@ Like the electricity rates, this is set in the apps.yaml template to a regular e
Note: **This event may need to be enabled in Home Assistant first** - see [How to Enable Octopus events](https://bottlecapdave.github.io/HomeAssistant-OctopusEnergy/faq/#there-are-entities-that-are-disabled-why-are-they-disabled-and-how-do-i-enable-them)
208
+
Octopus Energy integration v19.0.0 renamed this sensor from `..._octoplus_free_electricity_session_events` to `..._octoplus_power_up_events`. The above pattern matches either name, so existing
209
+
configurations keep working unchanged. The old sensor is retained by the integration until **January 2027**, after which only the Power Up naming will exist.
210
+
211
+
Note: **This event may need to be enabled in Home Assistant first** - the new Power Up sensor ships disabled by default (`entity_registry_enabled_default: False`), so if it is not appearing in
212
+
Predbat's entity list, enable it in the entity registry - see [How to Enable Octopus events](https://bottlecapdave.github.io/HomeAssistant-OctopusEnergy/faq/#there-are-entities-that-are-disabled-why-are-they-disabled-and-how-do-i-enable-them)
201
213
202
214
If you normally increase your house usage during a free session then you can change **input_number.predbat_load_scaling_free** to allow Predbat to assume an energy
203
215
increase in this period. E.g. setting to a value of 1.2 would indicate you will use 20% more energy than normal during this period. (Default is 1.2)
0 commit comments