Developing an http integration like the mqtt integration

Feature description
To be able to have an integration module like the MQTT module where we can also create objects but not with triggers tied to an MQTT subscription and instead HTTP, and change the device state according to an HTTP command with a configurable interval (a poll every x milliseconds)


example: on my IPX800 I can activate/deactivate relay 1 of my IPX only via a Gladys scenario

So I would like to be able to create an object « IPX800-Relay 1 » that I would control like any other element in Gladys!
I don’t know if other hardware than those from GCE-electronics could be concerned by this type of request but I think there must be some (Denkovi for example)

Finally have a usable API for all Gladys elements?

Not really; for example, in the MQTT interface you can create a lamp or outlet object and link it to an MQTT publish or subscribe. The idea is to add the ability to do this via an HTTP PUT or an HTTP GET but make it configurable — for example, send a GET every x milliseconds (with a subscribe it’s the mosquitto engine that listens continuously; with HTTP to get the state you have to poll frequently).

Ideally, it would be like having an HTTP broker to which you would give the list of items to monitor via GETs and the list of PUTs to command, which you would link to ‹ virtual › objects in Gladys, but the end result is the same as above!!! :+1:

But maybe the API is the same…

Interesting integration to control tablets that uses Fully Kiosk Browser.
In my scenes I control my tablet via sensors and HTTP requests.
As a result I end up with many scenes that send the same request.
Whereas I could have a tablet device with on/off, alarm, etc. features in an HTTP module