Possibly related to my previous report of issues with the switch to Z-Wave JS, I had six Z-Wave mesh devices that became unresponsive to Z-Wave commands. All six devices are Leviton ZW6HD 800 series dimmers, in mesh mode. One other dimmer of the exact same model came across and continues to work fine (I have seven of the Leviton ZW6HD in total).
I was using the Universal Z-Wave Dimmer driver and the interesting info from the driver's query/information capability is that the Leviton device is suddenly unknown ("Device Model UKN00"). This happened to all six problem devices but was not reported as unknown for the one working Leviton ZW6HD Dimmer.
Any attempt to interact with these "broken" dimmers through Hubitat resulted in an effective total loss Z-Wave on the hub (Hubitat went into a endless loop of reporting all devices timing out in the Z-Wave JS logs). I would have to reboot Hubitat to "calm" the network.
Broken:
Working:
The initial resolution was to exclude and re-include the six dimmers, but there was a "rub". Once re-included the dimmers worked as expected except that the Universal Z-Wave Dimmer driver could not correctly update state. It would cause device to turn on and off as commanded, but the reported switch state was always "On". Note, the one dimmer that was not broken is still using the Universal Z-Wave Dimmer fine. It's only the re-included dimmers that do not work correctly with UZWD
The fix to the switch state issue was to go back to using the built-in Generic Z-Wave Plus Dimmer driver. Using the built-in driver the dimmers work as expected - correct reporting of state as (de)activated.
The one thing I didn't think to do early on was try the built-in driver in the initial 'broken state' to see if that would also work around the original issue.
Standard trace logs for UZWD, post re-include but not correct state tracking:
