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

After migration to Universal Display Driver WS2812 and OLED SSD1306 somehow interconnected #21726

Closed
dkadioglu opened this issue Jul 4, 2024 Discussed in #21679 · 3 comments
Assignees
Labels
bug Type - Confirmated Bug fixed Result - The work on the issue has ended

Comments

@dkadioglu
Copy link

I still have the issue, that power controls always both the WS2812 LED stripe and the OLED display and transfer the discussion to an issue, I hope that is ok.

Discussed in #21679

Originally posted by dkadioglu June 22, 2024
I have migrated to Universal Display Driver according to https://tasmota.github.io/docs/Universal-Display-Driver/#migrating-to-udisplay. However, now I have an issue with my also connected WS2812 LED stripe. When I run DisplayDimmer x, also all 20 LEDs of my WS2812 get enabled. When I disable them again with Power off, the display is also switched off. I also reset the device to the default settings, still the same issue. Is this something known? Anything I can do about that?
I have a ESP8266 NodeMCU board and a SSD1306 OLED display with a self built build, as I need MQTT_TLS.

Edit 240623:
What I realized just now is, that before the update I had two Toggle buttons in the web ui, one for the LED stripe and one for the OLED display. After the update I now have only one button, which influences both devices.

If you need further info, please ask.

@arendst arendst self-assigned this Jul 5, 2024
@arendst arendst added the bug Type - Confirmated Bug label Jul 5, 2024
@arendst
Copy link
Owner

arendst commented Jul 5, 2024

I notice the same if I setup a display with a light.

I'll chk if anything can be done to overrule the display backlight to become a light.

@arendst
Copy link
Owner

arendst commented Jul 5, 2024

Pls provide your GPIO config (command gpio) and output of command status 0.

NB. As a workaround, while I see how to fix this, you might want to configure a spare GPIO as Backlight and see if this fixes your issue.

@arendst arendst added the fixed Result - The work on the issue has ended label Jul 5, 2024
@dkadioglu
Copy link
Author

It works again! Thank you very much for the immediate fix! I'll close this as it is fixed for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Type - Confirmated Bug fixed Result - The work on the issue has ended
Projects
None yet
Development

No branches or pull requests

2 participants