[Feature Request] RFID - on Slots

Open
#830 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
embedded-iot

Research direction

The issue names no files, tests, or entry points; begin by tracing how code and RFID slots are represented and how current lock state is read. Done means defining fob-only slots without erasing existing codes, supporting names, and determining whether current code/RFID state can be imported from the lock.

Written by the indexing model from the issue text.

Description

enhancement
Problem Description

Hi,
On my Yale lock we use Codes & RFID Fobs. I do 1-10 codes & 11-20 for fobs. i want to see slots 11-20 but they should be fob only not for code use. So, unsure if you cover this already or not as i don't want to enable them and erase the folbs currently setup.

Feature Description

is there away to have the slots allocated to fobs setup with names? i assume that would mean that the codes shouldn't be erased when adding slots. Also could the manager pull the current codes/rfid state from the lock, this would save having to re enter and give out new codes to people?

Anything else?

No response

Dominant language
Python
Stars
105
Forks
18
Avg merge
8h 53m
Merged PRs (30d)
81

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from raman325/lock_code_manager

All issues in raman325/lock_code_manager

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.