Shutdown subscription??

[bkoblenz]

I have had a couple of unusual issues this past week and would welcome advice as to what information to collect and how to debug should they happen again.

I have multiple thread-based matter devices (nodes 1,5,12) that are commissioned and one wifi device (node 14)

Everything is going along fine and then get a series of failures ending with:
2025-01-27 05:24:21,958 - chip.native.DIS - Level 39 - OperationalSessionSetup[1:000000000000000E]: operational discovery failed: src/lib/address_resolve/Addre>
2025-01-27 05:24:21,959 - chip.native.DMG - Level 39 - Failed to establish CASE for re-subscription with error 'src/lib/address_resolve/AddressResolve_DefaultI>
2025-01-27 05:24:21,961 - matter_server.server.device_controller - INFO - Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 13
2025-01-27 05:24:21,961 - matter_server.server.device_controller - INFO - Node considered offline, shutdown subscription

I assume the 00000E refers to node 14 but not sure? It would be helpful if node ids were include with device controller messages.

What does it mean to shutdown the subscription? How do I force resubscribing?

A little later I got:
2025-01-27 06:08:41,156 - chip.native.DIS - Level 39 - OperationalSessionSetup[1:000000000000000C]: operational discovery failed: src/lib/address_resolve/Addre>
2025-01-27 06:08:41,157 - chip.native.DMG - Level 39 - Failed to establish CASE for re-subscription with error 'src/lib/address_resolve/AddressResolve_DefaultI>
2025-01-27 06:08:41,159 - matter_server.server.device_controller - INFO - Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 13
2025-01-27 06:08:41,159 - matter_server.server.device_controller - INFO - Node considered offline, shutdown subscription

Here I think node 12 is considered offline. In reality I do not believe anything was offline.

When I rebooted my hub/server, everything was fine? What might I look at while the problem persists to understand what is going on and what might I try to work around the issue short of needing to reboot my server.

On a separate time, I seem to have lost access to all of my devices. Performing a reboot did nothing to solve the problem. I saved the data (./matter_server/*) recreated that directory and recommissioned all of my devices and everything is fine. I still have the old database, but again, I am wondering what I might try or collect (should this happen again) to understand what went wrong and to get things back on track?

thanks
-brian