v2.0.0

Krisinformation 2.0.0 – Release Notes

• New

  • New binary_sensor that shows if there are active alerts (VMA) for the selected municipality/county.
  • New settings: language (sv-SE/en-US), minimum severity level, option to include Update/Cancel in sensors, and choice of API environment (production/test).
  • New events on the event bus for automations: krisinformation_new_alert, krisinformation_updated_alert, krisinformation_canceled_alert.

• Improvements

  • Switch from v3-beta to the stable v3 API.
  • Smarter fetching: support for ETag/Last-Modified and 304 Not Modified, “since” parameter for deltas, handling of 429 (backoff), and dynamic update interval based on Cache-Control.
  • Normalized CAP structure (consistent data in all alerts).
  • Device information to Device Registry (manufacturer/model), plus improved logging.

• Behavior Changes

  • Sensors now only show active alerts by default.
  • You can choose minimum severity level and whether Update/Cancel should be counted in sensors.
  • Attributes under sensor now expose full CAP objects for each alert (previously only a short summary).

• Breaking Changes

  • The structure in extra_state_attributes["alerts"] has changed from a summary list to full CAP objects. Any dashboards/Jinja templates that read the old field names need to be updated.

• Migration

  • Existing configurations are migrated automatically (v1→v3). Unique IDs are preserved, so entity names should not change.
  • Adjust new options in the integration settings if needed (language, severity, Update/Cancel, API environment).

• Other

  • New binary_sensor with device class safety.
  • Clearer error handling and timezone-safe date parsing.

• Tips for Automations

  • Listen to krisinformation_new_alert, krisinformation_updated_alert or krisinformation_canceled_alert to trigger flows when new, updated, or canceled VMAs are published.