mirror
/
WLED
kopia lustrzana https://github.com/Aircoookie/WLED
1
0
Forkuj 0
Kod Zgłoszenia Packages Projekty Wydania Wiki Aktywność

Updated FAQ (markdown)

master
Aircoookie 2020-06-04 11:25:14 +02:00
rodzic c521546d58
commit b9c54e924d
1 zmienionych plików z 63 dodań i 89 usunięć
Pokaż statystyki Ściągnij plik aktualizacji Ściągnij plik porównania Expand all files Collapse all files

152
FAQ.md

@ -1,110 +1,97 @@
This page will continually get updated with questions often asked.
## Installation
<details>
<summary>What binary should I use?</summary>
### What binary should I use?
Please see [this page](https://github.com/Aircoookie/WLED/wiki/Install-WLED-binary).
</details>
<details>
<summary>I've flashed a bin, but i get no response at all</summary>
### I've flashed a bin, but i get no response at all
Some users report first erasing the flash (yes, even on a new device) sometimes helps .
</details>
## Connection issues
<details>
<summary>Once I attach LEDs, I can't connect to the ESP anymore!</summary>
### Once I attach LEDs, I can't connect to the ESP anymore!
The gpio2/D4 pin needs to be high (pullup) at powerup time for the controller to boot successfully.
If you accidentally connected the strip the wrong way (if it has arrows printed on, make sure they face away from the pin, otherwise pay attention to the DIN printing). Most strips have the 3-pin male JST connector with 3 holes on the input side. Some users have reported troubles booting even with the direction being correct. In that case, please try adding a 3.3 or 4.7kOhms resistor between the data pin and 3v3 pin!
</details>
<details>
<summary>I have entered my WiFi credentials and rebooted, but I can not connect to the module now!</summary>
### I have entered my WiFi credentials and rebooted, but I can not connect to the module now!
If you did not enter a static IP, the module will automatically obtain a dynamic IP from the router.
You can check it in the router configuration or in the settings page, if the Access Point is still enabled.
An easier way is to use the WLED Android app which features automatic discovery!
</details>
<details>
<summary>The module once was connected, but I can no longer reach it.</summary>
### The module once was connected, but I can no longer reach it.
First, make sure you can reach the connected WiFi yourself (with another device).
See if you can connect to the Access Point, then go to **4.3.2.1/reset**.
Else, power-cycle the module manually.
</details>
<details>
<summary>The wled-xxx.local address (mDNS) does not work.</summary>
### The wled-xxx.local address (mDNS) does not work.
This only works with Apple devices out of the box. You can install Bonjour to make it work in Windows.
For Android there is no convenient way to achieve it, though you can use apps like "Bonjour search" to find the IP.
I highly recommend you install the WLED app, which makes automatic discovery easy!
</details>
<details>
<summary>Is it safe to do a port forwarding to the public internet to control the lights from anywhere?</summary>
### Is it safe to do a port forwarding to the public internet to control the lights from anywhere?
See [this](https://github.com/Aircoookie/WLED/wiki/Security) page.
</details>
<details>
<summary>My device is unresponsive or animations lag!</summary>
### My device is unresponsive or animations lag!
You are probably using too many sync interfaces. Please only enable one of Hue sync, MQTT, or Blynk at a time.
For optimal performance, use two devices and sync them via the UDP notifier.
Maybe you are also using a very high amount of LEDs. 750 is the recommended maximum.
</details>
<details>
<summary>I'm having a bootloop! (LEDs turn on every ~5seconds)</summary>
### I'm having a bootloop! (LEDs turn on every ~5seconds)
Please open an issue or message me on Discord to resolve your issue. Most of the time, wiping the flash (Arduino IDE compile setting: Erase flash -> All flash contents) resolves the issue. Unfortunately it will also reset all your settings and presets. You can also try if using a different ESP resolves the issue. If you compiled with lwip version 2, try version 1.4 Higher Bandwidth instead!
</details>
<details>
<summary>Still having connection issues/connection dropping: what more can i check?</summary>
### Still having connection issues/connection dropping: what more can i check?
Try disabling "Emulate Alexa device" in Sync settings before entering your home Wifi credentials.
Check whether mDNS is on or off and toggle it: does it make a difference? Same for 'NTP'. Same for 'Sync Send'. Check your router: is your 2.4Ghz on band 1: if not, try it please. If you have the possibility to try another 8266, please try it.</details>
Check whether mDNS is on or off and toggle it: does it make a difference? Same for 'NTP'. Same for 'Sync Send'. Check your router: is your 2.4Ghz on band 1: if not, try it please. If you have the possibility to try another 8266, please try it.
## Compilation issues
<details>
<summary>When compiling WLED in VS Code using platformio, I get an error.</summary>
### When compiling WLED in VS Code using platformio, I get an error.
Try building again. If the error says the `wled00.ino.cpp` or `.sconsign27.db.dblite` file could not be found, this often helps.
You can also try [this](https://github.com/Aircoookie/WLED/issues/361#issuecomment-557818554)!
</details>
## LED issues
<details>
<summary>My LEDs don't turn on at all.</summary>
### My LEDs don't turn on at all.
Please make sure you have connected the strip to GPIO2 and it is sufficiently powered.
</details>
<details>
<summary>My LEDs don't get as bright as they should!</summary>
### My LEDs don't get as bright as they should!
If the brightness slider in the UI is already at maximum, try checking the auto brightness limiter in the LED settings.
Set the milliamp limit to slightly below the rating of your power supply.
If the LEDs are still too dim or change color towards the end of the strip, there may be a significant voltage drop. Try injecting 5v power at the end or middle of the strip with some appropriate cabling.
</details>
<details>
<summary>When I select green, the LEDs turn red!</summary>
### When I select green, the LEDs turn red!
Depending on the type of LEDs used, Red and Green or other colors might be reversed. You can change the order in LED settings.
WS2812B and most related chips use GRB, WS2811 uses RGB in most cases.
</details>
<details>
<summary>My LEDs act funny and flicker randomly.</summary>
### My LEDs act funny and flicker randomly.
#### Reason 1
If you use an external 5V power supply for your LEDs, please connect the GND of power supply, LEDs, and ESP.
@ -123,10 +110,9 @@ Your data line can only be [so long](https://youtu.be/ZFO_QOBG9Bs?t=657). Try ou
#### Reason 4
If they don't flicker, but display funny colors, try switching between RGB/RGBW modes in LED settings.
</details>
<details>
<summary>Not all my LEDs turn on.</summary>
### Not all my LEDs turn on.
#### Reason 1
By default the LED count is set to 30.
@ -138,39 +124,35 @@ WLED supports up to 1500 individual LEDs right now (recommended maximum is 750 L
#### Reason 2
An LED in your chain may be broken. Try another strip or removing the first LED that doesn't light up. Make sure you are in solid effect mode and the LED count is set high enough first!
</details>
<details>
<summary>How to turn off the bright blue onboard LED?</summary>
### How to turn off the bright blue onboard LED?
This LED can be very distracting. Unfortunately it can't easily be disabled as it shares the gpio2/D4 pin with the LED output. Currently there are 3 workarounds:
- Cover the LED
- Remove the LED permanently (desolder or apply pressure with e.g. a flathead screwdriver)
- Use a different `LEDPIN`, although the default is recommended for stable operation
</details>
<details>
<summary>Why is gpio2/D4 the default LED pin?</summary>
### Why is gpio2/D4 the default LED pin?
Although pins D1 and D2 are usually regarded the best GPIO pins to use in an ESP8266 project, D4 is the default in WLED, despite having two major and one minor drawback. The major drawbacks are the permanently lit blue onboard LEDs and the fact that the pin level needs to be high (pullup) at powerup or the controller will not boot. A minor drawback is that the `Serial1` bus can not be used, but this is irrelevant in most cases, as the USB/serial converter is connected to the other `Serial` interface. The reason for using this pin is that it uses UART hardware driving, which increases stability and decreases CPU overhead especially with larger amounts of pixels.
</details>
<details>
<summary>Why can I only use 500 LEDs on the ESP8266 GPIO pin 3?</summary>
### Why can I only use 500 LEDs on the ESP8266 GPIO pin 3?
The problem is the DMA hardware driving method used on (just) that pin. It works well, but uses **4x (!)** as much RAM memory as the UART hardware driving on pin 2 and the bitbang driver on all other pins.
</details>
## General Questions
<details>
<summary>What does the name WLED mean?</summary>
### What does the name WLED mean?
WiFi Lighting Effects Driver. Also it has LED in the name and is similar to the official term for WiFi, WLAN!
</details>
<details>
<summary>What LED strip hardware is supported by WLED?</summary>
### What LED strip hardware is supported by WLED?
The compatible chipsets for the color-coding are
@ -196,39 +178,31 @@ Beside the **digital addressable** LED stripes the good old **analog** LED strip
- 4 pins: RGB
- 5 pins: RGBW / RGBWW / RGBCW / RGBNW (RGB + one white channel)
- 6 pins: RGBCT (RGB + 2 white channels)
</details>
## My question or solution is not on this page
<details>
<summary>How about checking out the forum?</summary>
### Check out the WLED forum!
You can check out and use [the WLED Discourse forum](https://wled.discourse.group).
</details>
<details>
<summary>Search through the Issues</summary>
### Look through the Issues
Maybe someone already reported your issue, so everybody supplying support would be grateful if you take some time to [search through the existing issues](https://github.com/Aircoookie/WLED/issues).
</details>
<details>
<summary>If I report a new Issue, what do i need to share?</summary>
### If I report a new Issue, what do i need to share?
When you create a ticket, please share:
- your devices
- exact controller, maybe a link to the shop you bought it from
- LED-strip type
- Amount of LEDs
- specifications of your power supply
- LED-strip type and amount of LEDs
- Specifications of your power supply (max. current/voltage)
- how you wired up all components (a diagram and/or picture often helps)
- the BIN-file you tried to flash (version and file name)
- What software and command and config did you try to flash with?
- the BIN-file you tried to flash (version and file name) or your IDE version if compiling from source
- Have you followed the quick start and compile settings at https://github.com/Aircoookie/WLED/wiki ?
- Has it worked before?
- Does it works without any LEDs connected? (for instance the controller just connected to your PC over USB)
- Are you using/trying to use DHCP or static IP?
- Did you try to use a mobile hotspot instead of your WLAN AP/home wifi?
</details>