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

Multiple Potentiometers not working since 0.14.0.b1 #3549

Closed
1 task done
rhinomods opened this issue Nov 25, 2023 · 6 comments
Closed
1 task done

Multiple Potentiometers not working since 0.14.0.b1 #3549

rhinomods opened this issue Nov 25, 2023 · 6 comments
Labels
bug confirmed The bug is reproducable and confirmed fixed in source This issue is unsolved in the latest release but fixed in master

Comments

@rhinomods
Copy link

What happened?

I had 0.13.3 working with multiple potentiometers for brightness, speed, intensity, and color working, Updated to 0.14.0 and only the first enabled button would work. (brightness.)

To Reproduce Bug

with Esp32dev v1, flashed with wled 0.14.0
I attached 10k Potentiometers to ADC 0,3,6,7 (gpio 36,39,34,35)
Under [LED PREFERENCES] set buttons 0-3 to analog inverted and (Respective GPIO pin#)
Under [TIME AND MACROS] set buttonActions for Button 0-3 SHORT 0,0,0,0 LONG 0,0,0,0 DOUBLE to 200,250,249,248

Adjust Potentiometers, I notice ONLY the First button that is enabled or set to ANALOG inverted will work, the others will not register.
IF I set button 0 to DISABLED, button 1 will work but others will not. ETC.

I attempted to use the checkbox to enable or disable pull up resistor No change.

Expected Behavior

On 0.13.3 I was able to have multiple Potentiomers working.

Install Method

Binary from WLED.me

What version of WLED?

WLED 0.14.0

Which microcontroller/board are you seeing the problem on?

ESP32

Relevant log/trace output

No response

Anything else?

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@rhinomods rhinomods added the bug label Nov 25, 2023
@blazoncek
Copy link
Collaborator

Please contact me on Discord and I'll send you a debug version so we can diagnose.

@blazoncek blazoncek added the waiting for feedback addition information needed to better understand the issue label Nov 26, 2023
@blazoncek blazoncek mentioned this issue Nov 27, 2023
@softhack007
Copy link
Collaborator

@rhinomods any new insights from using the debug version?

@Hubes101
Copy link

Hubes101 commented Jan 16, 2024

I just updated my esp32 to 0.14.1 (not beta) and I’m having the same problem
I was wondering if this has been fixed and I just haven’t noticed it yet

@softhack007 softhack007 added the needs investigation The bug has not yet been reproduced by me. Analysis or more details are needed. label Jan 16, 2024
@softhack007
Copy link
Collaborator

I was wondering if this has been fixed and I just haven’t noticed it yet

As far as I know, there was no progress on this issue.
@blazoncek asked @rhinomods for help on debugging, but no response or feedback arrived. At least that's my understanding.

@blazoncek
Copy link
Collaborator

There was no feedback. Last communication was on December 16th to say "working on it. sorry for long delay. hopefully i can respond tomorrow".
I did check the code but couldn't find any clue where the problem may be.

blazoncek added a commit that referenced this issue Feb 10, 2024
blazoncek added a commit that referenced this issue Feb 10, 2024
@blazoncek blazoncek added confirmed The bug is reproducable and confirmed fixed in source This issue is unsolved in the latest release but fixed in master and removed needs investigation The bug has not yet been reproduced by me. Analysis or more details are needed. waiting for feedback addition information needed to better understand the issue labels Feb 10, 2024
@blazoncek
Copy link
Collaborator

will be available in 0.14.2 and/or 0.15

softhack007 pushed a commit to MoonModules/WLED that referenced this issue Feb 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug confirmed The bug is reproducable and confirmed fixed in source This issue is unsolved in the latest release but fixed in master
Projects
None yet
Development

No branches or pull requests

4 participants