The latest Android beta app now supports adding Lua code in Scenes as well as sending http requests.
I hope They add a password for logging to unit locally
Super excited about Ezlo! Was just researching replacement options for my VeraLite. She has served me very well since January/2013 but has been experiencing sporadic issues as of late.
Hello, I have a few questions about the the new EZLO platform. Specifically will it support the following. If not now, but maybe in future?
- Honeywell WiFi Thermostats Plugin (I think you stated you were developing this)
- Scenes that had LUA Code to do various numerous things
- Ability for other local systems such as BluIris trigger a scene in EZLO as as we can do now in Vera using direct http calls (data_request). For example: YourServerIP:3480/data_request?id=action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=RunScene&SceneNum=YourSceneNum
- Will all of the lua scripting functionality and scripts directly portable from Vera to EZLO?
Good morning BGILL,
Here is the integration request: https://jira.mios.com/browse/ECS-125
Scenes with Lua code is a feature we are currently working on adding. Here is the feature request: https://jira.mios.com/servicedesk/customer/portal/72/ECS-477
I have put a feature request for this point. Here is the request https://jira.mios.com/servicedesk/customer/portal/72/ECS-478
They are not compatible because they have a different system, in other words, you would have to set it up from scratch.
Thanks so much for your prompt reply.
Like so many others of your faithful Vera die-hard users/customers, when I heard the news of the discontinuation of the Vera hardware, frankly it sent shivers down my spine. I like many others have probably easily invested close to 100 hours of time configuring, refining, debugging and otherwise cobbling together a combination of core code, lua scripts, plugins and the like into an integrated solution that works well for me. I personally operate 4 Vera controllers at 4 different homes.
It will be a nightmare if everything has to be re-done and reengineered all over again.
Anyhow, I have confidence that your team will make this transition as painless as possible (hope). I realize that it won’t all be there on day1. It seems like we have probably a couple of years at least to work things out.
Regarding item #3 - I see you added a feature request, however I stumbled across a post last evening that seems to suggest that this capability is or will already be there?
Regarding item #1 - On this post “Ezlo Platform FAQ” from January 6th, Sorin stated the following:
“We plan to develop plugins for the Ecobee and Honeywell thermostats, as well as Philips Hue lights.”
I am assuming and hoping that you are referring to the redevelopment of the current Honeywell WiFi Thermostats Plugin as I use this plugin extensively with 2 of my 4 Vera controllers. I am sure there are many users of this popular plugin.
There are many advantages to this plugin which uses the Honeywell API as it doesn’t tie us to using only ZWave capable Honeywell Thermostats.
If this is not the plugin already planned for development, then I will add the feature request as you suggested.
Please, note, I am unable to view the Feature Requests you referenced above. The system advises me that I don’t have permission to review the requests. (Perhaps it’s because I only today created my account on the platform where the feature requests are published.)
Thanks in advance.
You can do that now already, just follow my guide on how to construct the HTTP(S) command to run the scene.
You can also run LUA code in Ezlo scenes now as well I believe.
Thanks for your reply.
Yes I saw your post about that last night. So yes I believe you are correct, this is exactly what I was after. CW's IDIOT GUIDE - To Ezlo platform HTTP API commands aka Luup Requests
- That’s why I was asking why Jesus was suggesting I create a feature request. You have indicated that it’s already supported. So this is what I was asking about. If in fact it is there, then it would not make sense for me to submit a feature request to Ezlo.
Setting up your lua codes that way is not a native feature, hence why I put the feature request. But that is something you can try in the meantime, of course.
For legacy units there won’t be new integrations or plugins as we will only be providing firmware updates to fix bugs and general issues. We will have to wait for our engineers to determine how the integration is done for the Honeywell thermostat with the new Ezlo controllers. If you use the plugin for other purposes, please specify them so I can put a feature request separately.
I’m not sure why it isn’t visible as we have configure it to be visible to the public, we will be looking at this matter.
What is not a native feature?
The HTTP Server API is native.
Thanks for the clarification.
I use the current Honeywell WiFi Thermostats Plugin to control my Honeywell Thermostats at my homes. So that part is standard.
However, I also have several scenes with Lua Scripts that do different things, such as detect if both apartments (tenants) in my home are away, if so I reduce the set point.
I also have scenes with Lua script that synchronize two thermostats that essentially control 1 furnace. I have about 5 different scenes that are using Lua script to vary the heat set point up/down on these thermostats. However I would assume this is would not be considered a special use of the plugin. Its simply the need to be able to get/set the thermostat (any type of thermostat) properties via Lua scripting in a scene. I require the Honeywell WiFi Thermostats Plugin, and also Lua scripting capabilities for all thermostats, in fact Lua scripting capabilities for all devices. I understand that is being worked on.
If a feature request is required, would you like me to submit it or will you?
I’m not sure what he’s talking about.
There is already a HTTP API on the Ezlo hubs as covered in my guide.
And as you can see in these screen shots you can now add Lua script to Ezlo scenes.
Yes I see that. So I am unsure what he is talking about also. I know I asked 4 different
related questions, so perhaps his response was not intended for the HTTP request.
Your guide explains how to do what I call an inbound http/https request to invoke a scene assuming I understood your tutorial correctly. The screen capture above would be going the other way, invoke something on the web or local network (such as BlueIris) as part of a scene. So this means http requests both inbound and outbound are currently supported and working. Correct? Assuming that I understood your tutorial showing how to do this.
The guide I wrote is about how to send http requests inbound to the Ezlo hub to control things, ether have a scene run or operate a device on the Ezlo hub etc.
As for outbound http requests, I’ve not tested it, but if it works the same as lua script on the Vera hubs, then you could create a scene with lua script to send out a http request for example
I’ve just tested it by creating a new scene with a lua script that contains
This should make my Google Home speaker say “This is a test”.
However when running this Ezlo scene nothing happens.
The same code on my Vera hub does work OK
So we need some confirmation from the Ezlo staff why “luup.inet.wget” doesn’t appear to be working?
Using curl to send out a http command from an Ezlo scene works OK just tested that now.
But using wget doesn’t appear to be working.
They should be confirming on this new thread.
Rather than sending out a http request as part of lua script, there is actually a dedicated action for http request you can select in your scene.
I had understood you wanted the lua code and the http request as an “activation event” or trigger. Also, on the previous hubs, under Apps there was an option to send luup code manually, I had understood thats what you wanted to do. Hence why I put the feature request.
I don’t think that’s what he was asking for.
However both of those things you have mentioned would be good to have. Especially the Lua code test box you refer to.