Ok, 'Debug Logging' is on.
codeFetchComplete should be 1
You may need to run the "Get Codes" command and see if you can get that to finish.
If you turn on debug logging and open a logs tab you will be able to see what it is doing.
The driver has to go through every single code slot and ask for the code, so it can take a minute depending on how many slots the lock has.
Hi, been busy with kids for a couple days, where do I run 'get codes' command,
Everything is 'failing' again. I just did the update as well.
On the device page like @danabw showed.
Is the lock failing or just the code handling?
Programming any code is failing after I was successful programming 4 last week.
What about if you do it on the device page itself? NOT through LCM. Also click get codes on the device page to see what's showing up.
Ok turned on debug and clicked on Get Codes
Nothing happens on the 'device page'. I clicked 'get codes' and nothing shows
you need to have the live logs open to see the results
need to see the live logs, if getCodes isn't getting responses in an timely fashion from the device then there's a communication issue with the lock, and setCode will do no better in setting codes...
Yup what Mike said. That’s what I was getting at a dozen posts up. Been waiting for the info…
from my PC
Code handling, adding users mainly
Are you seeing anything under the Current States like I posted above?
This is the only thing we need to know right now:
- Turn on debug logs for the device
- open new browser tab with logs open
- Click the "Get Codes" command on the device page
- Post screenshot of resulting logs.
So I added 2 codes manually, and they are listed in the app as well above as code 5 and code 6, so it is communicating.