≪ View Page

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
hardware:space-door-lock [2025/12/27 06:18] – diamondhardware:space-door-lock [2025/12/29 10:17] (current) – diamond
Line 7: Line 7:
 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, code)` service call. **Code slots are 1-based, not 0-based.** These 200 codes are partitioned like so: 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, code)` service call. **Code slots are 1-based, not 0-based.** These 200 codes are partitioned like so:
  
-- `[1,   50]` - arbitrary and/or legacy codes, codes may be changed+- `[ 1,  50]` - arbitrary and/or legacy codes, codes may be changed
 - `[51, 200]` - member-specific code (150 total), allocated entirely by the Monolith - `[51, 200]` - member-specific code (150 total), allocated entirely by the Monolith
  
Line 13: Line 13:
  
 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. 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.
 +