Zemismart MTP1 Fails to connect to HAOS

stepper126 · November 10, 2025, 8:22pm

I’m aware that there are a few similar type topics floating around, but wanted to throw my hat into the ring for my specific permutation.
tl;dr this is my first Matter over Thread device, it can connect to either Google Home or Apple Homekit, but can’t seem to pass along/pair to Home Assistant no matter the flow.

As far as my particular topography, I have ipv6 enabled at the router level (though the ISP doesn’t seem to assign anything externally), flat lan (no separate-vlans) HomePod minis and some Nest Hubs floating around the house and Home Assistant installed via VM.

I’ve tried uninstalling and reinstalling the Matter server and Thread Add-on in HOAS, to see if there was something I had tweaked by accident, but default settings and trying to pass the device from Google Home app over to HOAS on mobile results in the following logs:

-----------------------------------------------------------
 Add-on: Matter Server
 Matter WebSocket Server for Home Assistant Matter support.
-----------------------------------------------------------
 Add-on version: 8.1.1
 You are running the latest version of this add-on.
 System: Home Assistant OS 16.3  (amd64 / qemux86-64)
 Home Assistant Core: 2025.11.1
 Home Assistant Supervisor: 2025.11.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service banner successfully started
s6-rc: info: service matter-server: starting
s6-rc: info: service matter-server successfully started
s6-rc: info: service legacy-services: starting
[09:50:52] INFO: Starting Matter Server...
s6-rc: info: service legacy-services successfully started
[09:50:53] INFO: Using 'enp0s3' as primary network interface.
[09:50:53] INFO: Successfully send discovery information to Home Assistant.
2025-11-10 09:50:54.919 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Logging...
2025-11-10 09:50:54.919 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Controller Stack...
[1762797054.967051][117:117] CHIP:CTL: Setting attestation nonce to random value
[1762797054.969473][117:117] CHIP:CTL: Setting CSR nonce to random value
[1762797054.977715][117:117] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
[1762797055.007156][117:117] CHIP:DL: Wrote settings to /tmp/chip_kvs
[1762797055.007373][117:117] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_factory.ini
[1762797055.009412][117:117] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_config.ini
[1762797055.009642][117:117] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_counters.ini
[1762797055.028804][117:117] CHIP:DL: Wrote settings to /data/chip_counters.ini
[1762797055.028823][117:117] CHIP:DL: NVS set: chip-counters/reboot-count = 2 (0x2)
[1762797055.029167][117:117] CHIP:DL: Got Ethernet interface: enp0s3
[1762797055.029337][117:117] CHIP:DL: Found the primary Ethernet interface:enp0s3
[1762797055.029691][117:117] CHIP:DL: Failed to get WiFi interface
[1762797055.029704][117:117] CHIP:DL: Failed to reset WiFi statistic counts
[1762797055.029710][117:117] CHIP:PAF: WiFiPAF: WiFiPAFLayer::Init()
2025-11-10 09:50:55.030 (MainThread) INFO [chip.storage] Initializing persistent storage from file: /data/chip.json
2025-11-10 09:50:55.030 (MainThread) INFO [chip.storage] Loading configuration from /data/chip.json...
2025-11-10 09:50:55.080 (MainThread) INFO [chip.CertificateAuthority] Loading certificate authorities from storage...
2025-11-10 09:50:55.080 (MainThread) INFO [chip.CertificateAuthority] New CertificateAuthority at index 1
2025-11-10 09:50:55.081 (MainThread) INFO [chip.CertificateAuthority] Loading fabric admins from storage...
2025-11-10 09:50:55.081 (MainThread) INFO [chip.FabricAdmin] New FabricAdmin: FabricId: 0x0000000000000002, VendorId = 0x134B
2025-11-10 09:50:55.082 (MainThread) INFO [matter_server.server.stack] CHIP Controller Stack initialized.
2025-11-10 09:50:55.082 (MainThread) INFO [matter_server.server.server] Matter Server initialized
2025-11-10 09:50:55.082 (MainThread) INFO [matter_server.server.server] Using 'enp0s3' as primary interface (for link-local addresses)
2025-11-10 09:50:55.083 (MainThread) INFO [matter_server.server.server] Starting the Matter Server...
2025-11-10 09:50:55.104 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Skip fetching certificates (already fetched within the last 24h).
2025-11-10 09:50:55.104 (MainThread) INFO [chip.FabricAdmin] Allocating new controller with CaIndex: 1, FabricId: 0x0000000000000002, NodeId: 0x000000000001B669, CatTags: []
2025-11-10 09:50:55.158 (MainThread) INFO [matter_server.server.vendor_info] Loading vendor info from storage.
2025-11-10 09:50:55.161 (MainThread) INFO [matter_server.server.vendor_info] Loaded 365 vendors from storage.
2025-11-10 09:50:55.161 (MainThread) INFO [matter_server.server.vendor_info] Fetching the latest vendor info from DCL.
2025-11-10 09:50:55.204 (MainThread) INFO [matter_server.server.vendor_info] Fetched 364 vendors from DCL.
2025-11-10 09:50:55.204 (MainThread) INFO [matter_server.server.vendor_info] Saving vendor info to storage.
2025-11-10 09:50:55.206 (MainThread) INFO [matter_server.server.device_controller] Loaded 0 nodes from stored configuration
2025-11-10 09:50:55.209 (MainThread) INFO [matter_server.server.server] Matter Server successfully initialized.
2025-11-10 09:56:34.561 (MainThread) INFO [matter_server.server.device_controller] Starting Matter commissioning with code using Node ID 2.
2025-11-10 09:57:04.573 (Dummy-2) CHIP_ERROR [chip.native.CTL] Discovery timed out
2025-11-10 09:57:12.213 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:39620i with Node: <0000000000000000, 0> S:0 M:131387973] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4)
2025-11-10 09:57:20.952 (Dummy-2) CHIP_ERROR [chip.native.SC] PASESession timed out while waiting for a response from the peer. Expected message type was 33
2025-11-10 09:57:58.251 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:39621i with Node: <0000000000000000, 0> S:0 M:131387974] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4)
2025-11-10 09:58:07.269 (Dummy-2) CHIP_ERROR [chip.native.SC] PASESession timed out while waiting for a response from the peer. Expected message type was 33
2025-11-10 09:58:45.503 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:39622i with Node: <0000000000000000, 0> S:0 M:131387975] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4)
2025-11-10 09:58:53.586 (Dummy-2) CHIP_ERROR [chip.native.SC] PASESession timed out while waiting for a response from the peer. Expected message type was 33
2025-11-10 09:59:30.520 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:39623i with Node: <0000000000000000, 0> S:0 M:131387976] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4)
2025-11-10 09:59:39.902 (Dummy-2) CHIP_ERROR [chip.native.SC] PASESession timed out while waiting for a response from the peer. Expected message type was 33
2025-11-10 09:59:39.902 (Dummy-2) CHIP_ERROR [chip.native.ZCL] Secure Pairing Failed
2025-11-10 09:59:39.902 (Dummy-2) WARNING [chip.ChipDeviceCtrl] Failed to establish secure session to device: src/controller/python/ChipDeviceController-ScriptDevicePairingDelegate.cpp:96: CHIP Error 0x00000003: Incorrect state
2025-11-10 09:59:39.903 (MainThread) ERROR [matter_server.server.client_handler] [139899780441456] Error while handling: commission_with_code: Commission with code failed for node 2.

A more detailed Homekit → HOAS add attempt seemingly has the same results:

2025-11-10 10:35:36.465 (MainThread) INFO [matter_server.server.device_controller] Starting Matter commissioning with code using Node ID 5.
2025-11-10 10:35:36.466 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Setting attestation nonce to random value
2025-11-10 10:35:36.467 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Setting CSR nonce to random value
2025-11-10 10:35:36.468 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Stopping commissionable node discovery over DNS-SD
2025-11-10 10:35:36.468 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Starting commissionable node discovery over DNS-SD
2025-11-10 10:35:36.473 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Discovered device with discriminator 63 matches one of our setup payloads
2025-11-10 10:35:36.473 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Discovered device to be commissioned over DNS-SD
2025-11-10 10:35:36.473 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Attempting PASE connection to UDP:[fd58:8a6b:718a:0:fcc2:8363:941d:7904]:5540
2025-11-10 10:35:36.474 (Dummy-2) CHIP_DETAIL [chip.native.IN] SecureSession[0x7fa6c000c8d0]: Allocated Type:1 LSID:146
2025-11-10 10:35:36.474 (Dummy-2) CHIP_DETAIL [chip.native.SC] Assigned local session key ID 146
2025-11-10 10:35:36.474 (Dummy-2) CHIP_PROGRESS [chip.native.EM] <<< [E:49642i S:0 M:146497137] (U) Msg TX from FA1CC4549B020B34 to 0:0000000000000000 [0000] [UDP:[fd58:8a6b:718a:0:fcc2:8363:941d:7904]:5540] --- Type 0000:20 (SecureChannel:PBKDFParamRequest) (B:97)
2025-11-10 10:35:36.474 (Dummy-2) CHIP_PROGRESS [chip.native.EM] ??1 [E:49642i with Node: <0000000000000000, 0> S:0 M:146497137] (U) Msg Retransmission to 0:0000000000000000 scheduled for 2475ms from now [State:Active II:3000 AI:2200 AT:4000]
2025-11-10 10:35:36.474 (Dummy-2) CHIP_PROGRESS [chip.native.SC] Sent PBKDF param request [II:500ms AI:300ms AT:4000ms)
2025-11-10 10:35:36.475 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Commission called for node ID 0x0000000000000005
2025-11-10 10:35:36.475 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Discovered device with discriminator 63 matches one of our setup payloads
2025-11-10 10:35:36.475 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Discovered device to be commissioned over DNS-SD
2025-11-10 10:35:36.576 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Discovered device with discriminator 63 matches one of our setup payloads
2025-11-10 10:35:36.576 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Discovered device to be commissioned over DNS-SD
2025-11-10 10:35:36.577 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Discovered device with discriminator 63 matches one of our setup payloads
2025-11-10 10:35:36.577 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Discovered device to be commissioned over DNS-SD
2025-11-10 10:35:38.952 (Dummy-2) CHIP_PROGRESS [chip.native.EM] <<1 [E:49642i with Node: <0000000000000000, 0> S:0 M:146497137] (U) Msg Retransmission to 0:0000000000000000
2025-11-10 10:35:38.952 (Dummy-2) CHIP_PROGRESS [chip.native.EM] ??2 [E:49642i with Node: <0000000000000000, 0> S:0 M:146497137] (U) Msg Retransmission to 0:0000000000000000 scheduled for 2565ms from now [State:Active II:3000 AI:2200 AT:4000]
2025-11-10 10:35:41.520 (Dummy-2) CHIP_PROGRESS [chip.native.EM] <<2 [E:49642i with Node: <0000000000000000, 0> S:0 M:146497137] (U) Msg Retransmission to 0:0000000000000000
2025-11-10 10:35:41.521 (Dummy-2) CHIP_PROGRESS [chip.native.EM] ??3 [E:49642i with Node: <0000000000000000, 0> S:0 M:146497137] (U) Msg Retransmission to 0:0000000000000000 scheduled for 5549ms from now [State:Idle II:3000 AI:2200 AT:4000]
2025-11-10 10:35:47.073 (Dummy-2) CHIP_PROGRESS [chip.native.EM] <<3 [E:49642i with Node: <0000000000000000, 0> S:0 M:146497137] (U) Msg Retransmission to 0:0000000000000000
2025-11-10 10:35:47.074 (Dummy-2) CHIP_PROGRESS [chip.native.EM] ??4 [E:49642i with Node: <0000000000000000, 0> S:0 M:146497137] (U) Msg Retransmission to 0:0000000000000000 scheduled for 10521ms from now [State:Idle II:3000 AI:2200 AT:4000]
2025-11-10 10:35:57.602 (Dummy-2) CHIP_PROGRESS [chip.native.EM] <<4 [E:49642i with Node: <0000000000000000, 0> S:0 M:146497137] (U) Msg Retransmission to 0:0000000000000000
2025-11-10 10:35:57.603 (Dummy-2) CHIP_PROGRESS [chip.native.EM] ??5 [E:49642i with Node: <0000000000000000, 0> S:0 M:146497137] (U) Msg Retransmission to 0:0000000000000000 scheduled for 14576ms from now [State:Idle II:3000 AI:2200 AT:4000]
2025-11-10 10:36:06.477 (Dummy-2) CHIP_ERROR [chip.native.CTL] Discovery timed out
2025-11-10 10:36:06.478 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Stopping commissionable node discovery over DNS-SD
2025-11-10 10:36:12.184 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:49642i with Node: <0000000000000000, 0> S:0 M:146497137] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4)
2025-11-10 10:36:22.792 (Dummy-2) CHIP_ERROR [chip.native.SC] PASESession timed out while waiting for a response from the peer. Expected message type was 33
2025-11-10 10:36:22.792 (Dummy-2) CHIP_DETAIL [chip.native.IN] SecureSession[0x7fa6c000c8d0]: Released - Type:1 LSID:146
2025-11-10 10:36:22.792 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Ignoring SecurePairingFailed status for now; we have more discovered devices to try
2025-11-10 10:36:22.793 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Attempting PASE connection to UDP:[fd58:8a6b:718a:0:fcc2:8363:941d:7904]:5540
2025-11-10 10:36:22.793 (Dummy-2) CHIP_DETAIL [chip.native.IN] SecureSession[0x7fa6c0009a60]: Allocated Type:1 LSID:147
2025-11-10 10:36:22.793 (Dummy-2) CHIP_DETAIL [chip.native.SC] Assigned local session key ID 147
2025-11-10 10:36:22.793 (Dummy-2) CHIP_PROGRESS [chip.native.EM] <<< [E:49643i S:0 M:146497138] (U) Msg TX from 3979AFDC61485E62 to 0:0000000000000000 [0000] [UDP:[fd58:8a6b:718a:0:fcc2:8363:941d:7904]:5540] --- Type 0000:20 (SecureChannel:PBKDFParamRequest) (B:97)
2025-11-10 10:36:22.794 (Dummy-2) CHIP_PROGRESS [chip.native.EM] ??1 [E:49643i with Node: <0000000000000000, 0> S:0 M:146497138] (U) Msg Retransmission to 0:0000000000000000 scheduled for 2737ms from now [State:Active II:3000 AI:2200 AT:4000]
2025-11-10 10:36:22.794 (Dummy-2) CHIP_PROGRESS [chip.native.SC] Sent PBKDF param request [II:500ms AI:300ms AT:4000ms)
2025-11-10 10:36:22.794 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Commission called for node ID 0x0000000000000005
2025-11-10 10:36:22.794 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Trying connection to commissionee over different transport
2025-11-10 10:36:25.533 (Dummy-2) CHIP_PROGRESS [chip.native.EM] <<1 [E:49643i with Node: <0000000000000000, 0> S:0 M:146497138] (U) Msg Retransmission to 0:0000000000000000
2025-11-10 10:36:25.534 (Dummy-2) CHIP_PROGRESS [chip.native.EM] ??2 [E:49643i with Node: <0000000000000000, 0> S:0 M:146497138] (U) Msg Retransmission to 0:0000000000000000 scheduled for 2761ms from now [State:Active II:3000 AI:2200 AT:4000]
2025-11-10 10:36:28.297 (Dummy-2) CHIP_PROGRESS [chip.native.EM] <<2 [E:49643i with Node: <0000000000000000, 0> S:0 M:146497138] (U) Msg Retransmission to 0:0000000000000000
2025-11-10 10:36:28.298 (Dummy-2) CHIP_PROGRESS [chip.native.EM] ??3 [E:49643i with Node: <0000000000000000, 0> S:0 M:146497138] (U) Msg Retransmission to 0:0000000000000000 scheduled for 6425ms from now [State:Idle II:3000 AI:2200 AT:4000]
2025-11-10 10:36:34.730 (Dummy-2) CHIP_PROGRESS [chip.native.EM] <<3 [E:49643i with Node: <0000000000000000, 0> S:0 M:146497138] (U) Msg Retransmission to 0:0000000000000000
2025-11-10 10:36:34.731 (Dummy-2) CHIP_PROGRESS [chip.native.EM] ??4 [E:49643i with Node: <0000000000000000, 0> S:0 M:146497138] (U) Msg Retransmission to 0:0000000000000000 scheduled for 10323ms from now [State:Idle II:3000 AI:2200 AT:4000]
2025-11-10 10:36:45.065 (Dummy-2) CHIP_PROGRESS [chip.native.EM] <<4 [E:49643i with Node: <0000000000000000, 0> S:0 M:146497138] (U) Msg Retransmission to 0:0000000000000000
2025-11-10 10:36:45.065 (Dummy-2) CHIP_PROGRESS [chip.native.EM] ??5 [E:49643i with Node: <0000000000000000, 0> S:0 M:146497138] (U) Msg Retransmission to 0:0000000000000000 scheduled for 16319ms from now [State:Idle II:3000 AI:2200 AT:4000]
2025-11-10 10:37:01.399 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:49643i with Node: <0000000000000000, 0> S:0 M:146497138] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4)
2025-11-10 10:37:09.101 (Dummy-2) CHIP_ERROR [chip.native.SC] PASESession timed out while waiting for a response from the peer. Expected message type was 33
2025-11-10 10:37:09.101 (Dummy-2) CHIP_DETAIL [chip.native.IN] SecureSession[0x7fa6c0009a60]: Released - Type:1 LSID:147
2025-11-10 10:37:09.101 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Ignoring SecurePairingFailed status for now; we have more discovered devices to try
2025-11-10 10:37:09.101 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Attempting PASE connection to UDP:[fd58:8a6b:718a:0:fcc2:8363:941d:7904]:5540
2025-11-10 10:37:09.102 (Dummy-2) CHIP_DETAIL [chip.native.IN] SecureSession[0x7fa6c000c8d0]: Allocated Type:1 LSID:148
2025-11-10 10:37:09.102 (Dummy-2) CHIP_DETAIL [chip.native.SC] Assigned local session key ID 148
2025-11-10 10:37:09.102 (Dummy-2) CHIP_PROGRESS [chip.native.EM] <<< [E:49644i S:0 M:146497139] (U) Msg TX from FCF1E259DC8C24FA to 0:0000000000000000 [0000] [UDP:[fd58:8a6b:718a:0:fcc2:8363:941d:7904]:5540] --- Type 0000:20 (SecureChannel:PBKDFParamRequest) (B:97)
2025-11-10 10:37:09.102 (Dummy-2) CHIP_PROGRESS [chip.native.EM] ??1 [E:49644i with Node: <0000000000000000, 0> S:0 M:146497139] (U) Msg Retransmission to 0:0000000000000000 scheduled for 2614ms from now [State:Active II:3000 AI:2200 AT:4000]
2025-11-10 10:37:09.102 (Dummy-2) CHIP_PROGRESS [chip.native.SC] Sent PBKDF param request [II:500ms AI:300ms AT:4000ms)
2025-11-10 10:37:09.103 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Commission called for node ID 0x0000000000000005
2025-11-10 10:37:09.103 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Trying connection to commissionee over different transport
2025-11-10 10:37:11.720 (Dummy-2) CHIP_PROGRESS [chip.native.EM] <<1 [E:49644i with Node: <0000000000000000, 0> S:0 M:146497139] (U) Msg Retransmission to 0:0000000000000000
2025-11-10 10:37:11.721 (Dummy-2) CHIP_PROGRESS [chip.native.EM] ??2 [E:49644i with Node: <0000000000000000, 0> S:0 M:146497139] (U) Msg Retransmission to 0:0000000000000000 scheduled for 2756ms from now [State:Active II:3000 AI:2200 AT:4000]
2025-11-10 10:37:14.480 (Dummy-2) CHIP_PROGRESS [chip.native.EM] <<2 [E:49644i with Node: <0000000000000000, 0> S:0 M:146497139] (U) Msg Retransmission to 0:0000000000000000
2025-11-10 10:37:14.481 (Dummy-2) CHIP_PROGRESS [chip.native.EM] ??3 [E:49644i with Node: <0000000000000000, 0> S:0 M:146497139] (U) Msg Retransmission to 0:0000000000000000 scheduled for 6008ms from now [State:Idle II:3000 AI:2200 AT:4000]
2025-11-10 10:37:20.495 (Dummy-2) CHIP_PROGRESS [chip.native.EM] <<3 [E:49644i with Node: <0000000000000000, 0> S:0 M:146497139] (U) Msg Retransmission to 0:0000000000000000
2025-11-10 10:37:20.496 (Dummy-2) CHIP_PROGRESS [chip.native.EM] ??4 [E:49644i with Node: <0000000000000000, 0> S:0 M:146497139] (U) Msg Retransmission to 0:0000000000000000 scheduled for 9555ms from now [State:Idle II:3000 AI:2200 AT:4000]
2025-11-10 10:37:30.061 (Dummy-2) CHIP_PROGRESS [chip.native.EM] <<4 [E:49644i with Node: <0000000000000000, 0> S:0 M:146497139] (U) Msg Retransmission to 0:0000000000000000
2025-11-10 10:37:30.062 (Dummy-2) CHIP_PROGRESS [chip.native.EM] ??5 [E:49644i with Node: <0000000000000000, 0> S:0 M:146497139] (U) Msg Retransmission to 0:0000000000000000 scheduled for 15315ms from now [State:Idle II:3000 AI:2200 AT:4000]
2025-11-10 10:37:45.391 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:49644i with Node: <0000000000000000, 0> S:0 M:146497139] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4)
2025-11-10 10:37:55.418 (Dummy-2) CHIP_ERROR [chip.native.SC] PASESession timed out while waiting for a response from the peer. Expected message type was 33
2025-11-10 10:37:55.419 (Dummy-2) CHIP_DETAIL [chip.native.IN] SecureSession[0x7fa6c000c8d0]: Released - Type:1 LSID:148
2025-11-10 10:37:55.419 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Ignoring SecurePairingFailed status for now; we have more discovered devices to try
2025-11-10 10:37:55.419 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Attempting PASE connection to UDP:[fd58:8a6b:718a:0:fcc2:8363:941d:7904]:5540
2025-11-10 10:37:55.419 (Dummy-2) CHIP_DETAIL [chip.native.IN] SecureSession[0x7fa6c00095c0]: Allocated Type:1 LSID:149
2025-11-10 10:37:55.419 (Dummy-2) CHIP_DETAIL [chip.native.SC] Assigned local session key ID 149
2025-11-10 10:37:55.420 (Dummy-2) CHIP_PROGRESS [chip.native.EM] <<< [E:49645i S:0 M:146497140] (U) Msg TX from 4D413A9D98BE3E50 to 0:0000000000000000 [0000] [UDP:[fd58:8a6b:718a:0:fcc2:8363:941d:7904]:5540] --- Type 0000:20 (SecureChannel:PBKDFParamRequest) (B:97)
2025-11-10 10:37:55.420 (Dummy-2) CHIP_PROGRESS [chip.native.EM] ??1 [E:49645i with Node: <0000000000000000, 0> S:0 M:146497140] (U) Msg Retransmission to 0:0000000000000000 scheduled for 2525ms from now [State:Active II:3000 AI:2200 AT:4000]
2025-11-10 10:37:55.420 (Dummy-2) CHIP_PROGRESS [chip.native.SC] Sent PBKDF param request [II:500ms AI:300ms AT:4000ms)
2025-11-10 10:37:55.420 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Commission called for node ID 0x0000000000000005
2025-11-10 10:37:55.420 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Trying connection to commissionee over different transport
2025-11-10 10:37:57.946 (Dummy-2) CHIP_PROGRESS [chip.native.EM] <<1 [E:49645i with Node: <0000000000000000, 0> S:0 M:146497140] (U) Msg Retransmission to 0:0000000000000000
2025-11-10 10:37:57.946 (Dummy-2) CHIP_PROGRESS [chip.native.EM] ??2 [E:49645i with Node: <0000000000000000, 0> S:0 M:146497140] (U) Msg Retransmission to 0:0000000000000000 scheduled for 2704ms from now [State:Active II:3000 AI:2200 AT:4000]
2025-11-10 10:38:00.654 (Dummy-2) CHIP_PROGRESS [chip.native.EM] <<2 [E:49645i with Node: <0000000000000000, 0> S:0 M:146497140] (U) Msg Retransmission to 0:0000000000000000
2025-11-10 10:38:00.654 (Dummy-2) CHIP_PROGRESS [chip.native.EM] ??3 [E:49645i with Node: <0000000000000000, 0> S:0 M:146497140] (U) Msg Retransmission to 0:0000000000000000 scheduled for 6152ms from now [State:Idle II:3000 AI:2200 AT:4000]
2025-11-10 10:38:06.813 (Dummy-2) CHIP_PROGRESS [chip.native.EM] <<3 [E:49645i with Node: <0000000000000000, 0> S:0 M:146497140] (U) Msg Retransmission to 0:0000000000000000
2025-11-10 10:38:06.813 (Dummy-2) CHIP_PROGRESS [chip.native.EM] ??4 [E:49645i with Node: <0000000000000000, 0> S:0 M:146497140] (U) Msg Retransmission to 0:0000000000000000 scheduled for 9019ms from now [State:Idle II:3000 AI:2200 AT:4000]
2025-11-10 10:38:15.842 (Dummy-2) CHIP_PROGRESS [chip.native.EM] <<4 [E:49645i with Node: <0000000000000000, 0> S:0 M:146497140] (U) Msg Retransmission to 0:0000000000000000
2025-11-10 10:38:15.842 (Dummy-2) CHIP_PROGRESS [chip.native.EM] ??5 [E:49645i with Node: <0000000000000000, 0> S:0 M:146497140] (U) Msg Retransmission to 0:0000000000000000 scheduled for 13876ms from now [State:Idle II:3000 AI:2200 AT:4000]
2025-11-10 10:38:29.733 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:49645i with Node: <0000000000000000, 0> S:0 M:146497140] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4)
2025-11-10 10:38:41.737 (Dummy-2) CHIP_ERROR [chip.native.SC] PASESession timed out while waiting for a response from the peer. Expected message type was 33
2025-11-10 10:38:41.737 (Dummy-2) CHIP_DETAIL [chip.native.IN] SecureSession[0x7fa6c00095c0]: Released - Type:1 LSID:149
2025-11-10 10:38:41.737 (Dummy-2) CHIP_ERROR [chip.native.ZCL] Secure Pairing Failed
2025-11-10 10:38:41.737 (Dummy-2) WARNING [chip.ChipDeviceCtrl] Failed to establish secure session to device: src/controller/python/ChipDeviceController-ScriptDevicePairingDelegate.cpp:96: CHIP Error 0x00000003: Incorrect state
2025-11-10 10:38:41.738 (MainThread) ERROR [matter_server.server.client_handler] [140354313483664] Error while handling: commission_with_code: Commission with code failed for node 5.

Attempting to add directly to Home Assistant from an Android device yields similar results:

2025-11-10 10:09:35.268 (MainThread) INFO [matter_server.server.server] Matter Server successfully initialized.
2025-11-10 10:12:44.347 (MainThread) INFO [matter_server.server.device_controller] Starting Matter commissioning using Node ID 3 and IP fd58:8a6b:718a:0:2ace:b9a8:64c3:1a1b.
2025-11-10 10:12:44.348 (Dummy-2) CHIP_DETAIL [chip.native.IN] SecureSession[0x7fa6c000c8d0]: Allocated Type:1 LSID:144
2025-11-10 10:12:44.348 (Dummy-2) CHIP_DETAIL [chip.native.SC] Assigned local session key ID 144
2025-11-10 10:12:44.348 (Dummy-2) CHIP_PROGRESS [chip.native.EM] <<< [E:49640i S:0 M:146497135] (U) Msg TX from 8CA3ED5543F0FFA1 to 0:0000000000000000 [0000] [UDP:[fd58:8a6b:718a:0:2ace:b9a8:64c3:1a1b]:5540] --- Type 0000:20 (SecureChannel:PBKDFParamRequest) (B:97)
2025-11-10 10:12:44.349 (Dummy-2) CHIP_PROGRESS [chip.native.EM] ??1 [E:49640i with Node: <0000000000000000, 0> S:0 M:146497135] (U) Msg Retransmission to 0:0000000000000000 scheduled for 344ms from now [State:Active II:500 AI:300 AT:4000]
2025-11-10 10:12:44.349 (Dummy-2) CHIP_PROGRESS [chip.native.SC] Sent PBKDF param request [II:500ms AI:300ms AT:4000ms)
2025-11-10 10:12:44.349 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Setting attestation nonce to random value
2025-11-10 10:12:44.349 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Setting CSR nonce to random value
2025-11-10 10:12:44.350 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Commission called for node ID 0x0000000000000003
2025-11-10 10:12:44.693 (Dummy-2) CHIP_PROGRESS [chip.native.EM] <<1 [E:49640i with Node: <0000000000000000, 0> S:0 M:146497135] (U) Msg Retransmission to 0:0000000000000000
2025-11-10 10:12:44.693 (Dummy-2) CHIP_PROGRESS [chip.native.EM] ??2 [E:49640i with Node: <0000000000000000, 0> S:0 M:146497135] (U) Msg Retransmission to 0:0000000000000000 scheduled for 350ms from now [State:Active II:500 AI:300 AT:4000]
2025-11-10 10:12:45.044 (Dummy-2) CHIP_PROGRESS [chip.native.EM] <<2 [E:49640i with Node: <0000000000000000, 0> S:0 M:146497135] (U) Msg Retransmission to 0:0000000000000000
2025-11-10 10:12:45.045 (Dummy-2) CHIP_PROGRESS [chip.native.EM] ??3 [E:49640i with Node: <0000000000000000, 0> S:0 M:146497135] (U) Msg Retransmission to 0:0000000000000000 scheduled for 645ms from now [State:Active II:500 AI:300 AT:4000]
2025-11-10 10:12:45.691 (Dummy-2) CHIP_PROGRESS [chip.native.EM] <<3 [E:49640i with Node: <0000000000000000, 0> S:0 M:146497135] (U) Msg Retransmission to 0:0000000000000000
2025-11-10 10:12:45.692 (Dummy-2) CHIP_PROGRESS [chip.native.EM] ??4 [E:49640i with Node: <0000000000000000, 0> S:0 M:146497135] (U) Msg Retransmission to 0:0000000000000000 scheduled for 871ms from now [State:Active II:500 AI:300 AT:4000]
2025-11-10 10:12:46.564 (Dummy-2) CHIP_PROGRESS [chip.native.EM] <<4 [E:49640i with Node: <0000000000000000, 0> S:0 M:146497135] (U) Msg Retransmission to 0:0000000000000000
2025-11-10 10:12:46.565 (Dummy-2) CHIP_PROGRESS [chip.native.EM] ??5 [E:49640i with Node: <0000000000000000, 0> S:0 M:146497135] (U) Msg Retransmission to 0:0000000000000000 scheduled for 1686ms from now [State:Active II:500 AI:300 AT:4000]
2025-11-10 10:12:48.253 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:49640i with Node: <0000000000000000, 0> S:0 M:146497135] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4)
2025-11-10 10:12:54.797 (Dummy-2) CHIP_ERROR [chip.native.SC] PASESession timed out while waiting for a response from the peer. Expected message type was 33
2025-11-10 10:12:54.797 (Dummy-2) CHIP_DETAIL [chip.native.IN] SecureSession[0x7fa6c000c8d0]: Released - Type:1 LSID:144
2025-11-10 10:12:54.797 (Dummy-2) CHIP_ERROR [chip.native.ZCL] Secure Pairing Failed
2025-11-10 10:12:54.798 (Dummy-2) WARNING [chip.ChipDeviceCtrl] Failed to establish secure session to device: src/controller/python/ChipDeviceController-ScriptDevicePairingDelegate.cpp:96: CHIP Error 0x00000003: Incorrect state
2025-11-10 10:12:54.798 (MainThread) ERROR [matter_server.server.client_handler] [140354313483664] Error while handling: commission_on_network: Commissioning failed for node 3.

Attempting to add directly to Home Assistant from an iOS device seemingly fails at an earlier stage; no logs, the commission progress just gets stuck at the “Setting up…” phase indefinitely after the phone connects to the device.

I’m at a lost as to what needs to change in my setup to get this sort of thing to work, or if it’s just a lost cause and I should stick to Zwave/Zigbee lol.

WallyR · November 10, 2025, 9:09pm

I have two Zemismart blind kits and had no issue with pairing them.
I skipped reading the manual at first (true nerd behavior), but the it had a couple of different modes it jumped through when holding the button, so had to read it to figure out the correct method.

stepper126 · November 10, 2025, 9:15pm

Yeah, I mean the instructions I have only describe

Putting the device into pairing mode (3 taps)
Pairing the remote to the device (1 tap on the driver, 1 tap on the remote)
Factory Reset (Long press on the device or a button combo on a paired remote)

I’ve basically tried everything – it does pair to every mobile app EXCEPT for Home Assistant for some reason. Maybe my matter hubs (Homepod minis) aren’t doing what they’re supposed to and I need a more dedicated gateway/routers?

WallyR · November 10, 2025, 11:25pm

You did copy the Thread credentials to your iOS device?

It is done in the companion app under settings → companion app → troubleshooting.

peterxian · November 10, 2025, 11:28pm

If you can commission them to Apple Home but not HA, it usually suggests a network problem.

My recommendation is to commission to Apple Home, then use the settings page to re-open the commissioning window and add them to HA as a device “already in use”. Most of the time, this works. This way you can also completely ignore all the confusion wrapped around HA’s Thread implementation.

If that fails, make sure you have IPv6 enabled and set to auto in HAOS — even though it is required by the Matter add-on, for some reason it is not enabled by default or even issue a warning. Also make sure your HAOS and Homepod(s) are on the same subnet / vlan / broadcast domain.

stepper126 · November 11, 2025, 2:37am

Thanks for the suggestions~ Yes, I’ve tried both syncing thread credentials with iOS and Android at different points and I’ve tried the Apple Home to HOAS commissioning bit both via the add device option and the direct commision function in the server ui, to no avail.

I agree that it has to be something with the network setup since I’m able to pair across both apple and iOS and even with some 3rd party apps like Tuya, but honestly, I’m not sure where to even start. As far as I can tell, my router is only set up to be dishing out on one subnet and the ipv6’s are all local-only. There’s no toggles for mDNS or any multicast adjacent options like that in any of my settings, so I suspect that’s either not a problem or not something I can solve.
(For reference my router is a QNAP Qhora 301W)

It does seem like it sees something on ipv6 but seems to just died out after that.

2025-11-10 16:23:48.094 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Discovered device with discriminator 299 matches one of our setup payloads
2025-11-10 16:23:48.094 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Discovered device to be commissioned over DNS-SD
2025-11-10 16:23:48.094 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Attempting PASE connection to UDP:[fdf8:95a2:e1e7:0:d318:1116:c418:4d5a]:5540
2025-11-10 16:23:48.095 (Dummy-2) CHIP_DETAIL [chip.native.IN] SecureSession[0x7f574800c8d0]: Allocated Type:1 LSID:54614
2025-11-10 16:23:48.095 (Dummy-2) CHIP_DETAIL [chip.native.SC] Assigned local session key ID 54614
2025-11-10 16:23:48.095 (Dummy-2) CHIP_PROGRESS [chip.native.EM] <<< [E:5382i S:0 M:225085275] (U) Msg TX from BD0899B4C0B4788F to 0:0000000000000000 [0000] [UDP:[fdf8:95a2:e1e7:0:d318:1116:c418:4d5a]:5540] --- Type 0000:20 (SecureChannel:PBKDFParamRequest) (B:98)
2025-11-10 16:23:48.095 (Dummy-2) CHIP_PROGRESS [chip.native.EM] ??1 [E:5382i with Node: <0000000000000000, 0> S:0 M:225085275] (U) Msg Retransmission to 0:0000000000000000 scheduled for 2841ms from now [State:Active II:3000 AI:2200 AT:4000]

WallyR · November 11, 2025, 10:51am

When you commission a device that is already paired to another system, then you need a pairing code from that system.
The original code on the device only works for the first pairing after a factory reset.

stepper126 · November 11, 2025, 5:35pm

Yeah, when I’m attempting to pair from Google Home / Tuya / Apple Home, I’m using the new codes/processes that are provided in those apps to attempt to commission rather than the one that was used to originally pair the device to the first service. So it’s not that.

stepper126 · November 11, 2025, 8:09pm

Got it solved, for now at least.

Spun up a new VM on a different computer and it connected immediately, so I started poking around the (TrueNAS) VM setup settings for the original install – ticked Trust Guest Filters to see if that did anything. And I guess it did? Or maybe something else changed in the config in the process. Also cleaned up some of my add-ons, but not sure if those were doing anything to the network traffic really… so it was probably that one NIC toggle unless I come back here with and update.