Open nonsintetic opened 2 years ago
So those are errors thrown when MSI, Asus and Corsair devices are set up - do you have any such devices, and are the relevant applications installed? (MysticLight / Armory Crate / iCue / whatever)
Possibly the error here is we need to be able to enable/disable individual RGB.Net device types separately, rather than en bloc.
I do have a Corsair K63 Keyboard as stated in the issue, but I don't have any of the software installed anymore.
Only software related to these kinds of things is Logitech G HUB (doesn't run on startup though) and maybe Asus AI Suite (but that's more for fan control and such).
If it's just a matter of requiring the apps be installed, could just show a message to the user telling them to install whatever, seems good enough :)
Hi there and Merry Christmas!
i encountered exactly the same issue as @nonsintetic, getting identical error messages - word by word.
OS: Windows 11 23H2 HW: a set of ESP controllers with different builds (to be able to get around every known bug) • 2 x NODEMCUV1|ESP8266 (WLED 0.13.4 SR, WLED 0.15.0-A0 25.12.2023) • 3 x NODEMCUV3|ESP8266 (WLED 0.14.0 vanilla, WLED 0.14.2-B0 25.12.2023, WLED 0.15.0-A0 25.12.2023) • 3 x ESP32DEV-V1 (WLED 0.14.0-B28.34 SR MM 24.12.2023, WLED 0.14.0 vanilla, WLED 0.15.0-A0 25.12.2023) tied to 16x16, 10x8, 42x9 matrix WS2812B, 9x32 matrix LDP8806 and a 82+136+82x1 lineup WS2812b. All of these should work - no?
ESP32-S2 and RASPIB+ with HUB75_DMA-library controlling a 64x64 P3 panel seem not to be supported!?
No other products stated in the list of supported hardware are known to exist here or have gotten recognized by Home Assistant.
===== Edit: i guess i better should turn off the Hardware Support to avoid the error messages - or is the software core unaffected by those and still does its job?
When using hardware support, the following errors pop up on start. Using MaxLights 0.8 on Windows 10 fully updated. I have a Corsair K63 Keyboard.