Is Ezlo Plus Ready for Prime Time?

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.

Hi @augustov

Ezlo platform already supports GoControl Model: WS15Z5-1
Here is how you can pair the device, and use the button states in meshbots

Thanks @osman really helpful! Working on it now… just feedback that is really difficult to figure it out for a regular user. Thanks!!!

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

Not currently no, you cannot duplicate Meshbot rules to create another one based off the first one.

@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 ?



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.

Here is how its setup in MSR.

I am searching now for how we use to do it in PLEG.


Seems I linked to this thread in the past for the way we set this up in PLEG but it points to the old forum domain so can’t read it.,17409.0.html

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.


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!!!

1 Like

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.

Apparently its still on their roadmap and has been previously and continues to be investigated. No ETA however I am afraid.

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.

1 Like

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.

1 Like

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:

  1. 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)?

  2. 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)?

  3. Smart Start still does not include the device, it just sits there doing nothing and showing no useful status information?

  4. 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.

Hi @ryantatum20 , @cw-kid

Let us examine in detail those devices and see the actual reason behind it. @SaraV can you help on getting details about the problem pls.

Hello @ryantatum20 @cw-kid

Please check this recommendation to see if there’s anything that can make any improvements: Like with any wireless technology, checking the environment in which your devices are operating is important. Zigbee shares the same frequency band as the 2.4GHz wifi networks which means it might be possible to have channel overlaps due to a WiFi band that is shared with the Zigbee channel. Also, the same is true for Hue devices (if used) that are in the general area. Hue uses Zigbee. If the Hue happens to use the same Zigbee channel, problems can be expected. And finally, wireless is subject to the same physics as Wifi. Distance, solid objects and others can and will impact the wireless communication between devices.

Check for and resolve channel overlap with Hue/other Zigbee hubs, 2.4GHz WiFi. Build the Zigbee mesh in such a way that powered Zigbee devices with repeater capabilities can repeat the signal to fringe devices.) It could be that the Centralite devices do not broadcast as strong a signal as other devices, which could also explain some of the issues noted.

With those recommendations in mind and to be able to investigate further, would it be possible to provide a time frame or date between the device’s disconnections or inconsistent battery events? As well as devices details/models, relative distance to the controller, and controller serial numbers.

Hi @slapfrost

I sent Oleg my Zigbee device list already, but here it is:

Zigbee devices on Ezlo Plus 90000413

1. Centralite Door / Windows Sensor - 
"model": "3323-G"
Parent Device:
"_id": "6300fae6123e431226818306"
"name": "Centralite Door/Window Sensor"
Child Device:
"_id": "6300fae7123e43122681830a"
"name": "Centralite Door Temperature"

2. Centralite Motion Sensor -
"model": "3328-G"
Parent Device:
"_id": "61f0a3ac123e431284c14150"
"name": "Porch Entrance Motion"
Child Device:
"_id": "61f0a3ac123e431284c14154"
"name": "Porch Entrance Temp"

3. Centralite Water Leak Sensor -
"model": "3315-G"
Parent Device:
"_id": "61f0bce1123e4312a1900a1e"
"name": "Water Leak Sensor"
Child Device:
"_id": "61f0bce1123e4312a1900a23"
"name": "Water Leak Temperature"

4. Centralite Temp / Humidity Sensor - 
"model": "3310-G"
Parent Device:
"_id": "625034d1123e4312237332f5"
"name": "Bathroom Humidity"
Child Device:
"_id": "625034d1123e4312237332f8"
"name": "Bathroom Temperature"

Zigbee devices on Ezlo Secure 92033957

1. KonoZ Lux Thermostat
"model": "KONOZ"
"_id": "64d2352bc9efbc16e572cac4"
"name": "Thermostat (Lux)"

Hue Bridge is on Zigbee channel 11
WIFI Routers 2.4GHZ band is on Auto says its currently channel 3
Vera Plus channel 19 (0 Zigbee devices paired)

How do you tell what channel the Ezlo hub(s) are using? I couldn’t see any Zigbee settings in the mobile apps or the web UI.

Edit: I had to reboot the Ezlo controller(s) and then look in the ha-zigbeed.log log file.

Ezlo Plus (Main) Channel = 25 (4x Centralite Zigbee devices paired)
Ezlo Plus (Spare) Channel = 15 (0 Zigbee devices paired)
Ezlo Secure Channel = 25 (1x Zigbee device paired)

All my Zigbee devices the few I have are all battery operated and currently they are all sat in the same room as the Ezlo hubs.


This new beta firmware update mentions fixes for Zigbee device battery status.

I also have not visited this board for some time. I guess I just wanted to see if I made the correct choice when I made the tough decision to abandon Vera/Ezlo and switch to Hubitat + MSR + Home Remote. I certainly looks like I made the right decision, at least for me. Hubitat + MSR + Home Remote just works. No more excuses, no more broken promises, no more waiting forever - how many years has it been now waiting for the next release of Vera firmware or an Ezlo replacement that is “ready for prime time”? My Hubitat “suite” may not have the prettiest UI or the fanciest dashboards, or even the most powerful mobile app, but I have always been more into functionality than pretty or “wow”. Oh, did I mention that I have a completely local solution with zero cloud dependencies and EVL4 support?

Same with my Vera / MSR / Home Remote setup it just works. My Vera Plus has been rock solid for years and I never have to touch it or do anything with it. That setup is also local.

You could have a local setup with Ezlo / MSR also as MSR can use the Ezlo controllers local WS API.

But Home Remote doesn’t support Ezlo controllers and their new API which is a shame.

But yes the Ezlo Ezlogic web UI is only cloud based currently and will likely remain that way.