Severe Weather Alert

firstof9 · July 5, 2022, 5:05pm

Correct your YAML is wrong, it should be as follows:

 - condition: template
    value_template: '{{ "Tornado Warning" in state_attr("sensor.nws_alerts_3", "title") }}'

Nameless · July 5, 2022, 6:20pm

This is interesting. I apparently created this in the UI and it’s listed as {{ 'Tornado Warning' in state_attr('sensor.nws_alerts_3', 'title') }} in there. I’ll have to run some experiments to see how to get it to the correct format in YAML view.

Thanks for the tip. Glad it’s somehow still working, though. This has been a huge help being notified of tornado warnings overnight.

firstof9 · July 5, 2022, 7:48pm

In the UI that’d be fine, it sanitizes the code for you.

chicknlil25 · January 21, 2023, 2:08am

Out of curiosity, what are you guys using as a trigger for these severe weather automations? And do you do separate triggers for each possible severe weather alert?

Thanks for your time.

firstof9 · January 21, 2023, 3:26am

I have my google home’s broadcast warnings, while everything else goes to the phone here’s the announcer part:

- alias: NWS Announce Weather Alert
  trigger:
    - platform: state
      entity_id: sensor.nws_alerts
  condition:
    condition: and
    conditions:
      - condition: template
        value_template: "{{states.sensor.nws_alerts.state | int(0) > 0}}"
      - condition: template
        value_template: "{{ trigger.to_state.state|float(0) > trigger.from_state.state|float(0) }}"
  action:
    - service: script.weather_alerts

Script:

weather_alerts:
  alias: Weather Alerts
  mode: queued
  sequence:
    - choose:
        - alias: Sever Weather
          conditions:
            - "{{ 'Tornado' in state_attr('sensor.nws_alerts', 'title').split(' - ')[0] }}"
          sequence:
            - service: script.house_annoucement
              data:
                this_message: "The National Weather Service Has issued a {{ state_attr('sensor.nws_alerts', 'title').split(' - ')[0] }} ,, {{ state_attr('sensor.nws_alerts', 'spoken_desc').split('\n\n-\n\n')[0] }}"
                volume: 0.9
                priority: True
        - alias: Weather Warning
          conditions:
            - "{{ 'Warning' in state_attr('sensor.nws_alerts', 'title').split(' - ')[0] or 'Watch' in state_attr('sensor.nws_alerts', 'title').split(' - ')[0]}}"
          sequence:
            - service: script.house_annoucement
              data:
                this_message: "The National Weather Service Has issued a {{ state_attr('sensor.nws_alerts', 'title').split(' - ')[0] }} ,, {{ state_attr('sensor.nws_alerts', 'spoken_desc').split('\n\n-\n\n')[0] }}"
                volume: 0.9

My announcement script has a night mode so these don’t play after like 8pm unless there’s a tornado watch/warning.

_{Yes I am aware of the mis-spelling of the script name, I haven’t cared enough yet to fix it}

finity · January 21, 2023, 3:52am

I still use my NWS alerts integration linked in post #8

PrayerfulDrop · January 21, 2023, 4:50am

Hey there! I have your HACS installation installed but would like to find examples on how to execute automations based on the weather alert.

finity · January 21, 2023, 5:06am

There’s are examples in the packages folder at the github repo.

github.com

finity69x2/nws_alerts/blob/302f34f6793a6772c562f2074574991e6a133dca/packages/nws_alerts_custom_package.yaml

#################################################################################
#
#   This is the package for NWS ALERTS USING THE CUSTOM INTEGRATION
#
#################################################################################

## For testing the API

# https://api.weather.gov/alerts/active/count

# https://api.weather.gov/alerts/active?zone=INZ009,INC033

########################  SENSOR  ###############################################

## the NWS Sensor can now be installed using HACS. If you aren't using HACS you can uncomment the nws_alerts sensor here and configure it manually.

# sensor:
  # - platform: nws_alerts
    # zone_id: 'INZ009,INC033'
    # name: nws alerts yaml

This file has been truncated. show original

frakman1 · May 25, 2023, 3:15pm

Since the NWS alerts sensor’s attributes are only populated when there is an event, it’s nearly impossible to test. Does anyone have any ideas on how to do that?

I took a look at the yaml file in post #8 but it’s so complicated! haha Array indexing for multiple alert support etc.

Is there a way to have a simple automation that triggers when there is an alert and plays a voice message that is the actual alert itself? The example was playing a pre-set mp3 file and doing all kinds of text parsing for the popup alert. I believe there is a “spoken_desc” field that can be used but not sure how (see script below)

Since the visual UI editor didn’t make sense, I came up with this yaml automation based on the example and would appreciate some help with it from the experts here. It’s definitely wrong but wanted to start somewhere. The ‘message’ field is usually a constant string and this is the first time I try using variable expansion in its place.

alias: NWS Check for Multi Alerts
description: NWS Check for Multi Alerts
trigger:
  - platform: state
    entity_id: sensor.nws_alerts
condition:
  - "{{ states('sensor.nws_alerts') | int > 0 }}"
  - "{{ trigger.to_state.state|int > trigger.from_state.state|int }}"
action:
  - service: tts.google_translate_say
    data:
      entity_id: media_player.study_speaker
      message: |
        {{ state_attr('sensor.nws_alerts', 'spoken_desc') }}
mode: single
initial_state: true

frakman1 · May 25, 2023, 4:23pm

Quick update/answer to my own question.

I found that I could set the values of the sensor to whatever I want in the Developer Tools section:

The yaml automation posted above seemed to work for my test data.

I also changed my Zone ID to AKZ215 and reloaded the Integration which had a lot of weather alerts to test against.

finity · May 26, 2023, 12:23am

Just be aware tho that if there are multiple alerts that the TTS above will announce every one of them. It won’t just tell you the last one.

If there are 5 alerts and when number 6 comes in it will announce the entire text contained in the “spoken_desc” section of the sensor.

that’s the reason for all of the parsing that was done in the original template - so you only get the most recent one announced.

frakman1 · May 26, 2023, 4:55am

Thank you for the tip.
I would be eternally grateful if you could add just the minimal, required logic to handle that case to my automation. I tried but couldn’t follow the logic in the Github post. I guess I haven’t mastered yaml voodoo yet haha

finity · May 26, 2023, 6:48am

which case are you referring to? So that the automation only tells you the last alert received?

frakman1 · May 26, 2023, 5:48pm

Yes please.

finity · May 27, 2023, 1:37am

this should only announce the spoken description of the last alert received (index ‘[0]’):

alias: NWS Check for Multi Alerts
description: NWS Check for Multi Alerts
trigger:
  - platform: state
    entity_id: sensor.nws_alerts
condition:
  - "{{ states('sensor.nws_alerts') | int > 0 }}"
  - "{{ trigger.to_state.state|int > trigger.from_state.state|int }}"
action:
  - service: tts.google_translate_say
    data:
      entity_id: media_player.study_speaker
      message: |
        {{ state_attr('sensor.nws_alerts', 'spoken_desc').split(' - ')[0] }}
mode: single
initial_state: true

frakman1 · May 27, 2023, 1:38pm

Thank you!

H2OKing · October 11, 2024, 6:42am

Is this still an attribute? I don’t see it.

finity · October 12, 2024, 8:30pm

No.

there was a major re-write of the integration recently.

the new attributes are as follows:

Type
Status
Severity
Certainty
Sent
Onset
Expires
Ends
AreasAffected
Description
Instruction

I think the closest equivalent to the old spoken_desc attribute is the Description attribute

H2OKing · October 13, 2024, 4:55pm

I think I got a good setup on it now.