Use lock entity IDs as event_types for code slot events

[raman325]

Breaking change

Event entity event_types attribute now contains lock entity IDs instead of the generic "pin_used" type.

When a PIN is used to lock/unlock, the event_type will now be the entity ID of the lock where the PIN was used (e.g., lock.front_door) instead of the generic pin_used string.

What changes for users:

• Automations triggering on event_type: pin_used will need to be updated to trigger on the specific lock entity ID
• The event_types attribute on the event entity now lists lock entity IDs that support code slot events
• Locks that don't support code slot events (e.g., Virtual locks) are listed in a new unsupported_locks attribute

How to update automations:

# Before
trigger:
  - platform: state
    entity_id: event.lock_code_manager_code_slot_1
    attribute: event_type
    to: pin_used

# After (to trigger on any lock)
trigger:
  - platform: state
    entity_id: event.lock_code_manager_code_slot_1

Or trigger on a specific lock:

trigger:
  - platform: state
    entity_id: event.lock_code_manager_code_slot_1
    attribute: event_type
    to: lock.front_door

Accessing the lock entity ID in automations:

Use trigger.to_state.attributes.event_type in your automation actions to get the lock entity ID:

trigger:
  - platform: state
    entity_id: event.lock_code_manager_code_slot_1
action:
  - service: notify.mobile_app
    data:
      message: "Code slot 1 was used on {{ trigger.to_state.attributes.event_type }}"

Proposed change

Updates the event entity to use lock entity IDs as event_types instead of the generic "pin_used" type. This provides more granular information about which lock triggered the event.

Key changes:

• Adds supports_code_slot_events property to lock providers to advertise capability
• Event types are now the entity IDs of locks that support code slot events
• When a PIN is used, the event type is the lock entity ID where it was used
• Locks without code slot event support are listed in unsupported_locks attribute
• Handles dynamic capability discovery (providers can change support status)
• Preserves last event type from removed locks until next valid event

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New feature (which adds functionality)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:

🤖 Generated with Claude Code

[codecov]

Codecov Report

❌ Patch coverage is 97.72727% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 95.45%. Comparing base (a55da1f) to head (f47520a).
⚠️ Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
...components/lock_code_manager/providers/zwave_js.py	66.66%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #788      +/-   ##
==========================================
+ Coverage   95.20%   95.45%   +0.24%     
==========================================
  Files          29       29              
  Lines        2359     2397      +38     
  Branches       83       83              
==========================================
+ Hits         2246     2288      +42     
+ Misses        113      109       -4     

Flag	Coverage Δ
python	95.34% <97.72%> (+0.27%)	⬆️
typescript	96.44% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
custom_components/lock_code_manager/event.py	100.00% <100.00%> (ø)
...om_components/lock_code_manager/providers/_base.py	91.23% <100.00%> (+0.10%)	⬆️
..._components/lock_code_manager/providers/virtual.py	100.00% <100.00%> (ø)
custom_components/lock_code_manager/websocket.py	95.47% <100.00%> (+1.75%)	⬆️
...components/lock_code_manager/providers/zwave_js.py	82.22% <66.66%> (-0.22%)	⬇️

... and 2 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Copilot]

Pull request overview

This PR introduces a breaking change to event entities, replacing the generic "pin_used" event type with specific lock entity IDs. This provides more granular information about which lock triggered a PIN-used event.

Changes:

• Event entity event_types now contains lock entity IDs instead of the generic "pin_used" string
• Added supports_code_slot_events property to lock providers to indicate capability
• Locks without code slot event support are listed in a new unsupported_locks attribute
• Updated websocket code to read lock entity ID from event_type attribute instead of ATTR_LOCK_ENTITY_ID

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
custom_components/lock_code_manager/event.py	Implements dynamic event_types computation based on supported locks, handles lock entity IDs as event types, adds unsupported_locks attribute, and preserves last event type on state restoration
custom_components/lock_code_manager/providers/_base.py	Adds supports_code_slot_events property with default value of True and comprehensive documentation
custom_components/lock_code_manager/providers/virtual.py	Overrides supports_code_slot_events to return False for virtual locks
custom_components/lock_code_manager/websocket.py	Updates to read lock entity ID from event_type attribute instead of removed ATTR_LOCK_ENTITY_ID
tests/test_event.py	Adds comprehensive tests for new event_types behavior, event_type attribute values, and unsupported_locks attribute
tests/common.py	Adds SLOT_1_EVENT_ENTITY constant for test consistency

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated 6 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.