I’m somewhat in agreement. It seems to me that the Vera hub was much better at pairing with devices that were not officially on the list of included devices. I don’t know enough about z-wave but I thought that z-wave devices when asked will report their capabilities. I guessing that the Vera hub was better at determining a devices capabilities and pairing with the device.
I had to recreate my entire system, that’s excluding and including 90+ devices. The backups didn’t work, nor any of the other solutions that tech support had done to fix the problem. Their only solution was to factory reset my ezlo plus.
After reloading everything, somehow, I have an unknown device showing. I have no idea what it is, app displays “Can’t Detect Device”, and I cannot delete it (option grayed out/not available).
Devices are more responsive except for in the morning around 4:10am. I try to turn on the lights and turn off the fan in the bedroom and it takes over 40 seconds. Why, I don’t know. Maybe at that time there is something going on with the system (backup, update, etc). Does anyone have any idea about this lag at this time?
Rebuilding the zwave network with 90+ devices was a PAIN!!
Hello @ryantatum20
We are truly sorry for the difficulties you’ve faced while rebuilding your system. We completely understand that excluding and re-including more than 90 devices is an extremely challenging and frustrating task.
After thoroughly reviewing the case and your interactions with our support team, we’ve confirmed the root cause was several specific devices (mainly nodes 36, 160, and 185) flooding the Z-Wave network with excessive traffic. This caused significant instability and continuous restarts of the Z-Wave chip in your controller.
Initially, we attempted to resolve the issue by isolating and removing the problematic nodes and reviewing firmware versions. However, since the issues persisted, we determined the internal configuration of the controller was affected by corrupted data, meaning a backup restore was insufficient to definitively resolve the problem.
For this reason, a full factory reset of the Ezlo Plus controller was recommended as the final solution. While this procedure is extreme, it guarantees the removal of any internal corruption that could be causing the persistent failures you’ve described.
We understand this required significant effort on your part to reconfigure your entire network, but this recommendation was only made after exhausting all other technical alternatives.
Currently, based on your latest interactions with our technical team, we’ve observed considerable improvements in system stability and speed following the full reset and device reinstallation.
We are actively monitoring your system from our end and remain available to assist you in resolving any additional issues that may arise.
Thank you once again for your patience and understanding throughout this process.
Is there a way for the user to figure this out themselves? Perhaps some kind of monitoring could be implemented where they can see which device is generating which Z-Wave or CPU usage. A kind of task manager.
I have reset the system. I’m getting help from J. Lopez, doing a great job but still working thru issues.
1 Like
I need to follow up on the ECFI. What’s the status? With the exception of 80 open entries in the (old?) Ezlo Community Feature Request and Bug Tracker, all cases seem to have been migrated to the new ECFI.
New entries have since been created in the old system. When will the new ECFI be accessible to users so that the migrated cases and their status can be viewed, and shouldn’t the old system be closed down soon so that no new entries can be created there?
@JonathanB The buggy Android App is still an issue.
The current version still crashes when scrolling through the dashboard, the numbers are still not displayed correctly, and there’s still no geofencing. The dashboard still reverts to the old version after changing settings.
When will this be fixed?
1 Like
A new version of the Android App is released:
GPS seems to be built in now. I’ll test it when I leave the house.
The rest of the things I mentioned haven’t been changed yet. The worst thing is the crashes when scrolling through the dashboard. Am I the only one experiencing this? Would anyone at Ezlo want to provide log data or something similar (if that’s possible) to fix this?
I’ve created two cloud meshbots for User leaves the location and User arrives at the location with notifications. Both did not fire.
The Notifications are sent, when I run the Meshbots manually. But the location change doesn’t seem to be recognized. Should anything special be setup at my Android Phone like permissions?
Didn’t work for me when I tried it on iOS a long time ago. There also doesn’t seem to be a way to handle multiple devices either or setting house modes.
I believe I had mentioned all of this previously.
I had my Elzo Plus set on auto update, and it looks like it bricked my controller. I can’t even recover it with hard reset.
Hello @KennyR,
Thank you for your message and for submitting your firmware update request earlier today via this thread.
We haven’t processed the update yet, but from what I can see, your Ezlo Plus controller (ending in 70) is already running the latest firmware version.
I’ll be reaching out to you via email shortly to help guide you through some additional troubleshooting steps.
Thanks again for your patience!
@JonathanB Can you please take a look at the geofencing with Android? Can you test it at your side so we can see if I’m doing anything wrong or if there’s a general problem?
Hello @Odysee,
Thank you for your patience, and apologies for the delayed response.
I will try it over the weekend and will share an update with you as soon as I have the results.
Hello @Odysee,
I tested this over the weekend, and it’s not working because the trigger is not being registered. I’ll go ahead and create a new ticket so our developers can work on resolving it as soon as possible.
Thank you for bringing this to our attention.
What’s the status? Are there any new findings/progress regarding geofencing?
And again, generally speaking, regarding the topic “Ezlo Development going strong?”:
It seems like Jonathan is the only active Ezlo member here at the moment. Why is that? Are there too many projects being worked on in the background? Is everyone on vacation? I find it a bit of a shame that many inquiries/problems aren’t addressed here in the forum, even though the activity here is very manageable…
I’ve reviewed all of the release notes available; they only go back ti the beginning of last year. But in that 17 months the only new integrations I see are for your pwn products. The list of integrated products is not there. A list of integration requests is not available. I’m on the verge of moving on to another hub. This doesn’t look development going strong. The Vera Plus hub had better range and adding devices was easier.
Hello @Odysee,
Thank you for following up. To address your questions:
Geofencing
The geofencing issue has already been escalated internally. While it’s currently pending assignment to a specific sprint, the case is active and being tracked. We’re pushing for it to be prioritized soon, and I’ll make sure to share any updates as soon as they are available.
On the Development Side
There are actually multiple improvements in progress at the moment — across firmware, server infrastructure, and bug resolution. We’ve been seeing faster response times from developers in several areas recently, and we’re optimistic that this momentum will continue.
Regarding Forum Activity
You’re right that I’ve been the most active Ezlo representative on the forum lately — and that’s by design. I’ve taken on the responsibility of moderating and managing the forum to better channel customer feedback and make sure it reaches the appropriate internal teams efficiently.
While my colleagues remain fully engaged in projects across Ezlo and Customer Care, I’ve found that centralizing forum communication helps avoid fragmentation and ensures that your input is clearly heard and tracked.
That said, your feedback is invaluable, and I completely understand the importance of seeing more frequent and diverse engagement here. I’ll continue to advocate internally for that.
Thanks again for your patience and support — and for holding us to high standards. It helps us do better.
Hello @tinman,
Thank you for your honest feedback — I completely understand your concerns.
As you may have noticed, our main website is currently under maintenance while we work on a full revamp. This also includes an updated and more accessible list of supported devices, which we expect to make available again soon.
In the meantime, I can confirm that new integrations are actively being worked on. For example, support for the UltraPro ZW4001 was recently completed and is planned for release in an upcoming firmware version.
It’s also worth noting that many of the features and integrations available on previous platforms like Vera Plus were the result of years of accumulated development, and while we’re still building up the Ezlo platform, we’re deeply committed to improving it every day — not just in terms of stability and performance, but also in expanding device compatibility and usability.
I’ll make sure to pass along your comments to the product and engineering teams. Please don’t hesitate to share any specific devices or features you’d like prioritized — your input genuinely helps shape what we focus on next.
Thanks again for taking the time to share your thoughts.
It’s pretty quiet here, and it’s time to follow up on the question in the thread title “Ezlo Development going strong?”
I would like to know the status of the following topics:
-
Geofencing: When will this feature be available (on Android)?
-
Dashboard of the web frontend: When will the dashboard be completely redesigned? I suspect it will look like the new dashboard in the app.
-
Dashboard Designer: Is anything else planned? Will it be possible to create your own dashboard at some point?
-
Firmware Update: The firmware seems to be automatically updated to the latest version again. Perhaps not everyone wants this. When will the option be implemented to choose between automatic and manual updates?
-
Instability of the (Android only?) app: As I’ve mentioned several times, the app often crashes for me just scrolling through the dashboard. Am I the only one with this problem? Are there similar reports from users (perhaps from support?). It would be nice if we could address the problem with log files or something similar.
-
New controllers: Melih mentioned some time ago that something like this is in development. What’s the status here? Will there be a beta test?
-
ECFI (Ezlo Community Features and Issues): How is the transition going? There are relatively few (82?) unresolved issues left in the “Community Feature and Bug Tracker.” Those marked as resolved will presumably be in the new system? Will users eventually have access to them or be able to create new issues there?
-
Redesign of the main website: When will this be completed? Something like this should really be implemented with high priority and as quickly as possible. It doesn’t make a good impression on the client side if all it says for a long time is “we’re currently working on the new website.” Shouldn’t the new pages be completely finished first and then the switch is made without or with a short interruption?