Hello @Odysee,
Your controller has been flagged for an update to the requested version (2.0.69.2921.9 [production-189]) during its next restart. Please ensure the controller remains powered on and connected to the internet.
Any ideas when the automatic updates will get fixed?
Also, can you flag my controller for update?
The firmware update UI is ready for grooming by the engineering team. Once reviewed and prioritized in the development cycle, weāll provide further updates on its progress.
Thank you for your patience.
Is there a way you can flag my controller ******33 for update?
Hello @lior60
Your controller has been flagged for an update to the requested version (2.0.69.2921.9 [production-189]) during its next restart. Please ensure the controller remains powered on and connected to the internet.
That doesnāt seem to work. I restarted several times yesterday (including once by pulling the plug). I tried it again today. Firmware remains on .6.
@JonathanB My firmware is still not updated.
In addition, my controller was offline for some reason from yesterday afternoon until midday today (I noticed this yesterday when the shutters didnāt go down). Maybe you can take a look there too. Unfortunately, the warnings/history in the web front end doesnāt provide enough information.
@AntonSorokin What about geofencing? What is the status?
@melih What about the new generation of Hub? When itās ready, Iāll be happy to help with beta testing. I assume that migrating from the Ezlo Plus controller to the new one will be easier than from Vera to Ezlo, right?
I know releases have been made recently but it seems users keep asking the same questions and getting the same answers. It feels that things are stagnating and not really moving forward.
Today I had several status changes to my Community Feature and Bug Tracker requests and thought: Now itās finally starting and the list will be processed.
To my surprise, they were all set to āDone with resolution Obsoleteā. I would like to go through them now:
-
ECS-830: scheduler for thermostat control
There is still no convenient schedule for programming Z-Wave thermostats. This is still only possible using a large number of confusing mesh bots. -
ECS-962: Manage Z-Wave parameters more easily
It is still not possible to read existing parameters. It would also be an advantage if you could build in the parameters directly for known devices so that you could then set the values āāusing a slider or something similar. -
ECS-810: Compare values āāof different devices
Actually not such an exotic application: compare values āāfrom two devices directly with each other. -
ECS-838: Eurotronic Air Quality Sensor Z-Wave Plus (VOC Sensor)
I know the request was made almost 4 years ago and I donāt even know if the device is still available. Itās logical that problems like this will resolve themselves if you wait long enough
-
ECS-532: Support for every IP cam
The request was actually resolved a long time ago. Cameras can now be integrated. Unfortunately, my later addition that this should also be possible via the web front end is not answered. Should I open a new request for this? -
ECS-776: Map for rooms/devices
I would like to be able to create a map for rooms where you can visualize the location of the devices. For example, a map of the apartment where smoke detectors or window contacts are displayed, so that when the detector is triggered you can see exactly where it happened.
This gives me the impression that the list is being thinned out as quickly as possible without having properly read what it is all about. Closing it with DONE and OBSOLETE without any comment also looks to me (and probably to some others too - Iām probably not the only one affected) anything but like someone is listening to the users
There all still some webshops that have stock, so itās available. Kind of funny, as MiOS still states:
āAt Ezlo we work with an industry-leading number of devices, but if thereās a Z-Wave or Zigbee device we donāt currently work with that youād like to see us integrate, just fill out the form below to let us know. Weāll get it done within 90 days.*ā
Hello @Odysee,
Checkingā¦
Hello everyone,
As you may remember, we are now managing requests through the ECFI (Ezlo Community Features and Issues) project instead of ECS (Ezlo Community Support). During the migration process, there was a misunderstanding, and some tickets were mistakenly closed as āobsoleteā without a proper explanation.
We want to clarify that these issues and feature requests are being reclassified. For example, the thermostat schedules request is still in progress. Here are a couple of screenshots of the designs:
We apologize for the confusion and appreciate your patience. Please rest assured that your feedback, requests, and suggestions are very important to us. We remain committed to improving and prioritizing your needs.
Thank you for your support!
1 Like
Iāve just received more messages about completed requests and have looked at them again.
The requests that are accidentally marked as obsolete seem to be the rule rather than the exception. Iāve also read a question about why the request was closed for a request. Canāt this be communicated more cleverly?
So let me summarize:
The Ezlo Community Feature Request and Bug Tracker is migrating to a new system and now the cases are gradually being reviewed and migrated to the new system. So far so good. Unfortunately, things seem to be going a bit badly again:
Point 1) Why is this not communicated clearly? Perhaps it has already been mentioned in another thread. But it should be clearly visible in various places. How about a separate message in the āOfficial announcementsā section, for example?
Point 2) Why can you still create new requests in the old system? I would have expected that no new cases could be opened in the old system until the migration was completed, or that you would be referred to the new system where you could then create your request.
Point 3) Why are requests still closed with Obsolet without a comment? The person who created the request usually receives a message about it directly via email. Customers are bound to be dissatisfied. Canāt you add a short sentence like āThe case is currently being converted to the new system and will soon be available under XYā?
What exactly is the new system like? When will it be available (most requests seem to have gone through)? Will it only be available internally at Ezlo, or also for users?
Hello everyone,
Itās time again for an update on āwhere we are, what weāre working on, and where we want to go.ā
First of all, the things where I see improvements:
- The website https://updates.ezlo.com/ provides a central location for current updates.
- Updates are also published here in the forum.
- I like the interim solution of requesting firmware updates using a keyword until the new firmware UI is completed.
The things that are currently being worked on, although theyāre only hidden in various threads:
- Migration of the ECFI to the ECS: I described above how it went and how it should go.
- MiOS Web Frontend: A new web frontend and/or dashboard is supposed to be released. But thereās no information on when.
- Desktop Designer: They were working on something new a while ago, but thereās no information here about the status.
- Geo-fencing with the Android app: Thereās no word on when this will be implemented.
- There seems to be a roadmap (mentioned here). However, it seems too secret to be published publicly.
Things that definitely need to be improved:
- Communication: Questions are constantly being asked that simply go unanswered. How can EZLO improve this so that such things no longer fly under the radar here in the forum? As a user, you could add ā@Ezlo_Response_Teamā to your post each time. But not everyone would necessarily notice that. It would be better if EZLO staff monitored the threads more closely (there arenāt that many at the moment) and then responded to usersā questions.
- Indefinite delays: We keep hearing phrases like āIāll have to ask about that. Iāll get back to you shortly.ā or āWeāre working on it, but thereās no date.ā or āItās already been resolved and approved and should be included in the next release.ā And guess what happens then? Exactly! Nothing more. Thereās no news coming soon. Thereās no indication of when something will be implemented, and the problem usually isnāt resolved in the next release, as suggested. Itās really annoying and frustrating to have to keep following up to get some information.
1 Like
A new MiOS version for Android has just been released. I took a quick look at it. Aside from the fact that according to the changelog, geo-fencing still doesnāt work, it crashes even when scrolling through the dashboard:
Iām a bit upset at the moment, so when I saw this title it really set me off. Iāve got so many problems I am ready to get rid of my ezlo and start anew with something else. Here is a list of issues.
slow or failed action from devices
include/exclude does not activate at times
using the app, the device takes almost a minute to activate
adding devices hangs at 5% or does not work all
scenes run slow, partially or not at all
devices that have been connected for a long time all of a sudden become disconnected and unresponsive
Contact customer service, and recording says they open at 9, didnt get in contact with tech support til after 10.
Hello @ryantatum20,
We noticed your support request was recently submitted in a ticket that hadnāt been updated for almost a year. It has now been assigned, and one of our agents will review your case as soon as possible.
In the meantime, just a quick tipāZ-Wave device manufacturers recommend keeping the controller and the device within 3 feet of each other during the inclusion process for the best results.
A ticket was entered a year ago and not respond too, totally inexcusable.
It does not seem like development for the Ezlo controller is their priority, even though its claimed that development is going strong.
It seems that most of the older Vera users have moved on to other platforms as progress on the Ezlo appears to have stalled. Itās been almost 5 years and Ezlo is still not a viable replacement for its predecessor.
Hello @Tim88
That ticket in question was awaiting a response from the customer.
Thatās not how I read what you posted. What I read is your ticket fell into a nebulous hole and now that you pointed it out weāre going to respond to it. Honestly it wouldnāt surprise me that it would go silent as illustrated by many of the request/responses go radio silent for extended or indefinite periods of time, other users have pointed this out as well. There are numerous examples.
I understand trying to defend your company but when are the users going to get the answers to the questions theyāve been asking? When will all the itās in the pipeline and weāre working on its get delivered.
One example when do we get cloud services integration for Netamo Weather Station?
Another example how do I use geofencing with multiple devices to set house modes?
This product has been on the market to the public for 5 years and still lacks the ability to replace my Vera.
1 Like