From d7dea9e74ab82e11408f80adbc6665b276d2dde5 Mon Sep 17 00:00:00 2001 From: "J. Nick Koston" Date: Mon, 7 Sep 2026 17:33:48 +0200 Subject: [PATCH] Point at WatchdogManager for work longer than the watchdog timeout --- esphome/core/application.h | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/esphome/core/application.h b/esphome/core/application.h index 7d8b317067..c38a7b2281 100644 --- a/esphome/core/application.h +++ b/esphome/core/application.h @@ -649,8 +649,10 @@ class LoopBlockingGuard { /// Only work timed by a LoopBlockingGuard is affected, that is a component's /// loop() or a scheduler callback; setup() is not timed, so the scope does /// nothing there. Main loop task only. The watchdog is not fed inside the -/// scope, so the work must still finish within the watchdog timeout. Scopes -/// may nest; the outermost one decides how much of the pass is left out. +/// scope, so the work must finish within the watchdog timeout, or be paired +/// with a watchdog::WatchdogManager that raises the timeout for the same +/// stretch. Scopes may nest; the outermost one decides how much of the pass +/// is left out. /// App.get_loop_component_start_time() reads later in the same pass return /// the moved start, so elapsed time across the scope needs millis(). ///