Releases: BottlecapDave/HomeAssistant-OctopusEnergy
v10.0.3
10.0.3 (2024-01-20)
Bug Fixes
- Fixed current consumption not resetting to zero at midnight if data isn't available (19ae707)
- Fixed current consumption sensor resetting to zero after a minute when data hasn't refreshed (a13edef)
- Fixed issue intelligent based electricity rates not being adjusted when dispatches are refreshed between rate refreshes (f9514d3)
- Fixed issue when updating electricity rates and intelligent dispatches is unavailable (9bd2b9c)
- Fixed old Intelligent Go tariff not being picked up correctly (c935206)
- Increased timeout limit to 20 seconds to try and resolve issues people have been having (6de26f6)
- Removed duplicate logging of events (1f4e3da)
- Reset cost tracker every day at midnight (3328562)
- Updated various sensors to update their state based on recommended HA practices (9885528)
Enjoying the integration? Why not make a one time or monthly GitHub sponsorship or use my Octopus Energy referral link?
Multi-Account Support Beta 1
This is the initial beta release for supporting multiple accounts. I don't have multiple accounts so very hard for me to test.
This is a side feature, and the presence of the beta does not guarantee an eventual release.
All discussions should be directed to #223
v10.0.2
10.0.2 (2024-01-07)
Bug Fixes
- Removed entity migration from v10.0.1 as not working properly and putting things into weird state. Follow https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy/discussions/678 for updates (daa492f)
- Fixed being unable to edit target rate configuration (150d97a)
- Fixed initialising of integration to automatically retry if account information can't be retrieved (320eb15)
- Fixed issue when intelligent device provider is unavailable (6d9f469)
- Fixed warning raised in charge limit sensor (c43ef73)
- Fixed where intelligent entities were incorrectly available to users on intelligent flux tariff (0be466a)
Enjoying the integration? Why not make a one time or monthly GitHub sponsorship or use my Octopus Energy referral link?
v10.0.0
10.0.0 (2024-01-04)
Bug Fixes
- Added prevention around multiple access token requests (0ecd453)
- Fixed deprecated HA references (5751d3b)
- Fixed issue with cost override when last retrieved is not defined (59dbb7d)
- Fixed off peak sensor turning on during extended intelligent off peak periods (9b36f07)
- Fixed restoring of intelligent states (faa3a32)
- reduced API calls for intelligent data during setup (381c723)
- Reduced required data on startup to speed up initialisation. This may result in a slight delay to get updated data (5a2838f)
- removed various intelligent features for OHME as these were incorrectly exposed and not supported (9d52884)
Features
- added m3 representation of current accumualtive gas consumption for Octopus Home Mini (bc1be66)
- Added min/max/average rates to previous/current/next day rate events/entities (58c3488)
- Added support for custom sensors for tracking the cost of other entities (54604fd)
BREAKING CHANGES
- The current and previous accumulative gas consumptions meter entity ids have been updated to include
suffixes representing the reported unit of measurement. Any references to these entities will need
to be updated. - If you are on intelligent tariff and use OHME chargers, then various intelligent features will be
removed. These were incorrectly exposed. Please see
#573 for more information
Enjoying the integration? Why not make a one time or monthly GitHub sponsorship or use my Octopus Energy referral link?
v9.2.1
9.2.1 (2023-12-20)
Bug Fixes
- Fixed issue where user agent version was not updated (6660075)
Enjoying the integration? Why not make a one time or monthly GitHub sponsorship or use my Octopus Energy referral link?
v9.2.0
9.2.0 (2023-12-19)
Bug Fixes
- Added missing translation for target rate config (eb7c892)
- Fixed issue with target rate when offset is applied twice to next time value (20a1a8c)
- Updated account config to include instructions for where to find account id and api key (a409889)
Features
- Added indicator to target rate sensor to indicate if rate information is incomplete and therefore target times cannot be calculated (28676c3)
- Improved how data is retrieved from APIs and added backoff logic when failing to contact APIs (d461718)
Enjoying the integration? Why not make a one time or monthly GitHub sponsorship or use my Octopus Energy referral link?
v9.2.0-Beta 2
- Adds more logging around failures, outputted as warnings. This is to help debug potential issues with the new retrieval of information
- Updates sent user agent to include version of integration
v9.2.0-Beta 1
This beta release introduces a new way that data is retrieved. Taken from the FAQ
Based on a request from Octopus Energy, the integration polls and retrieves data at different intervals depending on the target data. Below is a rough table describing how often the integration targets refreshing various bits of data. This has been done to try and not overload the API while also providing useful data in a timely fashion.
| Area | Refresh rate (in minutes) | Notes |
|---|---|---|
| Account | 30 | This shouldn't change often so no need to poll often. This is used to get active tariffs |
| Intelligent tariff based sensors | 5 | Trying to balance refreshing settings and new dispatch information without overloading the API |
| Rate information | 15 | This is what drives most people's automations, but doesn't change that frequently |
| Current consumption data | Configurable (minimum 1) | This is most useful for a smart home to be as up-to-date as possible, but at the same time we don't want to flood the API with requests |
| Previous consumption data | 30 | This doesn't change frequently, so no need to request too often. |
| Standing charges | 30 | This should only change if the user's tariff changes, so no need to request data too often. |
| Saving sessions | 15 | Inactive for most of the year and new sessions have enough warning |
| Wheel of fortune | 30 | Doesn't change that frequently, so no need to request too often. |
If data cannot be refreshed for any reason (e.g. no internet or APIs are down), then the integration will attempt to retrieve data as soon as possible, slowly taking longer with each attempt. Below is a rough example assuming the first (failed) scheduled refresh was at 10:35.
| Attempt | Target time |
|---|---|
| 1 | 10:35 |
| 2 | 10:36 |
| 3 | 10:38 |
| 4 | 10:41 |
| 5 | 10:45 |
v9.1.0
9.1.0 (2023-11-28)
Bug Fixes
- Added checks to ensure current gas consumptions were not negative (b8418e1)
- Added defensive logic around loading of local completed intelligent dispatch data (4049c6d)
- Fixed expectation that charge_in_kwh is available in local intelligent dispatch data (6e0c3ed)
- Fixed issue where event entities were not being restored properly (00ec35c)
- Fixed octoplus points sensor to not be available for users who have not enrolled on the programme (3476fae)
- Fixed restoring of attributes on target rate sensor (7a384ef)
Features
- Added octopoints_per_kwh to joined saving session events (if known) (350ad20)
Enjoying the integration? Why not make a one time or monthly GitHub sponsorship or use my Octopus Energy referral link?
v9.0.2
9.0.2 (2023-11-25)
Bug Fixes
- Fixed issue with current consumption sensor not working properly in energy dashboard (08af21b)
- Fixed issue with not being able to unset price caps that were set when the integration was configured initially (838f2e3)
- When using the join saving session service, related data updates are forced in the next cycle (626c1c1)
Enjoying the integration? Why not make a one time or monthly GitHub sponsorship or use my Octopus Energy referral link?