Skip to content

Dropdown boxes for pin selection are now numeric boxes #5180

Description

@KrX3D

What happened?

hello,

in the newest versions the dropdown boxes for i.e. SDA/SCL etc, so all dropdowns where pins could be selected are now numeric boxes:

before:

Image

now:

Image

To Reproduce Bug

install newest 0.16 build

Expected Behavior

should be dropdown boxes again since it offered only the available pins and also shows already used pins

Install Method

Self-Compiled

What version of WLED?

0.16

Which microcontroller/board are you seeing the problem on?

ESP32

Relevant log/trace output

Anything else?

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Activity

  1. changed the title [-]Dropdown boxes for LED are now numeric boxes[/-] [+]Dropdown boxes for pin selection are now numeric boxes[/+] on Dec 10, 2025
  2. DedeHai commented on Dec 11, 2025

    @DedeHai
    Collaborator

    does #5013 fix it?

  3. added
    cannot reproduceDevelopers are not able reproduce. Might be fixed already, or report is missing important details
    on Dec 11, 2025
  4. KrX3D commented on Dec 11, 2025

    @KrX3D
    Author

    ok i found it. as soon as i use the usermod i created here: #4237

    the scl/sda are changed from the dropdown to the numeric input, so something was changed in wled and i need to fix that in the usermod.

    but i saw that the the LED output pin selection it in fact is still a numeric box (also is in my older wled installations) so it would be nice if this awould also change with the dropdown which would be more user friendly. all other options like relay, buttons etc are already dropdown menus

    Image Image

    EDIT: so far i could test it its the appendConfigData() part in the usermod

  5. DedeHai commented on Dec 11, 2025

    @DedeHai
    Collaborator

    LED output as dropdown is already done by @blazoncek its just a question of bringing it upstream which will happen eventually.
    So can this be closed?

  6. KrX3D commented on Dec 11, 2025

    @KrX3D
    Author

    Hi, yes it can probably be closed.

    Still odd that this happend since some changes in the last 2/3 months.

    And odd that the problem is that something like:

    	//INA226
    	oappend("dda=addDropdown('INA2xx','average');");
    	oappend("addOption(dda,'1 (default)',0, true);");
    	oappend("addOption(dda,'4',512);");
    	oappend("addOption(dda,'16',1024);");
    	oappend("addOption(dda,'64',1536);");
    	oappend("addOption(dda,'128',2048);");
    	oappend("addOption(dda,'256',2560);");
    	oappend("addOption(dda,'512',3072);");
    	oappend("addOption(dda,'1024',3584);");
    

    in the appendConfigData broke it, because it wasnt used since i used an INA219, so it couldnt find the average dropddown (which is only there for the ina226) and that "broke" it

    EDIT: i had localy an older verion of the usermod, the version in the PR had already the part fixed

  7. DedeHai commented on Dec 11, 2025

    @DedeHai
    Collaborator

    incorrect code on an embedded system is always problematic as it is not error proof and will just stop working.
    Only one thing changed in recent time (and I already have a better solution, see my first comment) 529edfc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugcannot reproduceDevelopers are not able reproduce. Might be fixed already, or report is missing important detailsuse-as-isexpected behaviour, not a bug, no change planned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions