This is still here on the production build.
WebCore refreshed the lock and this log was thrown again.
I'll try for some more detail if I can get it repeatable.
EDIT Removing and adding to HE and pistons again.
May have been corrupt like my iBlind. Stay tuned.
Ok.
Added back to everything and the lock status is correct on Commands only.
If I manually operate the lock the status never refreshes.
I captured the ZW logs and it seems that operating the lock manually sends no info at all.
My other locks send lots of data.
Do we chalk this up to a faulty lock?
Ouch.. Then yea, nothing was sent to the hub..
1 Like
Faulty lock it is.
I have lots of bits so maybe I can make a FrankenLock.
1 Like
If you haven't already, try putting fresh batteries in the lock before you scrap it.
2 Likes
Yes did that first.
I also tried replacing the lock components and I couldn't get anything to work except the OG lock/keypad pairing.
I came to the conclusion that the keypad is paired to the lock assy at time of install so swapping the body and keypad parts with the ZW card being the only common part that remains doesn't work.
I will have to delete the lock and re-pair every time swapping components. 
For now all I have to do is send a Refresh command to the lock every time the door contact changes. Oddly the Lock/Unlock commands work fine as well as the user codes.
1 Like
