Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| hardware:space-door-lock [2025/12/27 06:18] – removed - external edit (Unknown date) 127.0.0.1 | hardware:space-door-lock [2025/12/29 10:17] (current) – diamond | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | # Space Door Lock | ||
| + | |||
| + | The space door lock is a Yale Assure lock. It has Z-Wave capabilities and is connected to our local Home Assistant. | ||
| + | |||
| + | ### Door Code Provisioning | ||
| + | |||
| + | The lock can hold 200 codes in its memory in total. Each code can be set via Home Assistant using the `zwave_js.set_lock_usercode(code_slot, | ||
| + | |||
| + | - `[ 1, 50]` - arbitrary and/or legacy codes, codes may be changed | ||
| + | - `[51, 200]` - member-specific code (150 total), allocated entirely by the Monolith | ||
| + | |||
| + | Door codes generated by ButterflyMX for each member are automatically set into the door as well. With this, whenever door access is provisioned for a member via ButterflyMX, | ||
| + | |||
| + | Note that because of the theoretical 150 codes total limit, the system should keep track of what 150 codes were used most recently and be able to automatically provision an old code that hasn't been used the moment it detects that member entering via ButterflyMX. | ||