update manifest file

I forgot to update the manifest. Oops!

Minor Breaking Change (v6.0 or later)

After installing the update to version 6.x or later from an earlier version your sensor Unique ID and Entity ID will likely change.

The integration will likely create a new sensor entity that will have "_alerts" appended to the new entity ID. If you used the default naming for the original sensor the new sensor will be called "sensor.nws_alerts_alerts".

You can either choose to fix the new sensor entity_id to match the old one or update all of the locations in which you use the sensor to the newly updated entity_id. Either way you will need to delete the old unavailable entity_id. Fixing the new entity_id is the easiest in my opinion.

To fix the entity_id simply open the integration and navigate to the entities list.

You should now see that there are three entities associated with the updated integration - if there are only two then this likely doesn't apply to you. As you can see I've already fixed one of my test integration instances so it only has two entities now.

Select the old sensor entity. It will be the one without the "_alerts" added to the end and it will have a red circle icon at the right (indicating it is now "unavailable").

Open the settings cog in the top right corner.

Then delete that entity.

You can now go back to the prior entities list (there should now be only two entities listed) and edit the entity_id of the newly created sensor and just remove the "_alerts" from the end.

You should then be back to where you started before the update and all of your automations, scripts, etc should work as before.

Fixes

No longer have entities go unavailable when Weather.gov API get's flaky

Enhancement

Add new sensor "last_updated" to indicate when the last successful API call was completed.

Bug fix and adds additional sensor

Minor Breaking Change

After installing this update your sensor Unique ID and Entity ID will likely change.

The integration will likely create a new sensor entity that will have "_alerts" appended to the new entity ID. If you used the default naming for the original sensor the new sensor will be called "sensor.nws_alerts_alerts".

You can either choose to fix the new sensor entity_id to match the old one or update all of the locations in which you use the sensor to the newly updated entity_id. Either way you will need to delete the old unavailable entity_id. Fixing the new entity_id is the easiest in my opinion.

To fix the entity_id simply open the integration and navigate to the entities list.

You should now see that there are three entities associated with the updated integration - if there are only two then this likely doesn't apply to you. As you can see I've already fixed one of my test integration instances so it only has two entities now.

Select the old sensor entity. It will be the one without the "_alerts" added to the end and it will have a red circle icon at the right (indicating it is now "unavailable").

Open the settings cog in the top right corner.

Then delete that entity.

You can now go back to the prior entities list (there should now be only two entities listed) and edit the entity_id of the newly created sensor and just remove the "_alerts" from the end.

You should then be back to where you started before the update and all of your automations, scripts, etc should work as before.

Fixes

No longer have entities go unavailable when Weather.gov API get's flaky

Enhancement

Add new sensor "last_updated" to indicate when the last successful API call was completed.

Address an API glitch causing frequent state changes (issue #70)

Adds extra error handling for invalid attributes returned from API.

Add extra requested attributes

Small change to add two new attributes as requested for "ends" and "areaDesc" (areas affected) information.

Complete rewrite of alerts attributes structure

MAJOR BREAKING CHANGES!

The alerts attributes data structure has been completely reorganized for better human readability and it will hopefully lend itself to easier data retrieval as necessary.

None of the existing automations, scripts or dashboard examples will continue to function with this update so be sure to update those in your system as well if you use them.

I've tested the changes as thoroughly as possible but I can't guarantee that I have made some mistake that I've missed. So as always please let me know of anything that needs fixed and...

Use at your own risk.

add onset attribute

Added an "Onset" attribute and cleaned up some documentation

Changes to use async_forward_entry_setups

No functionality changes

Thanks @Snuffy2 for the updated code

minor update to manifest

4.1

Update manifest.json

Adds the ability to use a device_tracker for alert location data

You can now optionally configure a dynamically updated NWS Alerts sensor by adding a device_tracker entity to the sensor config.

This is particularly useful if you travel outside of your statically configured Zone or GPS location and want to get updated NWS alerts for your current location.

Combines the Zone ID integration and the GPS Location integrations

This is an updated version of the NWS integration that combines the previous Zone ID integration version with the new GPS location integration option.

There should be no breaking changes with this update.

Please report any issues.