Hyperk

[satgit62]

Hello,
Thank you for the Hyperk_0.0.2 alpha version. 🙏

Among other things, I wanted to report that the two ESP32 S2s, which were unable to save settings in the previous version, now work perfectly with the new “Hyperk_0.0.2-alpha_esp32s2_factory.bin” and the ESPtool flasher. 👍

Flashing an ESP32 via the 'Advanced Firmware Flasher' in Chrome and Edge also works as expected.

However, flashing an ESP8266 with CH340 and CP210x did not work via the 'Advanced Firmware Flasher'. The error messages 'Failed to open serial port' and 'Failed to initialize' were displayed. However, both ESP8266s can be flashed without error using the ESPHome flasher.

The setup via the web interface is very tidy and all important settings can be made and saved intuitively. The use of RGBW LEDs is also possible, whereby the version used (CW or NW) can be set here.

Hyperk is immediately recognized in HyperHDR under LED controller 'wled' and works as intended.
I have now tested the ESP32, ESP32 S2, and ESP8266 D1 Mini models in the CH340 and CP210x versions.
The performance is comparable to HyperSerial/Pico's, with no dropouts despite Wi-Fi being used:

2026-02-17T20:00:23.774Z [SIGNAL_OLD] (DetectionManual.cpp:74) Signal threshold set to: {0, 0, 0} and frames: 50
2026-02-17T20:01:25.387Z [PERFORMANCE] [INSTANCE0: FPS = 62.50, processed = 3750], [LED0: FPS = 50.00, send = 3000, processed = 3000, dropped = 0]
2026-02-17T20:02:25.384Z [PERFORMANCE] [INSTANCE0: FPS = 62.50, processed = 3750], [LED0: FPS = 50.00, send = 3000, processed = 3000, dropped = 0]
2026-02-17T20:03:25.384Z [PERFORMANCE] [INSTANCE0: FPS = 62.50, processed = 3750], [LED0: FPS = 50.00, send = 3000, processed = 3000, dropped = 0]
2026-02-17T20:03:57.493Z [WEBSOCKET] (HyperAPI.cpp:943) log streaming activated for client ::ffff:127.0.0.1
2026-02-17T20:04:25.384Z [PERFORMANCE] [INSTANCE0: FPS = 62.50, processed = 3750], [LED0: FPS = 50.00, send = 3000, processed = 3000, dropped = 0]
2026-02-17T20:05:25.386Z [PERFORMANCE] [INSTANCE0: FPS = 62.50, processed = 3750], [LED0: FPS = 50.00, send = 3000, processed = 3000, dropped = 0]

Since the modern code deliberately avoids unnecessary complexity, HyperK offers optimized performance with low latency and integrates seamlessly into Ambilight platforms such as HyperHDR.

HyperK Home Assistant detection also works, and the controls are added to the dashboard.

With HyperK, there is finally a serious Wi-Fi alternative to WLED controllers. I hope that a LAN control interface will be added in the future so that devices that have LAN can also use it when the Wi-Fi signal is not so good.

That's my experience with the new Hyperk LED controller so far, and I hope they continue to work on integration, add new innovative features, and fix any bugs.

[awawa-dev]

Hi
Thank you for the feedback. Regarding esp32-s2. Even the manufacturer: Espressif seems to have given up on proper web support for their own ESP32‑S2 board and they removed it from the ESP Launchpad: https://espressif.github.io/esp-launchpad/ So in a way, the karma caught up with them for releasing such a questionable board 😉

[awawa-dev]

With HyperK, there is finally a serious Wi-Fi alternative to WLED controllers. I hope that a LAN control interface will be added in the future so that devices that have LAN can also use it when the Wi-Fi signal is not so good.

Absolutely! ESP32-LAN board support is high on the priority list, especially since I’ve had these boards sitting on my shelf for a couple of years now ;) However, to avoid the hassle of manual wiring every time to update Hyperk on these boards, I need to implement an OTA mechanism first. Once that's in place, it will make life much easier after the initial installation.

[awawa-dev]

I've tested my esp8266 mini d1 again and it works in my case

Browser: Edge, esp8266 uart: CH340, VID=1A86, PID=7523

[satgit62]

I've tested my esp8266 mini d1 again and it works in my case Browser: Edge, esp8266 uart: CH340, VID=1A86, PID=7523

Hello,
After the new update 'Hyperk_0.0.2-alpha.2_esp8266', my ESP8266-D1 mini boards can also be flashed and Hyperk works as it should. 👍

[DeadDevil6210]

Thank You for al the great work on HyperHDR + this new HyperK add-on

I have a RPi 4 running HyperHDR 22 B1 and I have 5 esp32 modules that all have a SK6812 led strip in connected,

I flashed the first esp32 and immediately noticed better colour reproduction and a noticeable decrease in latency with really fast scene's
Home assistant also picked up on it with out any problems.

But when I converted the second ESP32 my home assistant was saying that it was already connected to it but it isn't, I think this has to do with all the board getting the name HyperK and I cannot find a way to rename the devices (with my WLED install I have renamed all the WLED instances) The second instance works fine with HyperHDR but just not with Home Assistant, Can it be that this has to do with device name being HyperKfor all devices and no option to change? Or did I forget something?

[satgit62]

Thank You for al the great work on HyperHDR + this new HyperK add-on

I have a RPi 4 running HyperHDR 22 B1 and I have 5 esp32 modules that all have a SK6812 led strip in connected,

I flashed the first esp32 and immediately noticed better colour reproduction and a noticeable decrease in latency with really fast scene's Home assistant also picked up on it with out any problems.

But when I converted the second ESP32 my home assistant was saying that it was already connected to it but it isn't, I think this has to do with all the board getting the name HyperK and I cannot find a way to rename the devices (with my WLED install I have renamed all the WLED instances) The second instance works fine with HyperHDR but just not with Home Assistant, Can it be that this has to do with device name being HyperKfor all devices and no option to change? Or did I forget something?

Hello,
The developers @awawa-dev, are working on a solution that will enable 'Hyperk name resolution' to be managed separately in Home Assistant. This will enable multiple devices to be used.

[awawa-dev]

Hi @DeadDevil6210, thank you for the feedback. The new version 0.0.2-alpha.5 has been released and should be visible on the servers within an hour at the latest. I think it will solve your issues, although you might need to re-add the devices to HA.

[DeadDevil6210]

Thank you @awawa-dev

I will try this out today I will let you know how things work out.

[DeadDevil6210]

I Have installed the software and everything works great now! I have all the esp's as seperate devices in Home Assistant.

I Have noticed something els, and it's compared to wled, My longer led strips (100+ leds) have a issue when displaying a white screen, My led strips of max size 90 have no issues with the white colour but my 100+ led strips gradually change from white to warm white --> orange --> orange red.

I have to be honest I don't have power to those led strips going from both sides so that can be an issue but non of my led strips are and wled never had an issues with that. So is there perhaps a issue in driving "bigger" led strip sizes?

And another thanks for your really quick work @awawa-dev

edit 2:

I have played around with some settings in hyperhdr (wled protocol vs udpraw) that does noting,
Playing around in the esp hyperk white channel calibration also does nothing, This seems to be something with the amount of power being send to the led strip, When I adjust the largest led strip from 230 led's back to 160 the color is good going above that introduces the going from white to orange color slightly incleasing it further makes the colors go as i first described.

And as far as I can notice it's only when the led's need to display complete white boarders, when colors are mixed it's awesome!

[awawa-dev]

I'm glad to hear it's working correctly now. The effect you're describing sounds like a classic voltage drop, and the best solution would be power injection. While Hyperk doesn't have a power limiter yet, if you're using it with HyperHDR, that app has one built into the processing where you can configure it.

[DeadDevil6210]

Sorry for the late response,

I have changed the power limit of the large led strips within hyperHDR and this fixed that issue as wel, for the time being, Untill I fixed the voltage drop issue, Thanks for your hard work! I'm really happy with the result this has given me!