Matter Server hat Probleme bei mir

Add-ons
1

Hallo…

habe habe seit kurzem einen Thread Border Router und einige Geräte damit verbunden. Vorher hatte ich schon eine Matter/WLAN Steckdose.

Nun geht plötzlich gar nichts mehr. Die Geräte sind nicht verfügbar.

HA-Neustart habe ich gemacht, hat nicht geholfen.

Hier das Protokoll vom Matter Server:

-----------------------------------------------------------
 Add-on: Matter Server
 Matter WebSocket Server for Home Assistant Matter support.
-----------------------------------------------------------
 Add-on version: 8.1.2
 You are running the latest version of this add-on.
 System: Home Assistant OS 16.3  (amd64 / generic-x86-64)
 Home Assistant Core: 2025.12.5
 Home Assistant Supervisor: 2025.12.3
-----------------------------------------------------------
 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
[20:05:55] INFO: Starting Matter Server...
s6-rc: info: service legacy-services successfully started
[20:05:55] INFO: Using 'wlp0s20f3' as primary network interface.
[20:05:56] INFO: Successfully send discovery information to Home Assistant.
2026-01-06 20:05:57.871 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Logging...
2026-01-06 20:05:57.871 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Controller Stack...
[1767726357.901669][117:117] CHIP:CTL: Setting attestation nonce to random value
[1767726357.901860][117:117] CHIP:CTL: Setting CSR nonce to random value
[1767726357.902512][117:117] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
[1767726357.903488][117:117] CHIP:DL: Wrote settings to /tmp/chip_kvs
[1767726357.903666][117:117] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_factory.ini
[1767726357.903975][117:117] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_config.ini
[1767726357.904285][117:117] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_counters.ini
[1767726357.905148][117:117] CHIP:DL: Wrote settings to /data/chip_counters.ini
[1767726357.905157][117:117] CHIP:DL: NVS set: chip-counters/reboot-count = 47 (0x2F)
[1767726357.905420][117:117] CHIP:DL: Got Ethernet interface: enp55s0u1u1c2
[1767726357.905570][117:117] CHIP:DL: Found the primary Ethernet interface:enp55s0u1u1c2
[1767726357.905662][117:117] CHIP:DL: Got WiFi interface: wlp0s20f3
[1767726357.905923][117:117] CHIP:DL: Found the primary WiFi interface:wlp0s20f3
[1767726357.905928][117:117] CHIP:PAF: WiFiPAF: WiFiPAFLayer::Init()
2026-01-06 20:05:57.906 (MainThread) INFO [chip.storage] Initializing persistent storage from file: /data/chip.json
2026-01-06 20:05:57.906 (MainThread) INFO [chip.storage] Loading configuration from /data/chip.json...
2026-01-06 20:05:57.981 (MainThread) INFO [chip.CertificateAuthority] Loading certificate authorities from storage...
2026-01-06 20:05:57.981 (MainThread) INFO [chip.CertificateAuthority] New CertificateAuthority at index 1
2026-01-06 20:05:57.982 (MainThread) INFO [chip.CertificateAuthority] Loading fabric admins from storage...
2026-01-06 20:05:57.982 (MainThread) INFO [chip.FabricAdmin] New FabricAdmin: FabricId: 0x0000000000000002, VendorId = 0x134B
2026-01-06 20:05:57.982 (MainThread) INFO [matter_server.server.stack] CHIP Controller Stack initialized.
2026-01-06 20:05:57.982 (MainThread) INFO [matter_server.server.server] Matter Server initialized
2026-01-06 20:05:57.982 (MainThread) INFO [matter_server.server.server] Using 'wlp0s20f3' as primary interface (for link-local addresses)
2026-01-06 20:05:57.983 (MainThread) INFO [matter_server.server.server] Starting the Matter Server...
2026-01-06 20:05:57.985 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Fetching the latest PAA root certificates from DCL.
2026-01-06 20:06:02.513 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Fetched 72 PAA root certificates from DCL.
2026-01-06 20:06:02.514 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Fetching the latest PAA root certificates from Git.
2026-01-06 20:06:03.022 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Fetched 2 PAA root certificates from Git.
2026-01-06 20:06:03.025 (MainThread) INFO [chip.FabricAdmin] Allocating new controller with CaIndex: 1, FabricId: 0x0000000000000002, NodeId: 0x000000000001B669, CatTags: []
2026-01-06 20:06:03.134 (Dummy-2) CHIP_ERROR [chip.native.DL] Long dispatch time: 106 ms, for event type 2
2026-01-06 20:06:03.141 (MainThread) INFO [matter_server.server.vendor_info] Loading vendor info from storage.
2026-01-06 20:06:03.145 (MainThread) INFO [matter_server.server.vendor_info] Loaded 380 vendors from storage.
2026-01-06 20:06:03.145 (MainThread) INFO [matter_server.server.vendor_info] Fetching the latest vendor info from DCL.
2026-01-06 20:06:03.547 (MainThread) INFO [matter_server.server.vendor_info] Fetched 381 vendors from DCL.
2026-01-06 20:06:03.547 (MainThread) INFO [matter_server.server.vendor_info] Saving vendor info to storage.
2026-01-06 20:06:03.576 (MainThread) INFO [matter_server.server.device_controller] Loaded 6 nodes from stored configuration
2026-01-06 20:06:03.595 (MainThread) INFO [matter_server.server.server] Matter Server successfully initialized.
2026-01-06 20:06:04.227 (MainThread) INFO [matter_server.server.device_controller.mdns] <Node:16> Discovered on mDNS
2026-01-06 20:06:04.228 (MainThread) INFO [matter_server.server.device_controller.mdns] <Node:17> Discovered on mDNS
2026-01-06 20:06:04.228 (MainThread) INFO [matter_server.server.device_controller.mdns] <Node:20> Discovered on mDNS
2026-01-06 20:06:04.229 (MainThread) INFO [matter_server.server.device_controller] <Node:16> Setting-up node...
2026-01-06 20:06:04.230 (MainThread) INFO [matter_server.server.device_controller] <Node:17> Setting-up node...
2026-01-06 20:06:04.230 (MainThread) INFO [matter_server.server.device_controller] <Node:20> Setting-up node...
2026-01-06 20:06:21.930 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from peer <0000000000000010, 1>. Current state was 1
2026-01-06 20:06:24.935 (MainThread) INFO [matter_server.server.sdk] <Node:16> Attempting to establish CASE session... (attempt 2 of 2)
2026-01-06 20:06:35.485 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:91i with Node: <0000000000000000, 0> S:0 M:220158429] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4)
2026-01-06 20:06:42.640 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from peer <0000000000000010, 1>. Current state was 1
2026-01-06 20:06:42.642 (MainThread) WARNING [matter_server.server.device_controller] <Node:16> Setup for node failed: Unable to establish CASE session with Node 16
2026-01-06 20:06:42.642 (MainThread) INFO [matter_server.server.device_controller] <Node:16> Retrying node setup in 60 seconds...

Was läuft hier schief?

Ohne, dass ich groß etwas gemacht habe, sind nun 2 von 6 Geräten wieder verfügbar…

image
image719×802 17.9 KB

2026-01-06 20:27:07.595 (MainThread) INFO [matter_server.server.sdk] <Node:20> Attempting to establish CASE session... (attempt 2 of 2)
2026-01-06 20:27:07.811 (MainThread) INFO [matter_server.server.device_controller] <Node:16> Setting-up node...
2026-01-06 20:27:38.605 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-01-06 20:27:38.815 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-01-06 20:27:52.597 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000014]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-01-06 20:27:52.598 (MainThread) WARNING [matter_server.server.device_controller] <Node:20> Setup for node failed: Unable to establish CASE session with Node 20
2026-01-06 20:27:52.598 (MainThread) INFO [matter_server.server.device_controller] <Node:20> Retrying node setup in 60 seconds...
2026-01-06 20:27:52.813 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000010]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2

Also bei mir gehen die Ikea Dinger auch immer wieder offline. Irgendwie ein schlafmodus. Wen ich dann den schalter drücke is er nach ca 2min wieder online.

Gruss adsid

3

Ok, das habe ich so zum Glück nicht. Seit der Unterbrechung gestern sind alle wieder online.

image
image560×207 13.7 KB

4

Das habe ich auch mit meinem Sensor auf dem Dachboden. Der ist aber auch am weitesten von allem weg. Ich vermute hier ist der am äußersten Ende seiner Reichweite. Ich warte gerade noch auf Steckdosen, mal schauen wie sich das ganze mit ein paar mehr Routern entwickelt.

5

Ich habe:

(Matter Geräte)

3 Google Nest Hub; 7 Ikea Thermometer; 1 Bewegungsmelder; 2 Schalter und 1 Lampe.

Alles direkt über HA ein gelernt und hat auch alles geklappt, aber immer wieder geht mal eines der Thermometer offline. Ich lösche es, lerne es neu an und dann ist es online. Dauert aber nicht lange bis es wieder offline ist. Das sind fast immer dir gleichen Geräte. Aber und zu gehen die Geräte auch von alleine online, aber nicht lange.

Ich habe keine Ahnung mehr woran es liegen könnte.

7

Moin!

Habe das Problem mit meinem Myggbett Sensor, der im Kühlschrank wohnt. Nach ca einer Woche offline, aber im Grunde wird er täglich genutzt, Tiefschlaf oder so macht demnach keinen Sinn. Aktuell gibt es aber keine weiteren Thread Geräte zum Testen.

Edit: Über Matter: IKEA - All New IKEA Matter devices -- loses connection, reconnection succeeds but doesn't work · Issue #158954 · home-assistant/core · GitHub gestolpert, kommt mir bekannt vor.

Edit2: Vielleicht läuft GitHub - matter-js/matterjs-server: Matter server based on Matter.js besser als die Python-Variante.

:crayon:by HarryP: Zusammenführung Doppelpost (bei Änderungen oder hinzufügen von Inhalten bitte die „Bearbeitungsfunktion“ anstatt „Antworten“ zu nutzen)