Hmm, that I don't have a good answer for. The lock is supposed to send these reports back to the hub right after you physically lock or unlock. (This isn't really a "refresh," which sends a command or few to the device that requests it to send the appropriate reports back; it's just a report the device should send on its own, though it's good to know that the lock really "knows" the lock status is accurate, at least.) Other people might have better ideas, but my guess is that either you have a mesh issue (again seems unlikely if digital locks/unlocks are fine and refresh works) or (this is my best, unfortunate guess) are one of the lucky few with wonky firmware.
"But, Robert, what about this?"
Here is a Hubitat user (and a former Wink tester) with an answer for why. It doesn't actually help anyone with problems on Hubitat, but it at least explains why it's the case for some people. 
