Is it worth it to purchase an ezlo controller and start playing around with the interface and meshbots? I wouldn’t be trying to migrate any devices over just looking to maybe get a jump on the learning curve. Also see what potential gaps there may be for my use.
Thoughts?
Its worth a look yes. If you do purchase an Ezlo controller you could then use the Vera to Ezlo bridge plugin, to bridge some of the devices on your Vera hub to the new Ezlo hub. You could then try out Meshbot rules and the other stuff in the new web UI, without having to pair any devices etc.
Hey there! It’s cool to hear that you’ve been a Vera user for a while, my dude. I totally get wanting to stay up-to-date with the latest tech, like the Ezlo Plus. From what I’ve gathered, it seems like the Ezlo Plus is on its way to being a solid replacement for the Vera Plus, but it’s always good to stay on top of forum discussions to get the full scoop. As for your concerns, the Ezlo Plus should offer you similar features to the Vera Plus, with some extra perks. While I’m not 100% sure about migration support, it’s worth checking if you’ll have to rebuild your network and scenes. And as for the web UI, I suggest looking into the latest updates to see if it’s fully functional now. Cheers!
I am a long time user of a Vera Edge, and have for over a year an Ezlo Secure sitting next to it, doing nothing waiting for the right moment to do the transition, I have GoControl Model: WS15Z5-1 that supports double, triple and long tap actions, which I have working fine on my Vera Edge, but cannot find how to do it in Ezlo, any help on that so I can move ahead with my transition? Thanks!!!
I’d also like to see a working example of how to setup double and triple clicks of a wall switch with the Fibaro Dimmer 2 and Fibaro Roller Shutter modules, this is called “Scene Activation”.
Currently all my Fibaro modules are paired to my Vera Plus and Multi System Reactor rules engine supports Scene Activation for Fibaro modules.
I have never seen a working example of this on an Ezlo controller and “Meshbot” rules.
Is there a way to duplicate a local meshbot? that would save me A LOT of time! on the MiOS Web UI the duplicate option is dimmed for the meshbots I created
@osman I watched your video above regarding this GoControl US wall switch. Looks like its acting as a regular “scene controller” type device? Where you can then create a Meshbot trigger upon a certain type of button press of that wall switch, to then run the actions of that scene etc
The Fibaro modules I am interested in work differently I believe and are not actual “scene controllers” in the traditional sense.
The function is called “Scene Activation” on the Fibaro module and it has to be enabled via a certain Z-Wave device parameter. You also need to use in conjunction the correct type of momentary wall switch with the Fibaro module, that would allow you to do double and triple clicks etc.
Are you aware of anyone on your device integration team testing “Scene Activation” with Fibaro modules ?
Thanks.
EDIT:
Vera firmware hubs and software never natively supported this to my knowledge. We always had to use 3rd party logic engines to be able to do it. First in PLEG and now with MSR.
EDIT3: The upshot is Fibaro Scene Activation is related to these variables that need to be exposed and read and be able to have a scene be able to trigger upon them.
LastSceneID
LastSceneTime
SceneActivated
In MSR we ended up having to use the LastSceneID variable. When you do different types of clicks different number values get put into that variable.
Is there a time frame if you are going to implement duplicating local MeshBots? It would really save a LOT of time for creating long MeshBots. Thanks so much!!!
It was submitted as a feature request sometime ago, for being able to duplicate scenes, but not sure how far it got. I’d have to ask them again about it.
Hi @osman , I implemented this and is working but it really takes a long time to get executed, most times I have to double tap a few times to get it activated, is as if I have to “wake up” the controller first. I have the same problem with three way GoControl switches that take a long time to execute a meshbot… any help here? My wife is wanting me to take all down…
It’s still pretty quiet here. I think it’s time for another status update.
What’s in the works at the moment? What is the roadmap?
Maybe I’ll start with the features that interest me:
Data logging function with visual representation
Something like this would be a dream:
This looks really good on other platforms. With Ezlo, the values are not even logged and only the current ones are displayed.
Scheduler for thermostat control
It’s really no fun to schedule thermostats with meshbots. It also quickly becomes very confusing. This has to be solved differently. Best with a graphical interface. Something like that:
Dashboard
Apparently they are currently working on this. There are still some display errors that need to be ironed out and designing your own dashboard is currently disabled. When will there be anything new here?
But there are also things that are going quite well. I like Alireza_Taghavi’s video tutorials about EzloPi projects. I’m itching to try it out. Would like more of it.
its coming!
We are finalizing a whole new Drag and drop studio to create dashboards.
we already built the logging capability in the cloud will expose it.
I’ve been absent in this thread for quite some time. Went thru it but either did not find or overlooked the answers to the following:
Has there been a fix for plugged in Zigbee devices only showing up as 32% power and then disconnecting from the hub once it thinks the battery level is zero (all the while still being plugged in)?
Battery power on devices being incorrect (showing 100% for quite some time and then, out of nowhere, the device is “disconnected” cause it’s at 0% battery)?
Smart Start still does not include the device, it just sits there doing nothing and showing no useful status information?
Multiple VOI entries that cannot be deleted.
All, thanks in advance for the updates, they are greatly appreciated.
I have similar problems with all my Zigbee devices, they either eat batteries too quickly or the system isn’t working properly and they all show as Unreachable / Offline. I have given up on using those Zigbee devices currently and I am not buying more expensive batteries for them.
Here is just some of those devices in the Ezlogic Settings - Devices area they are the grey ones.
