[ISSUE] Events with Matter+Aqara U200

[jprasm]

What happened?

Man, I've been waiting for this update and this integration!
I've got the integration set up with a couple of Aqara U200 locks. I can add and delete user codes to the locks just fine using the integration. All users and homekey were deleted prior to adding users/slots.

There are a few issues that I'm seeing:

1. I cannot disable a code - tried a binary sensor with the calendar, tried manual disable. Nothing. Once a user slot and pin have been put in, its active no mater what.
2. The event entity for each slot is greyed out and 'unavailable' - is that normal?
3. The integration doesn't seem to fire any events (probably related to Initial strategy implementation #2)

Nothing in the logs.

Steps to reproduce the issue

...

Home Assistant Version

2026.4

What version of Lock Code Manager are you running?

2.0.0

Lock make and model

Aqara U200 firmware 085

Debug logs (paste)

Debug logs (upload)

No response

Device diagnostics (upload)

No response

Device diagnostics (paste)

Browser console logs (paste)

Browser console logs (upload)

No response

Screenshots

Anything else?

No response

[raman325]

for 2 + 3 I hadn't implemented event support on Matter locks yet because Claude told me that it wasn't support. Quick Google says Claude was wrong so linked PR will address it

[raman325]

for 1, when you disable the slot, what happens? the name and PIN fields you see there won't change, but the active sensor at the bottom should go to off

[jprasm]

for 1, when I disable the slot, the active sensor goes off.

I've installed the latest update. Events still greyed out (as you can see). Went to the lock and all codes still work, even the ones I've disabled.

I'm also listening to lock_code_manager_lock_state_changed events, and I haven't seen any events at all.

Let me know what I can provide you for help!

A couple of other screenshots (I don't know what the amber color icon i lock status means)

[raman325]

Thanks for the details! Let's work through each:

For the disabled codes still working: When you disable a slot, the sync manager should clear the PIN on the lock. Can you enable debug logging for Lock Code Manager and share the logs? Add this to your configuration.yaml:

logger:
  logs:
    custom_components.lock_code_manager: debug

Then restart HA, disable a slot, wait ~10 seconds, and share the relevant logs. I'm looking for:

• Clearing usercode on lock.xxx slot N — confirms the clear was attempted
• Any Matter service matter.clear_lock_credential failed errors
• Any credential_exists check results

For the event entity being unavailable: That's expected on 2.0.1 — the event support shipped in 2.0.1 but the push subscription (which sets up the event listener) requires the Matter client and node ID to be available. Can you check:

1. Does the lock show a device in the Matter integration? (Settings → Devices → filter by Matter)
2. What version of Home Assistant are you running?

The event entity becomes available when at least one lock supports code slot events. If the subscription fails (client not found, node ID not resolvable), it stays unavailable.

For no lock_code_manager_lock_state_changed events: This is likely related to the event subscription not being established. The debug logs above should show whether subscription succeeded (subscribed to Matter events (node X)) or failed.

The debug logs will tell us whether the issue is at the HA service layer, the Matter integration layer, or the lock firmware layer.

[raman325]

lets also add homeassistant.components.matter to debug:

logger:
  logs:
    custom_components.lock_code_manager: debug
    homeassistant.components.matter: debug

[jprasm]

I really apprecaite you helping me here!

1. Matter integration shows both U200 locks:

2. I'm using HA version 2026.4.1

Here is a sample of the logs (let me know if you need more)....there are indeed some errors here.

I'm seeing a lot of this:

2026-04-04 10:29:05.722 DEBUG (MainThread) [custom_components.lock_code_manager.providers] Lock lock.door_to_garage: push subscription deferred: Matter client or node ID unavailable for lock.door_to_garage
2026-04-04 10:29:05.722 DEBUG (MainThread) [custom_components.lock_code_manager.util] Scheduling retry for push subscription for lock.door_to_garage in 10.0s

and also a lot of this:

2026-04-04 10:29:00.519 INFO (MainThread) [custom_components.lock_code_manager.sync] 01KNA4DQRP3HBR8BAK4A5V9YDY (Door to Garage Lock Codes): lock.door_to_garage slot 1: Lock disconnected during set usercode: Matter service matter.set_lock_credential failed for lock.door_to_garage: Failed to set credential: lock returned status duplicate. Will retry on next tick.

logs.rtf

[raman325]

Thanks for the logs! Two issues visible:

1. Push subscription failing ("Matter client or node ID unavailable")

This is why the event entity is greyed out. The lock provider can't find the Matter client or resolve the node ID from the device registry. Can you check:

1. In Developer Tools → States, search for lock.door_to_garage — does it show a device_id in the attributes?
2. In Developer Tools → Template, paste this and share the result:

{% set lock = states.lock.door_to_garage %}
device_id: {{ lock.attributes.get('device_id', 'NOT SET') }}
entity_id: {{ lock.entity_id }}

3. Also check: Settings → Devices → find the Door to Garage lock → what identifiers does it show? The Matter integration should show something like matter: <node_id>.
4. On the Door to Garage lock device page, download the device diagnostics and upload them here.

2. "duplicate" status on set_lock_credential

The Aqara U200 is rejecting the set_lock_credential call with status "duplicate." This means the credential index already has a PIN stored and the Matter service is refusing to overwrite it. This is a Matter spec behavior — some locks require you to clear the credential first before setting a new one at the same index.

This is a bug in our Matter provider — we should clear-then-set instead of just set. I'll open a fix for this.

3. Codes not clearing when slot disabled

The logs show set usercode operations failing, but I don't see Clearing usercode messages. When you disable a slot:

• Do you see Clearing usercode on lock.door_to_garage slot N in the logs?
• Or does it just show the set failures?

If no clear messages appear, the sync manager might not be detecting the state change correctly. The debug logs from disabling a specific slot would help narrow this down.

[jprasm]

Good morning! Here are some answers for you:

1. Push subscription failing ("Matter client or node ID unavailable")

1. There is no device_id in the attributes for lock.door_to_garage or lock.cold_storage_room (both aqara U200 locks, the only locks I have by the way).

2. Template result is: device_id: NOT SET ; entity_id: lock.door_to_garage

3. Settings → Devices → find the Door to Garage lock → identifiers (another screenshot). Node ID is 13 (the network name looks strange, I wonder if that's normal. I haven't really been concerned because the locks work perfectly):

4. I've attached the diagnostics file (forgive me, there is a bunch of stuff that chatGPT suggested I redact, let me know if I've redacted something you absolutely need to see)

Diagnostics (redacted).rtf

2. "duplicate" status on set_lock_credential

Clearing codes does not appear anywhere in the logs. Here is another log file - where I'm toggling the 'enabled' button on the dashboard several times:

home-assistant_2026-04-05T11-04-30.403Z.log

[raman325]

Thanks for the detailed diagnostics!

Root cause found: lock entity has no device_id

The lock entity (lock.door_to_garage) is not linked to its device in the entity registry. This is why:

• Push subscription fails (can't resolve Matter node ID from device identifiers)
• Event entity stays unavailable
• The lock provider can't find the device to subscribe to events

The device itself exists (node 13, visible in Settings → Devices), but the entity registry entry doesn't have the device_id field set. This is unusual — the Matter integration should link the lock entity to its device when creating it.

Possible fixes:

1. Try removing and re-adding the Matter integration — this would re-create the entities with proper device links
2. If that doesn't work, this may be a bug in the Matter integration's entity registration for lock entities on the Aqara U200

For the "duplicate" error:
We just shipped a fix in the latest release that detects the "duplicate" status from the lock and properly surfaces it as a repair issue instead of retrying forever. The duplicate means the same PIN value already exists on another slot on the lock. You'll need to clear those conflicting codes — once the lock reset step (PR #983) ships, it will offer to do this during setup.

For the missing clear operations:
The logs showing only set operations (not clear) when you disable a slot is concerning. Can you check: when you toggle the enabled switch off, does the active binary sensor go to OFF? If so, the sync manager should attempt a clear on the next tick. The logs should show Clearing usercode on lock.door_to_garage slot N. If that message is completely absent, there may be a sync manager issue separate from the device_id problem.

Immediate workaround:
Try reloading the Matter integration (Settings → Integrations → Matter → 3 dots → Reload). After reload, check if device_id appears on the lock entity in Developer Tools → States.