Hi. Im having a really bad time compiling this because i don't know what versions of the includes you use. Got most of my compiling errors away be downgrading some packages, but some wont go away. Would be great if you included them in the README :) My error log:

In file included from C:\Users\pc\Documents\Arduino\portable\sketchbook\libraries\FastLED/FastLED.h:48:0,

                 from C:\Users\pc\OneDrive\Dokumenter\Hassio\LED\PinkyLEDs-master\PinkyLEDs\PinkyLEDs.ino:7:

C:\Users\pc\Documents\Arduino\portable\sketchbook\libraries\FastLED/fastpin.h: In instantiation of 'class FastPin<14u>':

C:\Users\pc\Documents\Arduino\portable\sketchbook\libraries\FastLED/platforms/esp/8266/clockless_esp8266.h:21:49:   required from 'class ClocklessController<14, 20, 50, 30, (EOrder)66u, 0, false, 50>'

C:\Users\pc\Documents\Arduino\portable\sketchbook\libraries\FastLED/chipsets.h:550:7:   required from 'class WS2812Controller800Khz<14u, (EOrder)66u>'

C:\Users\pc\Documents\Arduino\portable\sketchbook\libraries\FastLED/FastLED.h:103:52:   required from 'class WS2812<14u, (EOrder)66u>'

C:\Users\pc\Documents\Arduino\portable\sketchbook\libraries\FastLED/FastLED.h:302:39:   required from 'static CLEDController& CFastLED::addLeds(CRGB*, int, int) [with CHIPSET = WS2812; unsigned char D5 = 14u; EOrder RGB_ORDER = (EOrder)66u]'

C:\Users\pc\OneDrive\Dokumenter\Hassio\LED\PinkyLEDs-master\PinkyLEDs\PinkyLEDs.ino:233:66:   required from here

C:\Users\pc\Documents\Arduino\portable\sketchbook\libraries\FastLED/fastpin.h:207:2: error: static assertion failed: Invalid pin specified

  static_assert(validpin(), "Invalid pin specified");

Within the reconnect() function the program connects to the MQTT broker setting the LWT message "Offline" as non-retain (the second 0 parameter of the client.connect), but then the program publishes the "Online" message as retain.
The result of the disconnection is when another MQTT client is subscribed to the LWT topic it receives correctly the "Offline" message, but if the same client reconnects while the PinkyLED device is still unreachable then it would receive the "Online" message on reconnection since that was the last retained message of that topic.

The fix is easy change the second 0 parameter in the connect function to true or 1.

"stat/" DEVICE_NAME is not working .nothing happened when the LED change its state.

This is my goto code for controlling LEDs from HA. Thanks!
I'm trying to change the scaling for the animation speed (white_value) slider because it's difficult to get the speed I want.
I tried root[SPEEDTOPIC] = map(animationspeed,0,255,200,255);
but that didn't work.
Can't seem to change the slider scale within HA either.
Any ideas?

Hi,
got the pinkyleds up and running and they are stunning , thank you. just one issue, I noticed on the Dots effects it only works for half the length . I have 3 x 5 m (150) leds connected and all the other effects work great.
Not a big deal but thought I would mention it.
once again, thank you

Hi. first of all thank you for this great sketch. But I got a problem. My wemos D1 mini keeps restarting, if I choose effects like USA, Go blue, Christmas and other. Other effects do work good. Tried various power bricks, That does not help. Tried different D1 mini, same behavior.

It also reboots after few minutes in every effect :(

How can i debug the issue, or what could be the problem? Thanks

Have only 20 leds running.

got this on debug, when reboot occured:

MQTT message received {"state": "ON"}
MQTT message received {"state": "ON", "effect": "USA"}

Exception (9):
epc1=0x40202a12 epc2=0x00000000 epc3=0x00000000 excvaddr=0x3ffe8d5e depc=0x00000000

>>>stack>>>

ctx: cont
sp: 3ffffd40 end: 3fffffc0 offset: 01a0
3ffffee0:  0126c417 00000000 3ffef05c 40204a35  
3ffffef0:  3fffff30 00000000 3ffef5e8 3ffef830  
3fffff00:  3fffdad0 00000000 00000002 3ffef830  
3fffff10:  00000000 00000000 3ffef57c 40205087  
3fffff20:  00000000 3ffef67c 3fff0bb4 40209912  
3fffff30:  93960000 4872001f 00696a00 00008919  
3fffff40:  66001774 0759000c 04034d01 32090340  
3fffff50:  09410303 01184b02 2c003748 cc000077  
3fffff60:  a180c05b 0000e7ff 3ffef5e8 4020316a  
3fffff70:  00000096 feefeffe 000000a1 00000067  
3fffff80:  ffcd0000 22b2dcf8 feefef22 feefeffe  
3fffff90:  00000000 00000000 00000001 3ffef830  
3fffffa0:  3fffdad0 00000000 3ffef800 4020fb74  
3fffffb0:  feefeffe feefeffe 3ffe8590 40100cf5  
<<<stack<<<

 ets Jan  8 2013,rst cause:2, boot mode:(3,6)

load 0x4010f000, len 1384, room 16 
tail 8
chksum 0x2d
csum 0x2d
v951aeffa
~ld
⸮⸮

Home Assistant uses Integrations now for auto discovered devices.
The Discovery in the PinkyLEDs script seems to work as far as the light being available, but it never shows in the MQTT Integrations in Home Assistant.
I've tried everything I can think of on the Home Assistant side of things, but have not been able to get it to work.
The information I have indicates that maybe the unique_id may not be populated, but I have found little information to confirm this.
The light works, it shows up as an entity, it just never shows in Integrations.
Can you assist further?

Sorry to throw another one at you for the Discovery.

It turns out one more option is needed for it to show as an entity and allow an "Area" to be assigned in integrations.

This needs to be added to the DISCOVERY_BASE directly after unique_id

\"device\":{\"identifiers\":\"" DEVICE_NAME "\",\"model\":\"generic\",\"manufacturer\":\"PinkyWafer\",\"name\":\"" DEVICE_NAME "\"},

That's what I used, obviously can use whatever you like to describe it. Most settings are optional, but it needs at minimum device: identifiers to show.

I was wondering why TASMOTA showed more details in it , so I had a look at the MQTT discovery topic from tasmota and found the device information.
I got the information from https://www.home-assistant.io/components/light.mqtt/

Thanks :)

Edit: the Model and the Manufacturer show in the Integration page.

Based on a request from DrZzs,
Allow use of rotary encoder to adjust brightness and animation speed
Could also be used for effect and color

hi, every time i try and compile i get this error
ESPAsyncE131.h:23:25: fatal error: ESPAsyncUDP.h: No such file or directory

#include <ESPAsyncUDP.h>
I have included the ESPAsynchE131 library v1 as shown but it wants to reference this file which isnt in the library. Using all the libraries as suggested.
thanks,

Here's the Weekly Digest for pinkywafer/PinkyLEDs:

ISSUES

Last week, no issues were created.

PULL REQUESTS

Last week, no pull requests were created, updated or merged.

COMMITS

Last week there were no commits.

CONTRIBUTORS

Last week there were no contributors.

STARGAZERS

Last week there were no stargazers.

RELEASES

Last week there were no releases.

That's all for last week, please 👀 Watch and ⭐ Star the repository pinkywafer/PinkyLEDs to receive next weekly updates. 😃

You can also view all Weekly Digests by clicking here.

Your Weekly Digest bot. 📆

Hi again!

The NodeMCU keeps rebooting, and after discussing it on DrZzs stream (His dreamlight has the same issue) we think its running out of memory and rebooting. Any ideas why or a solution? My knowledge comes to short here. As a temporary fix i commented out the boot connection flashing temporarily so its not flashing lights once an hour, so its not really a problem anymore. Just thought you should know that the problem exists:)