Hi @akiba and @sgtnasty,
There is an often overlooked settings option in both the UI and config file called: Startup Delay
This will add the specified number of seconds of delay to the startup procedure of the daemon(s) itself and should hopefully solve your startup issues.
I haven't run into this problem myself when testing a multitude of devices at the same time, but I have heard this from a few issues raised in GitLab: some devices (no clear culprit) not being completely "ready" to communicate when the service starts right after boot-up. That might be related to the motherboard/usb chip used rather than necessarily the devices themselves, but it's hard to say at this point.
Pinned Comments
codifryed commented on 2024-09-22 19:02 (UTC)
With the release of 1.4.1 CoolerControl has now been spit up into several packages. This requires users to uninstall and then reinstall the application.
See: https://gitlab.com/coolercontrol/coolercontrol/-/issues/347
There's an upside, there's now a binary AUR package
coolercontrol-bin
for less compile time!codifryed commented on 2023-02-07 22:54 (UTC) (edited on 2024-01-06 23:57 (UTC) by codifryed)
Post-installation steps:
Then open the desktop application.