I’m having random driver crashes after multiple days of running flawlessly, and I’m really scratching my head trying to debug these. I first noticed it on a LAN driver, where after running for anywhere from 2 to 7 or more days it would just stop and become non-responsive. When I set up a Pi to monitor logs for multiple days I found that it stopped in the middle of emitting a series of events (all identical to events generated a thousand times before by the driver) with nothing in the logs indicating a crash. It just stopped. The only way I was able to recover was with a hub reboot. This has happened a few times with that driver, though I only caught it once with the Pi running logcat.
I’m also running 3 Zooz 4-in-1 and 6 Q sensors on a lightly-modified version of the stock ST z-wave sensor driver. Sometime around 3am today they all stopped reporting, which I noticed around 1:30pm. I wasn’t actively logging that driver, so no clue if logs would have shown anything, but a hub reboot this afternoon immediately got them all reporting again. I’m pretty certain that I had the same problem with that driver a week or so ago, but at the time I only noticed it on the Qs and blamed it on them being newly added devices instead of a driver issue.
This is really painful to troubleshoot since it seems to be a random number of days before it happens. Seeing it happen on two drivers now though is making me think it’s something happening that’s outside of my control.