github BottlecapDave/HomeAssistant-OctopusEnergy v11.0.0

latest releases: v16.3.1, v16.3.1-beta.1, v16.3.0-beta.1...
16 months ago

11.0.0 (2024-05-12)

Bug Fixes

  • Accounted when intelligent device can come back with null data from OE (53db610)
  • Fixed issue when str error reported if config of target rate sensor fails first time (c5cfd83)
  • Fixed issue with dispatching sensor if rate is off peak from now until the end of the available rate data (c583b8b)
  • fixed tariff override data having rate value in pounds and pence for consistency (48f832a)
  • Fixed updating cost tracker config (c934614)
  • Fixed warning for deprecated EventType reference (e8786df)
  • Limited backoff logic to 30 minutes between attempts so it doesn't increase forever (f2de64d)
  • Updated attributes and events to have datetimes in local time (UTC in winter, BST in summer) (19ac60f)
  • Updated minimum Home Assistant version to 2024.5.0

Features

  • Added ability to configure optional minimum/maximum rates for target rate sensors (95ac448)
  • Added support for applying weightings to target rate slots (80bbb52)
  • Added support for tracking 3 rate tariffs (e.g. Cosy) via separate sensors (40d21d1)
  • Added the ability to delete devices manually (404d2e9)
  • updated the default names of various sensors to be more useful in areas of HA when space is limited (870c917)

BREAKING CHANGES

  • If you are relying on the previous default names of sensors then you will need to update your
    sensors manually. Only the visual default name of the sensors have changed; the entity ids will
    remain the same and therefore will not effect any automatmations. If you have manually changed the
    names of the sensors, this should not effect you.
  • For 3 rate tariffs (e.g. Cosy), the peak based sensors will no longer track consumption/cost for both peak and standard rates. There is now a third sensor (standard) which tracks the middle rate. In addition, if you are on a tariff that doesn't have off peak, standard or peak rates, the current off peak/peak based sensors will no longer be provided by the integration.
  • If you were relying on datetime based sensor attributes or event properties being in UTC, you will
    need to adapt accordingly
  • If you were using tariff override rate information, you may need to adjust your use due to changes
    in how value is reported

Enjoying the integration? Why not make a one time or monthly GitHub sponsorship or use my Octopus Energy referral link?

Don't miss a new HomeAssistant-OctopusEnergy release

NewReleases is sending notifications on new releases.