I have a Secuyou Patio Door Lock.
It is integrated via Thread on a Google Nest Hub v2, and that hub is connected to a Matter network where the Home Assistant is also attached, the lock is exposed to both systems.
When I lock the lock through Google Home it works without a hitch. After the later updates to the Matter Addon I start to see that it stays in 'locking' mode if I lock it from Home Assistant.
If I then unlock and lock it again through Home Assistant it works. It goes through the 'locking' shortly (as it should), and then 'locked'.
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
Matter Server
What is the version of the add-on?
6.2.1
Steps to reproduce the issue
Lock from Home Assistant
It goes to locking
it stays in locking
System Health information
System Information
version
core-2024.7.1
installation_type
Home Assistant OS
dev
false
hassio
true
docker
true
user
root
virtualenv
false
python_version
3.12.4
os_name
Linux
os_version
6.6.33-haos
arch
x86_64
timezone
Europe/Copenhagen
config_dir
/config
Home Assistant Community Store
GitHub API | ok
-- | --
GitHub Content | ok
GitHub Web | ok
GitHub API Calls Remaining | 4995
Installed Version | 1.34.0
Stage | running
Available Repositories | 1458
Downloaded Repositories | 60
Home Assistant Cloud
logged_in | true
-- | --
subscription_expiration | 31. oktober 2024 kl. 01.00
relayer_connected | true
relayer_region | eu-central-1
remote_enabled | true
remote_connected | true
alexa_enabled | false
google_enabled | true
remote_server | eu-central-1-6.ui.nabu.casa
certificate_status | ready
instance_id | 5d91cdafcacf4f7e8b74f0e03396225c
can_reach_cert_server | ok
can_reach_cloud_auth | ok
can_reach_cloud | ok
Home Assistant Supervisor
host_os | Home Assistant OS 12.4
-- | --
update_channel | stable
supervisor_version | supervisor-2024.06.2
agent_version | 1.6.0
docker_version | 26.1.4
disk_total | 146.9 GB
disk_used | 66.0 GB
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 | Node-RED (18.0.3), AppDaemon (0.16.6), ESPHome (2024.6.6), Samba share (12.3.1), Grafana (10.0.0), MariaDB (2.7.1), chrony (3.0.1), InfluxDB (5.0.0), Mosquitto broker (6.4.1), Vaultwarden (Bitwarden) (0.21.2), Home Assistant Google Drive Backup (0.112.1), Zigbee2MQTT (1.39.0-1), Advanced SSH & Web Terminal (18.0.0), Let's Encrypt (5.0.22), Whisper (2.1.2), Piper (1.5.0), Govee to MQTT Bridge (2024.04.29-30cf7732), TubesZB TI CC2652 FW Flasher (0.2.2), AdGuard Home (5.1.1), File editor (5.8.0), Studio Code Server (5.15.0), Matter Server (6.2.1), go2rtc (1.9.4)
Dashboards
dashboards | 11
-- | --
resources | 38
views | 55
mode | storage
Recorder
oldest_recorder_run | 25. juni 2024 kl. 16.29
-- | --
current_recorder_run | 8. juli 2024 kl. 10.34
estimated_db_size | 2844.50 MiB
database_engine | mysql
database_version | 10.11.6
Anything in the Supervisor logs that might be useful for us?
No response
Anything in the add-on logs that might be useful for us?
Not sure if it's relevant:
2024-07-09 09:29:24.090 (MainThread) INFO [matter_server.server.device_controller.node_4] Node could not be discovered on the network, returning cached IP's
Additional information
It's only in the later versions of the Matter Addon I've seen this problem I noticed that there was a note in the release notes about better handling of the 'locking' state, for me it has been quite opposite.
It looks like the 2024.7.2 solved it. I found out that it was happening if I locked the lock when it was already locked.
I saw the fix #121665 in the release notes, and it has solved the problem as far as I can see.
Describe the issue you are experiencing
I have a Secuyou Patio Door Lock. It is integrated via Thread on a Google Nest Hub v2, and that hub is connected to a Matter network where the Home Assistant is also attached, the lock is exposed to both systems. When I lock the lock through Google Home it works without a hitch. After the later updates to the Matter Addon I start to see that it stays in 'locking' mode if I lock it from Home Assistant. If I then unlock and lock it again through Home Assistant it works. It goes through the 'locking' shortly (as it should), and then 'locked'.
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
Matter Server
What is the version of the add-on?
6.2.1
Steps to reproduce the issue
System Health information
System Information
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 4995 Installed Version | 1.34.0 Stage | running Available Repositories | 1458 Downloaded Repositories | 60Home Assistant Cloud
logged_in | true -- | -- subscription_expiration | 31. oktober 2024 kl. 01.00 relayer_connected | true relayer_region | eu-central-1 remote_enabled | true remote_connected | true alexa_enabled | false google_enabled | true remote_server | eu-central-1-6.ui.nabu.casa certificate_status | ready instance_id | 5d91cdafcacf4f7e8b74f0e03396225c can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 12.4 -- | -- update_channel | stable supervisor_version | supervisor-2024.06.2 agent_version | 1.6.0 docker_version | 26.1.4 disk_total | 146.9 GB disk_used | 66.0 GB 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 | Node-RED (18.0.3), AppDaemon (0.16.6), ESPHome (2024.6.6), Samba share (12.3.1), Grafana (10.0.0), MariaDB (2.7.1), chrony (3.0.1), InfluxDB (5.0.0), Mosquitto broker (6.4.1), Vaultwarden (Bitwarden) (0.21.2), Home Assistant Google Drive Backup (0.112.1), Zigbee2MQTT (1.39.0-1), Advanced SSH & Web Terminal (18.0.0), Let's Encrypt (5.0.22), Whisper (2.1.2), Piper (1.5.0), Govee to MQTT Bridge (2024.04.29-30cf7732), TubesZB TI CC2652 FW Flasher (0.2.2), AdGuard Home (5.1.1), File editor (5.8.0), Studio Code Server (5.15.0), Matter Server (6.2.1), go2rtc (1.9.4)Dashboards
dashboards | 11 -- | -- resources | 38 views | 55 mode | storageRecorder
oldest_recorder_run | 25. juni 2024 kl. 16.29 -- | -- current_recorder_run | 8. juli 2024 kl. 10.34 estimated_db_size | 2844.50 MiB database_engine | mysql database_version | 10.11.6Anything in the Supervisor logs that might be useful for us?
No response
Anything in the add-on logs that might be useful for us?
Additional information
It's only in the later versions of the Matter Addon I've seen this problem I noticed that there was a note in the release notes about better handling of the 'locking' state, for me it has been quite opposite.