Another option might be Multi System Reactor. The first version that supports Ezlo hubs has just been released.
If I can control the colours of the RGB bulb paired to the Ezlo Plus hub via MSR, then I will be able to use MSR’s own much simpler HTTP API and create some different colour “scenes” in MSR and just send GET commands from Home Remote dashboard app to MSR to run those “scenes” etc to in turn control the bulb, effectively cutting out Ezlo’s own HTTP API that requires POST for controlling RGB lights.
I believe the MSR integration uses the wss web socket for interacting with the Ezlo hubs.
I have had it confirmed by an Ezlo developer that it does require POST to set colours on an RGB light, which makes it more difficult for end users to use.
The whole point of the HTTP Server API is for end users to be able to use, not just for developers or more technical types.
So it should be made more simple like the current Vera Luup Requests HTTP API.
Every time they make something POST it ups the difficulty. Also I have some other apps I use that don’t support sending POST commands, so it should all be GET like Vera is now in my opinion.
I know it’s not always possibile, but my own Virtual Plug-in is supporting curl commands, so you should be able to map an Elzo command this way. I’m using it for my own endpoints accepting POSTs and it’s rock solid (and it’s using RGB virtual devices as well). Give it a try.
I now thanks to the MSR developer, have a dashboard page like this, that works and changes the colours of my RGB bulb paired to the Ezlo Plus hub.
As I said it’s a shame the official Ezlo HTTP Server API can’t control colours on a light with GET instead of the more complicated POST.
It can be laggy sometimes however changing colours, when clicking on these buttons too quickly. Likely the Ezlo HTTP web socket API being slow to respond ?
