github
/
apprise
mirror of https://github.com/caronc/apprise
1
0
Fork 0
Code Issues Releases Wiki Activity

Updated Notify_homeassistant (markdown)

master
Chris Caron 2021-08-02 15:47:53 -04:00
parent 846a3b05e1
commit 70f7f5080b
1 changed files with 11 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
Notify_homeassistant.md

@ -47,7 +47,7 @@ Send a Home Assistant notification:
```bash
# Assuming the {hostname} we're hosting Home Assistant on is just myserver.local (port 8123)
# Assuming our {access_token} is 4b4f2918fd-dk5f-8f91f
apprise -vvv hassios:///noreply@myserver.local/4b4f2918fd-dk5f-8f91f
apprise -vvv hassio:///noreply@myserver.local/4b4f2918fd-dk5f-8f91f
```
Send a Home Assistant notification that always replaces the last one sent:
@ -55,5 +55,13 @@ Send a Home Assistant notification that always replaces the last one sent:
# Assuming the {hostname} we're hosting Home Assistant on is just myserver.local (port 8123)
# Assuming our {access_token} is 4b4f2918fd-dk5f-8f91f
# Fix our Notification ID to anything we want:
apprise -vvv hassios:///noreply@myserver.local/4b4f2918fd-dk5f-8f91f?nid=apprise
apprise -vvv hassio:///noreply@myserver.local/4b4f2918fd-dk5f-8f91f?nid=apprise
```
Secure access to Home Assistant just requires you to add an `s` to the schema. Hence `hassio://` becomes `hassios://` like so:
```bash
# Assuming the {hostname} we're hosting a secure version of Home Assistant
# is accessible via my.secure.server.local (port 443)
# Assuming our {access_token} is 4b4f2918fd-dk5f-8f91f
apprise -vvv hassios:///noreply@my.secure.server.local/4b4f2918fd-dk5f-8f91f
```