From 7b747bbd6b0f8ab489ab0e77ea7372c7cef052a5 Mon Sep 17 00:00:00 2001 From: "J. Nick Koston" Date: Thu, 10 Sep 2026 08:56:35 -0500 Subject: [PATCH] Soften the set_internal() limitations wording --- esphome/core/entity_base.h | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/esphome/core/entity_base.h b/esphome/core/entity_base.h index 01a1ef7111..c95d7184d3 100644 --- a/esphome/core/entity_base.h +++ b/esphome/core/entity_base.h @@ -94,7 +94,8 @@ class EntityBase { // from on_boot at the default priority, or a setup() that runs above setup_priority::AFTER_WIFI. // Calls after setup finishes are ignored and log an error. // - // Known limitations, all by design and not going to be fixed: + // Known limitations. Not bugs, so no issue reports please; a PR that removes one with no RAM + // or performance cost would be considered. // - No consumer is notified of a change, so the flag can only be decided once per boot. // - The guard is coarse: a call from a priority below AFTER_WIFI (an on_boot with a low priority, // or a setup() at LATE) still passes, but the API camera listener is already registered, MQTT