Ezlo Development going strong?

It’s sad but not surprising. There was a lot energy and excitement early on but it seems to have fizzled. It seems like a lot of the old faithful Vera crew have moved away from Ezlo.
I think with Vera they has a good framework to build Ezlo from but for some reason it just hasn’t progressed.
At this point I’m having to think of a backup strategy because I’m uncertain of how long the Vera platform will be supported and Ezlo unfortunately is still not a viable replacement.

The silence is deafening.

Hello everyone,

The integration process for this device has encountered several challenges, which has led to the creation of multiple new tickets. Our team continues to work on these issues, as well as on the energy metering system, which is still under development and not yet ready for release.

In the coming days, we will be rolling out new updates across the cloud, firmware, web UI, and mobile applications. We truly apologize for the delay—it has not been an easy task to fully investigate the status of this request, but please rest assured that progress is ongoing.

Thank you for your patience and continued feedback.

Its tough seeing these sorts of threads here still. 19 months ago I made the decision to move to Hubitat after too many Ezlo issues due to missing functionality and immature code. I see that hasn’t changed much. Clearly the development team on this is significantly under resourced and can never catch up.

As for me it was a learning curve moving to another hub after 12+ years on Vera and 2-3 yrs on Ezlo but the move was worth it. Massively better supported platform. Code drops 2-3 times a week (for beta users). Very stable platform. Rule machine is different than scenes and meshbots but probably a little more powerful and very stable. Tons of add in apps and endless devices (Z-Wave, Matter, and Zigbee) plus a hugely active user community.

I still have an Ezlo I use on a summer cottage but my principle residence is too complex and I don’t have the appetite for the drama that comes with Ezlo.

I see some of the same names struggling with Ezlo here but you owe it to yourself to look at alternatives. Ezlo just doesn’t seem to be fully committed to this product line.

edit: 2 days later and this is the most recent post on this forum? You get upwards of 40 posts a day on Hubitat forum…

Dashboard
Not looking for major updates other than I have multiple locations (homes) with Ezlo controllers deployed. It would be nice to see a dashboard that at least provides some organizational structure. Home, Rooms, etc. Even if I could just filter based on controller and have Views. We used to have that in the old Vera Home (yes been using your products since 2013.

Geofencing
Would be nice but it would really require a way to set Home, Away, status of all the devices and so until thats been made easier to configure, I personally wont use the Geofencing.

I think first priority is always UI and then add the features… Everyone else has incorporated Home and other UI essentials, why not Mios.

There’s also some trouble with the radiator thermostats at the moment:

I’ve noticed that the thermostat temperature doesn’t match the temperature displayed on the dashboard. If I turn the thermostats off and on again in the dashboard, the temperature set on the thermostat is initially adopted/updated. But then a very strange phenomenon occurs. The thermostat switches every few seconds between the temperature set on the thermostat (22°C) and the temperature previously displayed incorrectly on the dashboard (18°C). If I then try to adjust the temperature on the dashboard, it even switches back and forth between three temperatures:

TRV

Hello @Odysee

Are you experiencing the same issue in the MiOS app on your mobile device?

I just took a look at the MiOS app. I usually use the web frontend. At the moment, I can’t reproduce the error. However, I can describe the situation in more detail. Perhaps that will provide some insight into what might have happened.

I control my thermostats via Meshbots, which are started at specific times. The Meshbots always list all thermostats with their target temperatures. This seems to be working so far.

I just noticed that all the target temperatures in the dashboard were set to 18°C, even though they should have a higher temperature based on the time. A look at the thermostat showed that the correct higher temperatures were set. So I looked into why it wasn’t updating. Reloading the website didn’t change anything, so I set a thermostat from Heat to Off via the dashboard, which was done. Then I set it back to Heat. The temperature set on the thermostat was then correctly displayed on the dashboard. But when the thermostat suddenly started making a noise every few seconds, I became suspicious and first looked at the display on the thermostat and then at the dashboard. Both seemed to be changing the temperature back and forth as if by magic. Then I tried adjusting the target temperature again on both the thermostat and the dashboard, which even resulted in a third temperature changing back and forth. Eventually, things calmed down and the target temperature remained constant.

At the moment, everything seems to be working as it should again. I manually started a Meshbot, and the dashboard and app adopted the correct temperatures. Then I set the temperature on the thermostat, which is also correctly reflected in the app and dashboard.

Feel free to check the log files on my controller to see if there’s any further information available.

1 Like

There was some unusual behavior again. First, a few thermostats weren’t set correctly. The corresponding Meshbot wasn’t running correctly. Then I took a thermostat that was set to 18°C ​​(which was also correctly displayed on the web frontend). I manually set it to 22°C on the web frontend. It then started switching back and forth between 20°C and 22°C every second (visible on both the thermostat and the web frontend). I wanted to check the MiOS app, but by then it had calmed down and was staying at one temperature.
I wouldn’t have ruled out the possibility of the thermostat being the problem, but today it was a different thermostat than yesterday. And I think it’s rather unlikely that two devices are acting up at the same time.

I have been with Vera / Ezlo since about 2015 and have never felt more frustrated in time invested to keep things running… I have debated switching to hubitat or others, but the main issue that keeps me from moving is no one has 100% of devices in their system and that means either beg for adding or replace.

I’ve been wondering the same thing. It’s been really quiet lately — no noticeable updates or communication from the team. Hopefully, they’re still working on something behind the scenes, but it’s definitely starting to feel a bit stagnant.

The announcement was over a month ago now, and I haven’t seen anything yet. What about updates for cloud, firmware, web UI, and mobile applications? Is there any progress on those?

Hello @Odysee,

Android is scheduled for release on November 17th, and iOS is delayed but still in progress.

On November 5th, 2025, there was another MiOS update for Android. Was the update you mentioned released early, or was it just a minor interim update with a major one coming on the 17th?

The new features list states “Fixed issues with adding locations.”

I assume this refers to geofencing? So I tested it. When I go to Geofencing and select “Add new location,” the application crashes.

Hello @Odysee

We apologize for any confusion regarding which location was being referenced. While the plan specifies the controller location, it appears there was some misunderstanding with the geofencing location. We’ll ensure clearer communication about this going forward.

The update released on November 5th specifically addressed this issue. Furthermore, a major update is planned for November 17th, which is currently undergoing QA testing.