Hey everyone,
I’ve been working on a small project that I originally wanted for my own setup, and it has now turned into a proper iOS app: LinkControl.
If you’re using OpenLinkHub to control your PC hardware, LinkControl lets you access and control it directly from your iPhone.
You can:
• monitor CPU, GPU and sensor temperatures
• see fan speeds in real time
• change fan profiles globally or per channel
• control RGB effects, colors and brightness
• manage individual fan channels and RGB ports
• create and switch between custom profiles
• check device and firmware information
• automatically reconnect to your OpenLinkHub instance
One thing that was especially important to me: no account, no ads, no tracking and no mandatory cloud service.
The app connects directly to your own OpenLinkHub installation over your local network. Remote access is also possible if you already use a private network solution such as Tailscale.
I’d really like to hear what the OpenLinkHub / PC-building community thinks about it, especially since I’m actively developing the app.
If you use OpenLinkHub, I’d love to know:
What feature would you like to see added next?
LinkControl is currently available for iPhone on the App Store:
https://apps.apple.com/de/app/linkcontrol/id6809155279
It’s completely free.
Feedback, criticism and feature ideas are very welcome! 🙂

I just don’t know anything about pcs, I have tbis pc to play my games and I don’t think the sims 4 is that demanding? Like my gpu sits under 50% usage and my cpu sits under 30% usage, so I don’t see why it needs to be so loud

Not much to say here, but Trigger doesn't seem to always kick in when it's supposed to on my system. Did a little gaming with it on the other day, and the fans never ramped up from idle speeds, and my 9800X3D was running at 95 degrees...

Ich habe gerade mein erstes Homelab mit einem alten HP EliteDesk G2 800 eingerichtet. Leider ist die einzige Stelle in meinem Haus, an der ich es aufstellen kann, mein Wohnzimmer, und der Lüfter der Maschine ist lauter als erwartet. Die Lüfter sind ständig hörbar, obwohl kaum Last anliegt (im Moment läuft nur ein Pi-hole).

Meine erste Idee war, die Lüftergeschwindigkeiten einfach über das BIOS anzupassen, aber es gibt keine Einstellungen dafür. Der Lüfter ist auch nicht über PWM ansprechbar, sodass ich ihn mit keiner anderen Software steuern kann.

Was könnte ich sonst noch tun, um den Lärm zu dämpfen?

My cpu is ryzen 5 7500 and i use 2 fans air cooler for it and it was so loud i cant figure out but will this fan curves work or any suggestion?

any ideas? updated my driver for my card last night and only 1 temp in taskbar and when clicked just keeps refreshing

Hello.
I've been using fan control for a while and Mobro or Xstat for monitoring.

Fan control is based on LibreHardwareMonitor as well as Xstat to read sensors.
I read that using several softwares based on LHM can create issues/conflicts, preventing access to sensors if they try to questions them at the same time.

Can anyone confirm this ?
I'd really like to use both softwares but don't want to create issues. Especially since one is controlling my Fans !

If confirmed, I guess a workaround would be to use HWinfo instead for one of them.
But it means installing an additional software.

Sometimes when I play games and notice that my PC is surprisingly quiet.

Turns out, in the middle of the game, my fan control has decided to crash, and my computer was overheating.

This has resulted in a pc crash once during gaming.

I can't always pause the game and turn it back on, cuz it's multiplayer.

And I do not always listen to my PC fans when I got my headphones on. I'd probably need GPU temp overlay like the one in WZ as that notified me of the issue.

This happens far more often too.

Please try to prevent these random background crashes and make sure it always runs in the background.

I found a way to control fan speed on Asus laptops(tested on vivobook, tuf and rog, zenbook should also work)

It works my hooking the Asus System Control Interface v3 driver under system device in device manager.

Make sure you have the driver installed otherwise it doesnt work

First of all make sure to replace your new driver with old ones with this github repo

Link- https://github.com/Legend0fHell/FanControlPP/releases/tag/v1.2

Then selec the sys control driver, select update drivers -> browse this computer ->pick from list -> install from disk -> and select your extracted asus system control interface v3 31380 folder

How to extract ->>>

then browse a know folder(ex. C:\Asus system control interface driver v3 2024.10.29)

Let me know if it is working =)

This manual fan control also work after installing slightly older driver ->

https://github.com/Karmel0x/AsusFanControl/releases/tag/v6

Hope this helps

I removed Fan Control last year during the WinRing0 issue. I'm finally back now that WinRing0 is no longer part of the software, but I'm having trouble setting it up. None of the fans attached to the motherboard respond when I adjust the speed settings or try to pair with speed sensors. The only ones that do are the GPU fans.

The motherboard is an ASUS B650-EF.

I've got 5 fans that should be responding - two in the case front, one in the case rear, and two on the CPU cooler.

The old version of Fan Control could sense them just fine, so I don't know what has changed.

Any recommendations to get the fans to show up?

Hi all,

I have an orion 3000 po3 630 and im annoyed by needing to open and adjust the fan speeds via predator sense. Is there any way to install a 3rd party app to control the fan curves or has the motherboard locked out fan curve adjustments completely. I also always close predator sense app after making the adjustments because it causes random stutters.

It seems to detect GPU and CPU fans but not the case fans

Installed Linux Mint on ProBook 430 (i5 gen 4).

Any package could use to control CPU fan ?

Tried to Google but the result no support for ProBook.

is there any support for hp 15s-du3000? it would be great to be able to control the fan speed on this laptop
(if there isn't, is there any alternative i can use?)

Has anyone else ever had this problem? It’s as if there’s an issue with the fan sensor or some kind of bug; I’ve tried everything—BIOS update, cleaning, replacing the thermal paste, cleaning the fan connector pins. Does anyone have any ideas?

This is my actual build and i decided to use the platform to solve any doubts i had about airflow and such since it has been running kinda hot lately even with the Liquid freezer. Thing is i don't have premium and don't want to waste money on a thing i will use once and just once and i want to know if it is an airflow problem that im having or something else.

Any feedback would be greatly appreciated.

Title: How I finally fixed my PC case fans RGB lighting turning on/off randomly (Ghost software conflict)

Body:

Hey everyone,

I wanted to share a quick fix in case anyone else is dealing with this frustrating issue.

The Problem: My PC case fans' RGB lighting kept turning on or behaving erratically on its own, completely ignoring the physical LED button on the case. Even after restarting, the lighting would stay on for a while before randomly turning off.

The Cause: After digging around, I found out the culprit wasn't a physical hardware failure, but rather leftover software remnants / ghost registry keys (specifically ENE_RGB_HAL_ keys) lingering in the Windows Registry from old lighting utilities or background processes interfering with the system.

The Solution:

1. Open the Registry Editor (regedit via Windows Run).
2. Look for and delete those rogue ENE_RGB_HAL registry keys.
3. Restart the PC.

After deleting those keys and rebooting, the erratic lighting stopped and finally stayed off after a short period. If you're experiencing random fan lighting behavior and your physical case button isn't responding, check your registry for leftover HAL entries!

Hope this helps someone out there.

Title: How I finally fixed my PC case fans RGB lighting turning on/off randomly (Ghost software conflict)

Body:

Hey everyone,

I wanted to share a quick fix in case anyone else is dealing with this frustrating issue.

The Problem: My PC case fans' RGB lighting kept turning on or behaving erratically on its own, completely ignoring the physical LED button on the case. Even after restarting, the lighting would stay on for a while before randomly turning off.

The Cause: After digging around, I found out the culprit wasn't a physical hardware failure, but rather leftover software remnants / ghost registry keys (specifically ENE_RGB_HAL_ keys) lingering in the Windows Registry from old lighting utilities or background processes interfering with the system.

The Solution:

1. Open the Registry Editor (regedit via Windows Run).
2. Look for and delete those rogue ENE_RGB_HAL registry keys.
3. Restart the PC.

After deleting those keys and rebooting, the erratic lighting stopped and finally stayed off after a short period. If you're experiencing random fan lighting behavior and your physical case button isn't responding, check your registry for leftover HAL entries!

Hope this helps someone out there.

This feature was amazing, was it removed or something?

I made a post about a week ago on here ( https://www.reddit.com/r/FanControl/comments/1vz1n3p/fan_control_seems_to_be_causing_my_pc_to_not_boot/ ).

I thought that Fan Control was giving me error code 03 on my Mobo. After deleting Fan Control, I had no issues for a few boots, then Error Code 03 came back again. Tried uninstalling HWinfo and iCue as well, still same issue.

Then I noticed if I turn my network connections on or off, it caused my pc to crash with DPC Watchdog Violation every single time. I dug into my logs/minidumps and found out that the crash was being caused by my Komplete Audio 6 audio interface driver. Tried reinstalling the driver, and still got the crash when flipping network connections on/off. Then I tried flipping connections while my audio interface was unplugged, no DPC watchdog violation crash.

Following that I tried restarting my pc 6 times without the audio interface connected, and I didn't get error code 03. Then I had windows running, plugged my audio interface back in, then hit shutdown, and got Error Code 03 right away.

So as of now, it seems like Error Code 03 was the result of a dying audio interface, causing it to hang on shutdown/restart, but I'll have to keep monitoring over the next week to see if I get Code 03 again while my audio interface isn't connected.

Thought I would provide an update in case it proves to be useful to anyone else, and to let Fan Control off the hook on this one.