Hello, I'm a new owner and still figuring everything out so let me know if this can be done.

I have a 12v light hooked up to a fan channel and several RGB lights hooked to Farbwerk. The light I want to come on the wake event and then fade out over 30 minutes. So what I need is a timer 'sensor' which resets on an event. I might want a key press as an event also but you can dream up lots of events. While I'm on the topic .. is there a 'nice' UI for manual control of fan channels?

The RGB lights I want to go from blue to red as the PC "works harder". The formula for that will require some experimentation but I am thinking of a 30 minute moving average of GPU utilization. I don't want the lights to go red unless GPU is near 100% for more than 10 minutes or something. All this would require is a option to 'smooth' out a sensor with an average over time. To make things more difficult I want to include CPU utilization in the mix. I'm thinking that would be measured with another moving average of the two busiest threads. Not sure how to achieve this yet.

I think someone could code their own software sensor .. perhaps in csharp (I have skills). Or maybe someone could log sensors and then with powershell read them and then create a new file which can be read by the aquaero as a sensor input.

This is maybe wrong forum but I've heard of people doing similar with AIDA64 and Logitech keyboard (G15 or G19 or ARQ G910). I have the G910 and AIDA64 software. I think someone has read log from aquaero sensors (perhaps with AID64) and then used that to display on keyboard (again with AIDA64). AIDA64 can also change RGB lights on keyboards. I want to synchronize the lights somehow and also display aquearo info on LCD/ARQ.

Sure. I thought of doing that as well. Water temps are smooth and slow moving like I want except there is a problem. I have fan curves such that water starts at ambient rises to 37c - 40c and then sort of oscillate between 37c and 40c as fans speed up and slow down. So water remains fairly constant .. no matter the system load. Shoot, my 1080ti only gets to maybe 42c full load and CPU about 50c.

So using a moving average on CPU/GPU load would be preferred. I don't know if the aquaero has a "file sensor input" but if it doesn't I could create my own software sensor I think .. much harder but doable. I would need to pick and override one of the available or unused software "addresses". It would require looking at how software monitoring apps work (hopefully find some an open source one) and modify it to suite my needs.


The 12v light on the fan channel that fades out could be done similarly.

Sure would be nice if the aquero had "moving average" and "timer event" built in.

** update **

So far I've learned aquasuite 2017 has "web import/export" .. for monitoring remote server info. See here . Also, "Open Hardware Monitor" is open source and is compatible with the aquaero.

If anyone from Aquacomputer is listening ...

I think you misunderstand. I won't be using temps at all but instead percent utilization, also too aggressive for fans and pumps .. and probably even lights. Water temps are perfect for radiator fans and pumps since that is what is affected by those fan and pumps. But I'm trying to use lights to indicate how long the PC has been working hard .. not cooling.

But, like I said, I don't want my lights flickering all over the place so want to use the running average over 30 minutes. So lights will smoothly go from blue to red over 30 if PC is working hard for that long. Again, running average is easy to calculate .. perhaps a quick example?

Let's say every 5 minutes (in practice many times a minute of course) you polled GPU percent utilization, over an hour. You want the running average over 30 minutes.

5 min .. 50% utilization .. 50% is the average so far.

10 min .. 60% .. 55% is the avg so far (50 + 60) / 2

15 min .. 70% .. 60% is avg (50 + 60 + 70) / 3

20 min .. 60% .. 60 % is avg (50 + 60 + 70 + 60) / 4

25 min .. 80 % .. 64 % is avg (50 + 60 + 70 + 60 + 80) / 5

30 min .. 80% .. 67% is avg (50 + 60 + 70 + 60 + 80 + 80) / 6

35 min .. 100% .. 75% is avg (60 + 70 + 60 + 80 + 80 + 100) / 6 .. note we drop the first measurement

40 min .. 100% .. 82% is avg (70 + 60 + 80 + 80 + 100 + 100) / 6 .. we still have 6

45 min .. 100% .. 87% is avg (60 + 80 + 80 + 100 + 100 + 100) / 6 .. and so on

50 min .. 100% .. 93% is avg (80 + 80 + 100 + 100 + 100 + 100) / 6


55 min .. 100% .. 97% is avg (80 + 100 + 100 + 100 + 100 + 100) / 6


60 min .. 100% .. 100% is avg (100 + 100 + 100 + 100 + 100 + 100) / 6 .. only after 30 minutes of 100 do we read 100.


65 min .. 40% .. 90% is avg (100 + 100 + 100 + 100 + 100 + 40) / 6 .. a short large dip does not change moving average much


70 min .. 100% .. 90 % is avg (100 + 100 + 100 + 100 + 40 + 100) / 6

.. you get the idea. It will take 30 minutes for things to "cool down" after GPU goes idle. Again, water temps in my system are constant .. and GPU temps almost constant .. so percent utilization is best for what I want.
* Scientific applications may have more complex formulas

Anything is possible if you have coding skills