aircoookie / wled-docs Goto Github PK

Howdy AirCookie!

Great work as always. Just a note/correction that the documents for https://kno.wled.ge/basics/install-binary/#what-binary-should-i-use don't match the available binaries of the latest release - more specifically for users of 1Mb ESP8266 devices, there's new ones for 1Mb, 2Mb etc, but the documents still talk about ESP01 bin file.

Steve

Consider adding page with screenshots / tour of Web UI

I just discovered the new wiki.

Here are a few notes:

1. The link does not work (error 404)
2. Why is this link not clickable?
3. At first it was unclear I had to search with google.
   Searching with these keywords on the espressif site did not help. 😄
   But the link in (2) worked when I copied it correctly. So there was no need for using search in the first place.

afaik the "compiling from source code" page still suggest to change build_envs in platformIO.ini. This is not necessary any more when using VSCode.

• click on the small "folder" icon
• type part of the name you need, then you'll see a drop-down so select from it
• click on the checkmark icon for compiling
• click on the "plug" to start serial monitor
• click on "left arrow" for uploading firmware to your board

I found a typo in the docs (https://kno.wled.ge/advanced/remote-access-ifttt/)

3. Port Forwarding
   [...]
   Use a 5 digit port for better securuty.

In the documentation on playlists through JSON. It appears "transition" is a single value. This would indicate the same transition time is applied to all "shifts" in the playlist. However int the preset file the playlist transition appears to be an array, indicating the possibility to have different transition times between different steps in the playlist. Clarification needed. Also if the later is true, does the transition time in the array correspond to the transition time before or after the playlist step?

Maybe a documentation issue or an issue with https://github.com/arittner/WLED/blob/main/.vscode/tasks.json

The documentation describes, I can run a build (with the checkmark symbol), but the Build is not working for me. VS Code shows only the Command Palette with PlatformIO: Build and I cannot trigger the command. If I remove PlatformIO: , I see this task list:

All three tasks correspond to the tasks.json and only Build: binary only is working. For HTML builds, I need a NPM installation. It would be useful to link to https://kno.wled.ge/advanced/custom-features/#changing-web-ui to give more hints, how to compile with HTML and how to prepare the environment. And maybe also Custom Features with chapter Changing Web UI should be updated.

VS Code: 1.81.1
OS: Windows 11 x64
PlatformIO: v3.3.1

In the Top 5 mistakes page is a pinout diagram for the ESP8266 D1 mini (2nd image).
In there, pin D4 is labled GPIO 3, just like RX pin.
To my knowledge, it is actually GPIO 2.
@wled-faq

a do install the latest verion 13.xx and set it with alexa . if i ask to change color it always return to default color , does the same thing with WLed on ip adress , please help !

https://kno.wled.ge/basics/compatible-hardware/#levelshifters drawings for 74AHCT125 show OE pins connected to +5V but I think they are active low and should be connected directly to ground only.

Would like to configure continuous deployment, so gh-deploy does not need to be called every time a change is committed.

Reference

Would be nice if some kind soul who has ethernet up and running with WLED would make a short guide for ethernet setup.

• list of boards supported (you can take that directly from the source code)
• how to switch to ethernet, after first connecting to WLED-AP
• static IP, or dynamic IP
• notes / fallacies / pitfalls,
• limitations and caveats for specific boards (if possible)
• GPIO limitations (some pins are not usable)

The WLED UI does helpfully warn you if you try to use "input only" pins on the ESP32 for the strip outputs, but this info does not show up anywhere in WLED documentation - though I did find this forum thread after already soldering stuff and then wondering why I couldn't use pins 34 and 35.

I'm sure it's common ESP32 developer knowledge that pins 34 through 39 are input only, but one could understand the confusion for a newbie like myself considering they're all still called "GPIO" in all the pinouts - which of course stands for "general purpose input and output"...