HyperK preferred instead of HyperSerialESP32 for USB devices?

[sofakng]

If I'm going to be using an ESP32 over USB, is it preferred to use HyperK or HyperSerialESP32?

I'd like to use the ESP32 LEDs for both HyperHDR and basic ambient lighting, etc.

It would be neat if WLED could still control the LED strip when I'm not using HyperHDR.

[shrutikbalwan]

Short answer: if you want both HyperHDR and ambient lighting when HyperHDR isn't running, HyperK is the better fit. HyperSerialESP32 only does one thing: it streams colors from HyperHDR over USB.

Why HyperK

USB still works: it supports HyperSerial-style USB serial (the HyperHDR Adalight/AWA protocol), so you can keep driving it over USB from HyperHDR.

Wi-Fi too: it can also take HyperHDR over Wi-Fi, using the dedicated HyperK driver or DDP / udpraw / WLED.

Ambient lighting without HyperHDR: it has a web GUI and Home Assistant auto-discovery with on/off, color and brightness control.

Easy install: flash it from the browser at https://hyperk.hyperhdr.org, then update it over OTA.

About WLED

WLED and HyperK (or HyperSerialESP32) are separate firmwares, so one ESP32 can only run one of them at a time. You can still get close to what you want:

Option A: Run HyperK and control ambient lighting through Home Assistant or HyperK's web GUI instead of WLED.

Option B: Run WLED and point HyperHDR at it with HyperHDR's WLED driver over Wi-Fi. You give up the USB link and the lowest latency, but keep all of WLED's effects.

Note: HyperK turns the LEDs off 6.5 s after the stream stops. This is expected when you close HyperHDR, after which you control them from HA or the GUI.

More details: https://wiki.hyperhdr.eu/Hyperk