1 hour ago, PeterDB said:

I gotta ask @RandoUser 10 fans at 2.7A. that's 27A on the 12V rail, which power supply are you using? I know my Corsair HX1200 can handle max 100A and on multi rails 40A, but 27A for fans is a lot.

It's one fan (with the plan to go to 3 for the drives in my case). I didn't populate out all 10 fans with that model.

But, I'm not inclined to swap out fuses to force things beyond spec so I'll just find the max PWM the controller can handle with those fans.

7 minutes ago, RandoUser said:

It's one fan (with the plan to go to 3 for the drives in my case). I didn't populate out all 10 fans with that model.

But, I'm not inclined to swap out fuses to force things beyond spec so I'll just find the max PWM the controller can handle with those fans.

Okay, @RandoUser but can i ask why you opted for that fan versus other consumer fans? Is your build in a server room, because its gonna get loud with those fans? I made a similar mistake myself in the past and even my noise cancelling headsets couldn't cut the fan whining out.

1 hour ago, PeterDB said:

Okay, @RandoUser but can i ask why you opted for that fan versus other consumer fans? Is your build in a server room, because its gonna get loud with those fans? I made a similar mistake myself in the past and even my noise cancelling headsets couldn't cut the fan whining out.

Sure. I bought them for the limited scenario where the drives are getting up to 50C (but this seems reduced now that all of my data has been copied completely to Unraid). The Noctuas that I currently have are limited to 1500 RPM. I'm fine to burst the fan speeds for short periods of time. Yes, they're loud but my Unraid system is in a place where period noise increases aren't a problem. It looks like the fan controller can do about 4000 RPM on these fans without exceeding the fuse limit. When these fans are at 1500 - 2000 RPM they aren't any louder to my ears.

I updated the OpenFANservice container recently, but then realized today my HDD were dangerously hot.
After a quick check, I saw the container didn't want to connect to the controller container, so I tried to reinstall it. Now it doesn't want to start at all, what is going on here? Tried to reinstall it multiple times but nothing works. Note that if I change the host IP to something else, it does start but doesn't want to connect.

Here is the installation command I used:
docker run -d --name OpenFANservice \

-v /var/local/emhttp:/mnt/OpenFanService/sensors:ro \

-v /mnt/user/appdata/openfanservice/fan_profiles.yaml:/mnt/OpenFanService/data/fan_profiles.yaml:ro \

-e "OPENFAN_HOST=192.168.0.5" \

-e "OPENFAN_PORT=3000" \

-e "OPENFAN_SENSORS=/mnt/OpenFanService/sensors/disks.ini" \

-e "OPENFAN_PROFILE=/mnt/OpenFanService/data/fan_profiles.yaml" \

-e "OPENFAN_RELOAD=True" \

ghcr.io/sasakaranovic/openfanunraidservice:release

and here is the container's log:
Jul 01 2025 04:52:25.337 pid:7 fan_configuration.py 120 DEBUG -- Assigned Profile: LowerHDD

Jul 01 2025 04:52:25.337 pid:7 fan_configuration.py 119 DEBUG Created fan control OpenFAN/Fan/1

Jul 01 2025 04:52:25.337 pid:7 fan_configuration.py 120 DEBUG -- Assigned Profile: UpperHDD

Jul 01 2025 04:52:25.338 pid:7 temperature_sensors.py 24 DEBUG Sensor parity temperature is 41°C

Jul 01 2025 04:52:25.338 pid:7 temperature_sensors.py 24 DEBUG Sensor disk1 temperature is 37°C

Jul 01 2025 04:52:25.338 pid:7 temperature_sensors.py 24 DEBUG Sensor disk2 temperature is 39°C

Jul 01 2025 04:52:25.339 pid:7 temperature_sensors.py 24 DEBUG Sensor disk3 temperature is 37°C

Jul 01 2025 04:52:25.339 pid:7 temperature_sensors.py 24 DEBUG Sensor disk4 temperature is 41°C

Jul 01 2025 04:52:25.339 pid:7 temperature_sensors.py 24 DEBUG Sensor disk5 temperature is 42°C

Jul 01 2025 04:52:25.339 pid:7 temperature_sensors.py 24 DEBUG Sensor parity2 temperature is *°C

Jul 01 2025 04:52:25.339 pid:7 temperature_sensors.py 24 DEBUG Sensor cache_nvme temperature is 49°C

Jul 01 2025 04:52:25.339 pid:7 temperature_sensors.py 24 DEBUG Sensor cache_sata temperature is 35°C

Jul 01 2025 04:52:25.339 pid:7 temperature_sensors.py 24 DEBUG Sensor cache_sata2 temperature is 34°C

Jul 01 2025 04:52:25.339 pid:7 temperature_sensors.py 24 DEBUG Sensor flash temperature is *°C

Jul 01 2025 04:52:25.339 pid:7 start.py 70 DEBUG Setting fan OpenFAN/Fan/0 to 60% PWM based on sensor temperature of 41°C

Traceback (most recent call last):

File "/usr/local/lib/python3.10/dist-packages/urllib3/connection.py", line 198, in newconn

sock = connection.create_connection(

File "/usr/local/lib/python3.10/dist-packages/urllib3/util/connection.py", line 85, in create_connection

raise err

File "/usr/local/lib/python3.10/dist-packages/urllib3/util/connection.py", line 73, in create_connection

sock.connect(sa)

ConnectionRefusedError: [Errno 111] Connection refused

The above exception was the direct cause of the following exception:

Traceback (most recent call last):

File "/usr/local/lib/python3.10/dist-packages/urllib3/connectionpool.py", line 787, in urlopen

response = self._make_request(

File "/usr/local/lib/python3.10/dist-packages/urllib3/connectionpool.py", line 493, in makerequest

conn.request(

File "/usr/local/lib/python3.10/dist-packages/urllib3/connection.py", line 445, in request

self.endheaders()

File "/usr/lib/python3.10/http/client.py", line 1278, in endheaders

self._send_output(message_body, encode_chunked=encode_chunked)

File "/usr/lib/python3.10/http/client.py", line 1038, in sendoutput

self.send(msg)

File "/usr/lib/python3.10/http/client.py", line 976, in send

self.connect()

File "/usr/local/lib/python3.10/dist-packages/urllib3/connection.py", line 276, in connect

self.sock = self._new_conn()

File "/usr/local/lib/python3.10/dist-packages/urllib3/connection.py", line 213, in newconn

raise NewConnectionError(

urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x15208cb0ed40>: Failed to establish a new connection: [Errno 111] Connection refused

The above exception was the direct cause of the following exception:

Traceback (most recent call last):

File "/usr/local/lib/python3.10/dist-packages/requests/adapters.py", line 667, in send

resp = conn.urlopen(

File "/usr/local/lib/python3.10/dist-packages/urllib3/connectionpool.py", line 841, in urlopen

retries = retries.increment(

File "/usr/local/lib/python3.10/dist-packages/urllib3/util/retry.py", line 519, in increment

raise MaxRetryError(_pool, url, reason) from reason # type: ignore[arg-type]

urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='192.168.0.5', port=3000): Max retries exceeded with url: /api/v0/fan/0/set?value=60 (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x15208cb0ed40>: Failed to establish a new connection: [Errno 111] Connection refused'))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):

File "/mnt/OpenFanService/start.py", line 150, in <module>

main(None, None, None, None, None)

File "/usr/local/lib/python3.10/dist-packages/click/core.py", line 1442, in call

return self.main(*args, **kwargs)

File "/usr/local/lib/python3.10/dist-packages/click/core.py", line 1363, in main

rv = self.invoke(ctx)

File "/usr/local/lib/python3.10/dist-packages/click/core.py", line 1226, in invoke

return ctx.invoke(self.callback, **ctx.params)

File "/usr/local/lib/python3.10/dist-packages/click/core.py", line 794, in invoke

return callback(*args, **kwargs)

File "/mnt/OpenFanService/start.py", line 147, in main

OpenFan.run_forever(live_reload=arg_live_reload)

File "/mnt/OpenFanService/start.py", line 115, in run_forever

self.update_fan_controls()

File "/mnt/OpenFanService/start.py", line 38, in update_fan_controls

self.update_fan(fan)

File "/mnt/OpenFanService/start.py", line 71, in update_fan

return self.openfan_client.set_fan_pwm(fanData['Identifier'], fan_value)

File "/mnt/OpenFanService/openfan_client.py", line 47, in set_fan_pwm

r = requests.get(f'{self.api_url}/fan/{fan}/set?value={pwm}', verify=False, timeout=(0.5, 1))

File "/usr/local/lib/python3.10/dist-packages/requests/api.py", line 73, in get

return request("get", url, params=params, **kwargs)

File "/usr/local/lib/python3.10/dist-packages/requests/api.py", line 59, in request

return session.request(method=method, url=url, **kwargs)

File "/usr/local/lib/python3.10/dist-packages/requests/sessions.py", line 589, in request

resp = self.send(prep, **send_kwargs)

File "/usr/local/lib/python3.10/dist-packages/requests/sessions.py", line 703, in send

r = adapter.send(request, **kwargs)

File "/usr/local/lib/python3.10/dist-packages/requests/adapters.py", line 700, in send

raise ConnectionError(e, request=request)

requests.exceptions.ConnectionError: HTTPConnectionPool(host='192.168.0.5', port=3000): Max retries exceeded with url: /api/v0/fan/0/set?value=60 (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x15208cb0ed40>: Failed to establish a new connection: [Errno 111] Connection refused'))

Edited July 1, 20251 yr by JayBee_Unraid

@SasaKaranovic Can you please check what is happening with the latest version of the container? You can check the errors I am getting the previous message.

Hey @JayBee_Unraid the logs has [Errno 111] Connection refused

This means that 192.168.0.5 is refusing connection on port 3000

Most likely you don't have the OpenFAN Controller container running on that IP or it's not running on port 3000.

Maybe double check that you have the correct IP and the port specified. Also make sure that the containers can talk to each other (reachable over network).

p.s. You need to have both, the OpenFAN Controller docker and the OpenFAN Unraid Service docker running and properly configured.

1 hour ago, SasaKaranovic said:

Hey @JayBee_Unraid the logs has [Errno 111] Connection refused

This means that 192.168.0.5 is refusing connection on port 3000

Most likely you don't have the OpenFAN Controller container running on that IP or it's not running on port 3000.

Maybe double check that you have the correct IP and the port specified. Also make sure that the containers can talk to each other (reachable over network).

p.s. You need to have both, the OpenFAN Controller docker and the OpenFAN Unraid Service docker running and properly configured.

No I already double checked, and it is on the port 3000, else I would have fixed it already...

I didn't change anything in the config compared to the previous versions, and these versions were running fine.

I also tried with 3210 just in case but it's not working either obviously since it's the web interface port.

Are you sure the container version on the github was updated to the latest one this time? It wasn't the case last time.

Also did you try to do a fresh install on your unraid through your own github address to see what it does on your own machine?

On 7/5/2025 at 5:16 AM, JayBee_Unraid said:

No I already double checked, and it is on the port 3000, else I would have fixed it already...

I didn't change anything in the config compared to the previous versions, and these versions were running fine.

I also tried with 3210 just in case but it's not working either obviously since it's the web interface port.

Are you sure the container version on the github was updated to the latest one this time? It wasn't the case last time.

Also did you try to do a fresh install on your unraid through your own github address to see what it does on your own machine?

@JayBee_Unraid I have both latest versions installed and running without issue. As @SasaKaranovic mentions - and he is correct - some is causing the OpenFanController not to have it's port correctly configured. Can you try to get the log from it (without having OpenFANService running)? You should see the port number there or at least something indicating what the error is. Here's what I see.

For reference for others and just sharing!

I was just testing the new Arctic P12 Pro PST 5-Pack because I'm planning to replace all my fans in my cramped Inter-Tech 4F28 chassis.

Arctic designed the P12 Pro PST to be daisy-chained and according to their specs they draw 0.33A, but they draw more than that!

OpenFanController fan headers are rated at 1.1A and 99% motherboard fan headsers at 1A.

No matter what I did, my experience with both my motherboard (Asus Sabertooth X99) and the OpenFanController was the same:

• If 3 are daisy-chained, connected to one fan header and the PWM exceed 90% > The fans spin down, effectively tripping the fan header fuses. The fans try once in a while to spin up again, but trip the fuses again and spin down.

• If 2 are daisy-chained, connected to one fan header and the PWM exceed 90% > No issues, so far!

• No daisy-chaining and one fan per fan header > No issues at all

This wasn't really expected behaviour, since the fan specs state 0.33A, so I guess Arctic needs to still improve these new fans, but... I will say at 100% PWM they can push some serious airflow! Heck, even at 50% they are amazing and quiet. My Noctua's are getting retired and getting replaced with these.

Edited July 10, 2025Jul 10 by PeterDB

On 7/4/2025 at 8:16 PM, JayBee_Unraid said:

No I already double checked, and it is on the port 3000, else I would have fixed it already...

I didn't change anything in the config compared to the previous versions, and these versions were running fine.

I also tried with 3210 just in case but it's not working either obviously since it's the web interface port.

Are you sure the container version on the github was updated to the latest one this time? It wasn't the case last time.

Also did you try to do a fresh install on your unraid through your own github address to see what it does on your own machine?

You're running the container with bridge networking, so the IP address is 172.17.0.8 with port 3000. Your log shows

On 7/4/2025 at 8:16 PM, JayBee_Unraid said:

No I already double checked, and it is on the port 3000, else I would have fixed it already...

I didn't change anything in the config compared to the previous versions, and these versions were running fine.

I also tried with 3210 just in case but it's not working either obviously since it's the web interface port.

Are you sure the container version on the github was updated to the latest one this time? It wasn't the case last time.

Also did you try to do a fresh install on your unraid through your own github address to see what it does on your own machine?

Port 3210 is the default port for the web UI. It's not the port listening for API connections, which is 3000.

I recommend you re-check your network configuration on the OpenFanController. Here's how to rule out a network issue or confirm the controller is listening correctly.

From any device on the network, confirm that you can ping the IP address of the controller. If you want the controller to just use the IP address of the unRaid server as the destination, set the network type to host. You then just configure the OpenFANService to connect to the unRaid server IP address. If you want to use the fixed IP of 192.168.0.5 (which doesn't appear to be the IP of your unRaid server) then you need to change the network type to one configured for that network.

Once you confirm that the network packets can be delivered to the controller, confirm the controller is listening on that port. From any device on the network, do a "telnet <ip of controller> <port>". If it's able to connect, you'll see the telnet session clear your screen showing that it connected. You can then do a ctrl-c or ctrl-] to exit the session.

This will help you step through where it's failing. If the telnet works, then you at least have confirmed there's nothing on the network layer causing the issue. From what I can tell, you have a network issue and it's not the OpenFAN controller or service.

Edited July 11, 2025Jul 11 by RandoUser

On 7/11/2025 at 10:53 AM, RandoUser said:

You're running the container with bridge networking, so the IP address is 172.17.0.8 with port 3000. Your log shows

That was it! I just needed to switch it to host. Thanks for figuring that out.

On 7/11/2025 at 10:53 AM, RandoUser said:

If you want to use the fixed IP of 192.168.0.5 (which doesn't appear to be the IP of your unRaid server) then you need to change the network type to one configured for that network.

No, that address is the one used my unRaid server, you can see it in the screenshot. No problem with the port either. It was all about the container IP not being the same as the unraid IP.
I believe it was in host before, since it was working, but somehow somewhere on the updates it reverted to bridge, and I didn't notice.

Anyway, thanks for the help.

Is the OpenFan micro supported by the OpenFan Controller? I don't get any RPM reading from the Controller web UI, but the web interface for the micro works and shows the RPM.

Also, I get some other(maybe related?) error in the logs. See below.

192.168.1.2 is my Unraid computer where the micro is installed. 192.168.1.222 is my desktop computer.

500 GET /api/v0/fan/status (192.168.1.222) 6007.29ms

Sep 11 2025 15:13:09.070 pid:7 webserver.py 145 INFO Request:STATUS

Sep 11 2025 15:13:09.070 pid:7 FanCommander.py 24 DEBUG CMD:0 Data: None

Sep 11 2025 15:13:09.070 pid:7 FanCommander.py 25 DEBUG Sending >00

Sep 11 2025 15:13:15.076 pid:7 serial_driver.py 145 ERROR Timeout occured (1757603595.0768938 > 1757603594.070429)

Uncaught exception GET /api/v0/fan/status (192.168.1.222)

HTTPServerRequest(protocol='http', host='192.168.1.2:3210', method='GET', uri='/api/v0/fan/status', version='HTTP/1.1', remote_ip='192.168.1.222')

Traceback (most recent call last):

File "/usr/local/lib/python3.10/dist-packages/tornado/web.py", line 1788, in _execute

result = method(*self.path_args, **self.path_kwargs)

File "/mnt/OpenFan/webserver.py", line 147, in get

rpm = self.handler.get_all_fan_rpm()

File "/mnt/OpenFan/FanCommander.py", line 57, in get_all_fan_rpm

return self._parse_fan_rpm(res)

File "/mnt/OpenFan/FanCommander.py", line 38, in parsefan_rpm

res = response.split("|")

AttributeError: 'bool' object has no attribute 'split'

Appreciate any help I can get.

Edited September 11, 2025Sep 11 by raptorjr

4 hours ago, raptorjr said:

Is the OpenFan micro supported by the OpenFan Controller? I don't get any RPM reading from the Controller web UI, but the web interface for the micro works and shows the RPM.

Hey @raptorjr

Currently the OpenFAN Micro is not supported by the Unraid app, only the OpenFAN Controller.

OpenFAN Micro is designed to be used as a stand-alone device with it's own API and Web UI.

It could be integrated with the existing Unraid app but that would require significant amount of work. And honestly it might be just easier to use a simple script that reads temperature sensor and then makes an API call to update the fan speed.

10 hours ago, SasaKaranovic said:

Hey @raptorjr

Currently the OpenFAN Micro is not supported by the Unraid app, only the OpenFAN Controller.

OpenFAN Micro is designed to be used as a stand-alone device with it's own API and Web UI.

It could be integrated with the existing Unraid app but that would require significant amount of work. And honestly it might be just easier to use a simple script that reads temperature sensor and then makes an API call to update the fan speed.

That was sad to hear. I guess I should have asked before I bought it. But since you made both devices I just assumed that it was just a smaller version of the big one, not that it was a completely new device. A script is probably easy if you know how to do it, unfortunately I don't.

I have to find another solution for my fan needs.

Just one small follow up question. Is there any documentation on how to control the micro through USB? I only find the Web API examples.

13 hours ago, raptorjr said:

That was sad to hear. I guess I should have asked before I bought it. But since you made both devices I just assumed that it was just a smaller version of the big one, not that it was a completely new device. A script is probably easy if you know how to do it, unfortunately I don't.

I have to find another solution for my fan needs.

I'm sorry OpenFAN Micro does not work out of the box for your use-case. The Unraid application right now only supports OpenFAN Controller.
In the future I might add support for it in the original Unraid app or at least add some examples scripts to the documentation to show how it can be integrated. It's actually pretty simple to do but as you said, if you don't know how or don't want to spend time doing it, then it's obviously less than ideal.

It is possible to control the fan over USB but it would require a small firmware change. I have this on my to-do list. Also you would need something (ie. script, app) on the PC side to tell the fan controller what to do.

With that said if it does not work for your use-case, I don't want you to feel like you wasted your time and/or money (and for the controller to become a paper weight)... So please feel free to email me and we can arrange to have you send it back for a refund.

On 9/12/2025 at 10:16 PM, SasaKaranovic said:

I'm sorry OpenFAN Micro does not work out of the box for your use-case. The Unraid application right now only supports OpenFAN Controller.
In the future I might add support for it in the original Unraid app or at least add some examples scripts to the documentation to show how it can be integrated. It's actually pretty simple to do but as you said, if you don't know how or don't want to spend time doing it, then it's obviously less than ideal.

It is possible to control the fan over USB but it would require a small firmware change. I have this on my to-do list. Also you would need something (ie. script, app) on the PC side to tell the fan controller what to do.

With that said if it does not work for your use-case, I don't want you to feel like you wasted your time and/or money (and for the controller to become a paper weight)... So please feel free to email me and we can arrange to have you send it back for a refund.

You seem to be a honest and good man so I appreciate the offer. But trying to send this back would not do that much for me since postage for me would probably be at least half or more of the money I would get back. So I would lose anyway.

But even if there is no support, or no examples to help get it working. Maybe you could at least change the text on your webshop that the micro "works over WiFi and USB" and that it has an "open-source API that allows you to programmatically control your fan over USB".

This implies that it should already be working, not that you have to make changes to the product to get it working. Because control over USB don't work as it is sold now. Just because it gets power over USB, is not the same as works or control over USB.

Then I can only hope that there will be working in the future(or if I find a better solution first), and there will be some examples on how to get started.

Edit:

But I should maybe add that I think it is a cool product, and if I had the use and space for the big controller I would have bought that and everything would have been perfect. Maybe the micro will get the same support and features one day.

Edited September 15, 2025Sep 15 by raptorjr

14 hours ago, raptorjr said:

Maybe the micro will get the same support and features one day.

I can't remember how many times I've been in a position where someone on the internet who is more experienced than I am, helps me by answering my question with "It's actually pretty simple to do". Depending on the day, sometimes it would motivate me to learn how to do it or reassure me that what I'm trying to do is possible and I'm not reinventing the wheel. But if I am just looking to get the damn thing to work so I can do other stuff and not become a "developer" or subject matter expert... then it sucks. I don't want to leave you in that space...

So I found some time and have hacked up the firmware in probably the ugliest way possible to add support for USB API that is also compatible with the Unraid app.
It's not pretty, but I have tested it and it works with the existing docker image without any modifications.

There is a new firmware loading page that you can access here and load the new firmware onto your OpenFAN Micro device.

Then you will have to connect it to your WiFi network (it won't work without this step!) and configure the fan (5V/12V) over the web UI.

After this you can start your docker container and point it to the OpenFAN Micro serial port and it should work.

Please note since the Unraid app is designed for OpenFAN Controller and we are hacking it to work with the OpenFAN Micro, you won't be able to switch fan voltage (5V/12V) through the Unraid app.

It will report the RPM only for the Fan #1, the remaining will always be zero... because OpenFAN Micro supports only one fan.

And you will have to control the fan by setting the PWM value. Setting the RPM will not work because the OpenFAN Micro does not have PID driver implemented (yet?).

Again, please keep in mind that this is a firmware hack... I have tested it for less than a day but it should work regardless. If it does not, please make a GitHub issue for it. Also if you want to take a look at the firmware modification, it's available in the separate branch.

Please note that this is an "unofficial" firmware hack and that you should ideally use the OpenFAN Controller hardware with this docker application, since that is the combination that this docker application was designed for and tested with.
I can't promise if/when, but I'm hoping that maybe in the future this docker application will be modified to support every flavor of the OpenFAN hardware. I have this on my to-do list but it will take a significant amount of time to complete.

15 hours ago, SasaKaranovic said:

I can't remember how many times I've been in a position where someone on the internet who is more experienced than I am, helps me by answering my question with "It's actually pretty simple to do". Depending on the day, sometimes it would motivate me to learn how to do it or reassure me that what I'm trying to do is possible and I'm not reinventing the wheel. But if I am just looking to get the damn thing to work so I can do other stuff and not become a "developer" or subject matter expert... then it sucks. I don't want to leave you in that space...

So I found some time and have hacked up the firmware in probably the ugliest way possible to add support for USB API that is also compatible with the Unraid app.
It's not pretty, but I have tested it and it works with the existing docker image without any modifications.

There is a new firmware loading page that you can access here and load the new firmware onto your OpenFAN Micro device.

Then you will have to connect it to your WiFi network (it won't work without this step!) and configure the fan (5V/12V) over the web UI.

After this you can start your docker container and point it to the OpenFAN Micro serial port and it should work.

Please note since the Unraid app is designed for OpenFAN Controller and we are hacking it to work with the OpenFAN Micro, you won't be able to switch fan voltage (5V/12V) through the Unraid app.

It will report the RPM only for the Fan #1, the remaining will always be zero... because OpenFAN Micro supports only one fan.

And you will have to control the fan by setting the PWM value. Setting the RPM will not work because the OpenFAN Micro does not have PID driver implemented (yet?).

Again, please keep in mind that this is a firmware hack... I have tested it for less than a day but it should work regardless. If it does not, please make a GitHub issue for it. Also if you want to take a look at the firmware modification, it's available in the separate branch.

Please note that this is an "unofficial" firmware hack and that you should ideally use the OpenFAN Controller hardware with this docker application, since that is the combination that this docker application was designed for and tested with.
I can't promise if/when, but I'm hoping that maybe in the future this docker application will be modified to support every flavor of the OpenFAN hardware. I have this on my to-do list but it will take a significant amount of time to complete.

Thank you so much. I will try it. I have some basic knowledge of code, so with examples I can many times cut and paste or modify others code to get something working. But it would probably be uglier than your hack. But when there is USB support for the micro I can at least try and find a solution. Great if it will work with the OpenFan controller software, if not, as long as USB works, maybe I can adapt some other solution with scripts or something. But now there is a possibility to get a working solution.

Sorry for being a pain. I really appreiate that you took the time to do this.

I bought the openfan controller in January and today I hooked up 3 new Noctua fans, they ran for a while and then all the fans stopped. The docker will no longer run.
Altogether there were 8 fans hooked up, could it be the board died?
I notice there are 2 buttons on the board, do they do anything?
All help welcome.
Patrick

Hey Patrick, sorry about later reply. I believe we already resolved your issue over email. :)
If you (or anyone else) are having any issues, it is usually much faster to email me directly.

19 hours ago, SasaKaranovic said:

Hey Patrick, sorry about later reply. I believe we already resolved your issue over email. :)
If you (or anyone else) are having any issues, it is usually much faster to email me directly.

Yes, you have been great support for your product. Very happy with all your help.

I purchased one of these today, I am curious about the enclosures, I know the unit doesn't come with an enclosure but will pay to get one made from a 3d printing company as I don't own a 3d printer.

It looks like there are 3 potential enclosures on the Githb page

Does anyone have pictures of each of the enclosures to help me make a decision on what one I should get printed?

Hello deek

I have printed one for my controller, can't remember which one. I'm back home tomorrow so will have a look and send a picture. Are you in the UK? I can print one off for you and post it.

47 minutes ago, crookers said:

Hello deek

I have printed one for my controller, can't remember which one. I'm back home tomorrow so will have a look and send a picture. Are you in the UK? I can print one off for you and post it.

Yes I am in the UK, thats really nice of you to offer, I would happy send you some beer money if you wanted to do that!