Hey Dan,
Unfortunately, the latest platform updates have broken again the pairing for these Zigbee-3.0-only devices, which were working for a short period when the C-8 was first publically released.
My smart plug TS011F _TZ3000_okaz9tjs, my power strip/extension TS011F _TZ3000_cfnprab5 also can not stay connected to HE with the latest platform versions ( currently on 2.3.5.123). They were working OK with the first publically released 2.3.5.1xx versions.
There is nothing that can be done on a driver level to fix these connectivity issues, we have to wait for Hubitat team to find and implement a solution soon.
Some technical details from your logs analysis:
When paired as a new device (DNI: CB07), the valve TS0001 _TZ3000_5ucujjtsand sent the first data packet at 08:12:32.642. Then it communicates normally to the hub until 08:12:39.887 when ZDO command responses for clusters 8005 (endpoint response) and 8004 (simple descriptor response) are received. These responses are the result of a previously sent ZDO command "Active Endpoints Request" (ZDO cluster 0x0005) and "Simple Descriptor Request" (ZDO cluster 0x0004), which commands are usually part of the Zigbee pairing process. This driver simply parses and processes the responses to these system commands but does not send such requests. (I also see the reason for an exception thrown in the code , will fix it in the next version, but this is not relevant to the device disconnection problem).
Then, at 08:19:50.214 (5 minutes later) the valve joins the Zigbee network again, but the Device Network Id (DNI) is now different - 838D. A few seconds later - new DNI : A6F6, FCC3, 4A84 ..
The device is not operational at this point... : (
I am monitoring the HE forum and I am applying and testing the latest platform fixes for my problematic TS011F devices ASAP, I am sure when these get fixed, the problem with this valve will be fixed too.
