
* Pushover: update webpage with clone URL Hi, Pushover developer here. I was notified that your app has a Pushover plugins, so I've listed it on our [apps page](https://pushover.net/apps) and enabled cloning for it. Instead of users having to upload an icon and fill in all the fields, users can be directed to https://pushover.net/apps/clone/home_assistant which pre-fills those fields and copies the icon. I'm not sure if the `date` field in this markdown page needs to be bumped when it's updated, or if it's a creation date. * Add some other minor changes
2.4 KiB
layout, title, description, date, sidebar, comments, sharing, footer, logo, ha_category, ha_release
layout | title | description | date | sidebar | comments | sharing | footer | logo | ha_category | ha_release |
---|---|---|---|---|---|---|---|---|---|---|
page | Pushover | Instructions on how to add Pushover notifications to Home Assistant. | 2015-01-20 22:36 | true | false | true | true | pushover.png | Notifications | pre 0.7 |
The Pushover service is a platform for the notify component. This allows components to send messages to the user using Pushover.
{% linkable_title Configuration %}
In order to get an API key you need to register an application on the Pushover website. Your Pushover user key can be found on the Pushover dashboard.
To use Pushover notifications, add the following to your configuration.yaml
file:
# Example configuration.yaml entry
notify:
- name: NOTIFIER_NAME
platform: pushover
api_key: ABCDEFGHJKLMNOPQRSTUVXYZ
user_key: ABCDEFGHJKLMNOPQRSTUVXYZ
Configuration variables:
- name (Optional): Setting the optional parameter
name
allows multiple notifiers to be created. The default value isnotify
. The notifier will bind to the servicenotify.NOTIFIER_NAME
. - api_key (Required): Your API key.
- user_key (Required): Your user key for Pushover.
Example Automation:
- service: notify.entity_id
data:
message: "This is the message"
title: "Title of message"
data:
url: "https://www.home-assistant.io/"
sound: pianobar
priority: 0
Component specific values in the nested data
section are optional.
To use notifications, please see the getting started with automation page.
When sending a notification, optional parameters can also be set as per the pushover API documentation.
Example notification triggered from the Alexa component for an intents is shown below which also uses Automation Templating for the message:
{% raw %}
# Example configuration.yaml entries
alexa:
intents:
LocateIntent:
action:
service: notify.notify
data_template:
message: "The location of {{ User }} has been queried via Alexa."
data:
title: "Home Assistant"
data:
sound: falling
device: pixel
url: "https://www.home-assistant.io/"
{% endraw %}