No, database might be corrupted. Download all your backups from the diag tool for safe keeping. Then do a soft reset and restore the latest backup.
See if you can boot to the normal UI from there.
3 Likes
Everyone beat me to this discussion while I was cooking dinner. I agree with all of the previous comments. 
1 Like
That worked. I was able to restore from a backup and have access to the ui now. Earlier, I started factory resetting some of my inovelli zeave switches to add to the new hub. Should I re add them to the old hub before migrating?
1 Like
I wish you hadn’t done that - you’ve created some ghost nodes now.
Remove those switches from any apps and rules they are used in, and then EXCLUDE each of those switches from your C-7. That will delete the ghost node.
Then after confirming there are no ghost nodes, make the migration backup.
P.S. Your C-7 is easily fixable - you may not need a new hub.
1 Like
I wish I hadn’t. I gave up on this hub and thought I would be starting over. It failed once before, not with the power. So I think I am ready for the new one
1 Like
No it wont, not if they factory reset the switches. An exclude will just say unknown device excluded.
Do not remove them from apps, that should not be needed.
You could try using the z-wave replace feature to get them back in the nodes they were in before. [Guide] Updating Firmware and ZWave Replace
1 Like
With the C-5, I know it removed the device. Because I went through that.
If you factory reset the device, it would erase the node id from the device. So when you do an exclude how would the hub know what node/device to remove? The only link is the node ID which the devices stores (and erases when you factory reset). Z-wave devices do not have any sort of unique ID like Zigbee does.
Here’s what I do know. I updated the firmware on a bunch of Zooz switches using the first firmware updater that @bcopeland wrote as a device driver for the C-5. They factory reset upon update. Then I excluded them. The Hubitat device was removed. Then I included them.
The first switch I updated, I did not exclude before including it - and that created a ghost that I had to remove using PC Controller.
All the others, that I included after an exclusion did not.
I will give it a shot. Big thank you to everyone! Yo all saved me years of lost work!
1 Like
I actually found that they often did not truly factory reset when the update was done, they just lost the life line association so they would not send messages to the hub anymore. They would still know their node ID though. I found I could often times just send them a command to set the lifeline back (via configure) and they would start working again. Not all drivers set the lifeline on a configure so it may not have worked with the drivers at the time you did it.
1 Like
Got it - that makes sense!
And reconciles my claim with reality.
