What you are describing is the luup engine reloading, and during the reload, deleting devices and then discovering and trying to reconfigure the device.
This can be caused by: corruption of the DRAM, I now have proof of this with the ghost trips we were seeing which I believe is due to the vera updating wrong variable (in this case the “tripped” one) which gets fixed after a luup reload. Corruption of your user data… more likely in your case. It would be that your device data suddenly got corrupted and therefore the vera engine decides to dump it and regenerate it. And it does it… during the luup reload which is also why a luup reload takes so long…
You might want to check your vera for bad sectors.
that’s already one thing I suggest to Vera support and i’m waiting for another “level” of support to help me. It’s totally insane and unusable since a couple of weeks
Just to update this issue… after several months of waiting for the support to get back… after some emails telling me to wait 'cause they are checking with a higher level team…