You begin by taking a backup NOW and saving it locally to your PC.
That step 'cleanses' the DB. No corrupted data is saved.
Then you do a Soft Reset that deletes the DB in the Hub.
The reboot finishes with you having two options: Start over adding Apps and Drivers and Rules OR restore that backup you just took. You will have exactly what you had before, with no corruptions... assuming there were any.
As has been mentioned, all your devices are intact. After the reboot, you'll get the green start screen with "Restore from backup" in tiny type at the bottom..
Soft Reset should be a fearless step. In fact I've occasionally suggested that everyone try it at least once.. so when you NEED it, it's not a strange process.
I use this process several times a week when I'm doing a lot of testing. I have what I think of as a "Library" of backups that I can restore to test various configs. For example I have a backup with No HubConnect installed. So I can restore that and then install HubConnect and verify all the steps are still intact. Then I just Soft Reset again and go back to my 'today' backup or on to yet another test.
Hi there, we have replied to your ticket with further instructions to perform the Soft Reset, this morning around 10am. If you didn't receive the email, please check your spam. Let us know here or via email if Soft Reset doesn't help.
I'm walking on eggshells, tho. Have no clue what hosed it up.
No clue what got zapped when in the DB cleanup, but it does sorta seem like I'm seeing one of my new dimmers NOT referenced in places I expected it to be.
Make a backup after each new device and the rules you add for it. Then wait a bit and do the next then maybe you’ll be able to find it and it will be little lost if is acts up again.
@bobbyD Hmmm..... It seems that I may have ended up with another serious issue.
It appears the hub isn't receiving any Z-Wave commands.
I'm having no luck getting the Hub to respond to Z-Wave initiated trigger events. It seems to be able to "send" Z-wave commands as all the devices seem to generally behave on command. Refreshes seem to at least generally work "on command" but I'm not getting rules to fire on "contact sensor changed", button tap/double tap, motion, etc.
So------------ I messed around for a bit-------------------
And. Not much clue what happened--but it seems to suddenly be more cooperative.
I did a "refresh()" action on nearly all my devices--and I did a Z-Wave "refresh" one "ghost" node. I manually ran some actions--and did a Zigbee button action. But, not sure what made the z-wave triggers suddenly come to life.
I'm always nervous about those devices that show up empty in the Z-Wave Device list with nothing but a "discover" button. I truly wish I knew what those WERE before they got ghosted.
If there is ANY way you can have some sort of "(was: xxx light)" text there, that would help me know what disappeared.
And, after all this, it seems that the Inovelli Red Series Dimmer that I was using (with no load) to associate with another of those dimmers--but was acting wonky--suddenly started working.
Due to all these issues, I decided to do a full "repair". 7 devices failed, so I manually repaired them--and they worked that time.
FYI: After all that, things did seem to be mostly back in order. There were a group I didn't think I put in an action--but I sure wouldn't swear to that.
It is a good thing to have a "soft reset" under my belt.