The next release has a few breaking changes, so wanted to get some more eyes on it before I release it to the masses. The main areas of focus are
- All attributes now display timestamps in local time. This will hopefully avoid any confusion during the BST months
- Refactored how off peak/peak sensors work to now better support 3 rate tariffs (e.g. Cosy) with an additional split between peak and standard rates and any future tariffs that may have 3 unique rates.
- Updates the default names to better support areas of HA with limited space.
The full release notes are below
Bug Fixes
- fixed tariff override data having rate value in pounds and pence for consistency (48f832a (48f832a))
- Fixed updating cost tracker config (c934614 (c934614))
- Updated attributes and events to have datetimes in local time (UTC in winter, BST in summer) (19ac60f (19ac60f))
Features
- Added ability to configure optional minimum/maximum rates for target rate sensors (95ac448 (95ac448))
- Added support for tracking 3 rate tariffs (e.g. Cosy) via separate sensors (40d21d1 (40d21d1))
- updated the default names of various sensors to be more useful in areas of HA when space is limited (870c917 (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