esphome / esphome/feature-requests

Support arbitrary light for status_led

Open
#1,603 14 comments 7 reactions 0 assignees View on GitHub
component: addressable_light component: status_led
Dominant language
No language data
Stars
450
Forks
29
PR merge metrics
No merged PRs in 30d

Description

**Describe the problem you have/What new integration you would like**

The [M5Stack Pico mate](https://shop.m5stack.com/products/m5stamp-pico-mate-with-pin-headers) has a SK6812 LED onboard but no other LED. So it is impossible to use the [status_led light component](https://esphome.io/components/light/status_led.html).

![M5Stack Pico](https://cdn.shopify.com/s/files/1/0056/7689/2250/products/9_3f66cf5c-4ac6-4f6a-b2ea-84952cfab478_1200x1200.jpg)

**Please describe your use case for this integration and alternatives you've tried:**

It'd be nice if we could use the onboard RGB led as a status LED.

I think it'd be better to simply make status_led more generic than do a one-off to support a SK6812 specifically.

**Additional context**

I took a quick look at the code and there's no way at the moment hook events when STATUS_LED_ERROR or STATUS_LED_WARNING are set. I suspect this feature request would require some deep internal refactoring inside https://github.com/esphome/esphome/blob/dev/esphome/core/component.cpp.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the status_led light component and esphome/core/component.cpp, focusing on how STATUS_LED_ERROR and STATUS_LED_WARNING are set and propagated. The work is done when status_led can use the onboard SK6812 or another arbitrary light through a generic mechanism, with the relevant status behavior covered.

Written by the indexing model from the issue text.

Assessment

Domain
embedded-iot
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.