I wanted to access the controller via the web frontend. Unfortunately, the dashboard only showed “No Devices,” and the controller status was offline.
I then gave the controller a bit of time and waited to see if it was a temporary issue (server unreachable or something similar). That wasn’t the case, so I took a closer look at the controller. It was flashing orange, which means it was offline.
So I unplugged the controller and rebooted it. After that, it was accessible again.
Luckily, the controller is at my location and not in a vacation rental or something similar. Then this would have been a real problem. Perhaps someone from Ezlo would like to take a closer look at what exactly happened and what could be improved to prevent this from happening.
A workaround would be to have the controller automatically restart every x days, plug the controller into a Wi-Fi outlet for a remote restart, or create a MeshBot that restarts after x hours of offline status. But of course, that’s not really that elegant. And I don’t know if the controller would have executed it.
Today, the controller was unavailable again. This time, however, the LED was turquoise. So the controller should be online. After several hours, I unplugged the controller and rebooted. After that, it was accessible again.
It might be a good idea if someone could take a look at this…
I have been dealing with the same issue since yesterday, but I have noticed this problem before. The app would load with a blank dashboard, although it would show the Controller, then everything would be back to normal after awhile. The issue I’m having is the fact that noone responds to my support realted issues. They flag them as resolved and just close the ticket. I honestly don’t know if there is anyone theree anymore.
My controller was unavailable all day today. This time, the LED blinking indicated “Booting application partition.” After restarting the controller (unplugging it), it was accessible again. Is this related to the update?
That’s too many outages in such a short period of time for me. @JonathanB Can you take a closer look?
I honestly don’t know where to begin. I think there may be multiple issues at play here. As I mentioned before, sometime it sees my controller, but when it loads there are no devices and it wants me to add devices. Other times, it may load, and I might get a blank screen on my Samsung Note Ultra running Android 13. Other times it struggles to load so I close and reopen the app in which case it loads on the 2nd try. The other issue that I run into 100% of the time is the jittery nature of the dynamic dashboard if and when it loads. It opens with the tiles loading and justifying to the left, then it tries to center the tiles, oddly enough it doesn’t always justify to the center, especially in portrait mode. Scrolling up or touching the screen during this process or immediatly after it has populated the tiles will either freeze or crash the app eveytime casuing the OS to throw he following error messege.
“Something went wrong with MiOS
MiOS closed because this app has a bug.
Try updating this app after its developer provides a fix for this error.”
We’ve been able to replicate the issue on our end and have already submitted a ticket to our development team so they can work on resolving it as soon as possible.
We truly appreciate your patience and understanding — we’ll make sure to keep you updated here as soon as we have news.
It just happened again. The controller is online (LED turquoise) and the web frontend also recognizes that the controller is online. However, I can’t see any devices in the dashboard (neither in Chrome nor in Firefox).
So I rebooted the controller (disconnected power). The first boot attempt resulted in a permanent offline status (flashing orange). After the second attempt, it went back to turquoise.
But that didn’t change the fact that no devices are displayed in the dashboard.
The devices are visible in the MiOS app (Android). So it seems to be a problem with the web frontend. But it’s useless due to constant crashes…
Thank you for bringing this to our attention, and sorry for the inconvenience you’ve been experiencing.
̶W̶e̶ ̶a̶t̶t̶e̶m̶p̶t̶e̶d̶ ̶t̶o̶ ̶r̶e̶p̶l̶i̶c̶a̶t̶e̶ ̶t̶h̶e̶ ̶i̶s̶s̶u̶e̶ ̶o̶n̶ ̶o̶u̶r̶ ̶e̶n̶d̶ ̶b̶u̶t̶ ̶w̶e̶r̶e̶ ̶u̶n̶a̶b̶l̶e̶ ̶t̶o̶ ̶r̶e̶p̶r̶o̶d̶u̶c̶e̶ ̶t̶h̶e̶ ̶s̶a̶m̶e̶ ̶b̶e̶h̶a̶v̶i̶o̶r̶. ̶H̶o̶w̶e̶v̶e̶r̶,̶ ̶b̶a̶s̶e̶d̶ ̶o̶n̶ ̶y̶o̶u̶r̶ ̶d̶e̶s̶c̶r̶i̶p̶t̶i̶o̶n̶ ̶—̶ ̶e̶s̶p̶e̶c̶i̶a̶l̶l̶y̶ ̶t̶h̶e̶ ̶f̶a̶c̶t̶ ̶t̶h̶a̶t̶ ̶d̶e̶v̶i̶c̶e̶s̶ ̶a̶p̶p̶e̶a̶r̶ ̶i̶n̶ ̶t̶h̶e̶ ̶M̶i̶O̶S̶ ̶m̶o̶b̶i̶l̶e̶ ̶a̶p̶p̶ ̶b̶u̶t̶ ̶n̶o̶t̶ ̶o̶n̶ ̶t̶h̶e̶ ̶E̶z̶l̶o̶g̶i̶c̶ ̶d̶a̶s̶h̶b̶o̶a̶r̶d̶ ̶—̶ ̶i̶t̶ ̶d̶o̶e̶s̶ ̶s̶e̶e̶m̶ ̶r̶e̶l̶a̶t̶e̶d̶ ̶t̶o̶ ̶t̶h̶e̶ ̶w̶e̶b̶ ̶f̶r̶o̶n̶t̶e̶n̶d̶.̶ We have replicated the issue and has been reported to our cloud department.
I’ve already escalated this case to our cloud team for further investigation. We’ll keep you updated as soon as we have more information or need additional details from your side.
Thank you again for your patience and detailed feedback — it really helps us improve the platform.
Since the thermostats were apparently not set correctly, I wanted to change the temperature from 18°C to 22°C via the dashboard. So I clicked the higher temperature number four times (for some reason, you can’t click the arrows). After that, the thermostat kept moving back and forth (not just on the dashboard, the thermostats also kept moving back and forth):
Best Home Automation shopping experience. Shop at Ezlo!
