-
-
Notifications
You must be signed in to change notification settings - Fork 88
Next release #1460
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Next release #1460
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
….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.
… be more user friendly (2 hours dev time)
Required to support v16.2.0 as needs Pydantic v2 included in HA 2025.1 (https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy/releases/tag/v16.2.0)
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.
…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
…ts_per_hour (15 minutes dev time)
…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)
…15 minutes dev time)
…ed to octoplus device
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.