Basically, why is it trying to set code 1, then basically saying no change, and retrieving code 11. =/
Looking at LCM logs, it just retries over and over. Kinda wonder if it doesn't work since the length isn't being set properly.
Going to force length on the lock itself... since it doesn't act like HE is properly setting the length to 6 (entering a code fails after 4 digits)
Update: Yup. forced the code length to 6 on the lock itself (programming code, 8, then 6, and 6 again in my case (since I have 6 digit codes)). retrying failed LCM jobs immediately worked. So the "set code length" in the driver doesn't work properly...