I did not have any problems with the driver you linked to on the C-5. Even tried on a C-4 (even more different) and that worked, too.
If they are on 2.3.7 or earlier on the C-5, the Java runtime did indeed change in 2.3.8 (always been what it is on the C-8/C-8 Pro), but that's the only thing I could think of.
I have message on my c-7 with 2.2.8 can anyone help I just got 10 tuya presence sensors the ZY-M100 kind they connect but no state changes tried the generick motion the konbee and Xiaomi motion tried everything just not the custom driver but I can't load the custom driver gives me the same error message
You are 3 years behind in Hubitat firmware. Is this intentional, or an oversight? I would suggest that you are having issues due to what was said here:
Did do since all was working besides the ZigBee disconnecs and all but do have way to much stuff the rest was working fine and it seemed not worth the trouble but might have to now and I wonder if I'll loose any thing from the upgrade also did try an update at one point in the past caused failure and ad to restart and gave me a headache so I haven't update since I now have a home assistant waiting for a Chinese hub to connect the many Chinese product I purchased on a a hub just for them since I've been told so many things that I ad was messing my mesh I now have a giant box full of things that was the problem but they ain't on anymore and I still have the problems really been tryna ng for years and years to fix do love the motion lighting apps the simplicity of hubitat compare to home assistant but neither are perfect and seems I'll need hue hubs m3 hub home assistant hubitat and harmony hubs to make it all work like it should but like I said scared to loose some abilities specially the ones that are not under monthly payments and also I have lots of custome drivers and apps and that as been great for most part scared some might stop working as well so that the why the all and all
If you're afraid of a hub update breaking anything, you can keep a hub database backup (from Settings > Backup and Restore), restore any of the last few hub platform versions (from the Diagnostic Tool), and then get back to where you were before if needed.
But at this point, I don't think you're going to get much troubleshooting for a platform version that is several years old. The particular problem you note is likely due to the changes mentioned above, so the most reasonable choices seem to either do without this custom driver (or modify it to suit your older platform, perhaps removing this annotation) or upgrade your hub platform. Though these devices are old enough they might not work with the Zigbee stack on your older hub model, either, based on the below. So finding replacement devices, ideally ones on the compatible device list, may also be a better option.
If you are having problems, it may be best to state what they are more clearly. I would suggest using a clearly written, punctuated post to make things easier to read (the above was quite difficult) and including more detail about what devices you have, what problems you're having exactly, and what specific troubleshooting you have already tried. For example, if Z-Wave, this may be a good place to start: How to Troubleshoot Z-Wave | Hubitat Documentation
I'll try again and it's c-7 not 5 and my Chinese stuff is old also not new besides the ones I just got in get it's new and need updates but like I said it's more the none recurring payments I wanna keep
It's ZigBee tuya zy-m100 that I'm trying to catch nnect but can't install the custom drivers most likely because I'm on an old platform I have the c-7 hub and running on 2.2.8 so way old but besides the ZigBee problems most is great hubitat takes care of some important stuff
No one attacking your driver here some other dude got the same sensor I have working so I know it will work just gotta be able to install it but if the Jason thing works differently after 3.3.8 then some other stuff I have might stop working not a tech guy but tis does make sense