client VS UniFi-API-client

PHP has extensive API support, offering developers a robust foundation for seamless integration with various services and technologies. Whether interacting with databases, third-party applications, or web services, PHP's versatile ecosystem and well-documented APIs empower developers to create interconnected and feature-rich web applications. This extensive API support enhances PHP's versatility and simplifies the development process, enabling developers to harness the power of external services and libraries effortlessly. One example is the OpenAI PHP which is a supercharged community-maintained PHP API client that allows you to interact with OpenAI API. Explore more here: https://github.com/openai-php/client

Also, let’s use the OpenAI PHP library to work with the REST API of OpenAI. This library is a supercharged community-maintained PHP API client that allows you to interact with OpenAI API. We have to install it via composer :

I ran into this the other day. If it's an option, you should use the openai-php/client library.

You should give the OpenAI PHP Client docs a read, they are great.

There are some packages you can use. Saw this today on another sub: https://github.com/openai-php/client

Anyone already compared the linked library with Nuno’s https://github.com/openai-php/client?

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