[Solved] Matter and Thread Issues with 2025.4.0 and 4.1

TH3xR34P3R · April 5, 2025, 12:04pm

I have started a github to track and provide details with current issues I am facing with Thread and Matter over wifi since updating to 2025.4.0 and 4.1.

Figured I would link it here as well to get more eyes on the issue to see what is happening to get this resolved:

github.com/home-assistant/addons

Border Router Missing after HA core update to 2025.4.0

opened 11:38AM - 03 Apr 25 UTC

TH3xR34P3R

[config_entry-thread-01JR0RSNXETJ100RN7KXVZSVBW.json](https://github.com/user-at…tachments/files/19607469/config_entry-thread-01JR0RSNXETJ100RN7KXVZSVBW.json) ### Describe the issue you are experiencing As of updating to core 2025.4.0 my GL-S200 is not showing up as a border router under Thread configuration and trying to re-attach it using the rest link gives me the error that the border router is already configured, nothing has changed with my configuration other than this update to the core build of HA. ![Image](https://github.com/user-attachments/assets/46401a9d-d668-4d80-b160-2e36a4140924) All the thread network information matches what is on the device itself and my aqara P2 is still connected to the S200 without issue and I am still seeing BT scan report via MQTT Explorer so there is communication working there but there is some issue preventing this Thread setup from seeing the border router. Clicking on reset in the screenshot above does nothing even though it does push the configuration for a new network to the GL-S200, but it still does not re-appear as a border router as it was previous to this update. I have also done a test restore of the last backup and the same issue persists, something def went belly up with this and I will have to wait for a fix since I forgot to rotate in a new snapshot before doing the update.. least it gives me the chance to test. I have attached the current diagnostic file generated by the thread intergration to help see what may be the issue here. ### 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? OpenThread Border Router ### What is the version of the add-on? 2.13.0 ### Steps to reproduce the issue Other than updating to the build I am unsure of how to reproduce it as its just an issue with HA rediscovering the border router that has been already set previous. ### System Health information ## System Information version | core-2025.4.0 -- | -- installation_type | Home Assistant OS dev | false hassio | true docker | true user | root virtualenv | false python_version | 3.13.2 os_name | Linux os_version | 6.12.20-haos arch | x86_64 timezone | Australia/Sydney config_dir | /config <details><summary>Home Assistant Community Store</summary> GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok HACS Data | ok GitHub API Calls Remaining | 4998 Installed Version | 2.0.5 Stage | running Available Repositories | 1626 Downloaded Repositories | 25 </details> <details><summary>Home Assistant Cloud</summary> logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok </details> <details><summary>Home Assistant Supervisor</summary> host_os | Home Assistant OS 15.1 -- | -- update_channel | stable supervisor_version | supervisor-2025.03.4 agent_version | 1.7.2 docker_version | 28.0.4 disk_total | 30.8 GB disk_used | 19.9 GB healthy | true supported | true host_connectivity | true supervisor_connectivity | true ntp_synchronized | true virtualization | oracle board | ova supervisor_api | ok version_api | ok installed_addons | Terminal & SSH (9.16.0), Mosquitto broker (6.5.0), VLC (0.3.0), Matter Server (7.0.0), Studio Code Server (5.18.4), File editor (5.8.0), Silicon Labs Flasher (0.3.2), OpenThread Border Router (2.13.0), MQTT Explorer (browser-1.0.3), Music Assistant Server (2.4.4) </details> <details><summary>Dashboards</summary> dashboards | 2 -- | -- resources | 13 views | 4 mode | storage </details> <details><summary>Network Configuration</summary> adapters | lo (disabled), enp0s3 (enabled, default, auto), hassio (disabled), docker0 (disabled), vethf0b3e01 (disabled), veth8197fcb (disabled), vethf989ee8 (disabled), veth60e2f90 (disabled), veth6deb64a (disabled), vethbf16a56 (disabled), veth31f0e21 (disabled), vethd12acde (disabled), veth52ac30f (disabled), veth8380df8 (disabled) -- | -- ipv4_addresses | lo (127.0.0.1/8), enp0s3 (192.168.1.250/24), hassio (172.30.32.1/23), docker0 (172.30.232.1/23), vethf0b3e01 (), veth8197fcb (), vethf989ee8 (), veth60e2f90 (), veth6deb64a (), vethbf16a56 (), veth31f0e21 (), vethd12acde (), veth52ac30f (), veth8380df8 () ipv6_addresses | lo (::1/128), enp0s3 (dd5f:3fe8:ca12::aef/128, dd5f:3fe8:ca12:0:ad23:56be:38f8:9c60/64, fe80::583:cb0a:2a85:404d/64), hassio (fe80::38d1:34ff:feec:dd5d/64), docker0 (fe80::82f:3cff:fe24:ffbd/64), vethf0b3e01 (fe80::c:4aff:fee3:b063/64), veth8197fcb (fe80::a828:23ff:fedf:24b8/64), vethf989ee8 (fe80::3452:b3ff:fe0c:ee19/64), veth60e2f90 (fe80::38ef:a7ff:fea9:6270/64), veth6deb64a (fe80::301d:73ff:fe91:3ee0/64), vethbf16a56 (fe80::44d5:a0ff:fe4f:df4c/64), veth31f0e21 (fe80::a4f9:adff:fe3c:c507/64), vethd12acde (fe80::4b5:e8ff:fea3:2b41/64), veth52ac30f (fe80::3c78:4bff:fe75:bf69/64), veth8380df8 (fe80::186b:9bff:feb8:9ae8/64) announce_addresses | 192.168.1.250, dd5f:3fe8:ca12::aef, dd5f:3fe8:ca12:0:ad23:56be:38f8:9c60, fe80::583:cb0a:2a85:404d </details> <details><summary>Recorder</summary> oldest_recorder_run | March 22, 2025 at 8:52 AM -- | -- current_recorder_run | April 3, 2025 at 10:12 PM estimated_db_size | 623.65 MiB database_engine | sqlite database_version | 3.48.0 </details> ### Anything in the Supervisor logs that might be useful for us? ```txt ``` ### Anything in the add-on logs that might be useful for us? ```txt ``` ### Additional information I have also just noticed that all of my matter over wifi devices are not showing as online so it may be an issue with the matter addon not just thread. Removing the matter over wifi devices and commissioning them again puts them as online again, only solution at this time in relation to that version of matter. There is something seriously wrong with matter and this 2025.4.0 and 4.1 build of Core as updating to 4.1 my matter over wifi devices are offline again as it can't seem to find or is forgetting the IP address of the devices even though they are connected to the network without issue. Also now getting this message: ![Image](https://github.com/user-attachments/assets/6d93d84c-9b3b-424b-9e55-c34ec8bf564f)

The short of it is that my border router is not showing up whilst configuration changes are able to be pushed to it via HA and the matter integration is forgetting the IP’s of the commissioned devices until removed and re-commissioned.

Not to mention that the open thread border router addon crashes at startup.

edit: turns out root issue was security settings in network switch, specific setting will be listed in thread linked once I go through the list to validate which one caused it.