Pushover sounds/priority?

Configuration
1

Hello,

I saw a commit merged back in June for additional Pushover parameters (https://github.com/home-assistant/home-assistant/pull/2381/commits/6fa095f4a7c0d005381e9f3f6b621f9919cb779e) and was wondering if anyone was using custom sounds yet?

alias: Notification
sequence:

  • service: notify.john
    data:
    message: “shut up”
    sound: “siren”

16-08-26 16:55:13 homeassistant.core: Invalid service data for notify.john: extra keys not allowed @ data[‘sound’]. Got ‘siren’

Dump of data object:
{‘sound’: ‘siren’, ‘title’: ‘Home Assistant’}

Am I formatting this incorrectly or is it not yet supported?

2

Have you tried the example in the pull request #2309?

automation:
  alias: Garage Door is Open
  trigger:
    platform: state
    entity_id: sensor.garage_door
    state: 'open'
  action:
    service: notify.pushover
    data:
      title: Garage Door
      message: The garage door is open.
      target: iPhone,MacBookPro
      data:
        url: https://home-assistant.io/
        url_title: Home Assistant
        priority: 1
        timestamp: 1466024112
        sound: siren
1 Like
3

I did not see that, thank you very much!

1 Like
4

The recent updates for all pushover parameters now support emergency messages that must be acknowledged by the user using the syntax shown below. Pushover does not recommend setting sound in the message but letting the receiver set that in the client “As sounds may change in the future” causing the message to fail. Setting timestamp: true is setting the timestamp to now.

action:
- service: notify.pushover
  data:
    title: 'Fibaro Smoke Sensor: '
    message: 'Smoke Detected'
    data:
      priority: 2
      timestamp: true
      expire: 3600
      retry: 30
1 Like
5

I appreciate the heads up, thank you.

Sounds sent in the message still work for now though correct? I am using group messaging so using different sounds to identify non-critical events are a lot easier than customizing each client (I will use something different for critical messages in the future).

6

According to the documentation on Pushover it will work. And they are probably not removing sounds, just adding so I guess you are safe.

1 Like
7

Hi,

I am using pushover and am trying to use a data_template within an automation:

  • service: notify.po
    data_template:
    title: ‘HomeAssistant:’
    message: ‘{{ trigger.to_state.attributes.friendly_name }} Opened’

This works fine but If I try to add:

  • service: notify.po
    data_template:
    title: ‘HomeAssistant:’
    message: ‘{{ trigger.to_state.attributes.friendly_name }} Opened’
    priority: ‘1’

Then I get an error about extra keys not allowed @

I am sure I am using priority elsewhere without issues

8

I do something similar… Try the following (mind the formatting):

      - service: notify.all
        data_template:
          data:
            title: 'Home Assistant'
            sound: 'alien'
            priority: 1
          message: >
            {{ trigger.from_state.attributes.friendly_name }} was opened!