Matter Server Log shows errors but it is working

Configuration Matter/Thread
1

Hello Community.
I’ve struggled some days to get my new Aqara U200 Lock connect to HA as my first Matter/Thread device but got it finally to running and it works flawless (till now)

When I dig through the “Matter Server” logs during troubleshooting the connection I’ve stumbled upon these error messages and I am concerned if they could lead to some error situtations in the future or if I have a general problem in my setup.

2024-08-07 19:17:42.218 (MainThread) INFO [matter_server.server.server] Starting the Matter Server...
2024-08-07 19:17:42.221 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Skip fetching certificates (already fetched within the last 24h).
2024-08-07 19:17:42.221 (MainThread) INFO [chip.FabricAdmin] Allocating new controller with CaIndex: 1, FabricId: 0x0000000000000002, NodeId: 0x000000000001B669, CatTags: []
2024-08-07 19:17:42.326 (Dummy-2) CHIP_ERROR [chip.native.DIS] Failed to advertise records: src/inet/UDPEndPointImplSockets.cpp:416: OS Error 0x02000065: Network is unreachable
2024-08-07 19:17:42.332 (Dummy-2) CHIP_ERROR [chip.native.DL] Long dispatch time: 109 ms, for event type 2
2024-08-07 19:17:42.338 (MainThread) INFO [matter_server.server.vendor_info] Loading vendor info from storage.

As I said. It is working right now and the log also ended with

2024-08-07 19:17:42.608 (MainThread) INFO [matter_server.server.server] Matter Server successfully initialized.

Everything in HA (Rspi5) is up-to-date. No errors in the OTBR Log.
I’m using a SONOFF Dongle E with OpenThread RCP firmware in additon to a SONOFF Dongle E with Zigbee.

Any ideas? Searching through net didn’t enlightened me…

Thanks in advance
Olaf

2

The “Failed to advertise records” probably means you have a interface which the Matter Server considers for mDNS lookup (e.g. is considered up) but can’t be used for some reason (e.g. not multicast ready, or not really up, this can be a WiFi/VPN or a virtual network). Since the device are generally found by the Matter Server it seems that access to the interface which is relevant works. So you can safely ignore this.

The long dispatch time just means that the event loop of the server has been blocked for quite some time, which can cause sluggy behavior. It is not really relevant since that is only during startup. We probably should suppress the error during that time. So you can safely ignore this too.

1 Like
3

Hi and thanks.
That’s what I wanted to here.