[Device] Confirmation: NZXT Kraken Elite 360

[Mondkeks]

Manufacturer

NZXT

Model / Device

Kraken Elite 360

Status

⚠️ Partially working

Operating System / Distro

CachyOS

Additional Notes

• Display shows Data, but flickering/showing NZXT-Logo every few (10-15) seconds
• CoolerControl shows Errors:
  • ERROR coolercontrold::liqctld] Failed to setup bucket for data transfer
  • ERROR coolercontrold::liqctld] Failed to switch active bucket
• Resolution adjustment seem to do nothing / image too large
• screen rotation to 270° shows the same orientation as 0°

[damachine]

Thank you very much for your report. It's a shame to hear that.

The Elite has a different resolution, etc. Since I can only test it with the Kraken 2023 (240x240px) :o, my options are limited. Unfortunately, since I don't have the device to test it with, it's difficult to offer a solution. I can imagine that it works just because you can see something on the display. Someone here in the project would have to get involved who can test the device better and then adjust it.

• The output of curl http://localhost:11987/devices | jq would be very interesting to see if your device is recognized correctly in CoolerControl.

• If you run it again and could post me the output of journalctl -xeu coolerdash.service -f, that would be useful information.

• Do you see your LCD in the CoolerControl app?

• Does the integrated single temp function work there?

• Have you tried manually setting the resolution for your device in the coolerdash.ini? It's possible that the automatic resolution isn't working. see here for example: https://github.com/damachine/coolerdash/blob/main/docs/config.md

• The orientation is a known problem. You should set it in the coolerdash.ini file. Sometimes devices want values ​​like 0, 1, and 2. The 2 should then be 270°.

KISS

[Mondkeks]

Well, thanks for your response and for working on making these devices work under linux!

The LCD is shown in CoolerControl and fully working with single temps, gifs and so on.
CoolerControl is on Version 3.0.1 by the way and the active bucket error does not show immediately after program start, only after a few minutes.

I tried adjusting the resolution to 640x640 in the coolerdash.ini, but it didnt seem to change anything.

Here is the relevant section of the output for curl http://localhost:11987/devices | jq:
"name": "NZXT Kraken 2023 Elite (broken)",
"type": "Liquidctl",
"type_index": 1,
"uid": "0cc94a795dc875e3924853befcaf990e77707b41412fa364f18e31dca51b37cf",
"lc_info": {
"driver_type": "KrakenZ3",
"firmware_version": "2.0.0",
"unknown_asetek": false
},
"info": {
"channels": {
"lcd": {
"label": null,
"speed_options": null,
"lighting_modes": [],
"lcd_modes": [
{
"name": "liquid",
"frontend_name": "Liquid(default)",
"brightness": true,
"orientation": true,
"image": false,
"colors_min": 0,
"colors_max": 0,
"type": "Liquidctl"
},
{
"name": "image",
"frontend_name": "Image/gif",
"brightness": true,
"orientation": true,
"image": true,
"colors_min": 0,
"colors_max": 0,
"type": "Liquidctl"
},
{
"name": "temp",
"frontend_name": "Single Temp",
"brightness": true,
"orientation": true,
"image": false,
"colors_min": 0,
"colors_max": 0,
"type": "Custom"
},
{
"name": "carousel",
"frontend_name": "Carousel",
"brightness": true,
"orientation": true,
"image": false,
"colors_min": 0,
"colors_max": 0,
"type": "Custom"
}
],
"lcd_info": {
"screen_width": 640,
"screen_height": 640,
"max_image_size_bytes": 24903680
}
},
"fan": {
"label": null,
"speed_options": {
"min_duty": 0,
"max_duty": 100,
"fixed_enabled": true,
"extension": "AutoHWCurve"
},
"lighting_modes": [],
"lcd_modes": [],
"lcd_info": null
},
"pump": {
"label": null,
"speed_options": {
"min_duty": 20,
"max_duty": 100,
"fixed_enabled": true,
"extension": "AutoHWCurve"
},
"lighting_modes": [],
"lcd_modes": [],
"lcd_info": null
}
},
"temps": {
"liquid": {
"label": "Liquid",
"number": 1
}
},
"lighting_speeds": [
"slowest",
"slower",
"normal",
"faster",
"fastest"
],
"temp_min": 20,
"temp_max": 60,
"profile_max_length": 9,
"profile_min_length": 2,
"model": null,
"thinkpad_fan_control": null,
"driver_info": {
"drv_type": "Liquidctl",
"name": "KrakenZ3",
"version": "1.15.0",
"locations": [
"/dev/hidraw1",
"/sys/class/hidraw/hidraw1/device/hwmon/hwmon6"

and here for journalctl -xeu coolerdash.service -f:

Okt 09 20:21:35 Vlaakith coolerdash[4165]: [CoolerDash STATUS] Loading configuration...
Okt 09 20:21:35 Vlaakith coolerdash[4165]: [CoolerDash STATUS] PID file: /tmp/coolerdash.pid (PID: 4165)
Okt 09 20:21:35 Vlaakith coolerdash[4165]: [CoolerDash STATUS] Initializing CoolerControl session...
Okt 09 20:21:35 Vlaakith coolerdash[4165]: [CoolerDash STATUS] CoolerDash initializing device cache...
Okt 09 20:21:35 Vlaakith coolerdash[4165]: [CoolerDash STATUS] Device cache initialized: NZXT Kraken 2023 Elite (broken) (640x640 pixel)
Okt 09 20:21:35 Vlaakith coolerdash[4165]: [CoolerDash STATUS] Device: NZXT Kraken 2023 Elite (broken) [0cc94a795dc875e3924853befcaf990e77707b41412fa364f18e31dca51b37cf]
Okt 09 20:21:35 Vlaakith coolerdash[4165]: [CoolerDash STATUS] Sensor values successfully detected
Okt 09 20:21:35 Vlaakith coolerdash[4165]: [CoolerDash STATUS] Display configuration: (640x640 pixels) (Device confirmed)
Okt 09 20:21:35 Vlaakith coolerdash[4165]: [CoolerDash STATUS] Refresh interval: 2.500 seconds
Okt 09 20:21:35 Vlaakith coolerdash[4165]: [CoolerDash STATUS] Starting daemon

Thanks again for taking the time to look into this :-)

[damachine]

Thanks for the detailed info. Actually, the log doesn't look that bad. It basically recognizes the device, the driver, and the resolution etc.

I've already written to the developers of CoolerControl about how to interpret the "broken" message in the log, because it's probably related to the liquid driver. I'll definitely research it. I'll keep an eye on it.
Peace

[Mondkeks]

Yeah, i was suprised by that tag too.

Thanks again und schönes Wochenende!

[damachine]

Haha Gude.

Ich habe bei Discord eine Diskussion angefangen.

Wollte dir mal den link schicken, da sind schon nützliche Infos. Gerade wenn es broken oder bucket geht: https://discord.com/channels/908873022105079848/1426001305700401192/1426001305700401192

Dir auch ein schönes Wochenende!

KISS

[Mondkeks]

YouCut_20251012_221231373.mp4

Vielleicht hilf das ja. Die Zeit, wann das Logo wieder aufflackert, ist übrigens nicht konstant.

Ich habe es mit dem 10sec. stromlos machen versuche, scheint aber nix zu ändern.

[damachine]

Danke für das Video und die mühe.

Der Fehler mit der Anzeige (Auflösung) ist nicht das problem, dass könnte man beheben. Wenn du willst, teste mal in der .ini 240x240px. Dann sollte meine app das hoch skalieren.:o

Bei dem Gerät ist das flackern aber ein bekanntes problem mit dem liquidctl Treiber. Was mich ein wenig wundert, dass die image und single temp Funktion bei dir funktioniert ohne das das flackern dort auftritt. Mein Programm nutzt im Grunde die gleichen Funktion.
Vielleicht testest du die Funktion nochmal eine weile und beobachtest das mal, ob der Fehler dort auftaucht.

Gruss