Weatheralerts Versions Save

Changes:

weatheralerts v0.1.5

• Fix 'async_timeout.timeout with loop keyword argument' deprecation warning. (Issue #51)
• Fix 'implements device_state_attributes' warning. (Issue #52)
• Fix for template errors that are logged when sensor is unavailable. (Issue #52)
• Add icons for each alert type (Issue #50)

Changes:

weatheralerts v0.1.4

• Update manifest to include 'version' key.

Changes:

weatheralerts v0.1.3

• Update README.md so links will work in HACS

Changes:

weatheralerts v0.1.2

• Update and add documentation
• Changed default icon from mdi:weather-hurricane to mdi:alert-octagram
• Simplify alert object sorting; reverse sort alerts by alert ID
• Tweak logging levels and messages
• Log sorted alert IDs for debugging purposes
• Add endsExpire, hailSize, windGust, and waterspoutDetection alert attributes
• Increase initial setup timeouts from 10 seconds to 20 seconds

weatheralerts YAML packages v0.1.2

• Various improvements and fixes
• Add input_text sensors to track triggered alerts
• Turn off ended alerts (using endsExpire) if weather.gov has extended outage
• Add additional count attributes to the weatheralerts_*_active_alerts sensor

If you use your own automations and have problems with constant re-triggering notifications, you should examine the YAML packages in the *weatheralerts* GitHub repository to see how the input_text sensors are used with the automations in the YAML packages. If you still have problems, open a new issue and include your automation configuration and any relevant Jinja template code or YAML code.

If you use the *weatheralerts* YAML package(s), this should (fingers crossed) fix the constantly re-triggering alerts that seemed to happen on occasion. The YAML packages don't install or update via HACS, so be sure to download them from the GitHub repository. Also be sure to check out the updated documentation. More documentation updates will be coming.

This release addresses a problem when multiple alerts are issued with the same 'sent' date/time. The json alert feed will randomly swap these alerts around and can cause notifications to be continually re-triggered, potentially every 30 seconds (or whatever the scan_interval is set to in the weatheralerts yaml configuration). The alerts array is now sorted by 'sent' and 'id' fields, and should keep alerts in a consistent order even when they are swapped around in the json alert feed.

Added 'county' platform config option to specify an optional county ID number. 'zone' should be set to a proper zone ID number (and is required), the county ID number should then be specified with the 'county' option.

Additional alert properties have been added along with proper handling in the event an attribute is not included in the json alert feed. Feel free to request additional alert properties by submitting an issue here on github (https://github.com/custom-components/weatheralerts/issues).

The main platform sensor entity state will contain the number of active alerts, unless the sensor fails to connect with weather.gov to retrieve alerts. If the sensor cannot connect to weather.gov to retrieve the json alert feed, the sensor state will be set to 'unavailable'. The yaml package(s) with this pull request includes template sensors that will retain active alerts and the active alert count (for a short period), even when the main sensor becomes 'unavailable'.

PlatformNotReady is added to allow the platform to continue to retry the initialization if the weather.gov site is too slow to respond or experiencing other issues.

Added additional checks to verify the specified zone and county IDs are valid.

Included a set of comprehensive yaml packages that include tracking for up to 5 active weather alerts and automations and script to handle UI notifications.

Started update of README.md documentation.