Sorry, I guess I didn't have notifications turned on for this post...
This is what I have:
I tested it a bunch yesterday with specific times and short timeouts and it worked. I verified it both at the keypad and using HE's device page to show the lock.
Good luck!
tried a couple times with no luck. I have a feeling it has to do with the number for the position of the code. Can you use any number that is not currently in use? For example, I have 6 codes, so can I put it at position 7? It looks like you reset your lock completly, then set this up without any other codes since this is position one, is that correct?
The code was always at 1, but as part of my troubleshooting I did end up deleting all of the codes from the lock (I didn't do a factory reset or anything like that at the hardware end) using Lock Code Manager and then added them back in using Lock Code Manager.
I had started with codes programmed into the lock using the lock's interface and they were at the same location after deleting them via LCM all and putting them back in via LCM.
Originally LCM would show the lock-entered codes as ???? (even though the code was 6 digits long), but since deleting the codes and putting them back in with LCM, it shows the actual code.
One other thing I did was use LCM to set the code length to 6, which I previously done via the lock's keypad before setting the codes via the keypad.
So, order of events: Install lock, link to HE, set code length to 6 using lock, add two lock codes, , delete all codes using LCM, verify that lock didn't allow any of my codes (didn't test the factory codes), set lock code length to 6 using LCM (probably a no-op?), add in codes using LCM, start testing rules to add and delete codes, settle on using the configure() function before deleting and adding codes.
I hope this helps!
I checked the lock today, and the maid's code wasn't in it, luckily they don't come today (they'll come next Monday, this was a trial run).
I can't see that the rule ever fired by looking at the logs. I would expect to see something at 11:00:00 that says the Monday 11am rule fired, but nothing...
[app:8](http://hubitat.thecooksons.org/logs#pastapp8)2022-04-04 11:03:51.058 am [trace](http://hubitat.thecooksons.org/installedapp/configure/8)heartbeat 15 minute keep alive poll()...
[dev:33](http://hubitat.thecooksons.org/logs#pastdev33)2022-04-04 10:51:06.766 am [info](http://hubitat.thecooksons.org/device/edit/33)Mud room motion sensing light was turned off [physical]
And I see that it's next set to run tomorrow at 11am, which seems weird since tomorrow is Tuesday (Logs->Scheduled Jobs):
Is there a better way to debug this? When I was testing last week I was setting the time for every day of the week and just a few minutes in advance. Is "every Monday" broken?
Thanks!
And watching the logs at 4:57pm until now (5:03pm), I don't see the action running to delete the code, so I'm thinking HE thinks today is Sunday... I'll check the logs tomorrow to see if it runs.
I updated the rule to make it add the code on Monday at 5:15pm and then delete it at 5:20pm and that rule fired at 5:15 and the device status page shows the code, so it looks like the rule just didn't fire at 11am this morning.
Looking at "Past logs" I see this instance of the rule firing at 5:15pm, but the 11am one just isn't there. Let's hope that when I change it back to Monday at 11am it will fire next Monday.
Download the Hubitat app
