This night my Vera Edge stopped working. The Zwave light is off. After a while I get a message in my browser: Luup engine is taking longer to reload, contact support (Christmas Eve…)
I can ping the devise and with ttp I can get as far the Linux login page.
I even tried to hard reset the device. I’m not sure how that works (one click or 2 clicks on the button?)
I have had with Mios Vera Edge and returning to Domoticz.
Although open source, Domoticz is much richer in functionallity: Configuring modules, Usb, RFXCom, P1 smartmeter, nice graphs, Logitech connect. It all works out of the box.
And even more important even their beta updates are stable.
pimvolkert did you resolve your issue in the end ? mine developed the same issue last night
The Zwave light is off. After a while I get a message in my browser: Luup engine is taking longer to reload when trying to access my vera
if anyone has any idears open to sugestions.
i have tried the usual reboot, pushing the reset pin on the side for varying lengths of time but made no difference
ssh access is still working and found a log file called LuaUPnP.log and this file shows:
2015-01-01 23:34:12 - LuaUPnP Terminated with Exit Code: 245
2015-01-01 23:34:12 - LuaUPnP crash
every couple of seconds with a load of other dubugging info that i can supply if anyone thinks it could be usefull.
another sugestion i saw was to run the factory reset script this caused the power to flash and ssh connections to be rejected left for 45 min and nothing changed so rebooted and back to where i started ssh access restored and the luup taking too long with zwave light off
i have sent a email to vera support but other reviews i have seen dont speak highly of vera’s responce time so any help would be apppreciated
thanks
My problem was not solved. As I already had the problem that USB is not working I did quit with Vera. I have shipped my Vera Edge back to my supplier and I’m extremely happy with Domoticz.
I also had the same problem with my 5 day old Vera Edge.
Just when I had finished associating all of my existing Z-Wave devices with the new Edge, it suddenly stopped responding - I could ping the device but the web interface would not load and it would not respond to the iOS app.
I tried all variants of resetting the Edge with the reset button and command line without any success. There was always one of two results, either all of the Edge lights were lit except for the Z-Wave led, or the power light was flashing with all other led’s lit.
Contacting MCV was hopeless - I still don’t have any response from them many days after my first issue was logged.
Using ssh to investigate the log’s, I found that the LuaUPNP,log file shows the LuaUPNP Terminated with Exit Code: 245 message.
The good news - and hopefully it can help one or two others on this forum - is that I think that I have found a cure!
I powered up the Edge as normal (no reset button) and connected via ssh. Looking in /etc/cmh I saw a number of user_data.json.lzo files with timestamps from before and directly after the problems started.
When I replaced the current user_data.json.lzo file with the oldest backup of this file and restarted cmh everything worked again.
The commands that I used once I logged in the the Edge by ssh were:
cd /etc/cmh
Stop_cmh.sh
mv user_data.json.lzo user_data.json.lzo.bak
mv user_data.json.lzo.5 user_data.json.lzo
Start_cmh.sh
I cannot guarantee that this will work for everyone, but if it helps even one of you then it is worth me posting.
Thanks for your post, it was very useful. When I received my Vera Edge I tried to migrate from the Vera 3 using directions I found in the forum. After following those directions, and after restarting the Vera Edge, I ended up with the LUUP taking too long error, and no Z-Wave light. I sent a note to support, and they did respond. However it was the holidays and I wasn’t checking emails. When I got around to it, I enabled Tech Support on the Vera Edge and reported that information back. When I didn’t hear back I started searching this forum again and found your post.
I used WinSCP to login to the Vera Edge and looked for the files as you instructed. Since all my files were bad, because of the initial migration attempt, I found a clean file in the /etc/cmh/orig directory. I Renamed the current file as you instructed and duplicated the file in the /etc/cmh/orig directory to the /etc/cmh directory. As soon as I did that, without doing anything else, the Z-Wave light came on and the unit connected via the web gui.
I was able to reset to default on the backup page, and now it’s totally back to try again.
We can get to the ssh interface but we are unable to authenticate with our user name and password. Tried resetting to no avail. Is there a default username and password that we should try?
I have the same problem. i don’t know how to get to the vera edge to fix the files? can any body help me with that, i’m on a iMac OS X the latest version. i’m using terminal
to get to the edge, how do i do that?
How do I fix this. I’m having the same issue currently where the z-wave green light is out and I can’t load the web interface. From reading the thread it looks like this was resolved, but how?
I was having troubles with the 4in1 Motion and had created a ticket only to get told there is a firmware update that is suppose to address battery operated devices. So after backing up then trying to update the firmware I’ve got a Black BRICK sitting on my desk.
I’ve tried the reset button (sat over night)
I’ve tried the direct connection (login) to factory reset : http://wiki.micasaverde.com/index.php/How_to_reset_to_default_network_settings
I’ve tried to SSH into the box (wrong password every time) tired my original one and the default neither worked. Tried to Login as my original user and as root again neither worked.
This solved my issue!!! I will write this on my blog and give you all creds and link to this post
[quote=“chrislaw, post:5, topic:184915”]I also had the same problem with my 5 day old Vera Edge.
Just when I had finished associating all of my existing Z-Wave devices with the new Edge, it suddenly stopped responding - I could ping the device but the web interface would not load and it would not respond to the iOS app.
I tried all variants of resetting the Edge with the reset button and command line without any success. There was always one of two results, either all of the Edge lights were lit except for the Z-Wave led, or the power light was flashing with all other led’s lit.
Contacting MCV was hopeless - I still don’t have any response from them many days after my first issue was logged.
Using ssh to investigate the log’s, I found that the LuaUPNP,log file shows the LuaUPNP Terminated with Exit Code: 245 message.
The good news - and hopefully it can help one or two others on this forum - is that I think that I have found a cure!
I powered up the Edge as normal (no reset button) and connected via ssh. Looking in /etc/cmh I saw a number of user_data.json.lzo files with timestamps from before and directly after the problems started.
When I replaced the current user_data.json.lzo file with the oldest backup of this file and restarted cmh everything worked again.
The commands that I used once I logged in the the Edge by ssh were:
cd /etc/cmh
Stop_cmh.sh
mv user_data.json.lzo user_data.json.lzo.bak
mv user_data.json.lzo.5 user_data.json.lzo
Start_cmh.sh
I cannot guarantee that this will work for everyone, but if it helps even one of you then it is worth me posting.[/quote]
After about 8 back and forth e-mails with Vera support and 1 phone call they gave me an approved RMA to send my (3) x 4in1 motion detectors back for replacement.
I figured out what causes this error in my case atleast. If you were creating associations and you suddenly had this problem…
Watch your association creation very carefully. Sometimes the Vera Edge will freak out when you try to set the association and will put a checkmark next to the device “zwave” in your unassociated device list (this will be device #1, when you look at the Set list). I have found Vera likes to do this on my when trying to associate to device #41. Instead will try to set the associate to #4 and #1.
Do NOT leave “zwave or device #1” in your association list, and certainly do not go try your newly associated switch to see if it is working… because guess what… you just turned the zwave model off on your Vera!, when you turn off your switch, there is nothing you can do to turn it back on except to follow the steps in this thread to SSH in and restore a backup.
Instead if you see 1 in your associate “set” list, Carefully go back into the device options and uncheck the “zwave” device and make sure only the devices you intended are associated.
I know for sure it happened atleast twice for me with Device 41, the first time… hosed my box, the second time, I caught it and fixed it before messing with the switch. Device 41 is a light switch with two accessory switches on my device and so getting both Aux switches to set correctly was a little painful.
Don’t have any other switches with a 1 on the end that I have messed with yet.
I think associations currently are just buggy in general. I have 2 battery powered cooper switches. First one associated fine.
Second one, everytime I try to associate it to Device 66, it kills my Sonos and Concord 4 app, and I have to restore from backup. I am just going to use a minimote to do the associations moving forward. Vera just gets buggy and bad when you try to do associations.