New bad weather alert system

What's Changed

New bad weather alert system

Predbat can take data directly from Meteo-Alarm feed and use it to trigger keeping your battery charged so you have power in the event of a power cut.

Please look at their web site for more details. The apps.yaml must be configured to select the URL for your country.

https://meteoalarm.org/en/live/

The event severity and certainty are all regular expressions and can be set to one or multiple values using regular expression syntax. Any unset values are ignored.

Your location (from Home Assistant) is used to filter on alerts that apply only to your area.

Events that match the given criteria will try to keep your battery at the percentage level specified by keep (default 100%) during the entire event period. This works by using a much stronger version of best_soc_keep but only for that time period.

Your Predbat status will also have [Alert] in it during the alert time period and the triangle alert symbol will show on your HTML plan for the time period of the alert.

  # Alert feeds - customise to your country and the alert types, severity and keep value
  # customise to your needs, delete the ones you don't want to trigger on - e.g. remove Amber, Moderate and Possible.
  alerts:
    url: "https://feeds.meteoalarm.org/feeds/meteoalarm-legacy-atom-united-kingdom"
    event: "(Amber|Yellow|Orange|Red).*(Wind|Snow|Fog|Rain|Thunderstorm|Avalanche|Frost|Heat|Coastal event|Flood|Forestfire|Ice|Low temperature|Storm|Tornado|Tsunami|Volcano|Wildfire)"
    severity: "Moderate|Severe|Extreme"
    certainty: "Possible|Likely|Expected"
    keep: 40

• Alert system by @springfall2008 in #1916
• Alert update to include location by @springfall2008 in #1917
• Misc typos by @springfall2008 in #1919
• Update output-data.md by @springfall2008 in #1920
• Version 8.13.0 by @springfall2008 in #1923
• Update apps-yaml.md by @springfall2008 in #1924

Bug fixes

Catch a potential crash with GivTCP V2 and REST mode:

• Catch bad discharge percent by @springfall2008 in #1922

Full Changelog: v8.12.0...v8.13.0

Support Energidataservice

What's Changed

Features

Adding support for Energidataservice for EU users

https://github.com/MTrab/energidataservice

• Add Energidataservice to Predbat by @Scholdan in #1887
• Update predbat.py - new file by @springfall2008 in #1913
• Energy data service cleanup and unit tests by @springfall2008 in #1914

Bug fixes

Missing rate for late tonight now takes from last night rather than the 30 minutes before

• Correction to rate replication for Agile by @springfall2008 in #1911

New Contributors

• @Scholdan made their first contribution in #1887

Full Changelog: v8.11.6...v8.12.0

Control export target for GE V3 inverters

What's Changed

Features

Added support to control the export target for GE V3 inverters, thus preventing this from being set too high.

• Unit testing and minor fixes by @springfall2008 in #1904
• Fixes for discharge target soc by @springfall2008 in #1905
• Second attempt at export target by @springfall2008 in #1906
• Fix discharge target code by @springfall2008 in #1907
• Inverter changes to set discharge target by @springfall2008 in #1909
• Guarding new discharge target with v3 rest by @springfall2008 in #1910

Full Changelog: v8.11.5...v8.11.6

Catch some cases where energy rate URL creates too much data

What's Changed

• Catch some cases where energy rate URL creates too much data, causing memory issues @springfall2008 in #1900
• Updated agile API link by @MathewBurnett in #1885

New Contributors

• @MathewBurnett made their first contribution in #1885

Full Changelog: v8.11.4...v8.11.5

Fix rate rounding issue with high threshold

What's Changed

In the case where your highest import rate was lower than the export rate but had more than 2 decimal places it was ignored!

• Fix rate rounding issue with high threshold by @springfall2008 in #1894

Full Changelog: v8.11.3...v8.11.4

Fix issue where clipping removes a charge hold causing bad plan

What's Changed

• Fix issue where clipping removes a charge hold by @springfall2008 in #1893

Full Changelog: v8.11.2...v8.11.3

Reduce writes in low power mode, solar charging fix

What's Changed

Improvements

Try to reduce register writes in low power mode but sticking with current charge rate if a change is not required
Minor fix related to modelling of solar charging

• Fix related to solar charging, change to try to reduce register writes in low power mode charge by @springfall2008 in #1882

Documentation

• Update faq.md to talk about losses by @springfall2008 in #1879
• Add repeat to service templates by @springfall2008 in #1880

Full Changelog: v8.11.1...v8.11.2

Optimiser fixes, tweak levelling order and fix for charging with solar

What's Changed

Changes made to the optimiser to catch some corner cases:

• Optimise levels from the end of the plan first
• When charging with solar that won't provide the full rate charge account of the additional export of that solar.

• Fix for issue related to metric self sufficiency by @springfall2008 in #1877
• Fixes related to charging with active solar by @springfall2008 in #1878

Full Changelog: v8.11.0...v8.11.1

Max charge rate temperature curve

What's Changed

Features

• Max charge rate temperature curve adjustments by @springfall2008 in #1869

This feature allows you to model temperature dependant charging and discharging of the battery. You can set a charge and a discharge maximum rate scaling based on temperature and then using a temperature sensor predict future battery temperatures. Low power mode will also account for this in its calculation.

To try this feature with GivTCP (Givenergy) can you update your apps.yaml to both give battery temperature and also define charge curve. I don't know what the correct charge or discharge curves are for particular makes and models but this charge curve came from some comments made by GivEnergy.

  battery_temperature:
   - sensor.givtcp_battery_stack_1_bms_temperature
   - sensor.givtcp2_battery_stack_1_bms_temperature

  # Battery temperature charge adjustment curve
  # Specific in C which is a multiple of the battery capacity
  # e.g. 0.33 C is 33% of the battery capacity
  # values unspecified will be assumed to be 1.0 hence rate is capped by max charge rate
  battery_temperature_history: sensor.givtcp_battery_stack_1_bms_temperature
  battery_temperature_charge_curve:
    19: 0.33
    18: 0.33
    17: 0.33
    16: 0.33
    15: 0.33
    14: 0.33
    13: 0.33
    12: 0.33
    11: 0.33
    10: 0.25
    9: 0.25
    8: 0.25
    7: 0.25
    6: 0.25
    5: 0.25
    4: 0.25
    3: 0.25
    2: 0.25
    1: 0.15
    0: 0.00

Bug fixes

• Fix issue with key filtering in debug files by @springfall2008 in #1871

Full Changelog: v8.10.2...v8.11.0

Bug fixes, repeat service name, Service API for car hold

What's Changed

• Service repeat was called always, mistake to documentation by @springfall2008 in #1867

The documented name repeat did not match the code.

• Fix bug where service API was not used for car/iboost hold by @springfall2008 in #1868

The service API was not called when holding for car or iboost, this is now fixed.

Full Changelog: v8.10.1...v8.10.2