Hubitat team, I love my fleet of Hubitat hubs, they are the core of my home automation system, and all of us love shiny new features, but please, please finish off critical platform improvements before moving on to the next project.
Itās been many months since ZWJS was released and itās still broken to the point of being unusable for many of us. Eg
https://community.hubitat.com/search?q=Zwjs%20in%3Atitle%20order%3Alatest
Disclaimer: I am not a Hubitat employee, just a user like you.
I think most are aware that certain aspects of the hub are done by different staff members. Gopher does a lot of UI stuff. Mike does Zigbee. Bryan is the Z-wave expert.
Just because new features are introduced, doesn't mean that a different feature isn't being worked upon. Things are happening in parallel.
I think Z-wave JS is a larger project than other items that have been implemented. Maybe Bryan is doing things in the background that we aren't aware of. Maybe it just hasn't been released yet. Hard to say, but I think it is a bit disingenuous to say they are starting new stuff without finishing existing improvements.
This all true, but specific to this point, release 2.4.3 is newly out and has many Z-Wave JS fixes. (Though there are always things happening in the background. 
) If you are still having problems with a specific device (and have upgraded), please start a topic and include all relevant details, including the device model, driver, and at least any debug logs from the device (staff may also need Z-Wave JS logs or to turn up additional logging on your hub if that isn't enough).
I reported my device issues back in April and got zero response from Hubitat staff:
I am aware of this, but I've been watching the release logs closely and have seen mostly minimal references to issues. My ZWJS title only search (in the OP) found over a dozen major issues ppl have reported, and if I were to expand that to content, it would be a much longer list.
ZWJS is a critical upgrade to support Z-Wave in the long term, and it just doesnt seem to be getting much focus ... at least from a customer point of view.
Did you see this?
I am sorry to hear you are still having problems, and I'm sure they can be fixed. But it's not the case that no work has been happening.
I can assure you this is receiving close attention. As noted, version 2.4.3 includes a wide range of fixes. Not every reported issue appears in the release notes, since resolving a single root cause often eliminates several related problems. Some items are outside our direct controlāweāre either waiting on upstream bug fixes or actively testing new updates. We know JS is still new and not without challenges, but overall performance improvements and the decreasing volume of support incidents show that itās headed in the right direction.
Did you see this:
and this:
Every time there is a new release that mentions ZWJS, I test it and provide feedback, 2.4.3 has not been the exception.
That is good to hear, however, it wouldn't hurt for reported issues to get a staff acknowledgement that the issue is on the defect list, so we know it isn't being missed.
Fair point! (Emphasis added by me.) 
Be good to hear that @bcopeland is aware of these, added them to a list. (The Naughty one.) 
@dJOS Can you grab the json state from these 2 devices? It would help a lot in identifying what's happening here..
/hub/zwave2/getNodeState?node=xx
xx is the decimal form of the node id .. not the hex..
Sure thing:
Smart Implant:
https://raw.githubusercontent.com/dJOS1475/HubitatRules/refs/heads/main/getNodeState_Fibaro_SmartImplant.json
Dual Nano Switch:
https://raw.githubusercontent.com/dJOS1475/HubitatRules/refs/heads/main/getNodeState_AeotecDualNano.json
I'm watching thid closely as I have a boatload of fgbs-222#s deployed.
Im still on zip gateway and id need full fgbs-222 to move to zwavej, assuming warts are less (and i don't know that).
Im mostly working on zip, but
Adding new devices/,inclusion of anything on this is usually pain and suffering. Maybe not better/different/no worse with zwavejs...
I have zero LR devices at rhe moment but i need to add them. Not sure which stack is best course yet.
Im at the pivot point,not sure if i have enough data to decide .
I've only got 2 of them, digital inputs work, but outputs dont. I'm not sure about the other features, as I don't use them. Im using the community driver atm, but I got the same results from the official Hubitat driver.
Thanks @dJOS ā¦ Give me a bit to sort through these .. Should have a better answer soon
One more questionā¦ What driver are you using?
Thank you Bryan, very much appreciated.
For the Aeotec Dual Nanoās Iām using the official driver. For the Smart Implant Iām using the community driver (it seems to work better as a garage controller), but I have tried the official driver and got the same result.
I already see the problem with the aeotec.. Fix will be coming..
The smart implant.. Does anything show up in the driver logs like the aeotec? That's what got me there fast..
Amazing, thank you.
The community driver only shows this stange "Child on @ ep5" message:
But in the events for the digital output I can see it tried to open to trigger the relay, but nothing happened. There's noting in the logs for the child device.
I can switch back to the Hubitat driver if that helps, but it's a massive PITA due to the parent/child relationship. If I can find my spare Implant, I'll do some more testing with that.
I found my spare Implant.
Ok, I'll admit I hadnt tested the Hubitat driver on 2.4.3.x and it is now working, it's just the community driver that isnt. 
Unfortunately, the HE driver is missing critical features like "Output auto off" making it unsuitable for many use cases like "pushing buttons".
Download the Hubitat app
