Skip to content

Conversation

@BottlecapDave
Copy link
Owner

No description provided.

reedy and others added 30 commits August 25, 2025 03:39
….5 hours dev time)

BREAKING CHANGE: Due to repair issue key structure changing, you may receive repair notices that you have previously ignored. You will need to ignore them again to hide them.
…on' (30 minutes dev time)

BREAKING CHANGE: If you have automations that look at the heat pump water heater, then you'll need to update any reference to the state of 'on' to 'electric'
BREAKING CHANGE: If you are using blueprints provided by this integration, you will need to re-import them and potentially update automations in order to continue receiving updates.
BREAKING CHANGE: Intelligent device related entity ids have been changed from including the account id to including the device id. This is to support multiple EVs as well as other future intelligent devices OE might want to add in the future (e.g. Snug)

is_dispatching entity will now only show when the car is within a scheduled dispatching period. It will no longer turn on when within the standard off peak period. This is because the naming and behaviour was confusing with the name (on when it's not dispatching) and behavior in conjunction with the off peak sensor (off peak not turning on when in an ad-hoc off peak period). See https://bottlecapdave.github.io/HomeAssistant-OctopusEnergy/architecture_decision_records/0002_intelligent_is_dispatching_behaviour_changes for full details.
… dispatching (30 minutes dev time)

BREAKING CHANGE:
off_peak entity will now turn on during standard off peak rates as well as ad hoc scheduled
dispatches when on intelligent tariff. This is because the naming and behaviour was confusing (off
peak not turning on when in an ad-hoc off peak period). See
https://bottlecapdave.github.io/HomeAssistant-OctopusEnergy/architecture_decision_records/0002_intelligent_is_dispatching_behaviour_changes
for full details.
…shing of dispatches is enabled (10 minutes dev time)
…sources exist where one source is active and one isn't (1 hour dev time)
Fix the `raise_meter_added()` and `raise_meter_removed()` functions which were passing too many arguments to their `ir.async_create_issue()` calls.

Fixes #1479
The `raise_meter_added()` and `raise_meter_removed()` functions which
were passing too many arguments to their `ir.async_create_issue()`
calls. This appears to be a simple copy-paste error from an earlier
function.

This appears to fix #1479.
BottlecapDave and others added 28 commits September 27, 2025 14:16
…ervice device for easier discovery (30 minutes dev time)
…so they're attached to the correct devices (1 hour dev time)
…ng checked when data wasn't due to be refreshed
…refresh in diagnostic sensor to not be set (5 minute dev time)
…r current requests per hour (30 minutes dev time)
… upon unplugging vehicle (30 minutes dev time)
…sses to match rate sensors in other native integrations and provide min/max/average stats (30 minutes dev time)
…so they're attached to the correct devices (1 hour dev time) (#1497)
…ssions. Existing binary sensors have been deprecated. See repair notice for more information (2 hours 15 mins dev time)
@BottlecapDave BottlecapDave merged commit b7bd7a0 into main Oct 12, 2025
9 checks passed
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 12, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants