Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[ISSUE] A homeowner's Matter code at a turned-off slot's index suspends the slot

Aperta
  • Qualcosa non va?
#1,695 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@raman325 ci sta già lavorando.

Dal 15/10/2026.

  • #1702 di @raman325 — aperta

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
22/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
backend

Direzione di ricerca

Start from the core code that maps a credential index to a slot's occupancy, and from the clear path that removes only LCM-tagged users and returns False. The slot_suspended repair is raised after 3 failed clears. Reproduce with the fake Matter lock: create an untagged user at index 3 with slot 3 turned off, then check that the slot reads in sync. Done means the off slot reads clear, the untagged code is reported as foreign, and set-path adoption still works. This depends on the unmerged #1694, so confirm its status first.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug
What happened?

Found while reviewing #1694 (the feature/clean-room-core fix for #1518). It only happens once #1694 is in.

On a Matter lock, a homeowner's own untagged user ("Mom") may hold a PIN at the credential index matching an LCM slot that is turned off. #1694 makes sure LCM's clear never deletes Mom's code. That part works.

The slot itself gets stuck, though:

  • The read maps Mom's credential to the slot by its credential index, so the slot reads as occupied by its own code.
  • The clear only removes LCM-tagged users, so it finds nothing to remove and returns False.
  • After 3 tries the slot is suspended with a slot_suspended repair saying "a code may remain". That repair can never be resolved, and it calls Mom's code the slot's own.

Expected: an untagged user at a slot's credential index counts as someone else's code on the lock, not as the slot's own. The turned-off slot reads clear (in sync), and Mom's code is reported separately, like any other code LCM doesn't manage.

Constraint: we can't just stop mapping untagged users by index. Set-path adoption needs that mapping: a pre-tag LCM user is adopted and tagged on the next write. So this needs a new kind of reading, e.g. "occupied by an untagged user at this index", that the core treats as foreign when the slot is off and as adoptable when it is on.

Steps to reproduce the issue
  1. On a Matter lock, create user "Mom" with a PIN at credential index 3 through HA's own Matter fabric. Mom is untagged.
  2. Configure LCM slot 3 on that lock, with its user turned off.
  3. Let sync run.
  4. Mom's code stays on the lock, as it should. But slot 3 never reads in sync, and after 3 clear attempts it is suspended with an unresolvable slot_suspended repair.
Home Assistant Version

dev (test harness)

What version of Lock Code Manager are you running?

feature/clean-room-core with #1694

Lock make and model

Matter (reproduced with the fake Matter lock)

🤖 Generated with Claude Code

https://claude.ai/code/session_01Ej3snRj69NSu2qB2b9td9J

Lingua principale
Python
Stelle
108
Fork
18
Merge medio
2h 7m
PR unite (30g)
130

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di raman325/lock_code_manager

Tutte le issue di raman325/lock_code_manager

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.