VeraEdge: no access. "Luup engine is taking longer to reload."

[BruceWayne]

Hi,

For a week i have not been able to access my vera edge.
Nothing changed before that, no updates, no new devices.

- No scenes are running
- Tried several times to reboot, no change
- direct access also does not help
- firmware update not successful

I get this error message:
"Luup engine is taking longer to reload."

Any suggestions what i can do? The support has not replied to me for days, and it starts to get really annoying.

Thank you very much!

[carletoncompz]

Have you figured this out? I am having a similar problem with my VeraEdge. It has gone out twice in the last few weeks for days on end, and will not connect to the internet.

[myhomeserver]

Same here, This just happened on Feb 1st and I've been down since

[Zooz]

Are you guys trying to connect locally or from the outside via servers?
I was not able to connect for a about a week, until yesterday (Vera3/UI5). Local connection was just normal.

[integlikewhoa]

If your update failed a you need to power reset and try again, if that doesn't work they will have you hold down the reset button with a paperclip to wipe the unit clean then you can restore to a previous backup. If that doesn't work they are going to say unit is bricked.

Calling vera on Monday using a phone is your best bet. For the others you first need to unplug vera and replug back in.

[Santos]

Guys, what browser are you using? I have problems with Internet Explorer but Firefox works as expected. Previously Internet Explorer was working from within my wifi network and only failing when I was accessing Vera Edge remotely.

Maybe that's your problem. Try using a different browser.

[BruceWayne]

Sorry, i have not been able to fix this issue yet.
I get this error code after i have been provided with two links by the support team:

When you?re on the same network as the Vera controller, please go to the first link:
http://192.168.1.96/cgi-bin/cmh/tech_ra_check.sh?cmd=disable 
then go to the second one:
http://192.168.1.96/cgi-bin/cmh/tech_ra.sh

Obviously, the IP address is the internal one of the controller in my network.

"Provide this code: {serial number of my unit}-474501 to the support representative"

I will update as soon as i get a solution.

- I tried several browsers, and the apps (Vera and VeraMate)
- Update did not fail, it was an option on the trouble shooting page, but nothing happened
- i could not access the device from network or remotely

[legend99]

Just happened to me yesterday! Anyone thinking maybe there is a problem!

Same here, This just happened on Feb 1st and I've been down since

[Chrisfraser05]

I had the same problem and had to do a hard reset holding in the button with a pin

[BruceWayne]

If you do a hard reset, do you have to pair all the devices again? And before that, unpair them? This would be quite some hassle.

[legend99]

Once you do a reset, you then can use a previous backup that is stored by Vera.

If you do a hard reset, do you have to pair all the devices again? And before that, unpair them? This would be quite some hassle.

[integlikewhoa]

Once you do a reset, you then can use a previous backup that is stored by Vera.

If you do a hard reset, do you have to pair all the devices again? And before that, unpair them? This would be quite some hassle.

^^^^^ Yup as long as you have a back up with Z-wave network! And when you restore you check "restore z-wave network". This is why before you do an update or any major changes you run a backup, more importantly when you run that backup you use the button to backup the z-wave network first. By default it backups your settings but not all your z-wave devices. Your z-wave device backup is important when your restoring a device that has went missing, lost communication or like in your case missing all z-wave devices.

[Z-Waver]

Just adding my two cents for clarity.

Vera should and usually does perform a Z-Wave network backup when the nightly backup runs, after including a new device. For your safety, in the event that this does not occur as it should, it is best to do a Z-Wave network backup after the successful inclusion or exclusion of a Z-Wave node.

The Z-Wave network backup is stored as file on Vera. That file is included with every Vera backup. But, if you do backups without checking the backup Z-Wave network option, it is possible that the file could be out of date.

When restoring Vera, checking the restore Z-Wave network option applies the Z-Wave network backup file to your Z-Wave dongle. If the Z-Wave network backup file is from a few days ago, that's probably a good thing, but if it is months or years old, you might have to exclude and include devices that are not part of that backup.

[integlikewhoa]

Just adding my two cents for clarity.

Vera should and usually does perform a Z-Wave network backup when the nightly backup runs, after including a new device. For your safety, in the event that this does not occur as it should, it is best to do a Z-Wave network backup after the successful inclusion or exclusion of a Z-Wave node.

The Z-Wave network backup is stored as file on Vera. That file is included with every Vera backup. But, if you do backups without checking the backup Z-Wave network option, it is possible that the file could be out of date.

When restoring Vera, checking the restore Z-Wave network option applies the Z-Wave network backup file to your Z-Wave dongle. If the Z-Wave network backup file is from a few days ago, that's probably a good thing, but if it is months or years old, you might have to exclude and include devices that are not part of that backup.

Thanks for this!

[BruceWayne]

Good news,

The support has been able to fix the issue remotely. All back to normal.
I did not have to do a hard reset, apparently they could update the firmware, as well as installing a working backup.
All devices and scenes are working again.

Thumbs up for great support.

So if you have the same issue, they can help you.

Thanks everyone!