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 2025-06-23 20:51:01 -04:00
parent 7c4539af27
commit ed65921a73
1 changed files with 0 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Notify_homeassistant.md

@ -23,12 +23,6 @@ The other thing to note is that Home Assistant requires a `notification_id` asso
So by default Apprise will generate a unique ID (thus a separate message) on every call. If this isn't the effect you're going for, then define your own Notification ID like so: So by default Apprise will generate a unique ID (thus a separate message) on every call. If this isn't the effect you're going for, then define your own Notification ID like so:
* `hassio://{host}/{long-lived-access-token}?nid=myid` * `hassio://{host}/{long-lived-access-token}?nid=myid`
### Notes
- **HTTP vs HTTPS**: By default, Apprise examples use `http://` and port `8123` because this is the default for local/internal deployments of Home Assistant. In production, it’s strongly recommended to place Apprise API or Home Assistant behind a reverse proxy (e.g., NGINX, Traefik) that handles HTTPS termination.
- **Browser Access**: Using `http://localhost:8123` or `http://<your-ip>:8123` allows for easier development and testing without browser certificate warnings. This is especially useful in non-public or home network environments.
- **Custom Ports**: Port `8123` is Home Assistant’s default, but can be changed. Be sure to match it in your URL.
### Parameter Breakdown ### Parameter Breakdown
| Variable | Required | Description | Variable | Required | Description
| ----------- | -------- | ----------- | ----------- | -------- | -----------