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?