Hi Everyone,
At @ranneman 's request I am creating a post just for this topic.
We are currently working on a Web based UI that will enable our users to
1-Handle all their Device Settings
2-Rule Engine (you can call it next gen Reactor with much more capabilities)
Hoping to release it this summer (if not by summer) and will be a native app, meaning you don’t need to install a plugin etc to operate it.
Please do NOT provide feedback on these preliminary screenshots yet because they don’t represent the full picture. You will have plenty time to provide feedback once we start releasing it
We intend to release it in few steps, so that our community can test it.
-We will first introduce the framework (without much functionality) to make sure the framework, api calls etc all working…
-Then we will add more functionality as we go along and hopefully in summer (or by summer) you guys will have capability that is next gen to reactor.
I was asked the benefits of doing Ezlo Rule Engine natively vs as a plugin:
Here is the explanation
-Native C++ implementation is working much faster than combo of HTML/Java Script/Lua running as local service: All these capabilities will be implemented in C++ inside the Ezlo hub.
-All these capabilities will be exposed as API so that plugin developers can easily use these functions as well as mobile apps or custom software developers developing software to work with Ezlo Hardware.
-Remote management of these Rules will also be possible because of native implementation. (all rule engine functionality will be available from any location in the world)
We should create a Poll with all these names and let the community choose.
Please keep replying with your suggestions. By end of this week, we’ll collect all these suggestions and create a Poll with it. We’ll let it run for 1 week.
