hass-configurator VS apprise-api

hassconfigurator - Home Assistant online configurator container from https://github.com/danielperna84/hass-configurator

- [a web service (you host)](https://github.com/caronc/apprise-api) that can act as a sidecar. This solution allows you to keep your notification configuration in one place instead of across multiple servers (or within multiple programs). This one is for both Admins and Devs.

A lot of systems have already adapted to it such as HomeAssistant, Apache Airflow, ChangeDetection, Uptime Kuma and many others (<https://github.com/caronc/apprise/wiki/showcase#integrations>) which shows the commonality. Mailrise is an incredibly talented program that converts Emails sent to it to trigger notifications via Apprise.

*What else does it do?*

- Emoji Support (:rocket: -> ) built right into it!

One of the big features added is now the Apprise Web API can accept Attachments (all shapes and sizes) and then relay it to all of your endpoints. In the past you were limited to attachments only if you chose to use the CLI tool or write directly with the Apprise Python API.

Apprise is built into Home Assistant. You can centralize all of your configuration on a self serve web version of it and store all of your favorite endpoints there.

Oops forgot about that. Could host this and call it from node tho https://github.com/caronc/apprise-api

Looks like there is a server: https://github.com/caronc/apprise-api

So you can use the Apprise API from your app and have it trigger any number of notification services, configured in the Apprise config or web UI.

I just updated the (Apprise) API now. There was actually a bug with it and the new Apprise (v1.0.0) version (yikes!). This has been fixed now and I pushed a update to the API (v0.8.0) just now.

apprise-api - Apprise-api(https://github.com/caronc/apprise-api) Takes advantage of Apprise(https://github.com/caronc/apprise) through your network with a user-friendly API.