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.