-
-
Notifications
You must be signed in to change notification settings - Fork 459
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
Missing Control Sensor /nzxt/krakenz #2789
Comments
I went back to v174 and restored the v174 backup config (thank you for taking auto-backups!!) the message disappeared and my curves etc. have been restored. Not sure where to go from here. |
Does "suddenly" corresponds to an update for FanControl? Did you go from 174 to 20X? |
No, I've been updating each time there is an update, so I would say it's in the last couple of updates or so that I've noticed is |
Do yo use these at all in FanControl? If not, just save your config on top of the error and it will go away. |
Looking at the restored app and config it's paired to a sensor called CPU Pump. If I search the config for this, then I see...
So, I think yes, it was being used and now in the new version is no longer being recognized. |
Hi. I installed the Kraken plug-in and then restored my old config file and it seems to be working again now. In fact, I can now add the pump and fans and control them, which I couldn't do before. I thought the Kraken was supported natively, but maybe something changed there? |
The Native Kraken Support in LibHardware is not good. I also tested it and have Problems with my Kraken 280 (2023). |
Encountering the same issue with V209. Downgraded back to V206 to fix it. There's definitely a regression here. |
I believe the identifiers got modified, hence why the ones saved in your config are not recognized. Does a new "virgin" control card appeared? |
@Rem0o You are correct- I see a brand new set of AIO controls, which work fine after I configure them: The "duplicate" older controls don't do anything even if I try to control it manually after pairing. Is there a way to exclude these (as this behavior doesn't seem to happen on V206) I'm assuming FanControl is pulling these from the system as it looks like my motherboard reports the PUMP1 header separately from the Pump control also reported by NZXT: Edit: For some reason, the duplicate reporting doesn't seem to happen on V206 |
@mmshivesh could you send your new json config file saved? Really confusing as to what is what. Don't care about any old one. |
This has been working great and suddenly in the last couple of weeks I have started getting this error.
Is this a known issue, or has something gone wrong with my NZXT hardware? I haven't installed any NZXT updates as far as I remember.
The text was updated successfully, but these errors were encountered: