ISSUE: HA unlock lock feature use user code 2 last used feature

[xenovia]

Describe the bug

i activate the plugin added 2 slots second is disabled but when i unlock lock with HA the last used option of user 2 get updated why ?

Home Assistant version

2026.7.1

Keymaster version

0.5.2

Home Assistant installation type

Home Assistant Supervised

Lock provider

zwave_js

Lock make and model

GED18000 ZW

Steps to reproduce

Press the unlock /lock button
check the user code 2 last used section you will see it instantly get updated

Expected behavior

I would assume the unlock/lock button would be attribute to a user or get a specific last used option and not update the user 2 last use since i did not use the code on the lock directly and not even entering it via home assistant

Logs

Screenshots

No response

Additional context

No response

[tykeal]

Thanks for the report. To determine what the lock is sending and why code slot 2 is being credited, could you capture the following and paste it here.

1. Enable debug logging for keymaster. In configuration.yaml:

logger:
  default: info
  logs:
    custom_components.keymaster: debug

Restart Home Assistant (or reload the YAML/logger config).

2. Reproduce once. Unlock the lock using the Home Assistant lock button, and note the approximate timestamp. Then grab the keymaster log lines around that moment. The most important line begins with:

[lock_unlocked] ... Running. code_slot_num: ...

Please include the surrounding lines as well (they show the source of the event).

3. Capture the raw Z-Wave event. In Developer Tools → Events, subscribe to the event type zwave_js_notification, then unlock via the Home Assistant button again. Paste the event that fires for your lock. The fields I need from it are command_class, type, event, and the parameters object (which may contain userId).

4. Sensor states. Immediately after that unlock, from Developer Tools → States, paste the current state of your lock's two Z-Wave sensor entities:

• the alarm level / user code sensor, and
• the alarm type / access control sensor.

This will show exactly what value the unlock is being attributed to and which code path is assigning it. Thanks.

[xenovia]

Hi

If you need more info just tell me thanks a lot!!

#1

2026-07-07 21:03:07.971 WARNING (MainThread) [custom_components.keymaster.helpers] Action Not Found: script.keymaster_frontdoor_manual_notify
2026-07-07 21:03:15.553 WARNING (MainThread) [custom_components.keymaster.helpers] Action Not Found: script.keymaster_frontdoor_manual_notify

#2

event_type: zwave_js_notification
data:
command_class: 113
command_class_name: Notification
label: Access Control
type: 6
event: 4
event_label: RF unlock operation
parameters: {}
origin: LOCAL
time_fired: "2026-07-08T01:06:52.798269+00:00"
context:
id: 01KWZM6WQY1MJCK
parent_id: null
user_id: null

#3

binary_sensor.living_room_salon_prise_en_charge_de_la_recherche_de_telecommande
Prise en charge de la recherche de télécommande
on
Salon
Salon
friendly_name: Salon Prise en charge de la recherche de télécommande
binary_sensor.plugins_smartplug_with_energy_monitor_over_current_detected
Over-current detected
off
SmartPlug with Energy Monitor
Salle De Lavage
device_class: safety
friendly_name: SmartPlug with Energy Monitor Over-current detected
binary_sensor.plugins_smartplug_with_energy_monitor_over_load_detected
Over-load detected
off
SmartPlug with Energy Monitor
Salle De Lavage
device_class: safety
friendly_name: SmartPlug with Energy Monitor Over-load detected
binary_sensor.plugins_smartplug_with_energy_monitor_over_voltage_detected
Over-voltage detected
off
SmartPlug with Energy Monitor
Salle De Lavage
device_class: safety
friendly_name: SmartPlug with Energy Monitor Over-voltage detected
binary_sensor.plugins_zcombo_g_smoke_co_alarm_alarm_silenced
Alarm silenced
off
ZCombo-G Smoke/CO Alarm
Plugins
friendly_name: ZCombo-G Smoke/CO Alarm Alarm silenced
binary_sensor.plugins_zcombo_g_smoke_co_alarm_alarm_silenced_2
Alarm silenced
off
ZCombo-G Smoke/CO Alarm
Plugins
friendly_name: ZCombo-G Smoke/CO Alarm Alarm silenced
binary_sensor.plugins_zcombo_g_smoke_co_alarm_carbon_monoxide_detected
Carbon monoxide detected
off
ZCombo-G Smoke/CO Alarm
Plugins
device_class: carbon_monoxide
friendly_name: ZCombo-G Smoke/CO Alarm Carbon monoxide detected
binary_sensor.plugins_zcombo_g_smoke_co_alarm_replacement_required_end_of_life
Replacement required, End-of-life
off
ZCombo-G Smoke/CO Alarm
Plugins
device_class: problem
friendly_name: ZCombo-G Smoke/CO Alarm Replacement required, End-of-life
binary_sensor.plugins_zcombo_g_smoke_co_alarm_smoke_alarm_test
Smoke alarm test
off
ZCombo-G Smoke/CO Alarm
Plugins
friendly_name: ZCombo-G Smoke/CO Alarm Smoke alarm test
binary_sensor.plugins_zcombo_g_smoke_co_alarm_smoke_detected
Smoke detected
off
ZCombo-G Smoke/CO Alarm
Plugins
device_class: smoke
friendly_name: ZCombo-G Smoke/CO Alarm Smoke detected
binary_sensor.plugins_zcombo_g_smoke_co_alarm_system_hardware_failure
System hardware failure
off
ZCombo-G Smoke/CO Alarm
Plugins
device_class: problem
friendly_name: ZCombo-G Smoke/CO Alarm System hardware failure
binary_sensor.raspberry_pi_power_status
État de l'alimentation
off
Raspberry Pi
—
device_class: problem
friendly_name: Raspberry Pi État de l'alimentation
binary_sensor.serveur_connectivity
Connectivity
on
Serveur
—
cloud_api_last_received: 2026-07-08T01:14:11.925709+00:00
cloud_api_available: true
mqtt_available: true
ble_available: false
lan_last_failure_reason: no_lan_presence
lan_available: false
device_class: connectivity
icon: mdi:lan-connect
friendly_name: Serveur Connectivity
binary_sensor.smart_plug_connectivity
Connectivity
on
Smart Plug
—
cloud_api_last_received: 2026-07-08T01:14:11.946433+00:00
cloud_api_available: true
mqtt_available: true
ble_available: false
lan_last_failure_reason: no_lan_presence
lan_available: false
device_class: connectivity
icon: mdi:lan-connect
friendly_name: Smart Plug Connectivity
binary_sensor.smartcode_10_touchpad_electronic_deadbolt_current_status_of_the_door
Current status of the door
on
SmartCode 10 Touchpad Electronic Deadbolt
Vestibule
device_class: door
friendly_name: SmartCode 10 Touchpad Electronic Deadbolt Current status of the door
binary_sensor.smartcode_10_touchpad_electronic_deadbolt_replace_battery_now
Replace battery now
off
SmartCode 10 Touchpad Electronic Deadbolt
Vestibule
device_class: battery
friendly_name: SmartCode 10 Touchpad Electronic Deadbolt Replace battery now
binary_sensor.smartcode_10_touchpad_electronic_deadbolt_replace_battery_soon
Replace battery soon
off
SmartCode 10 Touchpad Electronic Deadbolt
Vestibule
device_class: battery
friendly_name: SmartCode 10 Touchpad Electronic Deadbolt Replace battery soon
binary_sensor.smartcode_10_touchpad_electronic_deadbolt_tampering_product_cover_removed
Tampering, product cover removed
off
SmartCode 10 Touchpad Electronic Deadbolt
Vestibule
device_class: tamper
friendly_name: SmartCode 10 Touchpad Electronic Deadbolt Tampering, product cover removed

[firstof9]

@xenovia if you'd like to test the proposed fix you can download zwave_js.py and place it in your custom_components/keymaster/providers directory and restart home assistant.

[xenovia]

@xenovia if you'd like to test the proposed fix you can download zwave_js.py and place it in your custom_components/keymaster/providers directory and restart home assistant.

Hello The fix seem to be working user code 2 last used does not get updated anymore when i clicked the unlock/lock button

[firstof9]

The fix will be in 0.5.4, thanks for testing!