[[6.9.2] Fix for Unassigned Devices temperature notifications]

Ah--that's excellent, thanks. The new approach of passing the appropriate $disk or $dev to check_temp (rather than just $name) makes a bunch of sense.

[[6.9.2] Fix for Unassigned Devices temperature notifications]

Hmm...very strange--the code you posted doesn't match the version of the monitor script I'm running. On my 6.9.2 install, /usr/local/emhttp/plugins/dynamix/scripts/monitor calls check_temp thusly:

 

// check array devices
foreach ($disks as $disk) {
..
// process disk temperature notifications
  check_temp($name,$disk['temp'],$text,$info);
..
}

// check unassigned devices
foreach ($devs as $dev) {
..
// process disk temperature notifications
  check_temp($name,$temp,$text,$info);
..
}

 

This explains why the tweak I posted makes check_temp work properly on my system, but doesn't explain why my 6.9.2 monitor code differs from what you expect.

 

Might the code you posted be from a post-6.9.2 revision?

[[6.9.1] Setting warning/critical temperature in SMART settings not possible]

+1

 

Under 6.9.2, the smart-one.cfg file behaves properly, in that GUI changes show up in the file and vice-versa.

 

However, I still get over-temp notifications in cases that I should not.

[[6.9.2] Mover does not move symlink files targeting non-existent files]

I'm unsure on the right priority for this--it is certainly not an Urgent data-loss emergency, but also seems more than Minor, as it can be a significant problem for those relative few unlucky enough to run into it.