Unable to read fan speed on R630 with iDRAC 8

[MNickelson]

I have a couple servers being monitored and working fine, a 720XD, a 730XD, and a 420 (when it's turned on) but the R630 I have doesn't seem to be filling out the fan speed or responding to adjustments.

Docker logs show the following:

serverManager-1  | > dscada-backend@1.0.0 start /usr/src/app
serverManager-1  | > node src/index.js
serverManager-1  | 
serverManager-1  | [ '/usr/local/bin/node', '/usr/src/app/src/index.js' ]
serverManager-1  | listening on port  8080
serverManager-1  | Loaded server data from disk
serverManager-1  | Highest temperature is 25.000 Setting fan speed 0 %
serverManager-1  | client is subscribing to timer with interval 
serverManager-1  | Highest temperature is 52.000 Setting fan speed 12 %
serverManager-1  | Highest temperature is 51.000 Setting fan speed 9 %
serverManager-1  | (node:26) UnhandledPromiseRejectionWarning: TypeError: Cannot read property '0' of undefined
serverManager-1  |     at /usr/src/app/src/index.js:110:56
serverManager-1  |     at Array.map (<anonymous>)
serverManager-1  |     at updateServers (/usr/src/app/src/index.js:98:44)
serverManager-1  |     at processTicksAndRejections (internal/process/task_queues.js:95:5)
serverManager-1  |     at async updateServerLoop (/usr/src/app/src/index.js:168:2)
serverManager-1  | (Use `node --trace-warnings ...` to show where the warning was created)
serverManager-1  | (node:26) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
serverManager-1  | (node:26) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

The temperature reads and settings are the 420, and the 7x0s followed by what I think is the R630 erroring out.

ipmitool on that server does work:

ipmitool -I lanplus -H 192.168.2.17 -U <user> -P <pass> sensor
SEL              | na         | discrete   | na    | na        | na        | na        | na        | na        | na        
Intrusion        | 0x0        | discrete   | 0x0080| na        | na        | na        | na        | na        | na        
Fan1A            | 6240.000   | RPM        | ok    | na        | 600.000   | 840.000   | na        | na        | na        
Fan2A            | 6240.000   | RPM        | ok    | na        | 600.000   | 840.000   | na        | na        | na        
Fan3A            | 6240.000   | RPM        | ok    | na        | 600.000   | 840.000   | na        | na        | na        
Fan4A            | 6120.000   | RPM        | ok    | na        | 600.000   | 840.000   | na        | na        | na        
Fan5A            | 6120.000   | RPM        | ok    | na        | 600.000   | 840.000   | na        | na        | na        
Fan6A            | 6120.000   | RPM        | ok    | na        | 600.000   | 840.000   | na        | na        | na        
Inlet Temp       | 22.000     | degrees C  | ok    | na        | -7.000    | 3.000     | 42.000    | 47.000    | na

FWIW I'm having the same issue discussed in the other thread and am using servermanager@sha256:b8399fb2b1a067c2d8e6731b43daa739ce2593be3cbe8f34d1770b590c1c4009

Thanks.