Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WS2811 #857

Closed
Gary202 opened this issue Sep 11, 2017 · 31 comments
Closed

WS2811 #857

Gary202 opened this issue Sep 11, 2017 · 31 comments
Labels
awaiting feedback Action - Waiting for response or more information question Type - Asking for Information

Comments

@Gary202
Copy link

Gary202 commented Sep 11, 2017

Will WS2811 led strips work with the WS2812 selection?

@chepa92
Copy link

chepa92 commented Sep 12, 2017

I'm trying to get it work, no luck.
I'm not a programmer :)

@arendst
Copy link
Owner

arendst commented Sep 12, 2017

It probably won't work as the timing is different between WS2811 and WS2812.

Perhaps you find more info on the NeoPixelBus library forum used in Tasmota and provides the WS2812 drivers.

@joecotton
Copy link

Likely the only difference is how the NeoPixelBus object is instantiated. The xdrv_ws2812.ino file, lines 27-39. Try changing Neo800KbpsMethod with Neo400KbpsMethod

@chepa92
Copy link

chepa92 commented Sep 12, 2017

That what I did, not working
NeoEsp8266BitBang400KbpsMethod and Neo400KbpsMethod

@chepa92
Copy link

chepa92 commented Sep 12, 2017

Maybe problem in low voltage?

@chepa92
Copy link

chepa92 commented Sep 12, 2017

I've added 4.7k on the gpio14 can this be a problem?

@Adminius
Copy link

try to use GPIO3

@chepa92
Copy link

chepa92 commented Sep 14, 2017

not working, same reaction

@Adminius
Copy link

are they are working without Tasmota? e.g. with NeoPixelBus test sketch only?

@chepa92
Copy link

chepa92 commented Sep 14, 2017

Didn't tested on sonoff, on arduino mini its working well

@Adminius
Copy link

328p is not ESP8266 ;)

  1. Try it on any 3.3V Arduino
  2. Try it on any ESP8266
  3. Try it with another Lib (e.g. Adafruit NeoPixel)
  4. Different modes: DMA, UART, Bitbang...

@skatun
Copy link

skatun commented Nov 16, 2017

Did anyone get it to work?

@chepa92
Copy link

chepa92 commented Nov 16, 2017 via email

@eogmau
Copy link

eogmau commented Jan 28, 2018

see here how I have them working on tasmota
#1690

Edit: fixed link

@stale
Copy link

stale bot commented May 28, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale Action - Issue left behind - Used by the BOT to call for attention label May 28, 2018
@ghost
Copy link

ghost commented Jun 5, 2018

Anyone else having issues with WS2811? This is a circuit diagram and parts list of my setup. I'm wondering if I can use Tasmota in my setup rather than the code in his example:
https://github.com/bruhautomation/ESP-MQTT-JSON-Digital-LEDs

Colours don't work, dimming isn't working. Other sketches like the one in GitHub work fine.

Edit: I wonder, I am using a Wemos D1 Mini & Pro which have 80mhz, specs are here:
https://wiki.wemos.cc/products:d1:d1_mini#technical_specs
Is this a timing issue?

@stale stale bot removed the stale Action - Issue left behind - Used by the BOT to call for attention label Jun 5, 2018
@ascillato
Copy link
Contributor

Hi, please, could you test the solution on #1690 ?
Thanks

@ghost
Copy link

ghost commented Jun 5, 2018

Also is there any reason why fast LED isn't included in Tasmota? It would be a great addition and I've seen it used in a few other uses and seems to have good compatibility

@arendst
Copy link
Owner

arendst commented Jun 5, 2018

Life is all about choices. Shall I buy a car or would a bicycle do too? I choose for the bicycle as it gets me there too.

@ghost
Copy link

ghost commented Jun 9, 2018

So yes, I tested the changes in:

#1690

Of editing user_config.h and no change.

The issue seems to be related to communication rather than a mix up of RGB colours.

Shall I open a separate bug report ? It does relate to WS2811 12v strip though, wired up like:

https://github.com/bruhautomation/ESP-MQTT-JSON-Digital-LEDs/blob/master/ESP%20MQTT%20Digital%20LEDs%20Wiring%20Diagram.png

@stale
Copy link

stale bot commented Jul 24, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale Action - Issue left behind - Used by the BOT to call for attention label Jul 24, 2018
@skatun
Copy link

skatun commented Aug 6, 2018

I got it to work without any modifications on a wemos mini, however colors are wrong, rbg, which seems to be standard for ws2811, either fix it in ur sketch or handle it in the smart home software. I did mention for @arendst that we maybe should add ws2811 as a sensor option where the colors are swapped compared to ws2812..

@stale stale bot removed the stale Action - Issue left behind - Used by the BOT to call for attention label Aug 6, 2018
@ascillato2
Copy link
Collaborator

Hi,

@skatun

You said that colors are swapped but you did not specify which ones?

@ascillato2 ascillato2 added question Type - Asking for Information awaiting feedback Action - Waiting for response or more information labels Sep 4, 2018
@ascillato2
Copy link
Collaborator

Hi,

@skatun

Can you share your configuration and your results?

@ascillato2
Copy link
Collaborator

Hi,

Closing issue as there is no feedback. Please, when you have time, share your findings. Thanks.

@skatun
Copy link

skatun commented Sep 11, 2018

@ascillato and @arendst , sorry I was away for the last 2 weeks. So I have tested with 4 different suppliers of ws2811 ledstrips and they all seems to be rbg coded in comparison to ws2812 that the user can select from the drop down menu, so my suggestion was to add ws2811 to the drop down menu. Can you point me out how to do this? The code that I use to fix this currently is:

Which then is defined in the user config as
#define USE_WS2812_CTYPE NEO_RBG // WS2812 Color type (NEO_RGB, NEO_GRB, NEO_BRG, NEO_RBG, NEO_RGBW, NEO_GRBW)

But I would like to have it defined through the tasmota webpage, because if I autoupdate the software this manual setting will be lost. It is also easier for beginners, because then they dont have to fiddle around with the arduino code..

@arendst
Copy link
Owner

arendst commented Sep 11, 2018

Won't work as the NeoPixelBus library inits it's space and Color type during compile time.

@skatun
Copy link

skatun commented Sep 11, 2018

@arendst How did you do it for the ws2812 type that you can select then? Why would ws2811 be different from the same approach? Maybe I am missing something

@arendst
Copy link
Owner

arendst commented Sep 11, 2018

For the WS2812 you will have to re-compile if you need another RGB sequence.

@skatun
Copy link

skatun commented Sep 11, 2018

@arendst For the WS2812 you will have to re-compile if you need another RGB sequence.
This is exactly what I ment for WS2812 the sequence is RGB, for WS2811 the sequence is RBG, so if we add this option to the drop down meny we have two hardcoded strips that will cover 90% of all strips on the market. For those using the rest 10% we will leave it as it is today.. Or add optional configuration as you do have for some of the other sensors

@arendst arendst mentioned this issue Nov 5, 2018
@skatun
Copy link

skatun commented Nov 5, 2018

I am not a programmer expert, but why is it not possible to copy the ws2812 sketch to ws2811 and change that one line to #define USE_WS2811_CTYPE NEO_RBG, can you please clearify why that is not possible?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting feedback Action - Waiting for response or more information question Type - Asking for Information
Projects
None yet
Development

No branches or pull requests

9 participants