Lots of way to break down RM. I find that multiple smaller rules that stack/call each other makes it easier for me to break up a complex rule into smaller easier to code individual functions. It's also easier to identify parts that aren't working as you designed. Others prefer a single more complex rule to keep the total number of rules they manage smaller.
Happy to provide examples, I'll cut and paste some here. Also check out the post below. I put several rules in there that I used to code a z-wave keypad to operate a garage door, and I included quite a bit of explanation/documentation. Not exactly what you are doing, but it has examples of how to integrate connect several rules, use hub variables and connectors, etc. The keypad also functions as a lock (uses the same generic lock driver), so much of that is similar.
Final point - if you haven't installed the HE lock code manager app, I'd add that in for your locks. It's not really used in conjunction with any rules, but it's a great app for managing your lock codes. It can be used across multiple locks and multiple users in any combination.
