Been progressing on my Ezlo Plus journey this week. I few more thoughts for those trying to decide to move forward from Vera.
- The ezlogic.mios.com web page to build scripts and scenes (called MeshBot) is far more powerful that Vera. I am still early in the learning curve but it is obvious you will be able to do things easier than complex LUA scripts for everything. The advanced programmer might prefer the old ways but people that are lower skilled in programming I think will like this more. It more intuitive, highly graphical interface. Big plus in my mind.
- The AND capability for triggers is significant. I looked at some of the LUA code I had in my Vera and many of the pieces were chunks of code in a scene that added additional test cases before running the scene action. In essence this was code in LUA to implement an AND function in a much more laborious and awkward way. Vera always had the OR capability for scene triggering (just add more triggers) but it didn’t have the AND. I like the new way better, less obscure LUA code creation required. This is a big plus as well.
- I haven’t figured out how to use Variables in MeshBots yet. I presume these are all global variable but I’m not positive. I see how you create them on the interface but not sure how to use then as triggers for a MeshBot or a test variable in a LUA script. I’m sure its possible but haven’t found any sample code for variables that would speed up my learning.
- Doing a Ezlo Plus reboot is too obscure. I spent 20 minutes searching through the ezlogic.mios.com function trees before I found it buried at MIOS/Controllers/Function/Maintenance. It seems it could warrant a dedicated line under the Function pull down (reboot) instead of burying it in the more obscure Maintenance/Remove tab. I still haven’t found how to reboot Ezlo Plus from the iPhone app.
- I do have a bug where I can’t delete some old Lua Scripts I was playing around with. I get an error when I try to delete them on the web interface (anonymous plugin required) and in the iPhone (Error, Sorry, something unexpected happened, please try again later). Trying later doesn’t help. So there a bug to fix in the next release but more broadly the crytic error messages aren’t very helpful. if the goal is to make this more applicable to broader user base the Linux O/S style error messages aren’t useful, in fact they can be infuriating. Might be better just to parse them and say …“Error, we know why but you won’t understand so we won’t trouble you with it. Have a nice day.”…
- Going to spend some time in variable, expressions and meshbots next to improve my fluency. I suspect I have much to learn in these areas.
Just some more thinking for someone who made the plunge over from Vera. Some issues but the good seems to outweigh the bad.
p.s. having a system that is being worked on with regular updates is also a plus. Vera was essentially EOL (end of life) for a few years now. At the least getting periodic releases give you hope again!