From ed65921a7349de6b1e8c5bbef50a23b6d65060bd Mon Sep 17 00:00:00 2001 From: Chris Caron Date: Mon, 23 Jun 2025 20:51:01 -0400 Subject: [PATCH] Updated Notify_homeassistant (markdown) --- Notify_homeassistant.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/Notify_homeassistant.md b/Notify_homeassistant.md index 48410d0..59dcd8c 100644 --- a/Notify_homeassistant.md +++ b/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: * `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://: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 | Variable | Required | Description | ----------- | -------- | -----------