Just let my Edge update to 7.0.24 and it died No z-wave light, no improvement from a reboot, nor from swapping user_data.json. Log was showing repeated LuaPnP failures with exit code 245.
A hard reset has it back on the default IP, but the web UI won’t load, eventually goes to the dreaded “LUUP is taking longer to start” message. The log seems to indicate that LuaUPnP is starting and then exiting immediately, now with error code 16.
Anyone seen that error code before or have any ideas, please?
Ah, I found another error log in /tmp, log.Init-LuaUPnP. This says “/usr/bin/LuaUPnP: can’t load library ‘libjpeg.so.62’”… so where the heck has that file gone to? A unix “find” from the root directory down fails to find anything of that name.
Failed upgrade, I’d guess. Maybe I can re-apply the update somehow from the command line (given that the UI is down)? Anyone have experience of doing that?
Contact CS immediately. They need to know that the FW is a failure before it becomes endemic and takes out too many Vera’s.
Thanks for the heads up on the failure, now many of us edge users will hold off updating.
Already called them. Voicemail - all busy! Emailed them too, asking for a callback as soon as it’s a civil hour of the morning here in blighty. I’ll let you know what they say.
I presume this version was beta tested on Edges, so hopefully this is an isolated screw-up by my controller rather than the FW, but on past experience, let’s reserve judgment…
My vera edge was circling the drain on this latest firmware update.
After upgrade all lights indicated it worked however, I could not connect via web portal or locally. I attempted two restarts. Each restart resulted in EVERY vera light indicating it was working however I was not able to log in locally. These two restarts occurred during a 30 minute time span, giving the vera time to unscrew itself. Old IP was unresponsive with no indications it was associated with vera (no hanging interface, just a browser message that nothing was there.) Then I hooked the vera to the network physically (cat 5 to switch). Still nothing for a good 15 minutes after a restart. Then a new IP showed up on my DHCP list, it was the vera. Logged in locally, started wifi, all seems well. I consider myself lucky given tK41’s experience.
[quote=“Don Phillips, post:5, topic:198043”]It sounds like you did not have enough memory to do an upgrade. I have similar experience with my 3. What I have done is:
Backup with z-wave.
Restore to factory settings.
Reboot
Update to new firmware.
Reboot
Restore with z-wave
Reboot
I have skipped 23 and will probably wait another week until I update to 24.[/quote]
Don, exactly what I was trying to do, but I’m at your stage 3 and have no UI, so I can’t do stage 4 unless it’s from the SSH command line!
Very helpful lady from support called me at 8am, spent almost an hour driving my PC remotely, manually installed the missing files and got Vera back online. That left us with a Vera that was alive but had issues with many devices stuck “configuring”. Error 16 gone, but lots of error 245 in the logs again.
Support then said there were some back-end systems problems this morning too, so enabled tech support access from ssh and went to work behind the scenes.
She called me back at lunchtime; Vera had clearly been reset again while I was away and that had created some networking issues that we had to fix. For some reason, the grumpy little box wasn’t doing well at getting a DHCP lease from my router, or at times got one then didn’t use it. Once she’d un-stuck the network settings page (a drop-down that wouldn’t drop!) so that I could force the IP config, things were looking up again.
I now have a working Vera that’s online locally and to the mothership and can talk z-wave once more.
Seems that the initial issue with the upgrade probably was space-related but it failed at a very unhelful point in the process and for whatever reason two key files - libjpeg and another library - were AWOL. The support lady seemed sure that those were the only two; I’m not sure how she identified the second file or had so much confidence about those being all, so perhaps Vera support have seen this issue before and know what to look for…
Why it decided to screw up networking too just for kicks, I have no idea. Inzax, yours sounds like it did something very similar but thankfully handled the DHCP properly for you in the end.
Hopefully it’ll now remain stable and behave itself; my Christmas lights won’t turn themselves on and off! (ok, nor the other 50-odd devices)
Need to add a couple of plug-ins to the system. Every time I try to add a device, I get an error “Z-Wave network failed to go into learn mode” and the Z-wave light goes out.
Why not assign a static IP address on the LAN by binding the MAC to an IP address?
Good idea.
I set up the Vera manually to use a static IP, but every time I restore the Vera, it reverts back to DHCP. I normally don’t reserve static IP addresses since it’s redundant in most situations, but in this situation it solves a problem!
So… Apparently my Vera doesn’t think it’s the SUC. No obvious reason for that.
Support had me reset the Z-wave network and restore a backup that they sent me, which I regret and wish they’d warned me about the effects of - different house ID, so all my devices are now not paired properly and are useless (or worse but slightly amusing, randomly triggered by the wrong scenes). >:(
After doing that, they’ve gone silent for the best part of 48 hours : Suggests to me that the people dealing with the issue don’t have the first clue how to fix it now. I think we’re in for a proper factory reset, re-upgrade the firmware to make sure all the bits and pieces are present, then rebuild the network the painful way - manually reset and re-include every one of my 50-odd devices. I will be cursing Vera by the end of the weekend!
That said, while I have to do this, I might take the opportunity to move to a Vera Plus for more power to handle automation… or nCube or Domoticz!! :-\
Best Home Automation shopping experience. Shop at Ezlo!
No z-wave light, no improvement from a reboot, nor from swapping user_data.json. Log was showing repeated LuaPnP failures with exit code 245.
