v2.0.0

Note that this is a relatively minimal update, however it does remove entities and thus a major breaking change as per semantic versioning.

The previously separate detailed price sensors have been removed and folded into the primary price sensors as an extra attribute:

• Removed entities: sensor.amber_express_home_general_price_detailed, sensor.amber_express_home_feed_in_price_detailed.
• The full forecast they exposed now lives in a detailedForecast attribute on the matching primary price sensor (sensor.amber_express_home_general_price, etc.), replacing the old forecasts attribute.
• detailedForecast is marked as an unrecorded attribute, so the full forecast no longer bloats the HA recorder database.
• Prices in the state and in detailedForecast now carry Amber's full precision (7 dp) instead of being rounded to 4 dp. The forecast list ({ time, value }, used by HAEO) is unchanged, and still rounded to 4 dp and recorded by HA in short term history.
• The detailedForecast list no longer strips any fields, which adds back in:
  • tariff_period
  • tariff_season
  • tariff_block
  • nem_time
  • descriptor
  • spike_status
  • estimate

Migration guide

The detailed sensors were disabled by default. If you never enabled them and never read their forecasts attribute, you are unaffected and can upgrade without any changes. If you did use the detailed sensors, simply point any templates at the primary sensor and use its detailedForecast attribute. e.g.

{# Before (v1.x) #}
{{ state_attr('sensor.amber_express_home_general_price_detailed', 'forecasts') }}

{# After (v2.0) #}
{{ state_attr('sensor.amber_express_home_general_price', 'detailedForecast') }}

What's Changed

• Combine detailed sensors into primary sensors by @BrendanAnnable in #82
• Provide state and detailed attributes full price precision by @BrendanAnnable in #83
• Improve documentation by @BrendanAnnable in #84
• Update dependencies by @BrendanAnnable in #85

Full Changelog: v1.0.2...v2.0.0