From 545f3acda26e032edb7c1c4cf81a2c5763654e49 Mon Sep 17 00:00:00 2001 From: Chris Caron Date: Mon, 23 Jun 2025 20:36:09 -0400 Subject: [PATCH] Updated Notify_homeassistant (markdown) --- Notify_homeassistant.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/Notify_homeassistant.md b/Notify_homeassistant.md index 91a6998..aea0ac6 100644 --- a/Notify_homeassistant.md +++ b/Notify_homeassistant.md @@ -32,6 +32,12 @@ 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 | ----------- | -------- | ----------- @@ -73,3 +79,7 @@ Send a simple notification using only your Long-Lived token to your instance run apprise -vvv hassio:///my.server.local/4b4f2918fd-dk5f-8f91f ``` +### Troubleshooting + +- If you receive a 401 Unauthorized error, ensure your token is valid and has not expired. +- If you are using HTTPS with a self-signed certificate, you may need to adjust your Home Assistant or Apprise configuration to allow unverified SSL connections. e.g. `hassios://my.secure.server/?verify=no`