Running a Hubitat C7 - Have had my dog sitter code in my lock and the app for months. She showed up in the list of users and in the stats. When I set to enable at a future time, she disappeared in the list and the code could not be activated. In the device page under users, she was flagged for enabled at future date but the action never executed properly. I have used the disable on scheduled date and this worked fine in the past. Enabling directly also works. I have since turned on verbose logging but no details of any actions from LCM were detected. I had to delete and reinstall the app before I could add her back into my lock. After this phantom entry, adding her said success but still never showed up in the user list for any actionable items. There is a bug in the algorithm for adding at a future date and there is no garbage cleanup for artifacts that cause the application to break. It appears this has been an issue for years and still has not been fixed (Based on post history) and these just get closed out. This is an easily repeatable action so devs should be able to replicate and troubleshoot. I am using a Kwikset Lock with generic lock driver.
1 Like
I am not able to reproduce. Can you confirm that you followed all steps after adding the lock code or changing its options?
- Select Update user code options, then
- Select Next when you see User code option change request completed, then
- Select Done.
The last step is particularly notable, as that is what will save all app settings and create the scheduled jobs.
If that does not help (or if you wanted to check regardless), I'd be curious:
- On the app status page for this LCM instance, what do you see under "Scheduled Jobs" after doing this? You should see one for the enable and one for the disable times, depending on which is/are set.
- Do you see confirmation in Logs that the enable and/or disable times were set (when you do the steps above) if you enable "Verbose" logging under "Options" in LCM?
