From 0af331d2809a7b3b4ed3023735e53da2cf031e31 Mon Sep 17 00:00:00 2001 From: Stefan Agner Date: Thu, 12 Sep 2024 13:38:36 +0200 Subject: [PATCH] Cleanup: Lower "Activity on mDNS" message (#883) Co-authored-by: Marcel van der Veldt --- matter_server/server/device_controller.py | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/matter_server/server/device_controller.py b/matter_server/server/device_controller.py index dc3e0e5a..5f730ff5 100644 --- a/matter_server/server/device_controller.py +++ b/matter_server/server/device_controller.py @@ -1481,7 +1481,13 @@ def _on_mdns_operational_node_state( self._setup_node_create_task(node_id) elif state_change == ServiceStateChange.Added: # Trigger node re-subscriptions when mDNS entry got added - node_logger.info("Activity on mDNS, trigger resubscribe") + # Note: Users seem to get such mDNS messages fairly regularly, and often + # the subscription to the device is healthy and fine. This is not a problem + # since trigger_resubscribe_if_scheduled won't do anything in that case + # (no resubscribe is scheduled). + # But this does speedup the resubscription process in case the subscription + # is already in resubscribe mode. + node_logger.debug("Activity on mDNS, trigger resubscribe if scheduled") asyncio.create_task( self._chip_device_controller.trigger_resubscribe_if_scheduled( node_id, "mDNS state change detected"