There were (are, in some cases) app/driver issues AND there were (are, in some cases) hub issues.
I always thought of it such that it was a lot easier for end users to test the app/driver impact 1st (as they can be disabled, and is sometimes the actual issue) while Hubitat worked on the hub side of things that end users can't do.
So what you’re saying is that when I had no custom apps/drivers installed and my hub needed nightly reboots, the bad apps/drivers were the stock ones? I had to add a second hub and use custom code to make the hub more forgiving of the stock apps.
Please don’t take offense. I feel a little good hearted razzing is called for now that so much progress is being made in hub stability. My original hub, that I had to reboot daily at one point, has been so stable since 2.2.3.118 that I even got so bold as to install Echo Speaks on it as a test. It hasn’t had a noticeable effect on the hubs performance in the past week and I disabled the reboot routine as well. Fantastic job to the HE team! Stability is appreciated more than any new feature you could have imagined.
Is there any particular action required to engage this feature in the update? Wait for nightly maintenance, try Repair on ghost device like below, or ?
Also, @mike.maxwell said he was going to look into the Zooz double plug, that he had one on order. Any love for the Zooz double plug in this release, or is that most likely a "Zooz fix required?"
I do have two Zooz ZSE18's. After updating to 2.2.3.135 the Z-Wave details page shows one with an OK status and the other as FAILED with remove, replace, refresh and repair options. However it is working and communicating with it just fine. So just an FYI. This is on a C7.
It is kinda ironic that I intentionally held off on moving to HE to wait until the platform had matured and offered broad device support and stable FW.
Then I decide make the move and my first HE device is the brand new cutting-edge C7 hub. Nobody's fault but mine.