For scenes, it’s something I’d like to add to Gladys: the ability to track the execution of scenes in the UI in a simple and clear way.
On that, we talked about it recently here if you’re interested:
Ok I understand better now.
In fact Gladys and Gladys Plus are two different things:
- Gladys is a local program that runs on your machine (Raspberry Pi, server, NAS) at home.
This program has a REST API which is used by the local frontend and this API is documented here => https://apidoc.gladysassistant.com (the link you posted above) - Gladys Plus is a cloud proxy that gives access to a user’s local instance from anywhere in the world. This proxy has an end-to-end encrypted Websockets API that allows you, when you access the frontend at plus.gladysassistant.com, to see the same thing as your local instance. The Websockets API is for frontend use only and is not intended to be used by the user. This proxy also has an « Open API », which by its nature is not end-to-end encrypted (but is encrypted in transit via SSL), which allows sending sensor states and your phone’s locations to your local instance. Because of the nature of this API (not end-to-end encrypted), I haven’t for now added any read routes, only a few write routes. I can add read routes later but I want it to be clear with the community that if we add read routes (optional), the Gladys Plus proxy will therefore see the traffic passing through (which wasn’t the case before).
I hope my explanation is clear 