You might wanna have a look at this. Looks like it was deprecated this week. addons/silabs-multiprotocol at master · home-assistant/addons · GitHub
If you go to → Settings - Devices and Services → Thread → Click on the gear → and go with the mouse under the Key
Appear a text: “Used for Android and IOS Credential”
Update? From where? The old SiliconLabs Multiprotocol Add-on provided by Home Assistant is not stable, you should use the SiliconLabs Multiprotocol Add-on from iHost Open Source Project. The current version is 1.0.0.
I confirm, the repository address for the SIlicon Lab Multiprotocol addon as SonOff says in the guide:
is: https://github.com/iHost-Open-Source-Project/hassio-ihost-addon
This is not the right repository to install the Silicon Lab Multiprotocol addon.
i’m a newbie… to update the Silicon Lab Multiprotocol addon have I to re-enter and reinstall the repository or does HA automatically update it? How it works?
Remove the old SiliconLabs Multiprotocol Add-on provided by Home Assistant, and install the SiliconLabs Multiprotocol Add-on provided by iHost Open Source Project.
Even these two add-ons share the same name, they are not from the same repository. So HA will not automatically update one from the other, you have to do it manually.
SonOff Reply to me:
“Based on the feedback we have received so far, the MultiPAN firmware provided in the online tool can be considered stable. If you encounter any problems, please clearly raise them.”
They planned to update the old Repository:
Next, we’ll be testing this setup in a Home Assistant environment . However, since the original SiliconLabs Multiprotocol Add-on has been deprecated and removed from the HA add-on store, we’re planning to:
- Upgrade the original SiliconLabs Multiprotocol Add-on
- Enable MultiPAN operation within Home Assistant for testing
Push on Multiprotocol solution:
We hope the Home Assistant community can re-accept it with an open attitude. Meanwhile, SONOFF will continue pushing the development of Matter, Zigbee, and Multiprotocol technologies
1 Like
I have no use for the bluetooth in my RPI other than Matter/Thread.
Do I need to remove the HA configuration of it?
Have you installed Matter server 8.1.1 from the hassio repo, or the official 8.1.2 from the HA repo?
Do you know is there is some specific sonoff code in the hassio repo?
When I install from the hassio repo, it is not visible in the “devices and integration page”
Here the one suggested is the official HA Matter Server. However i think its a mess if I add this one also, as then there will be 2 concurrent Matter Servers running.
----- UPDATE - EDIT -----
I was able to pair an IKEA Matter device in both hassio repo (8.1.1). And the official repo (8.1.2). However I believe there was some errors in log for 8.1.2 i didnt see for 8.1.1,
Also I believe the device was only visible under “devices” when added in 8.1.2.
Have you installed Matter server 8.1.1 from the hassio repo, or the official 8.1.2 from the HA repo?
I am using Matter Server 8.1.1 from iHost Open Source Project (the hassio repo). Never used the official 8.1.2 because it doesn’t support armv7 (32 bit) architecture.
Do you know is there is some specific sonoff code in the hassio repo?
There are some custom codes but they are mainly for compatibility with armv7.
When I install from the hassio repo, it is not visible in the “devices and integration page”
You mean it was not automatically discovered, right? You can always add integration manually. There is a button called Add integration at the bottom right corner of Devices & services -> Integrations page.
Yes, no other software may use it.
I am actually not aware how you were able to add the hassio repo Matter Server in the configured pages as you show yourself. Mine wouldn’t appear, only the official integration. And if wanted to add integration of the hassio one, it wanted me to point to an IP adress which I dont know anything about, and what to insert here.
If anyone else is finding this thread, I am running the HA OS on x86/x64 linux distro. I installed the “offical” HA Matter Server integration 8.1.2, and I have been able to add my first Matter Device to my HA system. The IKEA MYGGSPRAY motion sensor.
So now I have successfully added old IKEA bulbs on Zigbee, and new Matter device on single radio.
This is all on 1 single radio, the Sonoff ZBDongle-E with official 4.6.0 Multi-PAN firmware.
Really happy I didn’t need to spend another 25Euro on new radio, but could use the same for both protocols.
Even through I wasted alot of time getting this to work, this thread pointed me in right direction. The official Sonoff page from june-2025 had some missing holes in the explanations.
I only have 4 Zigbee devices (IKEA BULBS) and 1 Matter/Thread (IKEA MOTION SENSOR).
It crashes every 1-2 days. How sonoff are able to have 100zigbee devices and 50 matter devices on the same radio stable for many days is a mystery to me.
This is snippet from log of Silicon Lab Multiprotocol
Restarting
Cannot open file /usr/local/etc/zigbeed.conf
[2026-01-08T09:30:01.064012Z] Info : Endpoint socket #12: Client disconnected. 1 connections
[2026-01-08T09:30:01.064103Z] Info : Client disconnected
[2026-01-08T09:30:02.068186Z] Info : New client connection using library v4.6.1.0
[2026-01-08T09:30:02.073727Z] Info : Endpoint socket #12: Client connected. 2 connection(s)
otbr-agent[295]: 00:11:21.776 [W] Mle-----------: Failed to process Parent Request: Duplicated
otbr-agent[295]: 00:46:57.129 [W] Mle-----------: Failed to process Parent Request: Duplicated
otbr-agent[295]: 04:25:43.249 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
otbr-agent[295]: 05:46:16.982 [W] Mle-----------: Failed to process Parent Request: Duplicated
otbr-agent[295]: 05:46:28.909 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 05:46:32.709 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 05:46:44.050 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 05:46:51.361 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 05:58:40.355 [W] P-RadioSpinel-: Error processing result: InvalidState
otbr-agent[295]: 05:58:40.356 [W] P-RadioSpinel-: Error waiting response: InvalidState
otbr-agent[295]: 05:58:40.356 [W] SubMac--------: RadioReceive() failed, error: InvalidState
otbr-agent[295]: 06:02:58.400 [W] Mle-----------: Failed to process Parent Request: Duplicated
otbr-agent[295]: 06:03:03.701 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 06:04:09.865 [W] Mle-----------: Failed to process Parent Request: Duplicated
otbr-agent[295]: 06:04:12.650 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 06:28:15.066 [W] Mle-----------: Failed to process Parent Request: Duplicated
otbr-agent[295]: 06:31:05.895 [W] Mle-----------: Failed to process Parent Request: Duplicated
otbr-agent[295]: 06:37:38.764 [W] Mle-----------: Failed to process Parent Request: Duplicated
otbr-agent[295]: 06:37:46.844 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 06:43:34.304 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 06:43:40.809 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 06:54:26.544 [W] Mle-----------: Failed to process Parent Request: Duplicated
otbr-agent[295]: 06:56:05.048 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 07:09:34.868 [W] Mle-----------: Failed to process Parent Request: Duplicated
otbr-agent[295]: 07:25:25.479 [W] Mle-----------: Failed to process Parent Request: Duplicated
otbr-agent[295]: 07:25:37.541 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 07:26:44.623 [W] Mle-----------: Failed to process Parent Request: Duplicated
otbr-agent[295]: 07:26:56.711 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 07:27:14.812 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 07:35:50.011 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 07:35:50.042 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 07:35:50.042 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 07:35:50.072 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 07:35:50.073 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 08:41:48.755 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 08:41:50.511 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
otbr-agent[295]: 09:01:56.230 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 10:38:56.715 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 10:39:15.375 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 10:39:34.704 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 10:52:44.200 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 10:52:47.749 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 10:55:05.529 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 10:55:40.625 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 10:58:13.010 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 10:59:08.059 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 11:07:00.264 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
otbr-agent[295]: 11:13:03.051 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 11:14:22.738 [W] Mle-----------: Failed to process Parent Request: Duplicated
otbr-agent[295]: 11:44:49.619 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 11:44:53.156 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 12:08:45.863 [W] Mle-----------: Failed to process Parent Request: Duplicated
otbr-agent[295]: 12:09:48.903 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 13:46:46.054 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 13:46:47.479 [W] Mle-----------: Failed to process Parent Request: Duplicated
otbr-agent[295]: 13:46:51.039 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 14:07:38.438 [W] P-RadioSpinel-: Error processing result: InvalidState
otbr-agent[295]: 14:07:38.438 [W] P-RadioSpinel-: Error waiting response: InvalidState
otbr-agent[295]: 14:07:38.438 [W] SubMac--------: RadioReceive() failed, error: InvalidState
otbr-agent[295]: 21:55:18.206 [W] Mle-----------: Failed to process Parent Request: Duplicated
otbr-agent[295]: 21:55:21.046 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 21:55:26.873 [W] Mle-----------: Failed to process Parent Request: Duplicated
otbr-agent[295]: 22:10:55.425 [W] P-RadioSpinel-: radio tx timeout
otbr-agent[295]: 22:10:55.425 [W] P-RadioSpinel-: RCP failure detected
otbr-agent[295]: 22:10:55.425 [W] P-RadioSpinel-: Trying to recover (1/100)
otbr-agent[295]: 23:21:57.406 [W] P-RadioSpinel-: Error processing result: InvalidState
otbr-agent[295]: 23:21:57.407 [W] P-RadioSpinel-: Error waiting response: InvalidState
otbr-agent[295]: 23:21:57.407 [W] SubMac--------: RadioReceive() failed, error: InvalidState
otbr-agent[295]: 23:38:41.191 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
otbr-agent[295]: 23:38:53.092 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 23:39:27.588 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 23:42:39.655 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
otbr-agent[295]: 23:42:43.137 [W] Mle-----------: Failed to process Parent Request: Duplicated
otbr-agent[295]: 23:43:16.680 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 1d.00:00:41.288 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 1d.01:18:00.802 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 1d.01:18:00.819 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 1d.02:08:23.350 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 1d.02:08:28.368 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 1d.02:08:29.591 [W] Mle-----------: Failed to process Parent Request: Duplicated
otbr-agent[295]: 1d.02:08:36.192 [W] Mle-----------: Failed to process Child ID Request: Security
otbr-agent[295]: 1d.02:08:48.992 [W] Mle-----------: Failed to process Child ID Request: Security
Default: Received SIGPIPE - ignoring
Default: Received SIGPIPE - ignoring
otbr-agent[295]: 1d.02:23:22.166 [W] Mle-----------: Failed to process Child ID Request: Security
This is snippet from Matter Server Log:
2026-01-07 20:29:15.851 (MainThread) INFO [matter_server.server.vendor_info] Loading vendor info from storage.
2026-01-07 20:29:15.880 (MainThread) INFO [matter_server.server.vendor_info] Loaded 382 vendors from storage.
2026-01-07 20:29:15.881 (MainThread) INFO [matter_server.server.vendor_info] Fetching the latest vendor info from DCL.
2026-01-07 20:29:16.122 (MainThread) INFO [matter_server.server.vendor_info] Fetched 382 vendors from DCL.
2026-01-07 20:29:16.123 (MainThread) INFO [matter_server.server.vendor_info] Saving vendor info to storage.
2026-01-07 20:29:16.149 (MainThread) INFO [matter_server.server.device_controller] Loaded 1 nodes from stored configuration
2026-01-07 20:29:16.171 (MainThread) INFO [matter_server.server.server] Matter Server successfully initialized.
2026-01-07 21:01:02.985 (MainThread) INFO [matter_server.server.device_controller.mdns] <Node:4> Discovered on mDNS
2026-01-07 21:01:02.991 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Setting-up node...
2026-01-07 21:01:03.538 (MainThread) INFO [matter_server.server.device_controller.mdns] <Node:4> Discovered on mDNS
2026-01-07 21:01:19.171 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Setting up attributes and events subscription.
2026-01-07 21:01:25.743 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Subscription succeeded with report interval [0, 1800]
2026-01-07 23:25:04.649 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:43167r with Node: <0000000000000004, 1> S:12039 M:14980131] (S) Msg Retransmission to 1:0000000000000004 failure (max retries:4)
2026-01-07 23:26:41.426 (MainThread) INFO [matter_server.server.device_controller] <Node:4> The SDK is communicating with the device using fd1c:aea2:7760:1:e31f:8d3b:d5f4:ed07
2026-01-07 23:30:39.013 (Dummy-2) CHIP_ERROR [chip.native.DMG] Time out! failed to receive report data from Exchange: 10694i with Node: <0000000000000004, 1>
2026-01-07 23:30:39.022 (MainThread) ERROR [matter_server.server.client_handler] [547612227584] Error while handling: read_attribute (node 4): src/app/ReadClient.cpp:745: CHIP Error 0x00000032: Timeout
2026-01-08 00:01:33.111 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0x88989344, Peer = 01:0000000000000004
2026-01-08 00:01:33.143 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 0
2026-01-08 00:04:59.357 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:10696i with Node: <0000000000000000, 0> S:0 M:81087646] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4)
2026-01-08 00:05:39.211 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from peer <0000000000000004, 1>. Current state was 4
2026-01-08 00:05:39.213 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/protocols/secure_channel/CASESession.cpp:594: CHIP Error 0x00000032: Timeout'
2026-01-08 00:05:39.215 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 1
2026-01-08 00:07:23.663 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Re-Subscription succeeded
2026-01-08 00:38:07.941 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0x3c61bd23, Peer = 01:0000000000000004
2026-01-08 00:38:07.960 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 0
2026-01-08 00:41:34.948 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:10699i with Node: <0000000000000000, 0> S:0 M:81087649] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4)
2026-01-08 00:42:14.043 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from peer <0000000000000004, 1>. Current state was 4
2026-01-08 00:42:14.044 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/protocols/secure_channel/CASESession.cpp:594: CHIP Error 0x00000032: Timeout'
2026-01-08 00:42:14.049 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 1
2026-01-08 00:45:52.799 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:10700i with Node: <0000000000000000, 0> S:0 M:81087650] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4)
2026-01-08 00:46:27.177 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from peer <0000000000000004, 1>. Current state was 4
2026-01-08 00:46:27.179 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/protocols/secure_channel/CASESession.cpp:594: CHIP Error 0x00000032: Timeout'
2026-01-08 00:46:27.182 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 2
2026-01-08 00:46:27.183 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Marked node as unavailable
2026-01-08 00:50:21.401 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:10701i with Node: <0000000000000000, 0> S:0 M:81087651] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4)
2026-01-08 00:50:42.101 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from peer <0000000000000004, 1>. Current state was 4
2026-01-08 00:50:42.103 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/protocols/secure_channel/CASESession.cpp:594: CHIP Error 0x00000032: Timeout'
2026-01-08 00:50:42.106 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 3
2026-01-08 00:54:28.000 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:10702i with Node: <0000000000000000, 0> S:0 M:81087652] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4)
2026-01-08 00:54:57.661 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from peer <0000000000000004, 1>. Current state was 4
2026-01-08 00:54:57.662 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/protocols/secure_channel/CASESession.cpp:594: CHIP Error 0x00000032: Timeout'
2026-01-08 00:54:57.665 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 4
2026-01-08 00:58:46.453 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:10703i with Node: <0000000000000000, 0> S:0 M:81087653] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4)
2026-01-08 00:59:15.121 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from peer <0000000000000004, 1>. Current state was 4
2026-01-08 00:59:15.124 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/protocols/secure_channel/CASESession.cpp:594: CHIP Error 0x00000032: Timeout'
2026-01-08 00:59:15.127 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 5
2026-01-08 01:00:17.212 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-01-08 01:00:31.193 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000004]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-01-08 01:00:31.194 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout'
2026-01-08 01:00:31.196 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 6
2026-01-08 01:01:46.101 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-01-08 01:02:00.080 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000004]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-01-08 01:02:00.081 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout'
2026-01-08 01:02:00.084 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 7
2026-01-08 01:03:31.160 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-01-08 01:03:45.130 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000004]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-01-08 01:03:45.131 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout'
2026-01-08 01:03:45.134 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 8
2026-01-08 01:05:46.401 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-01-08 01:06:00.373 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000004]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-01-08 01:06:00.374 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout'
2026-01-08 01:06:00.377 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 9
2026-01-08 01:11:41.824 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-01-08 01:11:55.794 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000004]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-01-08 01:11:55.795 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout'
2026-01-08 01:11:55.798 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 10
2026-01-08 01:11:55.799 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Node considered offline, shutdown subscription
2026-01-08 05:27:29.636 (MainThread) INFO [matter_server.server.device_controller.mdns] <Node:4> Discovered on mDNS
2026-01-08 05:27:29.637 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Setting-up node...
2026-01-08 05:27:30.147 (MainThread) INFO [matter_server.server.device_controller.mdns] <Node:4> Discovered on mDNS
2026-01-08 05:31:00.149 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:10704i with Node: <0000000000000000, 0> S:0 M:81087654] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4)
2026-01-08 05:31:35.745 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from peer <0000000000000004, 1>. Current state was 4
2026-01-08 05:31:38.749 (MainThread) INFO [matter_server.server.sdk] <Node:4> Attempting to establish CASE session... (attempt 2 of 2)
2026-01-08 05:31:39.258 (MainThread) INFO [matter_server.server.device_controller.mdns] <Node:4> Discovered on mDNS
2026-01-08 05:34:03.172 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Setting up attributes and events subscription.
2026-01-08 05:35:40.458 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Subscription succeeded with report interval [0, 1800]
2026-01-08 07:36:29.247 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0x137b0725, Peer = 01:0000000000000004
2026-01-08 07:36:29.270 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 0
2026-01-08 07:36:36.504 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Re-Subscription succeeded
2026-01-08 08:47:41.273 (MainThread) INFO [matter_server.server.device_controller] <Node:4> No new update found.
2026-01-08 09:06:41.754 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0xc980e90c, Peer = 01:0000000000000004
2026-01-08 09:06:41.774 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 0
2026-01-08 09:10:12.052 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:10709i with Node: <0000000000000000, 0> S:0 M:81087660] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4)
2026-01-08 09:10:47.862 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from peer <0000000000000004, 1>. Current state was 4
2026-01-08 09:10:47.864 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/protocols/secure_channel/CASESession.cpp:594: CHIP Error 0x00000032: Timeout'
2026-01-08 09:10:47.866 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 1
2026-01-08 09:14:25.617 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:10710i with Node: <0000000000000000, 0> S:0 M:81087661] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4)
2026-01-08 09:14:58.581 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from peer <0000000000000004, 1>. Current state was 4
2026-01-08 09:14:58.582 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/protocols/secure_channel/CASESession.cpp:594: CHIP Error 0x00000032: Timeout'
2026-01-08 09:14:58.586 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 2
2026-01-08 09:14:58.587 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Marked node as unavailable
2026-01-08 09:15:40.838 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Re-Subscription succeeded
2026-01-08 09:18:44.449 (MainThread) INFO [matter_server.server.device_controller] Interviewing node: 4
2026-01-08 09:18:46.726 (MainThread) INFO [matter_server.server.device_controller] <Node:4> No new update found.
2026-01-08 09:19:27.341 (MainThread) INFO [matter_server.server.device_controller] <Node:4> No new update found.
2026-01-08 09:19:30.330 (MainThread) INFO [matter_server.server.device_controller] Interviewing node: 4
2026-01-08 09:19:39.425 (MainThread) INFO [matter_server.server.device_controller] Interviewing node: 4
2026-01-08 17:51:33.985 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:43355r with Node: <0000000000000004, 1> S:12058 M:119441260] (S) Msg Retransmission to 1:0000000000000004 failure (max retries:4)
2026-01-08 18:21:45.518 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0x0e6ddeb5, Peer = 01:0000000000000004
2026-01-08 18:21:45.534 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 0
2026-01-08 18:25:33.602 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:10719i with Node: <0000000000000000, 0> S:0 M:81087676] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4)
2026-01-08 18:25:51.625 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from peer <0000000000000004, 1>. Current state was 4
2026-01-08 18:25:51.626 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/protocols/secure_channel/CASESession.cpp:594: CHIP Error 0x00000032: Timeout'
2026-01-08 18:25:51.629 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 1
2026-01-08 18:26:30.917 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-01-08 18:26:44.904 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000004]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-01-08 18:26:44.905 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout'
2026-01-08 18:26:44.907 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 2
2026-01-08 18:26:44.908 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Marked node as unavailable
2026-01-08 18:27:25.299 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-01-08 18:27:39.286 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000004]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-01-08 18:27:39.287 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout'
2026-01-08 18:27:39.290 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 3
2026-01-08 18:28:18.570 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-01-08 18:28:32.554 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000004]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-01-08 18:28:32.555 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout'
2026-01-08 18:28:32.558 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 4
2026-01-08 18:29:31.450 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-01-08 18:29:45.430 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000004]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-01-08 18:29:45.431 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout'
2026-01-08 18:29:45.434 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 5
2026-01-08 18:31:00.919 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-01-08 18:31:14.901 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000004]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-01-08 18:31:14.902 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout'
2026-01-08 18:31:14.905 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 6
2026-01-08 18:32:33.019 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-01-08 18:32:47.006 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000004]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-01-08 18:32:47.007 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout'
2026-01-08 18:32:47.011 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 7
2026-01-08 18:35:17.008 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-01-08 18:35:30.996 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000004]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-01-08 18:35:30.997 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout'
2026-01-08 18:35:30.999 (MainThread) INFO [matter_server.server.device_controller] <Node:4> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 8
2026-01-08 18:38:10.701 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-01-08 18:38:24.683 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000004]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-01-08 18:38:24.684 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout'
Lastly Zigbee2MQTT does not seem to have crashed.
I think I dont want to waste more time on this, and I have to buy another adapter purely for thread/matter.