Update pushover on how to specify a device (#12837)

* Update pushover on how to specify a device

Correction of description after the pull request #31647

* Fix typo and a little less speci*

Co-authored-by: Fabian Affolter <mail@fabian-affolter.ch>
This commit is contained in:
androidemil 2020-04-12 12:03:35 +02:00 committed by GitHub
parent b84f596358
commit 01c2cd3189
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -58,9 +58,25 @@ Component specific values in the nested `data` section are optional.
Image attachments can be added using the `attachment` parameter, which can either be a valid URL for an image (ex: `http://example.com/image.png`) or a local file reference (ex: `/tmp/image.png`).
To use a specific Pushover device, set it using `target`. If one of the entered devices doesn't exist or is disabled in your Pushover account it will send a message to all you devices. To send to all devices, just skip the target attribute.
```yaml
- service: notify.entity_id
data:
message: "This is the message"
title: "Title of message"
target:
- pixel3
- pixel4a
data:
sound: pianobar
priority: 0
```
To use notifications, please see the [getting started with automation page](/getting-started/automation/).
When sending a notification, optional parameters can also be set as per the pushover [API documentation](https://pushover.net/api).
When sending a notification, optional parameters can also be set as per the Pushover [API documentation](https://pushover.net/api).
Example notification triggered from the Alexa integration for an intents is shown below which also uses [Automation Templating](/getting-started/automation-templating/) for the message:
@ -77,9 +93,9 @@ alexa:
message: "The location of {{ User }} has been queried via Alexa."
data:
title: "Home Assistant"
target: pixel
data:
sound: falling
device: pixel
url: "https://www.home-assistant.io/"
attachment: "/tmp/image.png"
```