WLED light output turns off

  • Ok I have a capture card connected to a pi and 3 WLED instances running, Left wall, Right wall and TV. When the TV turns on and the capture card comes on sometimes 1 or more instances turn on. But I always have to turn at least 1 on but mostly all 3.

    I read in the forums about WS281X needing root access which is weird because the controllers are not on the system itself but ran from root, reset the instances and still same thing.


    I cant find any other reference to this otters than people saying they are not coming on at all and the answer is to try root. So kinda lost here. Not sure what information is helpful so ask and I'll provide.


    Hyperion Server:

    - Build: (HEAD detached at a93d79b) (Paulchen-Panther-cb85d2d/a93d79b-1705568419)

    - Build time: Jan 28 2024 10:21:59

    - Git Remote: https://github.com/hyperion-project/hyperion.ng

    - Version: 2.0.16

    - UI Lang: en (BrowserLang: en-US)

    - UI Access: default

    - Avail Screen Cap.: dispmanx,framebuffer,qt

    - Avail Video Cap.: v4l2

    - Avail Audio Cap.: audio

    - Avail Services: boblight,cec,effectengine,forwarder,flatbuffer,protobuffer,mDNS,SSDP,borderdetection

    - Config path: /root/.hyperion

    - Database: read/write

    - Mode: Non-GUI


    Hyperion Server OS:

    - Distribution: Debian GNU/Linux 12 (bookworm)

    - Architecture: arm64

    - CPU Type: Raspberry Pi 4 Model B Rev 1.5

    - CPU Revision: c03115

    - Kernel: linux (6.1.0-rpi8-rpi-v8 (WS: 64))

    - Root/Admin: true

    - Qt Version: 6.4.2

    - Python Version: 3.11.2

    - Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) Ap



    • New
    • Official Post

    There is no need to run under root for WLED.

    Could you share the log output, please?


    In general, the WLED devices have a retry mechanism in case they are only shortly available after Hyperion start-up.

    In addition, it is good practice to disable the Wifi sleep mode in WLED.

  • Sorry didn't get a reply notification to this. Wifi sleep is off in all 3 WLED controllers. Yeah I did the root thing because I read about that and was trying to find anything that would work lol


    here's the logs. looking at it, I see the error timeout


    (ERROR) Device disabled, device 'wled' signals error: 'Retrieving device properties failed with error: 'Network request timeout error''


    This only happens when the system shuts off. the pi its running on always has power 24x7. The grabber has signal only when the receiver is on and passing it to it. Once the system shuts off (Apple TV, receiver adn tv) then I get bars >> then all 3 light sets shut off as expected. Once I turn everything on, sometimes I get the initial startup of the grabber screen lights on then normal operation. But yeah this must be the issue listed here but not sure how to stop it timing out. Once they are on and running they never time out they only do that when the grabber is off.


    PI, all 3 WLED controllers are always powered on, they never turn off. While they are not responsive to Hyperion aka turned off output like in the screen shots I attached. I can control then via WLED web interface no issue.


    Logs keep saying too big over 10k characters so cant post but this error is the problem if that helps.

  • OK, I had to copy this into a note and then save it as a PDF so hopefully this actually works for the upload. And yeah, it says it’s network related but again when it says that there’s no connection I can go in and access them at any point in time through the interface For Wled it just seems like once it turns off for like the TV and everything, but the pie stays on they just losees connections

    • New
    • Official Post

    In the logs I see


    1. That WLED seems to be busy and have some problems with the traffic (503 service not available)

    2. At some point in time the updates to the network were not able to be send (unable to send message)

    3. There are network timeouts even for simple requests. Those could also be cause by that WLED did not respond, is too busy to respond or the network has issues.


    Looking at the symptoms 1.-3. above, I would come to the conclusion that the is an issue with network connectivity between the rpi and WLEDs.

    On what devices are you running WLED and what is the WLED version?


    PS: I assume you switched the grabber off and on why I see the LedDevices being disabled and enabled afterwards, correct?

  • So when I turn my Apple TV off, it sends a signal through CEC to the receiver and the TV turning them both off. Since the grabber is connected to the HDMI output of the receiver, it receives no signal, and you just get the bars from the grabber, even though the grabber is still powered on. After it’s on the bars for a few seconds it turns all three LED sets off. Now that’s visually turns them off. I don’t think it actually turns them off in the system. I’ve never actually checked. A.k.a. the output.


    I saw those errors in the log as well. What’s interesting is that when it is on the raspberry pie is grabbing the capture output and the three instances are turned on. I can run it for numerous hours and I never have any lag. I never have any problems at all. There’s no communication issues. They don’t turn off. Everything‘s stays running fine. It’s only when I turn them off or they auto turn off. Then I come back hours later or days later whatever turn the TV on the TV comes on. I can go into Hyperion and see that all three instances are turned off under output to lights. I can then log into the webinar face of each one of those WLED instances And I can control them without issue.


    Case in point basically when the system turns off sometime between that, and when it turns back on, that’s when it has its network issues I hope that’s helpful.


    The devices are gledopto esp32


    WLED version 0.14.4


    Yes, when I turn the equipment back on, sometimes just flipping the output to lights on doesn’t actually turn them on. I have to turn the grabber off and back on and then output the lights back on to make it work.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!