Alternative firmware for ESP8266 and ESP32 based devices with easy configuration using webUI, OTA updates, automation using timers or rules, expandability and entirely local control over MQTT, HTTP, Serial or KNX. Full documentation at
The APA102, often called Dotstar, is a common multicolor LED, similar to the already-supported WS2182. Instead of a single wire it uses two - a data and a clock. It currently is not supported by Tasmota.
It should be possible to add support for this LED without too much work, since the NeopixelBus library used in Tasmota offers support for them.
[x] Set weblog to 4 and then, when you experience your issue, provide the output of the Console log:
Console output here:
Not applicable
### TO REPRODUCE
_Steps to reproduce the behavior:_
None, just a feature request.
### EXPECTED BEHAVIOUR
_A clear and concise description of what you expected to happen._
Dotstar data and clock lines should be available for assignment in templates.
### SCREENSHOTS
_If applicable, add screenshots to help explain your problem._
N/A
### ADDITIONAL CONTEXT
_Add any other context about the problem here._
I spent some time researching this before submitting here and could only find a single auto-closed issue, #10953, relating to this request so I don't think this issue is redundant. Unless the answer is "no", which is fine, but if that's the case then hopefully the next person looking up this topic can find the answer here. :)
Thank you for your time. :)
**(Please, remember to close the issue when the problem has been addressed)**
PROBLEM DESCRIPTION
The APA102, often called Dotstar, is a common multicolor LED, similar to the already-supported WS2182. Instead of a single wire it uses two - a data and a clock. It currently is not supported by Tasmota.
It should be possible to add support for this LED without too much work, since the
NeopixelBus
library used in Tasmota offers support for them.REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
Backlog Template; Module; GPIO 255
:21:48:23.369 MQT: test_tas/RESULT = {"NAME":"Funhouse","GPIO":[0,1,1,0,0,0,1,1,1,1,5411,5410,5409,5408,0,0,1,1,4704,0,0,992,608,640,864,896,832,1,6624,6592,1024,1,0,0,0,0],"FLAG":0,"BASE":1} 21:48:23.595 MQT: test_tas/RESULT = {"Module":{"0":"Funhouse"}} 21:48:23.831 MQT: test_tas/RESULT = {"GPIO0":{"0":"None"},"GPIO1":{"0":"None"},"GPIO2":{"0":"None"},"GPIO3":{"0":"None"},"GPIO4":{"0":"None"},"GPIO5":{"0":"None"},"GPIO6":{"0":"None"},"GPIO7":{"0":"None"},"GPIO8":{"0":"None"},"GPIO9":{"0":"None"},"GPIO10":{"5411":"Button_tc4"},"GPIO11":{"5410":"Button_tc3"},"GPIO12":{"5409":"Button_tc2"},"GPIO13":{"5408":"Button_tc1"},"GPIO14":{"0":"None"},"GPIO15":{"0":"None"},"GPIO16":{"0":"None"},"GPIO17":{"0":"None"},"GPIO18":{"4704":"ADC Input1"},"GPIO19":{"0":"None"},"GPIO20":{"0":"None"},"GPIO21":{"992":"Backlight"},"GPIO33":{"608":"I2C SCL1"},"GPIO34":{"640":"I2C SDA1"},"GPIO35":{"864":"SSPI MOSI"},"GPIO36":{"896":"SSPI SCLK"},"GPIO37":{"832":"SSPI MISO"},"GPIO38":{"0":"None"},"GPIO39":{"6624":"ST7789 DC"},"GPIO40":{"6592":"ST7789 CS"},"GPIO41":{"1024":"Display Rst"},"GPIO42":{"0":"None"},"GPIO43":{"0":"None"},"GPIO44":{"0":"None"},"GPIO45":{"0":"None"},"GPIO46":{"0":"None"}}
Status 0
:weblog
to 4 and then, when you experience your issue, provide the output of the Console log:Not applicable