Advanced Usage

WIP!

Lock Code Manager allows you to manage the slots for a single lock or a group of slots. The only requirement is that a particular slot for a particular lock can only be managed by one configuration.

Let's say you have the following locks: lock.lock_1 lock.lock_2

You could have one config entry for lock.lock_1 and lock.lock_2 slots 1-4 and a second config entry for lock.lock_1 and lock.lock_2 slots 5-8, but if you tried to create the second config entry for slots 4-8, it would fail because slot 4 is already being managed for at least one of the locks in the first config entry.

If you are trying to figure out how to automate lock codes for a rental property (as an example), you could have a config entry that manages the permanent PINs for you and your staff and a second config entry that manages the temporary PINs you assign to guests. All of the options (whether the PIN is enabled, the PIN itself, the name assigned to the slot) can be updated using the appropriate service call. For example, to update the PIN, you could call text.set_value on the entity ID for the slot's PIN.

While setting this up will definitely require some work, the integration is designed to maximize flexibility and give you as much control as possible.