Closed ozett closed 2 years ago
if i use DMA-Method, i get erros while compiling for my wemos mini d1 with the espeasymega source.
#define METHOD NeoEsp8266Uart800KbpsMethod //GPIO2 - use NeoEsp8266Dma800KbpsMethod for GPIO3(TX)
//#define METHOD NeoEsp8266Dma800KbpsMethod //GPIO3(TX)
is it a hardware issue, or something with the plugin-code? any hint to investigate?
the error-messages suggest me to disable plugin 008, and than 003...there are conflicts. (maybe i can use the uart-method, but the pixel did not light up on my first try)
(it works, as long as i use the P042 neopixel candle, which has this hardware-definition:
Candle_pixels = new Adafruit_NeoPixel(NUM_PIXEL, Settings.TaskDevicePin1[event->TaskIndex], NEO_GRB + NEO_KHZ800
)
i will read more about pins and methods and try something out: https://github.com/Makuna/NeoPixelBus/wiki/ESP8266-NeoMethods#neoesp8266dma800kbpsmethod
the pixel are off by default, default method worked, i read a little in the fhem thread. this one helped me: https://forum.fhem.de/index.php/topic,73949.msg755779.html#msg755779 it says: go to "tools" on espeasy and send the command: nfx kitt ff0000
it worked. this encouraged me to try to send this via mqtt... i will report
MQTT worked! 😸 👍
/usr/bin/mosquitto_pub -t ESP/014_test_led/cmd -m "nfx kitt ff0000"
very helpful to use rules to get the stripes lighing up on boot:
https://forum.fhem.de/index.php/topic,73949.msg773128.html#msg773128
On System#Boot do
nfx,rainbow,3
endon
is the gpio hard-coded? is there an option to change this (in actual espeasy-builds, maybe)