From db5b1de530fa5536601e7f7c82c42d4da03a58b5 Mon Sep 17 00:00:00 2001
From: eagleco <39813792+eagleco@users.noreply.github.com>
Date: Wed, 17 Apr 2024 22:04:42 -0700
Subject: [PATCH] Update status_led.rst (#3768)

Include note about status led blinking slowly when native API is included in configuration but no api client is connected.
---
 components/status_led.rst | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/components/status_led.rst b/components/status_led.rst
index 28af3bd75..26d9e2fdc 100644
--- a/components/status_led.rst
+++ b/components/status_led.rst
@@ -9,7 +9,8 @@ The ``status_led`` hooks into all ESPHome components and can indicate the status
 the device. Specifically, it will:
 
 - Blink slowly (about every second) when a **warning** is active. Warnings are active when for
-  example reading a sensor value fails temporarily or the WiFi/MQTT connections are disrupted.
+  example reading a sensor value fails temporarily, the WiFi/MQTT connections are disrupted, or 
+  if the native API component is included but no client is connected.
 - Blink quickly (multiple times per second) when an **error** is active. Errors indicate that
   ESPHome has found an error while setting up. In most cases, ESPHome will still try to
   recover from the error and continue with all other operations.