I think so, but some of the code is grayed out and the card doesn’t look quite right, but this kind of code is way over my head beyond copy and paste.
I assume you only have 1 alert at the moment? If so then it looks OK to me.
the template editor does weird things to the colors of text in the left side input section based on what the editor interprets the code to be. if it works as you expect the I wouldn’t worry about the colors. If it didn’t work then the error should be reported in the result section on the right.
ok, thanks. nice work on this integration.
1 Like
Could you share your complete automation? Not sure where to put this into the packages.yaml file.
Can you monitor multiple zones even if those zones are in different counties? I border several counties and usually by the time they alert my zone, I could have called them and told them about it.
yes.
just put in all of the zone/county codes into the config and will monitor all of them.
or you can set up two different instances of the integration with different monitored zones and that would allow you to do different automations with the different entities.
for example if there is a severe thunderstorm or tornado in your backyard you probably want to know that and take immediate actions but if it was in a county over you’ve got some additional time, etc.
1 Like
I’ve got an error with nws now. just had an update for it and now it won’t load at all. Getting this.
Logger: homeassistant.config_entries
Source: config_entries.py:751
First occurred: 5:15:31 PM (3 occurrences)
Last logged: 5:26:42 PM
Error setting up entry NWS Alerts for nws_alerts
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 751, in __async_setup_with_context
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/nws_alerts/__init__.py", line 71, in async_setup_entry
coordinator = AlertsDataUpdateCoordinator(
hass,
...<2 lines>...
config_entry.data.get(CONF_INTERVAL),
)
File "/config/custom_components/nws_alerts/__init__.py", line 149, in __init__
super().__init__(
~~~~~~~~~~~~~~~~^
hass,
^^^^^
...<3 lines>...
update_interval=self.interval,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 139, in __init__
self.config_entry.async_on_unload(self.async_shutdown)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'mappingproxy' object has no attribute 'async_on_unload'
Sorry I didn’t test it thoroughly enough.
unfortunately I don’t have time to deal with it right now since I’m leaving on vacation in an hour.
if you just redownload the last version (6.1) it should work again if this release is the only thing that broke it.
I’ve pulled the offending release from HACS now.
sorry again.
1 Like
This error is sorted in the latest version 
The earlier version (5) inside the init.py I was able to add my own attributes
Probably.
they are now located in the coordinator.py file
I’m sure everyone has noticed the recent activity on this integration.
I’ve finally got the energy to get some issues and requests taken care of.
I’ve released V6.4 a few days ago and V6.5 and V6.6 just today.
Sorry for the quick succession of updates. The last update included a request that I didn’t realize was so easy to implement so I didn’t include it in V6.5.
Anyway as always let me know if something breaks ( 
)
1 Like
Another day, another release.
But this time I haven’t changed anything with the integration.
I just added information to the readme about a new custom dashboard card created by another user (@seevee) that you can use in your frontend to nicely display the sensor data.
the thread discussing the card is here:
Be sure to check it out! 
5 Likes