The weirdness I see with my Yale and Kwikset locks since zwjs running generic z-wave lock driver is the lock code being read from (get codes) causes the driver to step from code storage number to storage number erring out so retrying many times before a success and stepping to the next location where the error cycle repeats. This can not be stopped without a hubitat reboot. If the driver is stopped the cycle picks up where it left off when the driver is resumed. Check the lock logs to see it that is happening.
This block repeats eventually working its way through all the code locations even though they are empty. Turning off encryption has no effect on the looping. After several minutes I will get an alert from Abode telling me there is a high load.
I split your post since its a different issue with locks than the other post, so it does not get overlooked.
Its odd that it seems to be out of sequence also. I wonder if this is related to the issue I found where two messages were being sent out in some cases (posted in beta).
I see it getting the 26 report, and confirming no changes,
Then it says fetching 28 but gets a 27 report,
Then says fetching 28 again but gets a 26 report again...
Would be interesting to see z-wave logs when this is going on, to see what the hub is actually sending to the device.
Could you try 2.4.2 that just came out and see if it continues?
Isn't Abode a security system? Or is it a Hubitat alert you are delivering through Abode?
opps. I meant hubitat.
