17 minutes ago, spl147 said:

This plugin is dead, use the fan control plus plugin

I just did, but still no PWM controller.

What actual hardware? probably too new/rare.

50 minutes ago, Kilrah said:

What actual hardware? probably too new/rare.

Odroid H4+ I think more and more people are using it as a minimalist board for basic usage.

I didn’t say it would work, was just stating the plugin is not actively maintained. Sensors-detect clearly states there is no driver available. This is why i keep saying research first purchase second

12 minutes ago, spl147 said:

I didn’t say it would work, was just stating the plugin is not actively maintained. Sensors-detect clearly states there is no driver available. This is why i keep saying research first purchase second

There is a driver, I just don't know how to install it under Unraid. https://wiki.odroid.com/odroid-h4/application_note/fan_speed_control_with_temp

If anyone got the same issue, I found the driver, it's called IT87 Driver plugin.

On Unraid 7.20-beta1, I believe the Dynamix System Temperature plugin 2024.07.10 started flooding my logs with the following error:

[08-Aug-2025 08:59:56 Europe/Berlin] PHP Warning: Undefined array key 1 in /usr/local/emhttp/plugins/dynamix.system.temp/nchan/system_temp on line 78

[08-Aug-2025 08:59:57 Europe/Berlin] PHP Warning: Undefined array key 1 in /usr/local/emhttp/plugins/dynamix.system.temp/nchan/system_temp on line 78

[08-Aug-2025 08:59:58 Europe/Berlin] PHP Warning: Undefined array key 1 in /usr/local/emhttp/plugins/dynamix.system.temp/nchan/system_temp on line 78

[08-Aug-2025 08:59:58 Europe/Berlin] PHP Warning: Undefined array key 1 in /usr/local/emhttp/plugins/dynamix.system.temp/nchan/system_temp on line 78

[08-Aug-2025 08:59:58 Europe/Berlin] PHP Warning: Undefined array key 1 in /usr/local/emhttp/plugins/dynamix.system.temp/nchan/system_temp on line 78

[08-Aug-2025 08:59:59 Europe/Berlin] PHP Warning: Undefined array key 1 in /usr/local/emhttp/plugins/dynamix.system.temp/nchan/system_temp on line 78

[08-Aug-2025 09:00:00 Europe/Berlin] PHP Warning: Undefined array key 1 in /usr/local/emhttp/plugins/dynamix.system.temp/nchan/system_temp on line 78

[08-Aug-2025 09:00:00 Europe/Berlin] PHP Warning: Undefined array key 1 in /usr/local/emhttp/plugins/dynamix.system.temp/nchan/system_temp on line 78

[08-Aug-2025 09:00:00 Europe/Berlin] PHP Warning: Undefined array key 1 in /usr/local/emhttp/plugins/dynamix.system.temp/nchan/system_temp on line 78

[08-Aug-2025 09:00:00 Europe/Berlin] PHP Warning: Undefined array key 1 in /usr/local/emhttp/plugins/dynamix.system.temp/nchan/system_temp on line 78

On 4/12/2024 at 2:22 PM, Rysz said:

Dynamix System Temperature

Probably low priority but a bunch of PHP8 warnings if one of the temperatures is not used:

 

[12-Apr-2024 14:19:41 Europe/Berlin] PHP Warning:  Undefined array key 1 in /usr/local/emhttp/plugins/dynamix.system.temp/nchan/system_temp on line 78
[12-Apr-2024 14:19:57 Europe/Berlin] PHP Warning:  Undefined array key 1 in /usr/local/emhttp/plugins/dynamix.system.temp/nchan/system_temp on line 78
[12-Apr-2024 14:19:57 Europe/Berlin] PHP Warning:  Undefined array key 1 in /usr/local/emhttp/plugins/dynamix.system.temp/include/SystemTemp.php on line 42
[12-Apr-2024 14:20:02 Europe/Berlin] PHP Warning:  Undefined array key 1 in /usr/local/emhttp/plugins/dynamix.system.temp/nchan/system_temp on line 78
[12-Apr-2024 14:20:07 Europe/Berlin] PHP Warning:  Undefined array key 1 in /usr/local/emhttp/plugins/dynamix.system.temp/nchan/system_temp on line 78
[12-Apr-2024 14:20:12 Europe/Berlin] PHP Warning:  Undefined array key 1 in /usr/local/emhttp/plugins/dynamix.system.temp/nchan/system_temp on line 78
[12-Apr-2024 14:20:17 Europe/Berlin] PHP Warning:  Undefined array key 1 in /usr/local/emhttp/plugins/dynamix.system.temp/nchan/system_temp on line 78
[12-Apr-2024 14:20:22 Europe/Berlin] PHP Warning:  Undefined array key 1 in /usr/local/emhttp/plugins/dynamix.system.temp/nchan/system_temp on line 78

 

That appears to be it. Should be higher priority given the impact on the logs and unnecessary CPU load. Mine fired multiple times a second and var/log filled up in just a few days.

Auto fan control is spamming my syslog file. with "adjusting fan speed" How do I prevent this and causing my syslog file to become too large?

Hello, i just discovered your System stats plugin, it looks great is well intergrated but i miss a major function! To be able to keep track of my nas temps over time, is this possible to add somehow? Thanks!

Bug Report: Duplicate remote syslog messages when S3 Sleep plugin debug mode is set to Syslog

Environment

• Unraid OS 7.1.4 (NAS: 10.1.1.17)

• Dynamix S3 Sleep plugin v3.0.11

• Syslog forwarding enabled (remote syslog-ng server on Alpine Linux, UDP 514)

Issue
When the S3 Sleep plugin’s Debug Mode is set to Syslog, every debug message is emitted twice to the syslog stream.

• On the local Unraid syslog (/var/log/syslog), messages appear only once.

• On the remote syslog server, tcpdump confirms that two identical UDP packets are sent for each event.

• Example (tcpdump from the remote server, capturing from NAS):

10:57:08.124480 10.1.1.17.46104 > 10.1.1.12.514: SYSLOG Msg: Sep  7 10:57:08 NAS s3_sleep: Disk activity on going: sdc
10:57:08.124483 10.1.1.17.50879 > 10.1.1.12.514: SYSLOG Msg: Sep  7 10:57:08 NAS s3_sleep: Disk activity on going: sdc
10:57:08.125477 10.1.1.17.46104 > 10.1.1.12.514: SYSLOG Msg: Sep  7 10:57:08 NAS s3_sleep: Disk activity detected. Reset timers.
10:57:08.125496 10.1.1.17.50879 > 10.1.1.12.514: SYSLOG Msg: Sep  7 10:57:08 NAS s3_sleep: Disk activity detected. Reset timers.

That results in duplicate lines being written to the remote syslog-ng log files and any downstream viewers (Frontail, etc).

Steps to reproduce

1. Enable Dynamix S3 Sleep plugin.

2. Set Enable DEBUG mode: → Syslog.

3. Configure Unraid → Settings → Syslog Server → enable forwarding to a remote server (default port 514).

4. Observe via tcpdump on the remote server:

   tcpdump -n -i any host <NAS-IP> and udp port 514 -vvv
   

   Each S3 Sleep debug message is transmitted twice.

Expected
Each debug message should be sent only once.

Actual
Each debug message is sent twice when “Debug Mode = Syslog.”

Notes / Workarounds

• Setting Debug Mode to Console avoids the duplication (but then you lose visibility in central syslog).

• Forwarding Unraid’s main syslog to a different port 1514 (Settings → Syslog Server → Remote) does not duplicate messages. The duplication appears to come from how the plugin itself calls logger/syslog.

• A possible cause: the plugin might be writing directly to syslog and also to stdout/stderr which gets captured by syslog, resulting in two emits.

I have a question about the Dynamix Sleep Plugin. For example, if the disk array is inactive but I am operating unraid, how can I avoid system sleep at this time? The effect I want is like Windows. When I don't have the operating system, for example, it will sleep for 5 minutes. If it is operating, it should not sleep.

Edited September 8, 2025Sep 8 by valenhua

The issue I'm having is that I'm unable to connect to my shares via SMB after the NAS wakes from sleep. The SMB connections work fine on a fresh boot. But if the NAS goes to sleep, and I wake it up either with a WOL packet or pressing the power button on the side of the NAS, I am no longer able to make a SMB connection to any of those same shares.

I am running unraid 7.1.4 and have the S3 Sleep plugin installed.

after sending a WOL packet, the NAS wakes up and I can connect via the webGUI. But trying to access the mapped SMB shares from either my phone or desktop doesn't work. If I reboot the NAS, every works again until the next time the NAS sleeps and asked to wake back up.

UPDATE: I am testing a possible solution - I had set "DHCP Renewal after wake-up" = "Yes". Setting this to "No" might have fixed the issue. I'm going to test some more and will provide another update.

UPDATE: After some additional testing, I can confirm that the issue was caused by setting "DHCP Renewal after wake-up" = "Yes". By setting it to "No", the NAS will wake from sleep with a WOL packet and I can connect to my shares with SMB from my desktop and phone.

Thanks,

sethree

Edited September 11, 2025Sep 11 by sethree

Is anybody here to support the s3 sleep plugin?

44 minutes ago, helgrimm said:

Is anybody here to support the s3 sleep plugin?

rather ask your question instead ask to ask ...

Anyone else seeing the Dynamix plugins as blacklisted in action center?

2 hours ago, lambolighting said:

Anyone else seeing the Dynamix plugins as blacklisted in action center?

Just saw it now too, wtf?

Probably something similar to https://forums.unraid.net/topic/38582-plug-in-community-applications/page/188/#comment-1566749

Working on the Dynamix problem

Hello Dynamix team, @bonienl and @Squid - I have been waiting patiently for a while for the Parity/Read-Check issue to be fixed.

Premise - If someone doesn't have a parity disk the Parity schedule settings don't show up in the schedule section in the settings menu. Read-Check can still be done.

Issue - The old versions of UnRaid used to have Read-Check schedule in case someone doesn't have Parity. I did that all the time. Still do that.

Someone like me who had a Schedule setup for Read-Check can still use the same schedule as the config exists '/boot/config/plugins/dynamix/dynamix.cfg ' and has the relevant section for that. However, I cannot change those settings without editing the config manually.

[parity]
mode="0"
dotm="1"
hour="0 13"
day="2"
month="2"
write="NOCORRECT"
frequency="1"
duration="1"

I do not have the documentation to know what possible values I can set them to if I need to change the settings. So, I have just let things run as is.

Unless, there is a reason that has not been explained why this section was removed from UI for people without parity, when can I expect it to come back. It is still possible to do those Read-Checks, why take away the scheduling part.

Thanks and looking forward to the response.

10 minutes ago, Unraid-arr said:

Hello Dynamix team, @bonienl and @Squid - I have been waiting patiently for a while for the Parity/Read-Check issue to be fixed.

Premise - If someone doesn't have a parity disk the Parity schedule settings don't show up in the schedule section in the settings menu. Read-Check can still be done.

Issue - The old versions of UnRaid used to have Read-Check schedule in case someone doesn't have Parity. I did that all the time. Still do that.

Someone like me who had a Schedule setup for Read-Check can still use the same schedule as the config exists '/boot/config/plugins/dynamix/dynamix.cfg ' and has the relevant section for that. However, I cannot change those settings without editing the config manually.

[parity]
mode="0"
dotm="1"
hour="0 13"
day="2"
month="2"
write="NOCORRECT"
frequency="1"
duration="1"

I do not have the documentation to know what possible values I can set them to if I need to change the settings. So, I have just let things run as is.

Unless, there is a reason that has not been explained why this section was removed from UI for people without parity, when can I expect it to come back. It is still possible to do those Read-Checks, why take away the scheduling part.

Thanks and looking forward to the response.

7.2 but weirdly its gone missing from the notes, im sure i saw it there. But at least its here again in writing. https://forums.unraid.net/topic/193500-unraid-read-check/#findComment-1578307

1 hour ago, Mainfrezzer said:

7.2 but weirdly its gone missing from the notes, im sure i saw it there. But at least its here again in writing. https://forums.unraid.net/topic/193500-unraid-read-check/#findComment-1578307

Thanks for this, it gives me hope. I am not sure why it was removed in the 1st place. But glad to see it is returning.

Thanks

Just wondering, is the Dynamix Share Floor plugin still being supported? it's not really doing anytihng anymore.

Does someone know how to get attention of the maintainer of the bergware/dynamix github repo? -> https://github.com/bergware/dynamix
AravindGopala from GitHub took the time to fix the bug in the S3SleepPlugin and we are trying to get this in via a Pull Request:
https://github.com/bergware/dynamix/pull/102

This fix makes the S3SleepPlugin usable again, should be interesting for anyone who was using it in the past.

Any help would be appreciated. Thanks!

Hi, i´m running with JGINYUE X99M GAMING D4/ARGB , Version V2.1 and i can see that the fans works better w/o the Fan Auto Control pluging and with the Bios settings on Auto, thanks!