New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NZXT E850 status now throws error with 1.4.0 #166
Comments
Thanks. Can you show me the comparable debug output with 1.3.3? |
Sure, here it is with 1.3.3:
|
There are some things I can double check, but it's noteworthy that the PSU appears to have responded differently to the same commands. Can you please also show me the complete output of
with liquidctl 1.4.0? I'm now specifically interested in the device probing preamble. Another thing that may help me is to see the complete output from
which forces liquidctl 1.3.3 to use the same HID backend that's used in 1.4.0. |
Sure, here is the output from 1.4.0:
And here is 1.3.3:
|
According to their HID descriptor, NZXT E-series PSUs do not use numbered reports. This is especially relevant when doing writes with Hidapi, since it has to work with non-compliant devices and thus needs to know the report ID, even if it's absent. The problem appears to be aggravated on Windows, possibly because it tries to fix the mess and ends up sending a report that is larger than what the PSU expects/accepts. But this is just conjecture... Related: #166 ("NZXT E850 status now throws error with 1.4.0")
Can you give liquidctl-3d2c61e1eb35-bin-windows-x86_64.zip a try and see if it helps? |
That one works! Here's the debug just in case you need it:
|
Happy to hear! And the rest of debug output also looks good to me. Thanks! Status: fix available in the main branch; will be included in liquidctl 1.4.1 (in a few days). |
The previous release read all the stats just fine, but now when I run the status command, I get this:
I know it can't currently control fan profiles or anything on the PSU, only read status, but wanted to put this out there so you knew.
Thanks!
The text was updated successfully, but these errors were encountered: