My Vera edge seems to have frozen up. I try to login through the web UI and it shows the tabs on the left, but the center just shows as white with the spinning green wheel. I’ve tried from multiple devices with the same result. I’ve tried to connect via my iOS app, VeraMate with no luck as well. What’s weird is that VeraMate still reports the devices and their current states. Also, I have a Minimote with 4 scenes setup. That is working just fine, I’m still able to control the scenes. I’ve unplugged it and left it powered off for five minutes getting the same result upon re-powering it. Has anybody else ran into is issue? Does anybody have a suggestion on what to do?
This exact same thing happened to me tonight too (though with a VeraLight)! Was working great earlier but now I can’t connect via the web UI.
I can however connect using any iOS app that connects directly to the box (not through getvera.com). Using that I can turn on/off lights, run scenes, etc as normal. When I SSH into the machine and check the logs nothing jumps out as being wrong. In fact it seems to be running normally past the fact that I cannot log on anymore through the web interface.
What gives?
Did this happen to anyone else?
I have had times that the Vera iOS app, or Vera Mate seem to hang trying to connect to my Edge but I usually kill it, or log out and back in and it’s fine. I use the web seldom to access it, but just tried and it was incredibly slow compared to other times and eventually took me in ok.
What’s even more strange is that if I use the firefox “FireBug” extension on the web UI, I can remove the overlay on the page that prevents anyone from clicking on the menu.
Once I delete that overlay, I can access each of the side menus, access my devices, turn them on and off, etc. At that point it’s almost as though it’s working normally.
I have a hunch (with nothing to support it, yet) that the web ui is actually calling home to vera when you first hit the page and for some reason it’s not getting a response back that it needs to remove the spinner and it’s causing the site to hang there.
Therefore, I get the feeling that this will be resolved on it’s own eventually.
You are probably correct. Well, I guess it’s time for me to learn how to use Homewave…
Think I might have found the culprit, thought can’t be sure because I have never watched the web console normally to see if this call usually works when I load the page. But there is an error on the page when it first loads.
Failed to load resource: the server responded with a status of 500 (Internal Server Error) http://vera/cgi-bin/cmh/proxy.sh?url=https%3A%2F%2Fmios.eemanager.net%2Feem%2Fapi%2Fenergy%2Fmiosseven%2F<redacted_by_me>%2F%3Frand%3D0.13386883307248354
That calls goes to “https://mios.eemanager.net/eem/api/energy/miosseven/<redacted_by_me>/?rand=0.13386883307248354” which either fails with an HTTP 500 or it responds successfully with json stating “Unable to find gateway from serial number”.
But who knows… maybe this thing always fails on a normal day and has nothing to do with this. Guess, we’ll have to wait and see.
Same thing with my VeraLite. I was adding an app when it happened so I figured something locked up and performed a factory reset. Still can’t login to the damn unit.
I am almost done with this thing. Always having issues and hardly any support/documentation except for enthusiasts on this forum.
Well, you were exactly right about other direct control apps working. I’ve loaded up the HomeWave and am able to dim the bedroom lights again. Wife-crisis averted for now!
Hopefully this is all related to the Connectivity issues they have been having lately. I’m just gonna wait and try again tomorrow. Glad patience prevailed and kept me from hard resetting the thing while chasing ghosts.
I am having the same issue today. I use Cinemar Mainlobby to control lights and it accesses Vera without an issue. Lights go off and on instantly
Yep… same here. Was working fine earlier today and now… the control tabs on the left and the “perpetually spinning green wheel of death” on the right… Derp!!
Decided to pass the time instead with continuing setup and config of HomeGenie. I like it and only need to dedicate an old netbook to run it with a Z-Stick. HomeGenie is free and continuing to grow at a surprising rate. Well supported and doesn’t appear to be stuck in the mud like VeraLite development and support… and after seeing the UI5 interface for the first time, elsewhere, and comparing it with UI7… jebus cripes! It begs the question, “What were they smoking?” when they scrapped 5 for 7… UI7 is hideous and the avail. android apps don’t even comply with Android development conventions… so… they are equally hideous.
The Imperihome app lets me control all of the devices without delay. I cannot login to the webUI. Just get the spinning green wheel. Sometimes I can’t even get that far. It will hang on an initial screen.
I had this happen and found that power cycling the device fixed it. Whether that really is cause and effect I have no idea.
EDIT: …but on a screen refresh the wheel of death returned 
Same here, started somewhere around 7 p.m. central last night … same this morning at 8 a.m. Already caused some frustration, planed to install 3 new systems this weekend. Just checked this forum, so … ya … me too …
Wish there was some “official” update area that micasa could or WOULD post current status updates letting customers know if there was a server problem or something on their end, would save everyone some headaches at the end of the day.
I started having this same issue last night. Power cycling has not resolved it. My scenes continue to work, but the UI is almost entirely inaccessible. I did manage to get into the controller UI after many attempts last night, but it was very slow and reverted to the spinning green wheel after a few minutes.
I don’t have any 3rd party apps configured to control my devices, but I might try one out today. It sounds like HomeWave is a popular one. One thing that I found to be odd was that my desktop machine that I had left logged in from the day before was still connected and able to control the vera UI pretty quickly. After a few minutes of exploring logs from that machine (constant use), I got the ‘your session has timed out’ error and it kicked me back to the login screen. After that point, the desktop machine had the same inaccessibility issues as my phone/tablet.
The fact that a device that was already connected was still working ok makes me think the andrewgarfield is onto something. I know these devices are supposed to work completely offline, but I wonder if there’s a webcall made when it detects an internet connection, and that call may be going unanswered due to issues at the remote server.
Either that or maybe a UI update might have been pushed that has messed up the auth/redirection pages?
The state of logging into my VeraEdge via home.getvera.com is indistinguishable from experiencing a DoS attack. I cannot login to the web UI since last night, only getting as far as the spinning green circle of death.
Is there a way to login to my local UI7 that completely bypasses Vera’s obviously borked services outside my local LAN? If not, then of course that’s terrible engineering. Any assistance is much appreciated. I used to love my old Vera3 running UI5, but the current state of things is driving me crazy.
I ssh’d into the VeraEdge and see all kinds of log spamming in NetworkMonitor.log and LuaUPnP.log, but I don’t know what any of it means, or if it is out of the ordinary. Oy…
watou
I’ve tried removing the internet from my network and still can’t get into the Vera UI (after reboots). I had thought that the VeraEdge didn’t require Internet access to manage. This is either not the case or our devices have been hacked. I was hoping this would resolve itself overnight. I’m going to put a ticket in and hope for the best.
All of that spam you’re seeing is precisely why I didn’t fill in my address on setting this thing up. Could you imagine the value of an address list complete with vera access for lock/alarm disabling? This sucks.
By “log spamming,” I meant tons of log messages whose value is questionable, grows the log files tremendously, and potentially obscures actually useful log messages (not email spam). It’s like there is a lot of debugging noise that was never turned off for the production release. So the log files grow and grow, but the messages aren’t clear enough as to their purpose to indicate normal operation vs. a problem that needs to be diagnosed and fixed.
Did you try removing cookies and clearing cache?
After several minutes, I’m allowed to choose which controller to connect to. Ten minutes in, all I know is 1) it’s 5 degrees C and partly cloudly outside in a distant town (since my town is not in the list), and 2) I hate the green spinning star. Why is this, when I’m looking at a local URL in the browser’s address bar? Why on earth would my local device care about broken servers on the Internet? Does UI7 have an Internet dependency to present its local UI locally?
For those impacted, can you confirm successful restoration of service this morning, please?
Our apologies for the service disruption. That’s unacceptable. I’ll round back with more details for you as soon as possible this weekend.
Thanks for your patience and support.