HyperHDR 22.0.0 beta1 Flashing LED

[ingbrzy]

Detailed Reproduction Path

Hello..

Sometimes my LED strip is flashing rapidly after update to HyperHDR 22.0.0beta1

hyperhdr-flashing.log

to stop it, I have to reboot my Rpi5..

Have you tested the latest Github Action/beta build?

Yes, the problem still exists in the latest beta/Github Action builds

Did this work in a previous stable version?

Yes, it worked in the previous version

Platform

Raspberry Pi 5

Capture Device / Grabber

MS2130 (USB)

LED Driver

HyperSerialPico

System About Info

Version

22.0.0beta1

Build source

master (GitHub-8a424cf/ec26d4f-1770207242)

Build date

Feb 4 2026 12:16:30

Main UI components

Bootstrap 5, AdminLTE, JQuery, JSON-Editor, Vanilla Picker, jQuery.i18n, Download, Gijgo

System info

HyperHDR Server:

• Build: master (GitHub-8a424cf/ec26d4f-1770207242)
• Build time: Feb 4 2026 12:16:30
• Git Remote: https://github.com/awawa-dev/HyperHDR
• Version: 22.0.0beta1
• UI Lang: auto (BrowserLang: sk-SK)
• Avail Capt: Linux (V4L2)
• Database: read/write

HyperHDR Server OS:

• Distribution: Debian GNU/Linux 13 (trixie)
• Architecture: arm64
• CPU Type: Raspberry Pi 5 Model B Rev 1.0
• CPU Hardware: c04170
• Kernel: linux (6.12.62+rpt-rpi-2712 (WS: 64))
• Qt Version: 6.8.3
• OpenSSL: OpenSSL 3.5.4 30 Sep 2025
• Browser: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36

Application Log

2026-03-05T16:32:36.156Z [JSONCLIENTCONNECTION] While validating schema against json data of 'JsonRpc@::ffff:192.168.31.88':[root].componentstate.component: Unknown enum value (allowed values are: ["ALL","HDR","SMOOTHING","BLACKBORDER","FORWARDER","VIDEOGRABBER","SYSTEMGRABBER","LEDDEVICE","GRABBER","V4L"])
2026-03-05T16:32:36.157Z [JSONCLIENTCONNECTION] While validating schema against json data of 'JsonRpc@::ffff:192.168.31.88':[root].componentstate.component: Unknown enum value (allowed values are: ["ALL","HDR","SMOOTHING","BLACKBORDER","FORWARDER","VIDEOGRABBER","SYSTEMGRABBER","LEDDEVICE","GRABBER","V4L"])
2026-03-05T16:32:36.157Z [JSONCLIENTCONNECTION] While validating schema against json data of 'JsonRpc@::ffff:192.168.31.88':[root].componentstate.component: Unknown enum value (allowed values are: ["ALL","HDR","SMOOTHING","BLACKBORDER","FORWARDER","VIDEOGRABBER","SYSTEMGRABBER","LEDDEVICE","GRABBER","V4L"])
2026-03-05T16:32:36.173Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:214) portName: ttyACM0
2026-03-05T16:32:36.174Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:215) systemLocation: /dev/ttyACM0
2026-03-05T16:32:36.174Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:216) description: Pico
2026-03-05T16:32:36.174Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:217) manufacturer: Raspberry Pi
2026-03-05T16:32:36.174Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:218) productIdentifier: 0xa
2026-03-05T16:32:36.174Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:219) vendorIdentifier: 0x2e8a
2026-03-05T16:32:36.174Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:220) serialNumber: E661640843255F2B
2026-03-05T16:32:36.178Z [LEDDEVICE0_ADALIGHT] Detected Rp2040 type board. HyperHDR skips the reset. State: 1, 1

Validation Check

• I understand that my issue will be automatically closed if logs are missing/incomplete or description is insufficient.

[awawa-dev]

Hi
Seems to me like an electrical issue (for ex. bad connection, missing level shifter or common ground) or damaged LEDs.

[ingbrzy]

video
https://github.com/user-attachments/assets/48ad907c-26fe-46ec-b59d-06f7a615b591

after Rpi reboot it is working OK for few hours... so not sure about HW issue..

[awawa-dev]

The LED driver (HyperSerialPico) is identical in both HyperHDR versions you tested, so HyperHDR is effectively decoupled from the hardware. All it can do is stream at a higher FPS or different brightness, which might simply be exposing an underlying instability that was already there in your setup.

[ingbrzy]

unfortunately I updated from bookworm to trixie at same time with HDR 22.0.0.beta1..
but can not go back to 21.0.0 as it is not available for trixie..

[awawa-dev]

You can compile v21 for trixie if you want, the manual is in the wiki. But better make sure first, you have a 3.3v to 5v level shifter because it's mandatory and you still have a ground connection between LED ground to Pico ground.

[ingbrzy]

Thanks, will try to compile..

I am sure, my HW setup is correct.. :)

[awawa-dev]

I prefer not to leave even unused OE pins floating - you can ask Gemini to explain why that's a bad idea. It can also fill you in on the massive issue with counterfeit or salvaged Texas Instruments 74AHCT chips. Next time your setup hangs, try a full power cycle on the LED power supply to see if it clears the glitch.

[awawa-dev]

try a full power cycle on the LED power supply to see if it clears the glitch.

If that doesn’t help, try disconnecting and reconnecting the Pico driver from RPI5 USB port and restart driver in HyperHDR. I assume that since you had to restart the RPi5, just restarting the driver in HyperHDR software alone didn’t help on its own. Ideally, power-cycle the level shifter before that as well if you can disconnect +5V from it, so we can narrow down which part is failing: the Pico, the level shifter, the LED strip or something else.

[ingbrzy]

That it a good idea..! will let you know when it happens again..

[ingbrzy]

So it happened again.. tried disconnect rpi pico and plug it back, same issue.. tried disable/enable usb capturing device, same issue.. only full Rpi reboot helps..

[awawa-dev]

Sorry to hear about the flashing LEDs, but to actually look into this I would need to be able to reproduce the problem or at least see some evidence of it in the logs.

Restarting the USB capture (but why did you restart it? - it's not directly related to flashing unless the grabber itself is malfunctioning) also automatically restarted the smoothing process. So if the smoothing had gotten stuck with some broken frame queue, it should have been cleared anyway (I already saw "Smoothing queue is cleared" in your previous logs anyway).

Right now I simply don't have any solid starting point to investigate further - there's no way to tell whether this is a general/systematic bug or something very specific to one particular setup/hardware combination.

I can rule out any issues with the communication to the Pico itself, because it is protected by a checksum.

[ingbrzy]

Could you build for me 21.0.0 for Rpi5 Trixie? I will downgrade HyperHDR and we will see if it is new beta issue or my setup..

thank you