Hyperion won't disable WLED after stopping streaming

[Nopel2020]

• I confirm that this is an issue rather than a question.

Bug report

I use Hyperion to operate a WLED instance using DDP. Streaming works fine, but when I stop streaming, WLED won't stop operating. Instead the effect is just frozen, and in the WLED webpage it keep saying "WLED is receiving live DDP data from IP ADDRESS". The LED strip also keeps consuming power since it isn't shut off.

This started in 2.2.0 but the problem remains in 2.2.1. In 2.1.1 it worked fine. As soon as I shut off the streaming WLED stopped receiving DDP data and powered off the LED strip.

Steps to reproduce

I normally compile Hyperion myself, but I've also tested this both on the precompiled releases (both 2.2.0 and 2.2.1) and on Hyperbian, to make sure it's not something I'm introducing myself while compiling.

Define a WLED instance, then stream any effect to the instance and stop streaming. With some effects (like Fire) the fire effect will freeze but stay on. With other effects (like Lights) the led strip will go dark, but WLED keeps receiving DDP data and keeps the LED strip powered on.

What is expected?

WLED stops receiving DDP data and powers down the LED strip completely. (This is what happens in 2.1.1.)

What is actually happening?

WLED says it is still receiving DDP data and keeps the LED strip powered on.

System

Hyperion Server:

• Build: Lord-Grey-3c603136/1a003600-1775493764
• Build time: 2026-04-07 07:42:55
• Build type: Release
• Git Remote: https://github.com/hyperion-project/hyperion.ng.git
• Version: 2.2.1
• UI Lang: nl (BrowserLang: nl)
• UI Access: expert
• Avail Screen Cap.: framebuffer,x11,xcb,qt,drm
• Avail Video Cap.: v4l2
• Avail Audio Cap.: audio
• Avail Services: boblight,cec,effectengine,forwarder,flatbuffer,protobuffer,mDNS,SSDP,borderdetection
• Config database: /home/stijn/Hyperion221living/db/hyperion.db
• Database: read/write
• Mode: Non-GUI

Hyperion Server OS:

• Distribution: 'Gentoo Linux'
• Architecture: x86_64
• CPU Model: AMD Ryzen 5 7545U
• CPU Type: 120
• Kernel: linux (6.18.18-nopel (WS: 64))
• Root/Admin: false
• Qt Version: 6.10.2
• Python Version: 3.13.12
• Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:149.0) Gecko/20100101 Firefox/149.0

[Nopel2020]

I'm attaching an export of my configuration in case there's something wrong with the way my WLED is defined.

HyperionBackup-2026-04-07_v2.2.1.json

[Lord-Grey]

Would you mind sharing a Debug log which includes the WLED power on and when you stop the LED Device, please?

[Nopel2020]

debuglog.txt

Here you go!

FYI, I have two instances, one WLED and one Philips Hue, but the Hue one seems to work fine, it's only WLED that's giving the problem.

I'm using Home Assistant to operate the effects. I've changed the IP address and FQDN in the debug log, but that's all I've redacted.

This is what I've done:

• Start effect "Fire." This works fine. The LED device in Hyperion is on, the effect is showing.
• Stop effect "Fire." The LED device in Hyperion is off. The LEDs go dark, but WLED still says "receiving DDP data" and the LEDs stay powered on.
• Start effect "Lights." This works fine. The LED device in Hyperion is on, the effect is visible.
• Stop effect "Lights." The LED device in Hyperion is stopped. The effect freezes, but the LEDS stay lit, WLED says "receiving DDP data."
• Start solid colour. This works fine, the LED device in Hyperion is on, the LEDs change to the chosen colour.
• Stop solid colour. The LED device in Hyperion is off, but the LEDS stay on. WLED is still "receiving DDP data."
• I stop Hyperion completely. WLED remains unchanged, still "receiving DDP data."

Perhaps the problem is in WLED, not in Hyperion? But as I said, with 2.1.1 there's no issue.

Thanks for looking into this!