I managed to get all my devices working (sorta) through a combination of re-interviewing and re-including (largely the latter). I attempted to reset the device and replace, but for whatever reason the device always ended up being excluded instead. I was unable to get the ZSE40 to include so I replaced it with a Zigbee device I had around.
For the record, ZWJS doesn't solve LR inclusion or removing ghost nodes 
I spoke too soon - several of my wired devices show as having a route, completed the interview with the right security, etc., But are not reporting status back to the hub. I'll need to play with it more this weekend to determine which devices work and which don't. Re-interviewing, repair, or hard restart of the hub didn't help.
So I went for the ZWJS. Took me over 5 hours to get everything back working. Most of my devices responded affirmatively to being interviewed. However enough devices looked ok but did not work which I tracked to the devices not reporting their status. A Rule condition was not able to determine the correct status of a switch or the level of a dimmer. Trying to get those devices to report ate up most of the effort. Leviton dimmers mostly. I tried changing the driver. I tried power cycling the device, I tried several interviews. What wound up working on two of the dimmers ZW6HD and two of the 4 Zen 37s was to exclude them, factory them, and include them with all that entails. Then I had some rules what did not run correctly until I edited the rule devices. Uncheck then recheck them and save. I think it was for devices that I reincluded. Folks. Don't change to ZWJS unless you have some time to kill getting the hold out devices to play nice again.
That is not the right driver for that device, it may expose settings for the Zooz that do not align with your device. Unless you have looked up the parameter numbers for the Zooz and your device, and they are both the same?
My custom ZSE40 driver could be used instead, it will disable all the settings if it does not detect the correct device, but all other functions will work. So it can be used as a generic driver for devices of the same type: [DRIVER] Zooz Sensors Advanced (ZSE11, ZSE18, ZSE40, ZSE41, ZSE42, ZSE43, ZSE44, ZSE70)
Yes it does, the system tries to match your device up with an installed driver and then runs a configure among other things. Your Monoprice device is not in the compatibility list though so there may not be a driver verified to work on it.
@jtp10181 Thanks for the input Jeff!
The driver I indicated appears to be reporting seemingly appropriate numbers and only the occasional error (which may be triggered by my futzing). The current states DOES NOT include an indication of sync status. That driver or at least a driver by that name (but not annotated as "new") is listed for use in the Hubitat officially supported list from what I can tell. However I do not know how I would be able to compare the adjustable parameters in the GUI as the driver preferences page does not list the associated parameter numbers.
When struggling to get these things out of "pending" status, I did try your indicated driver, and parameters 1-7 appear aligned. Your driver also appears to offer some very nice additional features like offsets for the sensor readings, motion clear delay adjustment and adjustment of the wakeup time, but they are not listed as availabe in the 15902 manual tables so I didn't know if they would work. When you say unavailable parameters are disabled, do you mean they are simply not presented to the end user?
I switched back to the "Zooz 4 in 1 Sensor New" because your handy sync status indicated that one of nine changes pending after full config/ force refresh/multiple wake up triggers refused to sync. I also left it for sometime in the hopes it would resolve itself. While I most appreciate that you are trying to create universal capability, as I didn't know what that parameter might be associated with (and this is not a Zooz device), I moved back to the other "official" driver.
If the pending change is not a concern, or there's a quick fix on my part, I would love to use your driver and the added capabilities - particularly the motion clear adjustment!
Thanks again!
Are you talking about a Zooz ZSE40 or the Monoprice device listed above?
If that system driver is listed for the monoprice device then I would use it. I searched the compatibility list by the model you have and came up with nothing.
My driver does not present any settings unless it’s a ZSE40, otherwise the settings would be hidden. So not sure how you managed to get all the zwave settings to show.
I'm talking about the monoprice 15920 as listed in the compatibility list
It looks identical to the zooz device but runs on two AAA batteries as opposed to the lithium button cell in the zooz. Perhaps it has the same chip etc and possibly slightly different firmware.
Not showing unavailable settings was my recollection from your Advanced Plugs driver.
FWIW, my update process went extremely smoothly. I use no security on Zwave devices, except for locks.
My lock and every single mains powered device worked perfectly fine within 5 minutes of the first boot after going from ZIP to ZW-JS.
All of my battery powered devices failed to connect automatically. It was no big deal though, I just went around my house to each remaining device with my phone in hand on the Zwave Settings page and hit the "refresh" button on each pending device while also hitting the wake button on the device. 10 minutes later and everything was back in business.
After that I upgraded the Zwave controller firmware, and there were no hiccups at all after that. Everything is working as it should.
I would just stick to that driver then, I guess it is the right one for it.
It should pick that one when paired, but possibly if you used security that changes the clusters and makes the driver matching not work the same.
I haven't made any security choices that I'm aware of with these devices. When I included them back after failling to get them to wake up with ZWJS, the hub picked "Generic Z-Wave DT Notification Sensor" (no idea what that is) and the official list driver is "Zooz 4-in-1 Sensor" not the available "Zooz 4-in-1 Sensor New" which I assume is just an updated version. It seems to handle the basics. If the lights don't come on when I walk into the basement I suppose I can probably use the switch 
For anyone else with these devices: I just checked the log with the ZSE40 driver, with the pending change sync status the device did not report any sensor data. So close and yet so far
Thanks again @jtp10181 - the help and advice is most appreciated.
I also finished my switch to JS and have all of my devices working after battery powered device wake ups and re interviewing some mains devices.
The only issue remaining is 2 of my 4 Homeseer HS-WX300 dimmers are not automatically updating status changes to the hub. Everything else works on them. I tried a hub power cycle, several re interviews, configure, and zwave repairs, but can't get switch state refreshes to happen without manually refreshing in the device tab. It's been almost 72 hours since the switch.
I have several long rules using the status LEDs on these switches, so I'm really hoping to not have to exclude and re include them. Anything else I can try?
This happened with a few other devices during the beta, and @bcopeland fixed the issue at the platform end.
So I'm tagging him on this issue.
Servalan (& Jeff) @jtp10181
Other rambling observations . . . (still running 2.4.0.151 but reading all I can before upgrading)
I currently have 3 of the Monoprice 15920 (Vision Security hardware) and believe they initially defaulted to Zooz 4-in-1 Sensor New in Hubitat
With help from the Basic Z-Wave Tool, I have come to the conclusion that the firmware inside the Monoprice(s) is slightly different to both the (auto-chosen) default driver as well as Jeff's ZSE40.
Namely, Humidity Detection (param 3) and Light Detection (param 4)
Can't prove it, but it's also possible that the Sensitivity (param 6) settings are reversed in the order of least sensitivity to most sensitivity on the 15920.
Either way, since all I really need are adjustable motion sensitivity and adjustable cool off times, I have mostly switched to the Generic Z-Wave Motion Sensor for my Monoprice 15920(s), which has no configurable parameter settings. I just switch to the Basic Z-Wave Tool if I need to change anything. (Aside: Why is there no Generic Z-Wave Plus Motion Sensor driver in Hubitat?)
I'll revisit & test the Monoprices again once I upgrade Hubitat to 2.4.1.XXX and the ZW-JS.
Was coming from an old Vera 3 which was using non Z-Wave Plus firmware. Have had the C8 Pro for 14 months and having a blast. Adding Z-Wave Plus (& Zigbee 
) hardware as pocketbook allows. Still have 2 Leviton non+ wall dimmer switches and can't wait till I can replace them and stop using the Z-Wave Poller app.
Had these Monoprices in my closet waiting 'till I buy a Z-Wave Plus controller. Liking Zooz and have since added (3) of the ZEN77, (2) ZEN04, (1) ZSE11, (1) ZSE41.
Of course, really enjoying the "Advanced" drivers and have contributed to support Jeff's continuing efforts.
Sorry for barging in,
/Ramble mode off
Hi @NewDude,
I appreciate any input I can get - Welcome!
If you don't have it, here's a link to the manual. The parameters are identical to the ZSE40 from what I can tell: The ZSE40 indicates retrigger period in seconds but I think that might be a typo. The 15902 lists minutes for that parameter. As for motion sensitivity the manual helpfully doesn't list if 1 or 7 is the most sensitive LoL. There's also command class and status info.
I haven't tried the basic z-wave tool - By the sound of it, you can send a parameter setting to a specified device... I will have to check that out! Keep me posted if you make further progress - though perhaps we should create a topic since this is for ZWJS issues. Good luck with your transition to ZWJS!
After more weirdness with my rules, I figured out that the "universal z-wave dimmer" driver in use with my Leviton ZW6HDs were not reporting the correct state. Like off or on or dimmer level. So my conditions could not do the expected branching. I tried a Hub reboot, Device power cycle, re-include but nothing fixed the device status issue. I gave up and switched to the generic z-wave plus dimmer driver. With that driver the device status is reporting and so my conditions are now branching correctly. So if your buttons or other rules are being wonky after switching to ZWJS, check that your rules are in fact showing the expected values.
Always good advice when troubleshooting.
I'm using the Universal Dimmer Driver with a Minoston dimmer plug and it's reporting changes quickly and accurately, FWIW. Another YMMV.
I can't get a ZEN31 and ZEN21 to work with ZWJS. I have worked on it for the last 2.5 hours. removed-readded, unplugged device, unplugged hub, and nothing will control or update status. I finally had enough and put it back on legacy zwave and now everything is working and reporting as it should. Guess I will wait some more for more bugs to be fixed.
Will do (in it's own topic). Thanks for the manual, identical to my copy.
I have several Zen21 switches on ZWaveJS with no issue.
If a particular device in your mesh doesn’t work, make sure you re-interview it. Sometimes, you may have to do that a couple times.
There’s zero need to exclude/re-include, which you appear to have tried.
I didn't remove the ZEN21 but did the 31. I have tried all that also with the re-interview and it said DONE but that seems like a generic message since you can type in 0000000000000000000000 and it will say done. I tried everything I could think of before I reverted back and now that I did it is all working without ZWJS. Oh and I did give it 24+ hours to fix itself and it didn't. Noticed this morning when my night scene still had devices on this morning as in the kitchen counter lights (ZEN31).
Download the Hubitat app
