P141 RGB Strip Plugin

Message

r_255 · #21 Post by **r_255** » 10 Mar 2018, 17:28

I think this should be a espeasy issue...

As a plugin could be used twice on a esp. Like neopixel strips and 12v leds on one h801
Best would be like to address them on Task#.

Something like http://192.168.1.109/control?cmd1=Mode,4,400

where cmd1 - cmd12 is one of the task# in the devices list, but thats just my 2 cents.

TD-er · #22 Post by **TD-er** » 10 Mar 2018, 18:52

Beter use the name given to the task.
That's already the convention for addressing the sensor values (e.g. [bedroom#temp] )

soif · #23 Post by **soif** » 11 Mar 2018, 21:45

r_255 wrote: ↑10 Mar 2018, 13:29More than happy to supply you with rgbw stipe/2812b so you get a little bit more back than a feed ( no obligations ), or we wait till the esp64 gets released....

At first I just don't clearly understand why such rgbW or (even rgbWW strip exists ? Is this just to have deeper whites (cold or warm?).

Is it just something like :

Code: Select all

if Requested_RGB_color==FF.FF.FF then RGBWW_Output=00.00.00.FF.FF

soif · #24 Post by **soif** » 11 Mar 2018, 21:47

r_255 wrote: ↑10 Mar 2018, 17:28 Something like http://192.168.1.109/control?cmd1=Mode,4,400

It doesn't sounds that bad...

soif · #25 Post by **soif** » 11 Mar 2018, 21:51

papperone wrote: ↑10 Mar 2018, 14:37 I do believe each plugin should make his own specific command clearly understandable... In this case "ON" or "OFF" are not clear to which plugin they are sent to and other developpers can easily use the same for complete different purpouses.

I absolutely agree with you, but without any command naming guidelines, and being at this stage only in the Playground repo, I've just named it as simple as possible. Onces told exactly how to name it, modifying the command names in the codes will be a matter of minutes if not seconds.

soif · #26 Post by **soif** » 11 Mar 2018, 21:53

TD-er wrote: ↑10 Mar 2018, 18:52 Beter use the name given to the task.
That's already the convention for addressing the sensor values (e.g. [bedroom#temp] )

Not sure to cleary understand what you mean

(there are more commands than task values in this case)

r_255 · #27 Post by **r_255** » 11 Mar 2018, 22:49

soif wrote: ↑11 Mar 2018, 21:53
TD-er wrote: ↑10 Mar 2018, 18:52 Beter use the name given to the task.
That's already the convention for addressing the sensor values (e.g. [bedroom#temp] )
Not sure to cleary understand what you mean
(there are more commands than task values in this case)

Instead of task number he means task name, like its used for rules and mqtt... i guess to be strict.

soif wrote: ↑11 Mar 2018, 21:45
r_255 wrote: ↑10 Mar 2018, 13:29More than happy to supply you with rgbw stipe/2812b so you get a little bit more back than a feed ( no obligations ), or we wait till the esp64 gets released....
At first I just don't clearly understand why such rgbW or (even rgbWW strip exists ? Is this just to have deeper whites (cold or warm?).

Is it just something like :
Code: Select all
if Requested_RGB_color==FF.FF.FF then RGBWW_Output=00.00.00.FF.FF

I use it for normal lighting or "party" lighting myself. So its not that its used to mix them but just to have a choice between a or b or mix a and b.
i know people that drive 5 white led stripes on a h801. Just because its possible and damned cheap.

As designer i do a lot of things with color, and i must say pastel a like colors look better with white mixed in and like my hue lamps the choice between warm and cold white is very nice to have....
But most of all, i dont see much color balanced rgb leds that do give a proper white light.

But thanks for the pointer, i will have another look....

papperone · #28 Post by **papperone** » 12 Mar 2018, 07:20

r_255 wrote: ↑10 Mar 2018, 17:28 I think this should be a espeasy issue...

As a plugin could be used twice on a esp. Like neopixel strips and 12v leds on one h801
Best would be like to address them on Task#.

Something like http://192.168.1.109/control?cmd1=Mode,4,400

where cmd1 - cmd12 is one of the task# in the devices list, but thats just my 2 cents.

I don't think is is the right approach and neither easy to implement due to the current structure of plugin calls...

r_255 · #29 Post by **r_255** » 12 Mar 2018, 07:58

Well this might be a dirty solution then.

http://192.168.1.109/control?cmd=1Mode,4,400

Nah just kidding,
But it might be something for future releases to fix this on espeasy level. As with more gpio's on the horizon, people will have more device connected and commands could easy overlap.

Ill pwm my white channels till i found some time and knowledge to change the code.
It's not a issue.

sisamiwe · #30 Post by **sisamiwe** » 24 Mar 2018, 17:44

Hi,

just a question to that plugin: Does it send the values for example HSV automatically to the defined controller on value change?

Thanks for the response.

soif · #31 Post by **soif** » 30 Mar 2018, 19:16

Not automatically, but HSV value are saved in the corresponding variables, so a simple rule, could do the job easily.

rwest · #32 Post by **rwest** » 16 Apr 2018, 13:01

just found your code and the idea is nice.

still have to test it but i already came up with an brigtness + / - command sample:

Command Examples :
- /control?cmd=dim_up
Steps brightness + 10
- /control?cmd=dim_up,x
Steps brightness + x
- /control?cmd=dim_up,3
Steps brightness + 3

Code: Select all

      //Brightness +
if (command == F("dim_up"))	{
	int dimstep = event->Par1 ? event->Par1 : 10 ;
        v_p141_cur_color.v 	= v_p141_cur_color.v + dimstep ;	 //Value/Brightness
        if(v_p141_cur_color.v > 100){
		v_p141_cur_color.v 	= 100;
	}
	else if(v_p141_cur_color.v < 0){
		v_p141_cur_color.v 	= 0;
	}
	Fp141_SetCurrentColor(v_p141_cur_color);
	Fp141_OutputCurrentColor();
}
      
      //Brightness -
if (command == F("dim_down"))	{
	int dimstep = event->Par1 ? event->Par1 : 10 ;
        v_p141_cur_color.v 	= v_p141_cur_color.v - dimstep ;	 //Value/Brightness
        if(v_p141_cur_color.v > 100){
		v_p141_cur_color.v 	= 100;
	}
	else if(v_p141_cur_color.v < 0){
		v_p141_cur_color.v 	= 0;
	}
	Fp141_SetCurrentColor(v_p141_cur_color);
	Fp141_OutputCurrentColor();
}

be aware this code is untested. i have to start with platformIO

im interested in fade/transition to ON and fade/transition to OFF and maybe there is a quick addition of controlling setting fade/transition for CW/WW single PWM/color led strip.
And i just recieved an Arilux / magic home with IR.

if i'll get it working i'll make an OpenHAB2 config example with the use of MQTT

budman1758 · #33 Post by **budman1758** » 15 May 2018, 23:37

Hello Soif. Is there any chance you could make a bin file with this plugin available? I have the H801 controller. My compile skills are still not quite ready for primetime.

Would really like to try this. Thanks in advance.

dolittle · #34 Post by **dolittle** » 12 Jun 2018, 06:58

r_255 wrote: ↑28 Feb 2018, 21:09 ...
C:\Users\robin\Documents\Arduino\src\ESPEasy\_P141_LedStrip.ino: In function 'boolean Plugin_141(byte, EventStruct*, String&)':
_P141_LedStrip:332: error: 'addFormSelector' was not declared in this scope
addFormSelector(string, F("LedStrip Type"), PLUGIN_141_CONF_0, i , options, optionValues, NULL ,type, true );

I did add the recommended fastled lib, added the include in espeasy.ino etc...
Should i declare all missing by hand or is there some other pointer you could think of ?

Hi Soif,
I'd like to use and compile the plugin with a current version of ESPEasy and I'm getting a lot of errors similar to the one noted above. Is it possible that you correct the plugin? I'm compiling it with your EspBuddy.

This would be really great.

Thanks ver much
>dolittle

choriz · #35 Post by **choriz** » 12 Jun 2018, 15:36

Hi Soif,

I have successful compile your code with platformIO and espeasy 2.0, but i 'm new to this and i have simple ( maybe stupid sorry) questions :

- I have magichome with ESP8285MOD, coud i use with this version ?

- If yes i have issue with compilation size for ESP8285 (Error: The program size (478829 bytes) is greater than maximum allowed (434160 bytes)),

do you have a solution for that ?

Regards

dolittle · #36 Post by **dolittle** » 27 Jun 2018, 08:21

Hi soif,
I was able to compile the plugin with the current version and posted a pull request. Nevertheless it turns out that your plugin somehow disables the rules functions TaskValSet and Publish <topic>, <value>. Is it possible for you to have a look on this? I like the plugin but these issues make it a no-go.

And btw, it would be very cool if the plugin could support transition fading e.g. when changing colors.

Thanks

Johny Mielony · #37 Post by **Johny Mielony** » 23 Jul 2018, 15:21

Did anyone manage to compile this plugin with the latest version of EspEasy Mega? If not, what's the latest version that this plugin works with?

dolittle · #38 Post by **dolittle** » 23 Jul 2018, 16:33

Johny Mielony wrote: ↑23 Jul 2018, 15:21 Did anyone manage to compile this plugin with the latest version of EspEasy Mega? If not, what's the latest version that this plugin works with?

Hi. There's a pending pull request in the Github repo (Commit #13ab228). Does it compile if you use this version of the plugin?

Johny Mielony · #39 Post by **Johny Mielony** » 24 Jul 2018, 11:16

dolittle wrote: ↑23 Jul 2018, 16:33
Johny Mielony wrote: ↑23 Jul 2018, 15:21 Did anyone manage to compile this plugin with the latest version of EspEasy Mega? If not, what's the latest version that this plugin works with?
Hi. There's a pending pull request in the Github repo (Commit #13ab228). Does it compile if you use this version of the plugin?

So I must've been using some earlier commit. Now with this one I don't get error related to 'addFormSelector' and other like that.
There are only left those errors:

Code: Select all

.pioenvs\normal_ESP8266_1024\libb3e\SoftwareSerial\SoftwareSerial.cpp.o: In function `sws_isr_0()':
SoftwareSerial.cpp:(.iram.text+0xf8): multiple definition of `sws_isr_0()'

.pioenvs\normal_ESP8266_1024\libb96\ESPEasySoftwareSerial\ESPeasySoftwareSerial.cpp.o:ESPeasySoftwareSerial.cpp:(.iram.text+0xd4): first defined here
.pioenvs\normal_ESP8266_1024\libb3e\SoftwareSerial\SoftwareSerial.cpp.o: In function `sws_isr_1()':
SoftwareSerial.cpp:(.iram.text+0x110): multiple definition of `sws_isr_1()'
.pioenvs\normal_ESP8266_1024\libb96\ESPEasySoftwareSerial\ESPeasySoftwareSerial.cpp.o:ESPeasySoftwareSerial.cpp:(.iram.text+0xec): first defined here
.pioenvs\normal_ESP8266_1024\libb3e\SoftwareSerial\SoftwareSerial.cpp.o: In function `sws_isr_2()':
SoftwareSerial.cpp:(.iram.text+0x128): multiple definition of `sws_isr_2()'
.pioenvs\normal_ESP8266_1024\libb96\ESPEasySoftwareSerial\ESPeasySoftwareSerial.cpp.o:ESPeasySoftwareSerial.cpp:(.iram.text+0x104): first defined here

I can get rid of those errors just by commenting out any occurrence of sws_isr in ESPeasySoftwareSerial.cpp, but that's just workaround, not a solution.

sledge · #40 Post by **sledge** » 11 Aug 2018, 15:17

Hi, i tried to compile the p141 plugin under actual mega branch and get a lot of errors.

Code: Select all

Linking .pioenvs\dev_ESP8266_4096\firmware.elf
.pioenvs\dev_ESP8266_4096\libe12\SoftwareSerial\SoftwareSerial.cpp.o: In function `sws_isr_0()':
SoftwareSerial.cpp:(.iram.text+0xf8): multiple definition of `sws_isr_0()'
.pioenvs\dev_ESP8266_4096\lib7f4\ESPEasySoftwareSerial\ESPeasySoftwareSerial.cpp.o:ESPeasySoftwareSerial.cpp:(.iram.text+0xd4): first defined here
.pioenvs\dev_ESP8266_4096\libe12\SoftwareSerial\SoftwareSerial.cpp.o: In function `sws_isr_1()':
SoftwareSerial.cpp:(.iram.text+0x110): multiple definition of `sws_isr_1()'
.pioenvs\dev_ESP8266_4096\lib7f4\ESPEasySoftwareSerial\ESPeasySoftwareSerial.cpp.o:ESPeasySoftwareSerial.cpp:(.iram.text+0xec): first defined here
.pioenvs\dev_ESP8266_4096\libe12\SoftwareSerial\SoftwareSerial.cpp.o: In function `sws_isr_2()':
SoftwareSerial.cpp:(.iram.text+0x128): multiple definition of `sws_isr_2()'
.pioenvs\dev_ESP8266_4096\lib7f4\ESPEasySoftwareSerial\ESPeasySoftwareSerial.cpp.o:ESPeasySoftwareSerial.cpp:(.iram.text+0x104): first defined here
collect2.exe: error: ld returned 1 exit status
*** [.pioenvs\dev_ESP8266_4096\firmware.elf] Error 1

Does this plugin work for the actual Mega branch or do i have to use an older version?

TD-er · #41 Post by **TD-er** » 12 Aug 2018, 12:31

I don't see anything related to SoftwareSerial in the code of P141.
But it is including Fastled.h, so maybe that one is trying to assign some interrupt triggers to some pins.
This may cause issues. I guess.
These function call SoftwareSerial instead of ESPEasySoftwareSerial: https://github.com/letscontrolit/ESPEas ... wareSerial
Have you added other files, other than the P141 file?

sledge · #42 Post by **sledge** » 12 Aug 2018, 18:16

I only added p141 and the fastled lib. It works if i comment out sws_isr_0() like mentioned by johny Mielony. BUT now i am not able to send a pwm command to a specified pin. My problem is that i am using a rgb-W power led and am not able to set white to a value. Only RGB through p141 is working. Is there a way to change white whithin the plugin? I set the led strip type to rgbw and mapped white1 to pin5 but i can´t see a command to switch white on.

BTW the plugin is awesome!

sledge · #43 Post by **sledge** » 15 Aug 2018, 16:10

Would it be possible to add a command to the plugin just to set a value for white? Something like this maybe:

Code: Select all

			if (command == F("w1"))	{
				analogWrite(v_p141_pins[3], v_p141_pin_inverse ? (PWMRANGE - event->Par1)  : event->Par1);
			}

I´m not familiar with C so i don´t know how to add another command.

sledge · #44 Post by **sledge** » 19 Aug 2018, 15:03

How funny, the code i posted above is working

Now i can control the white channel with mqtt command w1,255

I also added this line to void Fp141_CommandOff(){ function to ensure everything is off after command receives.

Code: Select all

analogWrite(v_p141_pins[3], v_p141_pin_inverse ? (PWMRANGE - 0)  : 0);

I know this is not intended by the plugin author but until the white channel is added it is useful for me and maybe an other.

coolduke · #45 Post by **coolduke** » 03 Sep 2018, 15:17

hi,

first of all, thx to the author for coding this plugin... I think it would be huge improvment for the whole project.

But I was not able to compile it successfully... got the following errors (compiled with platform IO):

Archiving .pioenvs/dev_ESP8266_1024/libFrameworkArduino.a
Indexing .pioenvs/dev_ESP8266_1024/libFrameworkArduino.a
Linking .pioenvs/dev_ESP8266_1024/firmware.elf
.pioenvs/dev_ESP8266_1024/lib52c/SoftwareSerial/SoftwareSerial.cpp.o: In function `sws_isr_0()':
SoftwareSerial.cpp:(.iram.text+0xf8): multiple definition of `sws_isr_0()'
.pioenvs/dev_ESP8266_1024/libc24/ESPEasySoftwareSerial/ESPeasySoftwareSerial.cpp.o:ESPeasySoftwareSerial.cpp:(.iram.text+0xd4): first defined here
.pioenvs/dev_ESP8266_1024/lib52c/SoftwareSerial/SoftwareSerial.cpp.o: In function `sws_isr_1()':
SoftwareSerial.cpp:(.iram.text+0x110): multiple definition of `sws_isr_1()'
.pioenvs/dev_ESP8266_1024/libc24/ESPEasySoftwareSerial/ESPeasySoftwareSerial.cpp.o:ESPeasySoftwareSerial.cpp:(.iram.text+0xec): first defined here
.pioenvs/dev_ESP8266_1024/lib52c/SoftwareSerial/SoftwareSerial.cpp.o: In function `sws_isr_2()':
SoftwareSerial.cpp:(.iram.text+0x128): multiple definition of `sws_isr_2()'
.pioenvs/dev_ESP8266_1024/libc24/ESPEasySoftwareSerial/ESPeasySoftwareSerial.cpp.o:ESPeasySoftwareSerial.cpp:(.iram.text+0x104): first defined here
collect2: error: ld returned 1 exit status
*** [.pioenvs/dev_ESP8266_1024/firmware.elf] Error 1

seems like there is still this problem with "sws_isr_0()"... but how to solve it?

when could we see this plugin in the "official" dev branch?

any help would be great!

thx

coolduke · #46 Post by **coolduke** » 12 Sep 2018, 09:25

.. using arduino IDE everyhting works fine

Tecumseh · #47 Post by **Tecumseh** » 27 Sep 2018, 21:05

Johny Mielony wrote: ↑24 Jul 2018, 11:16

Code: Select all

.pioenvs\normal_ESP8266_1024\libb3e\SoftwareSerial\SoftwareSerial.cpp.o: In function `sws_isr_0()':
SoftwareSerial.cpp:(.iram.text+0xf8): multiple definition of `sws_isr_0()'

.pioenvs\normal_ESP8266_1024\libb96\ESPEasySoftwareSerial\ESPeasySoftwareSerial.cpp.o:ESPeasySoftwareSerial.cpp:(.iram.text+0xd4): first defined here
.pioenvs\normal_ESP8266_1024\libb3e\SoftwareSerial\SoftwareSerial.cpp.o: In function `sws_isr_1()':
SoftwareSerial.cpp:(.iram.text+0x110): multiple definition of `sws_isr_1()'
.pioenvs\normal_ESP8266_1024\libb96\ESPEasySoftwareSerial\ESPeasySoftwareSerial.cpp.o:ESPeasySoftwareSerial.cpp:(.iram.text+0xec): first defined here
.pioenvs\normal_ESP8266_1024\libb3e\SoftwareSerial\SoftwareSerial.cpp.o: In function `sws_isr_2()':
SoftwareSerial.cpp:(.iram.text+0x128): multiple definition of `sws_isr_2()'
.pioenvs\normal_ESP8266_1024\libb96\ESPEasySoftwareSerial\ESPeasySoftwareSerial.cpp.o:ESPeasySoftwareSerial.cpp:(.iram.text+0x104): first defined here

I can get rid of those errors just by commenting out any occurrence of sws_isr in ESPeasySoftwareSerial.cpp, but that's just workaround, not a solution.

With the sws_isr commented in ESPeasySoftwareSerial.cpp I got it compiled and running. It is a very nice full featured RGB control. One thing that I am missing is the option to select a color and fade it in during a selectable time. This option is available in the lights plugin (https://github.com/ddtlabs/ESPEasy-Plugin-Lights), this one has not seen an update in the last 2 years so I am not sure if it would compile well with the latest version.

Dines · #48 Post by **Dines** » 10 Oct 2018, 23:59

Hi,

Can anyone share a .bin file with this RGB plugin for Wimos D1 mini?

budman1758 · #49 Post by **budman1758** » 11 Oct 2018, 00:11

+ 1 for ^. Standard 4 meg here.

TD-er · #50 Post by **TD-er** » 11 Oct 2018, 02:05

I added an issue for it on Github: https://github.com/letscontrolit/ESPEasy/issues/1889

Dylantje · #51 Post by **Dylantje** » 14 Oct 2018, 11:56

Dear all,

Is this project stil a live??
Is ther peperhaps a option this controller works with Domoticz?

i am searching for a H081 controller that i can use in Domoticz..
Or is this the wrong project?

dolittle · #52 Post by **dolittle** » 14 Oct 2018, 12:13

Dylantje wrote: ↑14 Oct 2018, 11:56 Dear all,

Is this project stil a live??
Is ther peperhaps a option this controller works with Domoticz?

i am searching for a H081 controller that i can use in Domoticz..
Or is this the wrong project?

Is it an option for you to use an MQTT server like mosquitto? It's pretty simple and you can use also other firmwares like tasmota or espurna as well.

I don't use and know Domoticz, but I suppose it has MQTT support as well.

Dylantje · #53 Post by **Dylantje** » 14 Oct 2018, 12:17

i have a mqtt server running in Domoticz..
I flashed a esp with espeasy
And i do have a esp with Thasmota.

Only my knowledge with mqtt is very low

dolittle · #54 Post by **dolittle** » 14 Oct 2018, 15:19

Dylantje wrote: ↑14 Oct 2018, 12:17 i have a mqtt server running in Domoticz..
I flashed a esp with espeasy
And i do have a esp with Thasmota.

Only my knowledge with mqtt is very low

I had also some doubts but love it now. It‘s pretty easy actually. The concept is just different.

Give it a try you won’t regret it.

ManS-H · #55 Post by **ManS-H** » 21 Oct 2018, 12:16

What do i wrong with compiling _P141?
When i compile ESPEasy_mega-20181017 with Platformio no problem at all.

But when I add _P141 to the map source/src and FastLED-3.1.8 to to map source/lib
Then i add #include "<FastLED.h>" to ESPEasy.ino is see this:
F:/ESPEasy Projects/ESPEasy_mega-20181017_P141/Source/scr/ESPEASY.ino:8923: fatal error scr\<FastLED.h>: Invalid argument

When i changed it in #include <FastLED.h> to ESPEasy.ino is see this:
collect2.exe: error: ld returned 1 exit status
*** [.pioenvs\dev_ESP8266_1024\firmware.elf] Error 1

When i changed it in #include "FastLED.h" to ESPEasy.ino is see this:
collect2.exe error: ld returned 1 exit status
*** [.pioenvs\dev_ESP8266_1024\firmware.elf] Error 1

If I follow the text of the developer, he used another directory structure.
Installation :
- Add the FastLED library in the 'src/lib/' folder from https://github.com/FastLED/FastLED/tree/3.1.8
- Move this file to the 'src/' folder
- Add "#include <FastLED.h>" at the start of src/lib/ESPEasy.ino file else compiler fails

Please, can anyone tell me what i doing wrong?

TD-er · #56 Post by **TD-er** » 22 Oct 2018, 10:21

For PlatformIO there is a separate lib directory at the same level as the src dir.
See directory structure here: https://github.com/letscontrolit/ESPEasy

ManS-H · #57 Post by **ManS-H** » 23 Oct 2018, 12:35

TD-er wrote: ↑22 Oct 2018, 10:21 For PlatformIO there is a separate lib directory at the same level as the src dir.
See directory structure here: https://github.com/letscontrolit/ESPEasy

Hello TD-er,

I'm not a programmer, only a simple user who was interrested in the possibilities of the _P141 Plugin together with a Huacanxing H801

This is the structure of testing the plugins,

: Structure.png (32.01 KiB) Viewed 13652 times

I started on another computer with Platformio as descriped in de Wiki. I used ESPEasy_mega-20181023 as file.
First i compiled ESPEasy_mega-20181023, no problem with the normal-test-dev_ESP8266 versions.

Then i add _P141, with the library FastLED-3.1.8 and #include <FastLED.h> to ESPEasy_mega-20181023.
Problems:
collect2.exe: error: ld returned 1 exit status
*** [.pioenvs\normal_ESP8266_1024\firmware.elf] Error 1

I started again this time with _P142 and ESPEasy_mega-20181023.
Problems:
F:/ESPEasy Projects/ESPEasy_mega-20181023_P142/Source_P142/src/_P142_RGB-Strip.ino:88:107: error: invalid conversion from 'const char*' to 'int' [-fpermissive]
F:/ESPEasy Projects/ESPEasy_mega-20181023_P142/Source_P142/src/_P142_RGB-Strip.ino:88:107: error: too many arguments to function 'void addPinSelect(boolean, String, int)'
F:/ESPEasy Projects/ESPEasy_mega-20181023_P142/Source_P142/src/_P142_RGB-Strip.ino:90:107: error: invalid conversion from 'const char*' to 'int' [-fpermissive]
F:/ESPEasy Projects/ESPEasy_mega-20181023_P142/Source_P142/src/_P142_RGB-Strip.ino:90:107: error: too many arguments to function 'void addPinSelect(boolean, String, int)'
F:/ESPEasy Projects/ESPEasy_mega-20181023_P142/Source_P142/src/_P142_RGB-Strip.ino:92:107: error: invalid conversion from 'const char*' to 'int' [-fpermissive]
F:/ESPEasy Projects/ESPEasy_mega-20181023_P142/Source_P142/src/_P142_RGB-Strip.ino:92:107: error: too many arguments to function 'void addPinSelect(boolean, String, int)'
F:/ESPEasy Projects/ESPEasy_mega-20181023_P142/Source_P142/src/_P142_RGB-Strip.ino:94:107: error: invalid conversion from 'const char*' to 'int' [-fpermissive]
F:/ESPEasy Projects/ESPEasy_mega-20181023_P142/Source_P142/src/_P142_RGB-Strip.ino:94:107: error: too many arguments to function 'void addPinSelect(boolean, String, int)'

The third try, _P150 and ESPEasy_mega-20181023.
Problems:
Environment dev_ESP8266_1024 [ERROR]
Environment dev_ESP8266_4096 [ERROR]

These are successfull:
Environment normal_ESP8266_1024 [SUCCESS]
Environment normal_ESP8266_4096 [SUCCESS]
Environment test_ESP8266_1024 [SUCCESS]
Environment test_ESP8266_4096 [SUCCESS]

Then i add _P141, with #include <FastLED.h> to ESPEasy_mega-20181023 but without the library.
Problems:
collect2.exe: error: ld returned 1 exit status
*** [.pioenvs\normal_ESP8266_1024\firmware.elf] Error 1

: Aantekening.png (49.42 KiB) Viewed 13653 times

My question to you, can you maybe try to compile the _P141 Plugin to see what the results are in your environment?

Regards, Herman

raist · #58 Post by **raist** » 19 Feb 2019, 09:17

Please provide somebody a .bin file

enesbcs · #59 Post by **enesbcs** » 21 Feb 2019, 19:00

raist wrote: ↑19 Feb 2019, 09:17 Please provide somebody a .bin file

I've such a binary with P142 RGB-Strip, but do not know what is the difference with P141.

4MB version.
download/file.php?id=3594

dolittle · #60 Post by **dolittle** » 22 Feb 2019, 17:13

Hi,
added two bin files with P141. One for 1MB and the other for 4MB flash.

Hope that helps.

BTW. I don't use ESPEasy for LED strips anymore although I love its flexibility. Tasmota has a much better implementation for this IMHO. This plugin flickers a lot in low dimming settings and it has no fading.

ManS-H · #61 Post by **ManS-H** » 22 Feb 2019, 20:50

dolittle wrote: ↑22 Feb 2019, 17:13 Hi,
added two bin files with P141. One for 1MB and the other for 4MB flash.

Hope that helps.

BTW. I don't use ESPEasy for LED strips anymore although I love its flexibility. Tasmota has a much better implementation for this IMHO. This plugin flickers a lot in low dimming settings and it has no fading.

Thanks.

uxhamby · #62 Post by **uxhamby** » 20 Jun 2019, 04:59

ws2811, 12, 12B & 52: "NOT yet implemented". Bummer.

Any ETA on support for those devices?

Thanks,

Brian H.

dolittle · #63 Post by **dolittle** » 20 Jun 2019, 07:13

uxhamby wrote: ↑20 Jun 2019, 04:59 ws2811, 12, 12B & 52: "NOT yet implemented". Bummer.

Any ETA on support for those devices?

Thanks,

Brian H.

Hi,
for me ESPEasy was not the right choice for ws2812 strips. I ended up using WLED for that after some research. It has a web interface and supports a variety of protocols.

I‘ve connected it via MQTT to my openHAB. Works like a charm.

Apart from the technical aspect a lot of effects are supported out of the box. It may be worth having a look.

Who is online