v2.4.0

Krisinformation – v2.4.0

New features

• Bundle and auto-manage the Krisinformation alert card
  The integration now includes the Krisinformation alert card and keeps it available automatically from /local without manual dashboard resource setup. Existing dashboards can keep using the same card type.

Documentation

• Document bundled card installation and migration
  The documentation now explains that the alert card is bundled and managed by the integration from a single repository. It also adds a migration guide for users moving from the deprecated standalone card repository, including cleanup and refresh steps.

☕ Support This Project

If you find Krisinformation useful, consider supporting its development

v2.3.1

Krisinformation – v2.3.1

Bug fixes

• Code improvment

☕ Support This Project

If you find Krisinformation useful, consider supporting its development

v2.3.0

Krisinformation – v2.3.0

New features

• Improve API handling and Home Assistant best practices
  Enhanced API communication with proper rate limiting, backoff recovery, and improved error handling. Updated entity implementations to follow current Home Assistant best practices.

☕ Support This Project

If you find Krisinformation useful, consider supporting its development:

v2.2.0

Release v2.2.0 – Krisinformation

• Normalize whitespace in alert text (description/headline/instruction) so CRLF/extra blank lines don’t render oddly in Home Assistant attributes.

⭐ Support Krisinformation

If you enjoy using Krisinformation and want to support its continued development, consider buying me a coffee or becoming a GitHub Sponsor.

Your support keeps the project alive and moving forward. Thank you 🙌

v2.1.0

Release v2.1.0 – Krisinformation

• API improvments

⭐ Support Krisinformation

If you enjoy using Krisinformation and want to support its continued development, consider buying me a coffee or becoming a GitHub Sponsor.

Your support keeps the project alive and moving forward. Thank you 🙌

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.

v1.0.0

This version introduces a significant internal refactor focused on aligning with Home Assistant's development best practices, improving long-term maintainability, and cleaning up the sensor structure.

⚠️ Breaking Changes

IMPORTANT:
Please remove the integration before upgrading to v1.0.0.
Otherwise, all entities will be re-created with a _2 suffix and previous ones will show as unavailable.

• All entities will be recreated due to changes in unique_id and platform structure

✨ What's New

• Reworked internal structure to improve code clarity and long-term maintainability
• Reuse Home Assistant's internal HTTP session for better performance and stability
• Ensured unique entity_id per config entry to prevent duplication and naming conflicts
• Introduced translation files (en.json) for UI localization and future language support
• Moved large data mappings (e.g., counties and municipalities) into a separate module for better separation of concerns
• Added a constant for the API base URL to make future updates easier
• Minor formatting improvements, including fixing missing newlines

🚀 Recommendation

To avoid duplicated sensors and legacy _2 suffixes, please remove the existing integration before updating to this version.

v0.1.4

What's Changed

• Fix aiohttp session cleanup
• Fix README wording
• Fix manifest documentation URL

Full Changelog: v0.1.3...v0.1.4

v0.1.3

HACS Default

v0.1.2

v0.1.2 – Preparing repository for HACS Default

Warning

If you haven't yet updated to v0.1.0, please read that release first.
It includes breaking changes due to a full migration to the Sveriges Radio VMA API and requires removing and re-adding the integration manually.

👉 Go to v0.1.0 release notes