Is there any forward progress on Ezlo bugs and features or is this product basically dead? It seems like there have been no updates in months or any posts on the track of the product.
You could actually get that impression. But every now and then there are new versions, firmwares, bugs that are fixed, etc.
The problem is still communication. Something is being worked on in the background, but the user is not informed about it. There are already a few threads that deal with this, but somehow everything is coming to nothing.
For example here:
It would really be nice if there was a roadmap. There are so many wishes, suggestions for improvement, bugs, etc. but the user remains completely in the dark as to when and if anything will happen in this regard.
What about the customized dashboards? What about geotagging/Android app? Will there ever be data logging? When will the web interface be able to do all the functions that the app can do? What is the status of the community feature and bug tracker? Why are there only sporadic reports about new firmware/dashboard/app versions and why are they scattered across various sites and not here in the forum (https://support.ezlo.com/hc/en-us/articles/15547378440860-EZlogic-Dashboard-Release-Notes).
Why canāt we just communicate openly what is being worked on and what is planned for when? Saying āItās on the plan, but nobody knows whenā doesnāt help anyone.
You could now either get the impression that Ezlo doesnāt listen to the user and doesnāt think itās necessary to reveal plans to them or, even worse, that Ezlo has no planā¦
I must be missing something because I havenāt seen any real updates. Looks like ezlopi is the place to be.
Amazing itās been over 4 years since the controller was released and itās still not a viable replacement for its predecessor.
Itās really a shame. One thing that has plagued this system, is its lack of reliability. The reviews have often indicated it was the case. The whole market has not turned out the way people expected. I have a couple of unknown devices that I have no idea where they came from.
Something is still happening.
Here is the last Update for the Dashboard v1.1.26 (but there is already the 1.1.27 without changelog):
MiOS for Android was updated not long ago (changelog only in thread):
MiOS for iOS was also updated (also only changelog in thread):
Latest Firmware Version is described here (not in the community forum):
I think Iāve already mentioned it a few times, but hereās my suggestion again:
If thereās something new, please post it here in the forum in the relevant category (Official announcements) and not scatter it somewhere where nobody will notice it or go into hiding and give no sign of life.
Make firmware updates from the controller adjustable between automatic and manual updates. In both cases, please send a notification when there is an update and what has changed. And of course a āsearch for updateā button.
MIOS app for iOS hasnāt updated in at least 2 months. The dashboard is still a mess. Geofencing is still unreliable. Sill canāt add devices via cloud integration. I still see reports of zwave and zigbee stability issues. Disconnects between app and webui for device configurations. It was said on another thread that you should expect more functionality in the web but this definitely does not seem to be the case with Nest devices. Iām not sure if this is still the case but meshbots didnāt support nested logic. Iām sure there are a lot more but honestly I donāt use the Ezlo controller for much of anything as my Vera is still performing.
In addition forgot to mention geofenceing has no feasible or easy way to integrate with house modes(kind of pointless without this integration).
I would like someone from Ezlo to chime in and discuss where we stand and what the plan is. It doesnāt have to be about specific problems/wishes. Just general.
all engineers are developing everyday and we continue to write code. its business as usual.
is there something specific you want prioritized higher?
do you have exact issues that makes you think that?
want to take these exact requirements and get it prioritized.
do you have any specific issues/tickets you reported re: reliability? FW seems to be running quite nicely last few months for me, I have 4 controllers i run at home and yes it did have reliability issues in the past, but have been running smoothly for me for about last 2 months.
please tell me exactly which tickets you have or issues to see if they are already addressed in the latest firmware or we can prioritize it.
Iāve mentioned some issues I have in an earlier post and in various posts in the forum.
Are you using any of the cloud services because I just tried to add one and it failed?
Do you have a lot of battery operated devices because it was reported not that long ago that battery management is still poor and kills batteries in devices?
Ezlo weather was removed and it was advertised as a service that didnāt need to have an additional account created. I still canāt get weather on my controller.
How do I use geofencing to switch house modes like the Vera controller does?
I still see various errors when launching the web interface(some sort of quota exceeded error)This was reported on the forum. Also get and unexpected error in the MIOS app when I try and reboot the controller.
These are just a few issues as I donāt use it as my main platform as I continue to use my Vera as Ezlo is still not āmatureā enough even after four years. I understand that there will be bugs but there are base functionalities that just donāt work(i.e. Cloud Sevices). I donāt want to be a product tester which is why I waited this long to try and start to use the Ezlo platform but for me there are still too many issues.
You mention that developers are writing code and its business as usual which is great but thereās no visibly to outside world as to what is going on. There was supposed to be some internal discussion about this and we still see no results of this discussion.
I do have battery operated devices and I donāt have a problem with batteries in them. They do last a long time.
āLong timeā is subjective. There are manufactures that rate battery life up to 5 years, are you seeing that battery life?
Other users on the forum have reported that Zigbee Centralite devices eat batteries. What do you expect battery life should be for say a window sensor that does not get activated frequently(maybe once a month)?
this is a new page. Still doesnāt have everything but shows you progress
1 Like
Here are just a few examples of threads in recent times where you would expect someone from Ezlo to comment, or which fizzle out:
Hi Tim. Please find the progress on the items you reflected below:
- As for cloud services - weāre about to release an update for it. In terms of tasks - there was one issue to be fixed, other than that - it is more about final testing and deployment
- As for battery-based devices - could you please provide a bit more information about it, so we could check and fix on our end?
- Ezlo weather - yes, it was delayed a bit, but the work on bringing it back is being done. You can expect it to be back within the next releases
- As for the web interface - weāre working together with @cw-kid on fixing the issues related to device settings, meshbots etc. So please expect the improvements to be released soon
Please feel free to share any issues found with me or @JonathanB, so we will register them, prioritize and pass to development
1 Like
So Iāll ask a few specific questions:
-
What about the development of the web frontend? When will it integrate all the functions that the app can do (such as adding devices), so that you no longer have to rely on the app?
-
Dashboard: Something seems to have been changed recently in the iOS version. Where is it headed? How and when will custom dashboards be created (Dynamic Dashboard, Native Dashboard, NuCal Studio, Dashboards Designer)
-
Geofencing: It seems to have already been integrated into the iOS app, but is not yet running quite as smoothly. What about Android?
-
Will there be data logging at some point, so that data can be collected for statistics or for further processing and evaluation?
-
Plugins: What is the development like here? On the one hand, the selection is quite clear and on the other hand, the handling could also be improved. For example, I only managed to integrate my Shelly 3EM Pro with the help of Ezlo via the IP plugin. That should be easier. I imagine that such devices can also be integrated using the Add Device Wizard.
-
Changelogs/News: Is there a plan in the future to only communicate such things via this new page or also here in the forum or here and there? This should be done uniformly, otherwise it will become chaotic and the information will quickly get lost.
-
Z-Wave parameters can be set, but not queried. In addition, these parameters should not all have to be installed manually. As part of the device integration, these parameters should also be able to be set via a selection menu or similar.
-
Will it ever be possible to carry out OTA updates for Z-Wave devices? The only way to carry out an update at the moment is to exclude the device, connect it to a manufacturer controller, for example, install the update there and then teach it back to the Ezlo controller. Last but not least, of course, all MeshBots have to be corrected there. Which leads us directly to point 9.
-
Replace Failed Devices: This function used to exist. Devices that fail currently result in a lot of work. After including the new device, all MeshBots have to be addressed. If this Replaced Failed Devices function existed, it would be much more convenient and it would only have to be included.
-
Warning/Event history: There is still potential here. When will this category be expanded? It still seems very sketchy. For example, the event trigger is included, but no other information about what was triggered. I am introducing something like a filterable log file here. I know that you can also log in with SSH or something and then somehow read these log files. But it would be nice if this could be done simply via the web interface. That would help considerably with troubleshooting and optimizing the MeshBots.
New iOS mios today
we have no plans in putting it there yet. Because we already have it on the mobile devices and its easier to take mobile phone than your computer when pairing a device.
We were building a āweb basedā dashboard. It had problems operating in mobile OSes due to security issues. We are now working on mobile OS native dashboards.
There already is. The data is being logged to the cloud so that historical data can be available.
we just need to provide the UI to be able to view it.
watch this spaceā¦canāt tell you what we are doing yetā¦just give me some timeā¦
I agree, we started putting the ārelease notesā as the main area and we are keeping that uptodate
is this a missing feature?
Feature request? (if so we need to create a ticket etc)
Feature request? Lets document and create a ticket
Feature request: lets expand and create the ticket.
Thank you for the update on my issues. Iām curious to see when this will be implemented. Iāve checked again. Apart from the warning/event history, there are already feature requests.
- Z-Wave parameters: ECS-962
- OTA updates: ECS-112
- Replaced failed devices: ECS-785/982
- Warning/Event history: ECS-1256