We’re happy to release a new Ezlo Linux update v. 1.0.25 for Vera Edge and Ezlo Plus controllers: New Features:
Added support HTTP Lua module
Implemented Lua API for changing items value of other plugin.
Bug fixing on Z-Wave and Zigbee devices
Issue with no “http_connection_closed” broadcast when the connection is closed via http.close_connection(id).
Issue on Z-Wave devices with “electric_meter_amper” that is updated only when the hub is restarted. Ampere meter not changing value instantly once pairing a device supporting it (for example pairing a switch and adding some load to it - e.g. connect a bulb)
Attached you can find the latest API documentation with the new features http_module_API.pdf (40.0 KB)
for http requests can you give us a quick creation system to create links to the vera please ? A request that would read in the vera and create virtual devices to select for example: this would save users a lot of time and ultimately allow a smooth migration to the Ezlo system
The http API on the Ezlo FW means a plugin can be created that can communicate using HTTP. It does not give any integration with Vera nor will it now allow the query an Ezlo Hub with http commands. The API is a building block for plugin writers.
I am trying a simple bridge so you see some Vera devices on an Ezlo, but that will not be the basis of a full working bridge. Well, at least not for now, who knows what the future brings.
Its all well and good having the full Ezlo API’s for plugin developers to be able to create plugins.
But end users need a simple and easy to understand single line HTTP API interface / web server for controlling their Ezlo hub devices and scenes from other devices and apps on their LAN.
Such as the existing “Luup Requests” feature we have in Vera today.
And also it needs to work in reverse for example to have a virtual on / off switch on the Ezlo hub to send out HTTP commands or SSH os.execute commands wget / curl etc, to the target device on the LAN, perhaps to a router to control a VPN client on / off. For devices that likely won’t be natively supported by Ezlo.
Could this be automated / scripted somehow for the end users ? For testing purposes.
Obviously if I can quickly and easily get a virtual device copy on the Ezlo hub of all my real devices on the production Vera hub, then I can more quickly start testing the new Ezlo dashboard app and the inbuilt rules engine, rather then messing around for days trying to create virtual devices on the Ezlo hub manually to try and replicate the real devices in Vera.
No one in their right mind is going to start unpariing Z-Wave devices from the relatively stable Vera unit for testing the Ezlo platform. I have only a few spare / old Z-Wave devices I could pair to an Ezlo hub.
Obviously the more devices we have on the Ezlo hub real or virtual we can test it out better and start building new dashboards.
Presumably it will be Vera Luup Requests http commands that the virtual devices on the Ezlo hub will be using to control the Vera devices.
So do we have the same Luup Requests feature on the Ezlo hub yet or is it planned?