The issue I see is that some of the community drivers broke with the change to JS, and there aren't alternatives available either system drivers or otherwise.
I am sure it wasn't intentional that these community drivers were broken. Maybe the community developer isn't aware that these are broken, or whatever.
It is possible that Hubitat can fix this incompatibility on their side of things, if they know about it. I know that has happened before where there was something in the back end that was preventing something from working correctly.
Yeah that was partly my point, I would have started with the community developer first just to see if they're aware of the issue, if they're still maintaining the driver, if they have a thought about how to fix it, if it's something about the community driver that really should be changed, rather than he staff patching something,etc. Don't know unless you ask.
If the drivers are hard-coded in a way that are not fully compatible with JS, there isn't much our engineers can do, short of rewriting the driver, which they have done many times in the past.
However, the problem may also stem from custom features that usually built-in drivers may not support.
If the problem is not specific to a custom driver, our engineers will be able to address any issues at platform level. This is a common practice that provides the fastest path to resolution.
I would strongly discourage taking this approach, though:
Although the rapid results may feel exciting at first, relying solely on AI can introduce new issues and make existing ones harder to diagnose.
A collaborative approach involving community developers or Hubitat engineers offers the best chance of obtaining reliable, lasting fixes for persistent problems.
Definitely. I wonder what the breakdown is currently. I imaging that JS user numbers are tiny compared to ZIP in Hubitat, it's only the C8 Pro that supports it and Hubitat continue to keep everything running on the older hubs (and rightly so)
Suffice to say I have not been silent
Correct but some system drivers appear to also be broke
100% - When I've looked at posts for the community drivers I have that were affected, they are dated, some being ported from SmartThings. One system driver with an issue that I've reported to Bryan was the Zooz RGBW Controller that controls my Fibaro RGBW2 modules. I did (albeit briefly) try the Zooz Zen31 advanced driver by @jtp10181 as a temporary substitute (apparently the Zen31 and Fibaro RGBW2 are the same hardware) but had the same issue with the state not being updated - maybe Jeff knows.
The two drivers I got working appear to be working as well as they were previously with a couple of changes.
It's maybe not convenient/a bit simplistic, but perhaps where a system driver is known to be 100% working under JS, its title could be appended with 'js' or something. It's only users who've migrated who will be able to highlight it to staff when somethings not right.
Yeah, I'm 57. I always got the sense that most users here are younger, but maybe this is an older group than I thought. Do we use Hubitat just because we are older and wiser? Seems the younger crowd is mostly on HA.
I've been on the home automation road since I was in my 20s, starting with X10, which I ran for over 20 years. A brief journey through both Wink and SmartThings led me to Hubitat.
At this point I'm settling in with Hubitat until it is gone, and I will work through any future issues like I have with past ones... a lot of bitching and moaning and then happiness when I get it working again, though trial and error or with help from the community.
Just thought I would chime in, I am 69 and graduated from some wifi devices to my 1st hubitat hub about 4 years ago. I have not had any issues after changing to ZWJS. 48 z wave devices including a fibaro FGBS-222, using custom driver.
That's what I'm doing also. I switched. Tried to let it settle. Switched back. Everything works as-is and I'm not inclined (usually) to fix things that ain't broken.
Well it became the proverbial 'straw that broke the camels back' for me. I didn't want to revert to ZIP if that is not where Z Wave is going and got no response after responding regarding issues with the particular device I was using. I switched a couple of devices out for Zigbee but then decided to give Home Assistant a try. My 40 odd Z Wave nodes are migrated to HA:
They all just work there. I was initially going to use HADB and keep Rule Machine doing everything but feel it's as difficult to do that as it is to start rewriting all rules over on HA. I've effectively ripped it up and started again - painful.
Yeah I'm not saying there's an issue with the protocol (despite my original whinge), just the translation in some drivers whether they be built in or community. I'm just unlucky that some of the devices I have wouldn't play nice with js here. Still using js in HA but there are no drivers as such; I don't understand the mechanics of it all but everything the device exposes is visible.
Don't know unless you ask. 
