Just create the auto-lock for the first door, and name and save it. Then create an auto lock the same way for the second door and name and save it, and so on.
It'll look something like below in your Apps list:
1 Like
Gotcha, I didn't catch that the name field was editable. 
Thanks again! -Joel
Done! Mind verifying it works?
1 Like
Done! I'm not sure the toggle is the most elegant solution, but i tested it and it works.
2 Likes
Everything works great. Checked HPM part too and it's all good. Thanks for this update!
1 Like
@lewis.heidrick, @chris.sader, I'm not seeing the update in HPM. Do you guys see it?
I checked for updates and didn't see anything, code version in HE currently shows 1.01.
Interesting - had to uninstall from HPM and re-install from HPM to get it to update. But 1.02 is now installed. 
Thanks for the update, Chris!!
Hi,
I've been using this package for a while and it works great. I have a door contact sensor and it works really well. Thanks again Chris!
I have a ask for an enhancement. I have the Yale SL zigbee locks. You can manually lock them by pressing your palm against them on the keypad. It's a neat feature but, if the door is open and I accidentally brush up against the keypad the bolt comes out... and since the door is open the bolt slams against the door frame, making no one happy....
My request for enhancement is that you add a check to see if the locks changes state to locked while the door contact sensor is reporting open, and Retract the bolt. Ideallywithout loosing the timer for when the door should Autolock. I assume (I should have verified this) that the Autolock timer doesn't start counting down until after the door is closed.
But automatically retracting the bolt if it comes out when the door is open would be a very nice feature!
Thanks!
I did play with it in RM4. worked well. However, the autolock app stopped locking the door once i put that in. Could have been a coincidence, i'll debug a bit tonight.
I generally like the idea of having all automation related to a behavior in one set of automation so in case an update adds capability there is no risk of accidental conflict.
Just giving you options. I've been using it for a few months without issue.
It's probably an error on my part. I'll fix it tonight.
I'm tempted at moving the entire logic to rule machine, it is amazingly powerful.
Yea, but it does run slower once you build all the logic needed to handle this.
Is there a way to see which app package is consuming cpu and memory?
No they have all the applications bundled up under one process but you can see the execution time and runcounts. Along with totals that let you see how long certain apps take.
http://hubitat.local/hub/enableStats (Run this to start stat collection and let it collect for about 5 minutes)
http://hubitat.local/hub/stats (Run this after the 5 minutes has elapsed to view the stats)
http://hubitat.local/hub/disableStats (Run this to stop stat collection)
For Winodws PC's Shift + Windows Key + S is an easy way to take a cropped screenshot.
You can use these links to track down the apps and devices by putting the id's from stats. Just replace the bold letter words with the ID's from the stats.
http://hubitat.local/installedapp/configure/APPIDHERE
http://hubitat.local/device/edit/DEVICEIDHERE
If you have trouble with the links, replace hubitat.local with the ip of your hub.
Submitted a pull request to fix debugging so the switch actually turns it on and off.
I don't see a pull request. I see an issue, is that what you mean? Or did you actually submit code for review?
Let me check, maybe I didn't click submit for the code.
See it now?
I do. Working on it. Thanks
1 Like
Changes merged. Thanks for squashing that.
