Set code from Locky Card tome out but stil set the new code

[eirikman]

System Health details

System Information

version	core-2026.3.4
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
container_arch	amd64
user	root
virtualenv	false
python_version	3.14.2
os_name	Linux
os_version	6.12.67-haos
arch	x86_64
timezone	Europe/Oslo
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
HACS Data	ok
GitHub API Calls Remaining	5000
Installed Version	2.0.5
Stage	running
Available Repositories	2981
Downloaded Repositories	34

Home Assistant Cloud

logged_in	true
subscription_expiration	24. september 2026 kl. 02:00
relayer_connected	true
relayer_region	eu-central-1
remote_enabled	true
remote_connected	true
alexa_enabled	false
google_enabled	false
cloud_ice_servers_enabled	true
remote_server	eu-central-1-10.ui.nabu.casa
certificate_status	ready
instance_id	5dabc3e53d374085a1163d04fb8f2a06
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Easee elbillader

component_version	0.9.73
reach_easee_cloud	ok
connected2stream	true

Home Assistant Supervisor

host_os	Home Assistant OS 17.1
update_channel	stable
supervisor_version	supervisor-2026.03.2
agent_version	1.8.1
docker_version	29.1.3
disk_total	30.8 GB
disk_used	26.7 GB
nameservers	192.168.10.1, 192.168.1.1, 2a04:981:50c:8a00::1
healthy	true
supported	true
host_connectivity	true
supervisor_connectivity	true
ntp_synchronized	true
virtualization	kvm
board	ova
supervisor_api	ok
version_api	ok
installed_addons	Terminal & SSH (10.0.2), File editor (5.8.0), Node-RED (21.0.4), MariaDB (2.7.2), Zigbee2MQTT (2.9.2-1), Mosquitto broker (6.5.2), Z-Wave JS UI (7.1.0), Studio Code Server (6.0.1), Glances (0.21.1), Duck DNS (1.26.0), Let's Encrypt (6.2.0), Advanced SSH & Web Terminal (23.0.4), Matterbridge (2026.4.1)

Dashboards

dashboards	7
resources	21
views	27
mode	storage

Network Configuration

adapters	lo (disabled), enp0s18 (enabled, default, auto), hassio (disabled), docker0 (disabled), veth1a57548 (disabled), veth2677ab1 (disabled), veth69f3994 (disabled), vethaf440c1 (disabled), veth5fe805d (disabled), veth774f23f (disabled), veth1c5538f (disabled), veth70e260e (disabled), veth5b82c89 (disabled), veth35ce2f3 (disabled)
ipv4_addresses	lo (127.0.0.1/8), enp0s18 (192.168.10.3/24), hassio (172.30.32.1/23), docker0 (172.30.232.1/23), veth1a57548 (), veth2677ab1 (), veth69f3994 (), vethaf440c1 (), veth5fe805d (), veth774f23f (), veth1c5538f (), veth70e260e (), veth5b82c89 (), veth35ce2f3 ()
ipv6_addresses	lo (::1/128), enp0s18 (2a04:981:50c:8a00:1bcd:99a9:6aaf:d9c7/64, fe80::1e87:1d32:62f2:7ba2/64), hassio (fe80::3c06:a9ff:fe0f:8ca9/64), docker0 (fe80::a43e:67ff:fea4:56fb/64), veth1a57548 (fe80::cc45:4bff:fef7:20/64), veth2677ab1 (fe80::c92:40ff:feeb:63e4/64), veth69f3994 (fe80::5ce2:c1ff:fee4:6de8/64), vethaf440c1 (fe80::605c:39ff:fe46:7f20/64), veth5fe805d (fe80::a042:5aff:fedd:c065/64), veth774f23f (fe80::cc69:1eff:fe00:6792/64), veth1c5538f (fe80::585b:fcff:fe44:f5a3/64), veth70e260e (fe80::c0a6:35ff:fe04:ce92/64), veth5b82c89 (fe80::6474:aff:fe3e:a2f4/64), veth35ce2f3 (fe80::44a6:a2ff:fef2:b319/64)
announce_addresses	192.168.10.3, 2a04:981:50c:8a00:1bcd:99a9:6aaf:d9c7, fe80::1e87:1d32:62f2:7ba2

Recorder

oldest_recorder_run	22. mars 2026 kl. 18:36
current_recorder_run	6. april 2026 kl. 19:16
estimated_db_size	10209.38 MiB
database_engine	mysql
database_version	10.11.6

Checklist

• I have enabled debug logging for my installation.
• I have filled out the issue template to the best of my ability.
• This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
• This issue is not a duplicate issue of any previous issues..

Describe the issue

When applying a code change from Locky Card, the code is actually changed but the card says timeout. Looking at the mqtt traffic, the correct message is sent to the lock, and the lock reply. However it seems like Locky do not recognise the reply as a confirmation, and the whole sequence is repeated three more times.

The lock is a Nimly Code Pro

Meldingen 198 ble mottatt på zigbee2mqtt/laas_entredoer klokken 19:26:
{
    "action_source_name": null,
    "action_user": null,
    "auto_relock_time": null,
    "battery": 92,
    "last_lock_source": "zigbee",
    "last_lock_user": "0",
    "last_seen": "2026-04-06T19:26:21+02:00",
    "last_unlock_source": "zigbee",
    "last_unlock_user": "0",
    "last_used_pin_code": "123456",
    "linkquality": 111,
    "lock_state": "unlocked",
    "pin_code": null,
    "sound_volume": null,
    "state": "UNLOCK"
}
QoS: 0 - Retain: false
Meldingen 197 ble mottatt på zigbee2mqtt/laas_entredoer/set klokken 19:26:
{
    "pin_code": {
        "user": 3,
        "user_type": "unrestricted",
        "user_enabled": true,
        "pin_code": "123456"
    }
}
QoS: 0 - Retain: false

Reproduction steps

1. Apply code in Locky Card
2. Wait for some seconds. Timeout will appear in the card.

...

Debug logs

NA

Diagnostics dump

No response

[bharat]

Hi — thanks a lot for opening this, and for the clear MQTT snippets. We’d love to get Lockly behaving properly for your Nimly setup.

What’s going on is that the card only clears the “working…” state when it sees a very specific kind of reply from Zigbee2MQTT (basically either a pin_code_added / pin_code_deleted style action, or a users map with slot status). Your lock may be doing the right thing on the device while only publishing other fields, so Lockly never gets the handshake it expects — hence timeout and retries even though the code stuck.

To move forward we need a quick peek at what your bridge actually sends. Here’s the smallest useful bundle:

1. One timed capture
Pick a moment, change a code from the card once, and grab every MQTT message for ~20 seconds on your device state topic (zigbee2mqtt/<friendly_name>). If you also have .../<friendly_name>/action, include anything that appears there. Replace real PINs with *** before pasting.

2. Short debug log
In configuration.yaml add:

logger:
  logs:
    custom_components.lockly: debug

Restart Home Assistant, reproduce once, then copy log lines from shortly before the click through shortly after the timeout (searching for lockly or MQTT response timeout is enough).

3. Context line
Zigbee2MQTT version + the exact device model name as shown in Z2M (firmware too if it’s there).

That’s enough for us to see whether we can match an existing path or need to teach Lockly your lock’s reply shape. Thanks again for sticking with it — we’ll dig in as soon as you can drop that in.

[eirikman]

Hi,
Thank you for the quick responce. I think your addon looks realy nice, so it would be great to have it propperly functioning:-)

1. One timed capture

[
    8.4.2026,
    18: 41: 25
] z2m:mqtt: Received MQTT message on 'zigbee2mqtt/laas_entredoer/set' with data '{
    "pin_code": {
        "user": 3,
        "user_type": "unrestricted",
        "user_enabled": true,
        "pin_code": "xxxxxx"
    }
}'
[
    8.4.2026,
    18: 41: 25
] z2m: Publishing 'set' 'pin_code' to 'laas_entredoer'
[
    8.4.2026,
    18: 41: 29
] z2m: Received Zigbee message from 'laas_entredoer', type 'commandSetPinCodeRsp', cluster 'closuresDoorLock', data '{
    "status": 0
}' from endpoint 11 with groupID 0
[
    8.4.2026,
    18: 41: 29
] z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/laas_entredoer', payload '{
    "action_source_name": null,
    "action_user": null,
    "auto_relock_time": null,
    "battery": 92,
    "last_lock_source": "zigbee",
    "last_lock_user": "0",
    "last_seen": "2026-04-08T18:41:31+02:00",
    "last_unlock_source": "zigbee",
    "last_unlock_user": "0",
    "last_used_pin_code": "xxxxxx",
    "linkquality": 72,
    "lock_state": "unlocked",
    "pin_code": null,
    "sound_volume": null,
    "state": "UNLOCK"
}'
[
    8.4.2026,
    18: 41: 29
] z2m: Received Zigbee message from 'laas_entredoer', type 'attributeReport', cluster 'closuresDoorLock', data '{
    "257": {
        "data": [
            18,
            52,
            86
        ],
        "type": "Buffer"
    }
}' from endpoint 11 with groupID 0
[
    8.4.2026,
    18: 41: 29
] z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/laas_entredoer', payload '{
    "action_source_name": null,
    "action_user": null,
    "auto_relock_time": null,
    "battery": 92,
    "last_lock_source": "zigbee",
    "last_lock_user": "0",
    "last_seen": "2026-04-08T18:41:31+02:00",
    "last_unlock_source": "zigbee",
    "last_unlock_user": "0",
    "last_used_pin_code": "xxxxxx",
    "linkquality": 72,
    "lock_state": "unlocked",
    "pin_code": null,
    "sound_volume": null,
    "state": "UNLOCK"
}'
[
    8.4.2026,
    18: 41: 35
] z2m:mqtt: Received MQTT message on 'zigbee2mqtt/laas_entredoer/set' with data '{
    "pin_code": {
        "user": 3,
        "user_type": "unrestricted",
        "user_enabled": true,
        "pin_code": "xxxxxx"
    }
}'
[
    8.4.2026,
    18: 41: 35
] z2m: Publishing 'set' 'pin_code' to 'laas_entredoer'
[
    8.4.2026,
    18: 41: 36
] z2m: Received Zigbee message from 'laas_entredoer', type 'commandSetPinCodeRsp', cluster 'closuresDoorLock', data '{
    "status": 0
}' from endpoint 11 with groupID 0
[
    8.4.2026,
    18: 41: 36
] z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/laas_entredoer', payload '{
    "action_source_name": null,
    "action_user": null,
    "auto_relock_time": null,
    "battery": 92,
    "last_lock_source": "zigbee",
    "last_lock_user": "0",
    "last_seen": "2026-04-08T18:41:38+02:00",
    "last_unlock_source": "zigbee",
    "last_unlock_user": "0",
    "last_used_pin_code": "xxxxxx",
    "linkquality": 72,
    "lock_state": "unlocked",
    "pin_code": null,
    "sound_volume": null,
    "state": "UNLOCK"
}'
[
    8.4.2026,
    18: 41: 45
] z2m:mqtt: Received MQTT message on 'zigbee2mqtt/laas_entredoer/set' with data '{
    "pin_code": {
        "user": 3,
        "user_type": "unrestricted",
        "user_enabled": true,
        "pin_code": "xxxxxx"
    }
}'
[
    8.4.2026,
    18: 41: 45
] z2m: Publishing 'set' 'pin_code' to 'laas_entredoer'
[
    8.4.2026,
    18: 41: 46
] z2m: Received Zigbee message from 'laas_entredoer', type 'commandSetPinCodeRsp', cluster 'closuresDoorLock', data '{
    "status": 0
}' from endpoint 11 with groupID 0
[
    8.4.2026,
    18: 41: 46
] z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/laas_entredoer', payload '{
    "action_source_name": null,
    "action_user": null,
    "auto_relock_time": null,
    "battery": 92,
    "last_lock_source": "zigbee",
    "last_lock_user": "0",
    "last_seen": "2026-04-08T18:41:48+02:00",
    "last_unlock_source": "zigbee",
    "last_unlock_user": "0",
    "last_used_pin_code": "xxxxxx",
    "linkquality": 72,
    "lock_state": "unlocked",
    "pin_code": null,
    "sound_volume": null,
    "state": "UNLOCK"
}'
[
    8.4.2026,
    18: 41: 55
] z2m:mqtt: Received MQTT message on 'zigbee2mqtt/laas_entredoer/set' with data '{
    "pin_code": {
        "user": 3,
        "user_type": "unrestricted",
        "user_enabled": true,
        "pin_code": "xxxxxx"
    }
}'
[
    8.4.2026,
    18: 41: 55
] z2m: Publishing 'set' 'pin_code' to 'laas_entredoer'
[
    8.4.2026,
    18: 41: 56
] z2m: Received Zigbee message from 'laas_entredoer', type 'commandSetPinCodeRsp', cluster 'closuresDoorLock', data '{
    "status": 0
}' from endpoint 11 with groupID 0
[
    8.4.2026,
    18: 41: 56
] z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/laas_entredoer', payload '{
    "action_source_name": null,
    "action_user": null,
    "auto_relock_time": null,
    "battery": 92,
    "last_lock_source": "zigbee",
    "last_lock_user": "0",
    "last_seen": "2026-04-08T18:41:58+02:00",
    "last_unlock_source": "zigbee",
    "last_unlock_user": "0",
    "last_used_pin_code": "xxxxxx",
    "linkquality": 72,
    "lock_state": "unlocked",
    "pin_code": null,
    "sound_volume": null,
    "state": "UNLOCK"
}'

2. Short debug log

2026-04-08 18:57:44.348 DEBUG (MainThread) [custom_components.lockly] Manually updated Lockly Configuration data
2026-04-08 18:59:02.142 DEBUG (MainThread) [custom_components.lockly] Updated slot 3 (name=Far, pin=***, enabled=False, busy=False, status=timeout)
2026-04-08 18:59:02.145 DEBUG (MainThread) [custom_components.lockly] Manually updated Lockly Configuration data
2026-04-08 18:59:02.146 DEBUG (MainThread) [custom_components.lockly] Persisted slots: [{'slot': 1, 'name': 'Familiemedlem', 'pin': '***', 'enabled': True, 'busy': False, 'status': 'timeout'}, {'slot': 2, 'name': 'Dominica', 'pin': '***', 'enabled': True, 'busy': False, 'status': 'timeout'}, {'slot': 3, 'name': 'Far', 'pin': '***', 'enabled': False, 'busy': False, 'status': 'timeout'}]
2026-04-08 18:59:02.164 DEBUG (MainThread) [custom_components.lockly] Applying slot 3 to locks ['laas_entredoer'] (enabled=False)
2026-04-08 18:59:02.164 DEBUG (MainThread) [custom_components.lockly] Updated slot 3 (name=Far, pin=***, enabled=False, busy=True, status=queued)
2026-04-08 18:59:02.166 DEBUG (MainThread) [custom_components.lockly] Manually updated Lockly Configuration data
2026-04-08 18:59:02.167 DEBUG (MainThread) [custom_components.lockly] Persisted slots: [{'slot': 1, 'name': 'Familiemedlem', 'pin': '***', 'enabled': True, 'busy': False, 'status': 'timeout'}, {'slot': 2, 'name': 'Dominica', 'pin': '***', 'enabled': True, 'busy': False, 'status': 'timeout'}, {'slot': 3, 'name': 'Far', 'pin': '***', 'enabled': False, 'busy': True, 'status': 'queued'}]
2026-04-08 18:59:02.167 DEBUG (MainThread) [custom_components.lockly] Updated slot 3 (name=Far, pin=***, enabled=False, busy=True, status=updating)
2026-04-08 18:59:02.170 DEBUG (MainThread) [custom_components.lockly] Manually updated Lockly Configuration data
2026-04-08 18:59:02.171 DEBUG (MainThread) [custom_components.lockly] Persisted slots: [{'slot': 1, 'name': 'Familiemedlem', 'pin': '***', 'enabled': True, 'busy': False, 'status': 'timeout'}, {'slot': 2, 'name': 'Dominica', 'pin': '***', 'enabled': True, 'busy': False, 'status': 'timeout'}, {'slot': 3, 'name': 'Far', 'pin': '***', 'enabled': False, 'busy': True, 'status': 'updating'}]
2026-04-08 18:59:02.171 DEBUG (MainThread) [custom_components.lockly] MQTT publish queued for slot 3 on laas_entredoer
2026-04-08 18:59:02.171 DEBUG (MainThread) [custom_components.lockly] Action timer started for slot 3 on laas_entredoer (attempt=1, timeout=10s)
2026-04-08 18:59:02.171 DEBUG (MainThread) [custom_components.lockly] Updated slot 3 (name=Far, pin=***, enabled=False, busy=True, status=updating)
2026-04-08 18:59:02.175 DEBUG (MainThread) [custom_components.lockly] Manually updated Lockly Configuration data
2026-04-08 18:59:02.175 DEBUG (MainThread) [custom_components.lockly] Persisted slots: [{'slot': 1, 'name': 'Familiemedlem', 'pin': '***', 'enabled': True, 'busy': False, 'status': 'timeout'}, {'slot': 2, 'name': 'Dominica', 'pin': '***', 'enabled': True, 'busy': False, 'status': 'timeout'}, {'slot': 3, 'name': 'Far', 'pin': '***', 'enabled': False, 'busy': True, 'status': 'updating'}]
2026-04-08 18:59:02.175 DEBUG (MainThread) [custom_components.lockly] MQTT publish to zigbee2mqtt/laas_entredoer/set: {'pin_code': {'user': 3, 'user_type': 'unrestricted', 'user_enabled': False, 'pin_code': '***'}}
2026-04-08 18:59:02.179 DEBUG (MainThread) [custom_components.lockly] MQTT publish complete to zigbee2mqtt/laas_entredoer/set
2026-04-08 18:59:12.171 DEBUG (MainThread) [custom_components.lockly] Retrying slot 3 on laas_entredoer (attempt=2/4)
2026-04-08 18:59:12.171 DEBUG (MainThread) [custom_components.lockly] MQTT publish queued for slot 3 on laas_entredoer
2026-04-08 18:59:12.172 DEBUG (MainThread) [custom_components.lockly] Action timer started for slot 3 on laas_entredoer (attempt=2, timeout=10s)
2026-04-08 18:59:12.172 DEBUG (MainThread) [custom_components.lockly] MQTT publish to zigbee2mqtt/laas_entredoer/set: {'pin_code': {'user': 3, 'user_type': 'unrestricted', 'user_enabled': False, 'pin_code': '***'}}
2026-04-08 18:59:12.174 DEBUG (MainThread) [custom_components.lockly] MQTT publish complete to zigbee2mqtt/laas_entredoer/set
2026-04-08 18:59:22.174 DEBUG (MainThread) [custom_components.lockly] Retrying slot 3 on laas_entredoer (attempt=3/4)
2026-04-08 18:59:22.174 DEBUG (MainThread) [custom_components.lockly] MQTT publish queued for slot 3 on laas_entredoer
2026-04-08 18:59:22.174 DEBUG (MainThread) [custom_components.lockly] Action timer started for slot 3 on laas_entredoer (attempt=3, timeout=10s)
2026-04-08 18:59:22.174 DEBUG (MainThread) [custom_components.lockly] MQTT publish to zigbee2mqtt/laas_entredoer/set: {'pin_code': {'user': 3, 'user_type': 'unrestricted', 'user_enabled': False, 'pin_code': '***'}}
2026-04-08 18:59:22.176 DEBUG (MainThread) [custom_components.lockly] MQTT publish complete to zigbee2mqtt/laas_entredoer/set
2026-04-08 18:59:32.174 DEBUG (MainThread) [custom_components.lockly] Retrying slot 3 on laas_entredoer (attempt=4/4)
2026-04-08 18:59:32.175 DEBUG (MainThread) [custom_components.lockly] MQTT publish queued for slot 3 on laas_entredoer
2026-04-08 18:59:32.175 DEBUG (MainThread) [custom_components.lockly] Action timer started for slot 3 on laas_entredoer (attempt=4, timeout=10s)
2026-04-08 18:59:32.175 DEBUG (MainThread) [custom_components.lockly] MQTT publish to zigbee2mqtt/laas_entredoer/set: {'pin_code': {'user': 3, 'user_type': 'unrestricted', 'user_enabled': False, 'pin_code': '***'}}
2026-04-08 18:59:32.176 DEBUG (MainThread) [custom_components.lockly] MQTT publish complete to zigbee2mqtt/laas_entredoer/set
2026-04-08 18:59:42.176 DEBUG (MainThread) [custom_components.lockly] Updated slot 3 (name=Far, pin=***, enabled=False, busy=True, status=timeout)
2026-04-08 18:59:42.177 DEBUG (MainThread) [custom_components.lockly] Manually updated Lockly Configuration data
2026-04-08 18:59:42.178 DEBUG (MainThread) [custom_components.lockly] Persisted slots: [{'slot': 1, 'name': 'Familiemedlem', 'pin': '***', 'enabled': True, 'busy': False, 'status': 'timeout'}, {'slot': 2, 'name': 'Dominica', 'pin': '***', 'enabled': True, 'busy': False, 'status': 'timeout'}, {'slot': 3, 'name': 'Far', 'pin': '***', 'enabled': False, 'busy': True, 'status': 'timeout'}]
2026-04-08 18:59:42.178 WARNING (MainThread) [custom_components.lockly] MQTT response timeout for slot 3 on laas_entredoer (attempts=4)
2026-04-08 18:59:42.178 DEBUG (MainThread) [custom_components.lockly] Updated slot 3 (name=Far, pin=***, enabled=False, busy=False, status=timeout)
2026-04-08 18:59:42.181 DEBUG (MainThread) [custom_components.lockly] Manually updated Lockly Configuration data
2026-04-08 18:59:42.182 DEBUG (MainThread) [custom_components.lockly] Persisted slots: [{'slot': 1, 'name': 'Familiemedlem', 'pin': '***', 'enabled': True, 'busy': False, 'status': 'timeout'}, {'slot': 2, 'name': 'Dominica', 'pin': '***', 'enabled': True, 'busy': False, 'status': 'timeout'}, {'slot': 3, 'name': 'Far', 'pin': '***', 'enabled': False, 'busy': False, 'status': 'timeout'}]

3. Context line

Device information

Organizationally Unique Identifier
(IEEE Vendor Prefix)OUI: Nordic Semiconductor ASA

Zigbee Model
NimlyCodePRO

Onesti Products AS

Definition (Zigbee2MQTT)
[NimlyCodePRO](https://www.zigbee2mqtt.io/devices/NimlyCodePRO.html)

Nimly Code Pro (custom) ([Onesti Products AS](https://www.zigbee2mqtt.io/supported-devices/#v=Onesti%20Products%20AS))

Firmware ID
4.8.01
20240625

Firmware version
Unknown

Last seen
4 minutes ago

MQTT
zigbee2mqtt/laas_entredoer

Zigbee2MQTT info
Zigbee2MQTT version: [2.9.2](https://github.com/Koenkk/zigbee2mqtt/releases/tag/2.9.2):

I don't know if it is important, but this specific lock is currently not supported by Z2M. I have therefor written a external coordinator file my selves. (Or Claude AI didt it for me...)

Shout out if you need anything else from my side:-)

[bharat]

Thanks again for the detailed Z2M log and HA debug output — that made the picture much clearer. And thanks for mentioning the external converter; that's an important piece. With a custom definition, Zigbee2MQTT only publishes what that converter returns, so if the payload doesn't match what "normal" lock devices expose, integrations that expect those fields won't see them.

How we think about Lockly: we intentionally target the same MQTT/JSON shapes that Zigbee2MQTT uses for supported door locks, as implemented in zigbee-herdsman-converters — not ad-hoc per-device protocols. That keeps behavior predictable and avoids chasing every one-off converter in the wild.

The relevant patterns are in upstream fromZigbee.ts, especially:

• lock_programming_event — maps lock programming events to a top-level action (e.g. pin_code_added, pin_code_deleted, pin_code_changed) and action_user (slot id):
  https://github.com/Koenkk/zigbee-herdsman-converters/blob/4d2f6d600f25e68794f6fcc4344f93923b673a7a/src/converters/fromZigbee.ts#L298-L317

• Alternatively, state updates that include a users object with per-slot status (as produced by the get PIN / get user status response converters a bit further down in the same file) — Lockly can complete pending jobs from that as well.

What we're seeing on your bridge is commandSetPinCodeRsp with status: 0 (great), but the MQTT state you shared doesn't include action + action_user or a matching users[…].status update. Lockly never gets the "done" signal it's built for, so the card times out and retries even though the lock actually applied the PIN.

Suggestion: update your external converter so that when programming succeeds (and when a user/slot is cleared, if applicable), you publish the same fields Z2M would — minimally action: pin_code_added or pin_code_deleted and action_user set to the Zigbee user id for that slot — or merge in users with the expected status values, following the herdsman patterns above. After that, Lockly should behave the same as with a first-party Z2M lock definition.

If anything in the spec is ambiguous for Nimly (e.g. the lock never sends Programming Event Notification on the wire), say so in a follow-up and we can note it for docs or a narrow, well-defined exception — but the first stop is aligning the published MQTT JSON with those standard shapes.

[eirikman]

Thank you for your time and the reply. Your comments make sence.

Actuall I see that a updated converter is available here https://github.com/Koenkk/zigbee-herdsman-converters/blob/master/src/devices/onesti.ts I guess it will be availablke in the next release of z2m. Maybe that will help. If not I will have a closer look at your sugestions.

Thank you again for your time and guidance.

[eirikman]

Short update on this: It apears tat the lock do not report standard values, and I had to make som converter extensions to make the lock response match the responce expected from Lockly. After that the set and deactivat code from Lockly works perfect! Exactly what I need:-)

The only remaining partfor me is to make the Lock Activity card working. It reports the PIN code changes, but nothing else. What kind of feedback is it expecting?