weatheralerts v2026.1.0

[jlverhagen]

Weather Alerts v2026.1.0

Release date: January 30, 2026

---

⚠️ IMPORTANT – READ BEFORE UPDATING ⚠️

This release introduces breaking changes to how the Weather Alerts integration is configured.

If you are upgrading from a previous version, do not update until you have reviewed the information below.

---

Breaking Changes and Deprecations

UI-Only Configuration

• YAML-based platform configuration is deprecated and no longer supported for new setups.
• All configuration is now performed entirely through the Home Assistant UI.
• Existing YAML-based platform configuration is automatically migrated to UI-based config entries on startup.

No manual migration steps are required, but you should verify your configuration after updating.

---

YAML Package Deprecation

• The optional YAML packages provided with earlier versions of this project are now deprecated.
• These YAML packages were intended as helpers and automations for easy use of the integration, but are not required for the integration to function.
• YAML packages are no longer maintained and will be removed in a future release.
• The Automation Examples and Dashboard Examples links will give you what you need to get started replacing the existing persistent notification automation and provide dashboard examples to use the integration sensor data.

If you are currently using a Weather Alerts YAML package:

• You may continue using it, but review the Installation documentation on how to upgrade and continue using the YAML Package.
• Review the updated Automation Examples and Dashboard Examples documentation for easy to use examples to help you migrate away from the YAML Package.

---

What You Should Do Before Updating

1. Review the updated README:
   https://github.com/custom-components/weatheralerts/blob/master/README.md

2. Review installation and configuration documentation:
   https://github.com/custom-components/weatheralerts/blob/master/documentation/installation.md
   https://github.com/custom-components/weatheralerts/blob/master/documentation/configuration.md

3. If you previously used YAML configuration or YAML packages:

   • Allow Home Assistant to start once after updating
   • Confirm the Weather Alerts integration is present and working
   • Remove legacy YAML configuration entries after verification
   • Plan migration away from the YAML Package if still in use

---

Summary of Changes in 2026.1.0

This release is a major update to the Weather Alerts integration, introducing built-in alert tracking for use with persistent notifications, improved configuration options, expanded documentation, and a fully UI-driven configuration experience.

---

New Features

• Persistent alert tracking

  • Alerts are tracked across Home Assistant restarts
  • Each alert includes lifecycle status (new, old, delete)

• Improved error handling

  • Automatic fallback to last known good data during NWS API outages
  • Structured error history exposed via sensor attributes

• Configurable update behavior

  • User-configurable sensor update interval
  • User-configurable API timeout with validation safeguards

• Optional alert deduplication

  • Removes duplicate alerts with identical descriptions when enabled

• Custom alert icon configuration

  • Per-alert event icon mappings configurable via integration options flow
  • Default fallback icon for unknown event types

• Expanded zone support

  • Public zones, county zones, and marine zones supported
  • Multiple zone types may be combined into a single sensor

---

Improvements

• Sensor state now consistently represents the number of active alerts
• Alert data is normalized and sorted consistently
• Expired alerts handled more reliably during API outages
• Entity naming and unique ID handling standardized
• Documentation fully rewritten and reorganized

---

Documentation

Full documentation, examples, and troubleshooting guides:
https://github.com/custom-components/weatheralerts/tree/master/documentation

---

Notes for Existing Users

• YAML platform configuration is deprecated
• YAML packages are deprecated and no longer maintained

---

Support

If you encounter issues after upgrading:

1. Review the documentation
2. Enable debug logging from the Weather Alerts integration page
3. Reproduce the issue
4. Open an issue with logs attached

Issue tracker:
https://github.com/custom-components/weatheralerts/issues

---

This discussion was created from the release weatheralerts v2026.1.0.

[kaijk]

I have been following along with the pre-release versions and just pulled 2026.1.0 with HACS.

Is the newest code in Github? The timestamps show two weeks ago.

After HA restart I don't notice any changes to the integration from what I already had:
I don't see in Devices and Settings > Weatheralerts any way to Reconfigure the integration (to enable de-duplicate, for example). There is just the one entity.

In looking at the Entity, it is named sensor.weatheralerts_zonename_zoneID_CountyID (I think), not just sensor.weatheralerts as expected in the sample automations and dashboards.

[jlverhagen]

Yes, the newest code is in Github. If you installed manually prior to the release, there were some updates to en.json translations and how the integration pulls them translation strings from the file. Those changes were not really bug fixes to fix something broken and they didn't change the functionality of the integration. Those final changes just made the en.json structurally correct the way Home Assistant wants it so it passes the Home Assistant hassfest github action that checks custom components for proper data, structure, and standards compliance. If you pulled with HACS, then you are fully up-to-date.

That is correct about the sensor name. In the automation and dashboard examples, you have to change sensor.weather_alerts to your actual sensor such as sensor.weatheralerts_zonename_zoneID_countyID. Once you paste the automation or dashboard code into your Home Assistant, highlight the weather_alerts part of those sensor.weather_alerts lines and start typing weather and Home Assistant should bring up a list of sensors to make it easy to select your weather alerts sensor. Most examples have more than one line that needs editing in order to work correctly.

[Earth7777]

Thank you for offering this to the community. really like it and ability to get key alerts as a "Card". is there a way to trigger thru automation a way to get either the weather alert summary or details via email? i use automation to trigger to email or cell other notifications but not sure how to do it for weather alerts

e.g. the follow summary advisory below today

Scottsdale/Paradise Valley (AZZ546,AZC013)
Wind Advisory: Wind Advisory issued April 18 at 11:58AM MST until April 19 at 11:00AM MST

[kaijk]

Here is how I send weather alert emails (from another discussion here): #90 (comment)

[Earth7777]

Here is how I send weather alert emails (from another discussion here): #90 (comment)

thank you very much! could use a bit more help

I do see the code but not sure where to copy it and save it... or do i start from the already existing blue print in my HA (WeatherAlerts – Persistent Notification and Cleanup)

Currently, I have one automation linked to the above blueprint (was setup per original instructions)... below is the YAML for the automation (just by click Edit YAML in automation screen)

alias: WeatherAlerts – Persistent Notification and Cleanup
description: ""
use_blueprint:
path: github.com/weatheralerts_persistent_notification_original.yaml
input:
sensor: sensor.weatheralerts_scottsdaleparadise_valley_azz546_azc013

[Earth7777]

i tried to create an automation (did not yet add email - just to test out) but not working

automation:

• id: weatheralerts_notifications
  alias: Weatheralerts Notifications
  initial_state: true
• platform: state
  entity_id: sensor.weatheralerts_scottsdaleparadise_valley_azz546_azc013
  attribute: alert_tracking
  variables:
  sensor: sensor.weatheralerts_scottsdaleparadise_valley_azz546_azc013
• variables:
  alert_msg: >
  {% set new_ids = alert_ids | selectattr('status','eq','new')
  map(attribute='id') | list %}
• service: persistent_notification.create
  data:
  notification_id: "{{ notif_id }}"
  title: Weather Alerts for {{ zone_name }}
  message: "{{ alert_msg }}"
  alias: New automation
  description: ""

[kaijk]

Try this automation. Change the zone sensor and email notifier to your own as indicated in the comments at the top of the automation.

FYI: to include yaml code in postings please bound the code in three backticks and yaml at the head and end of the code. See the Markdown is supported link below

```yaml
Your Code
```

[Earth7777]

really appreciate your help.. where do i save the new automation script? i tried creating a new automation (in settings), edit YAML, paste the code and replaced sensors/notifier but i got an error when i try to save "Message malformed: extra keys not allowed @ data['automation']"

instead should i be saving the code to /homeassistant/automations.yaml (append to the bottom of file) or somewhere else?

thank you

[kaijk]

I have the automation as a `package`. I've never done it, but if you do the automation > edit yaml and paste in the code, you may be able to just delete the line `automation:` from the code and be good to go (with your notifier and weather location changes). You may also wish to change the `id:` and `alias:` to match your location. Me, I'd put it in your automations.yaml file that I presume you have included in your configuration.yaml as `automation: !include automations.yaml` In this case, again, remove the `automation:` line, etc. But, you will also have to ensure that the indentation matches the indentation of other automations already in that file. You may need to remove the two leading spaces from every line in the automation. Not hard depending on your editor..

…

On Sat, Apr 25, 2026 at 8:44 AM Earth7777 ***@***.***> wrote: really appreciate your help.. where do i save the new automation script? i tried creating a new automation (in settings), edit YAML, paste the code and replaced sensors/notifier but i got an error when i try to save "Message malformed: extra keys not allowed @ data['automation']" instead should i be saving the code to /homeassistant/automations.yaml (append to the bottom of file) or somewhere else? thank you — Reply to this email directly, view it on GitHub <#92 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AL2THYUMZ6XD7R36QWPWJMT4XTMNNAVCNFSM6AAAAACTM3SBE6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMNZRGI2DSNY> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AL2THYXWQNL7HVOJUXGLVF34XTMNNA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRXGEZDIOJXUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android <https://github.com/notifications/mobile/android/AL2THYTJLLYSWAVFZDEVVE34XTMNNA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRXGEZDIOJXUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you commented.Message ID: <custom-components/weatheralerts/repo-discussions/92/comments/16712497@ github.com>

[kaijk]

I pulled a RAW copy of the automation from github just now, put it in a new file in my packages directory after moving the current one out . Restarted HA and the Automation is there. It runs on an HA Start Event, so there should be an entry in your log file to that effect toward the end of the HA startup sequence. There should also be several log messages about the Weatheralrets integration being loaded as well during startup. You have set up the weatheralerts integration as well as the automation?

[Earth7777]

yes, /config is my config directory in HA
in Dev Tools > States, i find the other automation but not this new one - see below
so it appears it is not loading.
I restarted HA did look at the logs for both HA Core and Supervisor, i do not see any automation logs which is odd as i know all my automations (30+) are working. also, i searched for "Weatheralerts Motherload Notifications" and nothing...

will keep looking

---

automation.weather_is_freezing
Weather Is Freezing
on
id: 1736662706280
last_triggered: 2025-01-24T14:50:37.142369+00:00
mode: single
current: 0
icon: mdi:snowflake-thermometer
friendly_name: Weather Is Freezing
automation.weather_is_lightning
Weather Is Lightning
on
id: 1736662948545
last_triggered: 2025-03-13T23:46:18.512875+00:00
mode: single
current: 0
icon: mdi:weather-lightning
friendly_name: Weather Is Lightning
automation.weather_is_raining
Weather Is Raining
on
id: 1736663005155
last_triggered: 2025-03-15T11:59:41.192009+00:00
mode: single
current: 0
icon: mdi:weather-pouring
friendly_name: Weather Is Raining
automation.weatheralerts_all_clear_notification
WeatherAlerts - All Clear Notification
on
id: 1770010164742
last_triggered: 2026-04-19T19:04:41.207354+00:00
mode: single
current: 0
friendly_name: WeatherAlerts - All Clear Notification
automation.weatheralerts_notify_on_recovery
WeatherAlerts - Notify on Recovery
off
id: 1770010101161
last_triggered: 2026-04-11T02:27:21.679176+00:00
mode: single
current: 0
friendly_name: WeatherAlerts - Notify on Recovery
automation.weatheralerts_notify_on_warnings
WeatherAlerts - Notify on Warnings
on
id: 1770010210334
last_triggered: null
mode: single
current: 0
friendly_name: WeatherAlerts - Notify on Warnings
automation.weatheralerts_notify_on_weatheralerts_error
WeatherAlerts - Notify on WeatherAlerts Error
off
id: 1770009964488
last_triggered: 2026-04-11T02:25:50.698773+00:00
mode: single
current: 0
friendly_name: WeatherAlerts - Notify on WeatherAlerts Error
automation.weatheralerts_persistent_notification_and_cleanup
WeatherAlerts – Persistent Notification and Cleanup
on
id: 1770009840306
last_triggered: 2026-04-28T04:59:47.851851+00:00
mode: restart
current: 1
friendly_name: WeatherAlerts – Persistent Notification and Cleanup

[Earth7777]

here a few screenshots if they help in the debug process...
i assume the indentation is correct as i copied RAW and pasted. see second screenshot.

... ...

[kaijk]

Packages needs to be a child of the homeassistant: key So, move your packages:... (line 36) to line 5 or so in configuration.yaml and indent packages two spaces so it aligns with allowlist. .
https://www.home-assistant.io/docs/configuration/packages/#create-a-packages-folder

homeassistant:
  packages: !include_dir_named packages 

Note that the email notifications cannot be dismissed so you may get several in a row.

[Earth7777]

thank you! this was the issue. completely missed it. and never got any error messages.
now i wait for a weather alert :)