Zwave Failed to Start

Community Playground General Discussions
1

I have somehow messed up my Veralite device after attempting to add a Monoprice door/window sensor. After trying to install the device, I ended up with a motion sensor, but it was of the wrong type. I attempted to delete it, but it would not delete. I reloaded from a backup, but it still was there. Which I ultimately think had been there prior to my attempt to add the Monoprice sensor.

In any case while doing a restore the 2nd time of a recent backup, the Veralite device got stuck in a mode with a blinking blue light. After hours of searching the internet for a solution, I finally decided to do a “Firmware Recovery” using the tool. I was successful at performing the recovery, and the Veralite device would complete the bootup and have all 3 lights on (Green, Orange, Blue), but I continued to get a “Zwave failed to start” message on the Web interface. I looked at the log messages, and see a zwave abort? with an exit code of 250, but I do not know why.

I then attempted to retstore to the older version of firmware that I had been running before this disaster, (7.06) and then restored from a backup. The green light and the blue light will come on solid, but the orange (zwave) does not stay lit. Eventually the web interface comes up and says the Luup has taken to long to restart and that I should contact support.

I have since done another “firmware recovery” and the device currently sits in that state with the continual message of ‘Zwave failed to start’.

I have reported this to support, but have not had any response other than to enable remote access.

I have NOT reset the z-wave chip as I know this will wipe out any hope of restoration of my scenarios, virtual devices, and etc that has taken me awhile to set up. However, this may be my only hope of fixing the problem.

I read elsewhere that sometimes a device will prevent the network from coming up, but I have removed the batteries from all of the sensor devices and only have my few light switches that have not been disabled. But since the problem occurred while restoring from backup I don’t know how those devices could have broken it.

If anybody has any thoughts or insight, I am open to suggestions.

thanks,

2

In all of your restores, did you also check the box to restore the Z-Wave network?

Your problem is in the Z-Wave chip. A reset/restore will be necessary. Hopefully there is a recent backup of the Z-Wave network to restore.

Only Z-Wave devices are stored in the Z-Wave chip. Your scenes, virtual devices and so forth are all in the Vera configuration(backup) not the Z-Wave chip. However…

If you do not have a Z-Wave network backup that can be used and have to wipe and recreate your Z-Wave network(excluding/including all Z-Wave devices), then your Z-Wave node numbers will change and your scenes won’t work since they address the previous node numbers. The scenes will still be present, but since the node numbers will have changed, the scenes won’t behave properly.

3

I have checked the box to restore the zwave network. I assume that the zwave network is saved as part of my normal backups. If it is not, then i dont have a backup. However if a restore zwave network is supposed to overwrite the chip contents then it doesnt work and I don’t know if a reset will work.

So it sounds like my only option is to try the to reset the zwave chip.

You have a good point in that I can restore my scenes and etc and then at least I can capture what I have set up. I have some code in a couple scenes that I need to recover.

4

Just to follow up. Vera support logged into my controller and was able to correct my problem with the Zwave. I have asked them what they did and am awaiting the answer.

I was then able to restore successfully from backups and everything is back up and running correctly. Thanks Vera Support!