UniFi-API-client VS apprise

UniFiClientAlerts is a Dockerized application that monitors UniFi networks for new device connections and sends alerts via Telegram. It leverages PHP code from the Art-of-WiFi/UniFi-API-client for interfacing with UniFi Controllers.

Take a look at the API Client here, https://github.com/Art-of-WiFi/UniFi-API-client. You can use the client to create a cron job or scheduled task to run a script to cycle the port.

I'm using a UDM SE (runs Unifi OS) and have cloud management up and running via a fixed external IP, and an external captive portal using port 443. SSL certificate installed and up to date. I'm trying to connect to using the API as 'documented' at https://ubntwiki.com/products/software/unifi-controller/api. I haven't been a dev for a long, long time, and although I think I could probably mug my way through using the stuff at https://github.com/Art-of-WiFi/UniFi-API-client, I'm first trying simply to connect to the API using curl. I'm falling at the first hurdle: I just can't connect to the API at all.

Personally, I have scraped together a custom portal before using the PHP API client - https://github.com/Art-of-WiFi/UniFi-API-client - UniFi passes the MAC address of the device as a GET parameter called 'id'

We try to avoid external classes and dependencies to reduce the potential for trouble. Especially with something rather simple like a REST API. But based on the UniFi API situation, we decided to make an exception and go with the fantastic UniFi-API-client class for PHP by Art-of-WiFi that can be found over on Github https://github.com/Art-of-WiFi/UniFi-API-client. It’s actively maintained and offers the benefit of people reporting broken stuff so it’s a community thing to make the UniFi API usable even if Ubiquiti decides to change or remove stuff.

There is a well-documented and maintained (though unofficial) PHP API for managing/talking to the controller. We use it for automating mundane tasks like loading lots of Mac-to-vlan bindings. It is quite feature complete. https://github.com/Art-of-WiFi/UniFi-API-client

PHP API library: https://github.com/Art-of-WiFi/UniFi-API-client

- [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!

I tried it and it was nice but ultimately I switched to apprise

While I'm sure of Gotify and ntfy.sh, I'm not sure if Apprise will do the needful because on its github page(https://github.com/caronc/apprise) it lists all the paid and free notification services for integration so I'm assuming it is just a library like the one I integrated for my django api (onesignal library).

Could you add apprise notifications?

I use mailrise which hosts a private SMTP gateway for Apprise notifications.

As a perhaps simpler alternative to send.sh and notify.sh commands, check out the Apprise integration. Apprise supports many notification channels, including Telegram.