ValueError when creating an OpenRGBClient object (Windows 10) about openrgb-python HOT 11 CLOSED

The common factor here seems like the NZXT Kraken cooler

from openrgb-python.

Nothing seems wrong with the kraken's implementation in OpenRGB. I'm working on adding good logging to get more info and make debugging easier.

from openrgb-python.

At first glance, this looks like a problem on the server side. What devices do you have that are supported by openrgb?

from openrgb-python.

I have...

• Corsair keyboard
• Razer mouse
• NZXT AIO cooler and Hue+ lighting
• Gigabyte RGB mobo w/ RGB RAM
• Gigabyte GPU

from openrgb-python.

I'm having the same issue,

Devices:

• Corsair K70 RGB MK.2
• LED Strip
• Logitech g502
• NZXT Kraken X2

OpenRGB 0.41 3767b3

from openrgb-python.

Just to add, I'm seeing the same issue when a this is a dependency.

Devices:

• Razer Blackwidow V2 Chroma
• Razer Mamba Wireless Chroma
• Razer Goliathus Extended Chroma
• NZXT Kraken x56
• NZXT N7 Z370 Motherboard (RGB)
• Corsair Vengeance Pro RGB

from openrgb-python.

Sorry I haven't gotten around to adding logging yet. From discussion on discord though, it seems like this error is a symptom of SDK connection issues, which are mostly caused by trying to request device info to quickly or in parallel. If you're using multiprocessing, don't. The library is thread-safe, but not multiprocessing-safe, so feel free to replace all multiprocessing with threading. I'll add a section in the docs about this. If this fixes any of your problems, great, otherwise I'll try to make time to add logging

from openrgb-python.

I think PR #11 should fix this. Could you give the latest git version a try? Alternatively you can also update OpenRGB to 23460959 or newer.

from openrgb-python.

The latest release added some fixes and locking that should (hopefully) help with network stability. Could you lmk if it does or doesn't help at all? If not, which example are you running when you get this error?

from openrgb-python.

Yeah I can run it when I get the chance

from openrgb-python.

Can anyone here verify that this issue is still occurring?

from openrgb-python.