The restore from the Cloud is certainly part of the problem. In my attempts I had restored migration backup a few times. I went back and recreated the backup to ensure I had a good backup and then restored. I also ended up going back and removing the LR devices and creating the backup again. Nothing would allow LR devices until a radio reset was performed.
In the end I restored from Cloud to get all the apps and config, Reset the Zwave Radio from the diagnostics page, removed all now non functional Zwave devices from the devices page. Performed another shutdown, removed power for 30 seconds, and then restarted. Then start to add Zwave devices back again.
I am using Smartstart for pretty much everything in my case
So far that has worked fine, now I just need to go through and fix all of my automations/apps and such.
Now I don't think anyone has been able to say what is bad from the backup. In my setup the C8 was loaded from a migration backup made on a C7. When I moved to the C8 Pro I use the migration process again. I was able to add these devices on the C8 during the beta. I wish I had a way to test what would of happened if I had never added the LR devices to the C8
2 Likes
The C8-Pro has ancestry back to a C5. The C8(test hub) that I tested, failed until I reset the radio,
and restored from platform. Only then was I able to add a LR device. My C8-Pro, I am not ready
to completely start over, as I need to restore from the cloud. Most of this is listed in the
beta channel discussion.
Well to be fair I did not say to restore from a cloud backup, but I also did not specify not to. I was implying to reset it and start over by not saying anything about restoring it.
1 Like
So if you switch to my driver after pairing it with the stock driver does it work fine now?
I am thinking maybe it got stuck in a state of "pending changes" which then can block the full configure from happening.
I was just able to delete all the states and the child from mine, and then configure ran and added the child back no problem. I will test a full inclusion later this week.
Something is way off with my hub. I saw another weird job a little while ago. Looked into it more and found a bunch of scheduled jobs for devices and apps in the past. So as of that i am not sure it is your driver.
I just backed up all of the smartstart data to my tablet. Then from the diag tool restored to the firmware the hub was shipped with. Going to work through the upgrade and test on 2.3.9 again before i restore anything to make sure that is resolved. Once i confirm that i will attempt the restore again.
Gremlins must have intercepted my hub before i got it.
1 Like
Ok let me know, its funny because another person is also having some ZEN30 troubles recently but I trust your capabilities much more than a random new user12345. I was thinking maybe the issues were related somehow.
So I have gotten some time to work on this. I did validate that after a soft reset without doing a restore I was able to use your double switch driver on the C8 Pro.
What is really throwing me off is that when I do a restore from the migration cloud backup I am getting a bunch of jobs that are in the past. Like days back from when the migration backup was likely taken.
I just did a restore from the last Migration backup I took. After restoring with that backup i have these jobs listed
I also just noticed this error with the scheduler..
I am fairly certain i saw something similar with the previous backup as well so i think this has persisted through multiple back jobs while working this.
I have my backups saved on my unraid server going to do a full reset and then restore from that to see if i get the hub back in a functioning state that can do adds. If i get all my apps and such atleast i can start to add devices back with the apps and such on there.. 
1 Like
I just tried moving one of my ZSE41 800LR devices to LR and is has done something similar.
I ceated a virtual device and replaced the ZSE41 in all the apps with the virtual device. I excluded the device (It wasn't incuded initially with SmartStart.) Included it with SmartStart. Realized I hadn't upgraded to 2.3.9.xxx. Upgraded. Deleted the SmartStart record. Factory reset the device. Added it via SmartStart. This is where I am now. 
Not sure what to do now.
Interesting discrepancy: If I go to edit the SmartStart entry, this is what it shows.
I'm not sure if it is, or is not included. My bet is it is not included.
@jtp10181 Thank you for this app!!! It is a great help for ferreting out these issues.
1 Like
I really can not give enough praise for thr SmartStart App that @jtp10181 created. It is fantastic and is a great way to backup your SmartStart data so if you ever need to exclude and add a device back it is super easy. It should also make it easy to switch hubs. This would have been such a headache without it.
I think i finally have it. In my case i needed to follow these steps.
- From Diag menue perform a full reset.
2 Restore from migration backup exclude zwave Radio data as it was part of the problem.
- Reset Zwave Radio
- Restore last local backup prior to migration.
- Load Smartstar backup file and start addinf back.
I had to reset the radio one more time because i had to many devices enabled for Smart Start. After adding about 10 or so switches the zwave radio just kind if blew up and was spewing busy messages. I have been keeping it limited to 4 enabled devices at a time now it i hasn't flinched and i can't keep up because i still need to do exclusions
So in the end it was two issues.
- The Zwave radio for some reason was in a bad state for the LR devices (the radio reset/exclude from restore was for this)
- The backup was having some kind of issues with the scheduler that wasn't obvious and didn't cause a complete failure. (The second restore to a older local backup was for this)
1 Like
To do a backup on the SS app did you just disable everything then use that automatic backup file?
I am going to add another options to just back up the whole thing without having to do that but I suppose that works for now.
Pretty much. I disabled all of the items in the list and the used the Hubitat file manager to download the file to my tablet.
To restore I installed SS, Opened it up to let it build the file and then overwrote the file with what I downloaded.
I did find a few quirks with it with suggestions for it
Observations
- After uploading the file, and I clicked on the option to load from the backup file everything appeared enabled. It wasn't though.
- Because of observation 1, I found I needed to disable and enable each device. During this process it would appear that two objects were list as disabled. Once I enabled though the entry would be back to one, So this is mostly cosmetic, but could be jarring for someone running through it the first time.
- I also found that it is important to only keep a few devices enabled at a given time. My initial attempts to use SS and having a everything enabled and going through and quickly excluding them I found that eventually I would trigger a Zwave Busy signal, Fail inclusions, and in general getting the Zwave radio in a bad state that was unrecoverable.
Suggestions.
- For observation 1 and 2, I would think finding a way to restore the list disabled would be the preferred option. I think that would be the state you want things to be in anyway so you can get the device prepped in a controlled environment
- This probably needs more experimenting, but when I self limited myself to only 4 enabled devices at once, stability with the process was achieved. It potentially could be a few more or even double that, but some kind of limit of enabled devices may help stability of the Zwave mesh while adding devices in back in a quick fashion.
- I would add a emphasis somehwere on downloading the file periodically in case of a hub failure or migration that it may need to be added to a new device.
If @support_team are watching there were clearly two issues that occured. The LR issue that triggered this initially, and the Scheduler problem in at least the last few backups. If you want to look at my cloud backup to see how it failed for those two items have at it. The LR issue could be related to other reported problems. The Scheduler on the other hand scares me. That wasn't super obvious and didn't completely break my hub. It just performed weirdly like it was sluggish and some device/app tasks just failed to run. Maybe worth looking at the cloud/migration backup process to see if anything weird is happening there. I don't have Hub Protect either. So this was just for Cloud Migration between the C8 and C8 Pro.
1 Like
I was just wanting to clarify. 
When the disable backup is loaded it should come in as disabled. Only way it would show enabled is if it was in the list pulled from the hub. Possibly since you started with an empty list it did not work right, I did not test that.
1 Like
So i just keep getting strange things.
I finally got my C8 Pro in a good state and made sure all of the automations are setup properly. So to ensure no conflicts I wanted to reset the original C8.
Well I used the Diag tool and did a Full reset, It performed the rest and powered down. I then had to pull the power to restart the hub. I went through the process to setup like a new hub. Went through the initial new customer screens and it all looks clean. Then I went to go fully turn off the Zigbee and Zwave radios.
The Zwave Radio did not clear. It still has all of the devices listed.
The Zigbee and Matter setup did clear though. The Zwave stuff is garbage anyways because all of that stuff has been excluded multiple times per all of the above stuff, but dang.
Just to validate I powered off the hub and pulled power one more time and left it without power for a while to ensure the radio full drained and reset. After that subsequent reboot the data was still there.
I just logged back into the Diag tool and performed the option for a reset but just on the Zwave Radio. That seemed to do it. All Entries are gone.
Did you by chance have the z-wave radio turned off when you did the first reset? I found that a reset will just turn the radio on but not reset it, was reported in the beta group.
I don't believe so. I wasn't worried about it since all the zwave radio data was no good since I had to reubild everything zwave on the C8 Pro.
