Actually, my tinkering is 100% documented. And, I am making limited changes each day according to a specific plan and then observing for a day for any issues. So, for instance, I added a single device type, and put them on automations, then tested those automations for expected functionality. THEN, I let them sit till the next day testing as possible and made sure they were acting as expected. Even though I have over a hundred items, I have only 14 device types. Having spent a few years on ST, I learned what specific things usually caused me problems over there and am working to a specific plan and checklist. Started with extenders, both Zwave and Zigbee, then bulbs, then switches, etc. Moving over from ST while using hub connect until all my items were over and I disconnected hub connect and then removed the hub connect apps. Then, I started with the apps making tweaks for the small differences between the platforms. This is more tedious, because I am only changing on thing a day to make sure I can isolate any issues. Also making local backups at the end of the daily testing period named with the change from the prior day.
This is how my brain works though. I do not do anything without a specific plan and checklists. Working in the Scientific and Quality fields, I also do not do anything without documenting every little step I take so I can backtrack.
Interestingly, i haven't run across ANY of the Zwave issues others have mentioned (specifically with Kwikset Locks and GE Switches). Maybe because before I started, I searched every different device type and searched and read every post I could find about the potential problems and the solutions. Additionally, many of the issues on HE that were posted about were also encountered on ST. So, I was familiar with them to some extent.
Wasn't really asking for advice on the reboots. Just why I wasn't seeing the backups. I know the nightly maintenance is supposed to clean things up. But, there are also several posts about how it may actually slow the hub down until the next reboot as well. So, I am eliminating that until I have everything settled down with reboots. Once everything is done and working as expected, I will pause the nightly reboots and observe. Then, depending on how the hub does over time, I will set the schedule as required (or even if required). However, there are ample posts stating that there are slowdown issues and a reboot seems to prevent/rectify. Not much different than needing reboots on the older versions of windows (and even on the current version depending on the machine specific hardware - I have two dells that will drop Wifi unless they do a reboot every 24 hours - should I have to? no, Is it a work around? sure. Am I going to keep doing it as long as it's fixing the problem? absolutely)
