OS X SMC Error is System.log

[CrazyC]

I have the pulseway daemon running on 3 different Macs. 2 are Mac Minis and 1 is a Mac Pro.  The 2 Mac Minis have a steady flow of errors like this in their logs:

Mar 30 20:23:52 ny2 kernel[0]: SMC::smcReadKeyAction ERROR TN0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80220d2000
Mar 30 20:23:52 ny2 kernel[0]: SMC::smcReadKeyAction ERROR TB0T kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80220d2000
Mar 30 20:23:52 ny2 kernel[0]: SMC::smcReadKeyAction ERROR F1Ac kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80220d2000
Mar 30 20:23:57 ny2 kernel[0]: SMC::smcReadKeyAction ERROR TN0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80220d2000
Mar 30 20:23:57 ny2 kernel[0]: SMC::smcReadKeyAction ERROR TB0T kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80220d2000
Mar 30 20:23:57 ny2 kernel[0]: SMC::smcReadKeyAction ERROR F1Ac kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80220d2000

From some searching I have done it is likely related to a none existent sensor that the daemon is looking for.  If I had to guess, I would say it's related to fans. The Mac Mini only has 1 cooling fan in it versus the multiple fans in the Mac Pro.

 

It would probably be good to have the option to specify fan monitoring and even other hardware options.

 

The Daemon could display the current state of any item being monitored and if it's error'ed or someting chosen not to monitor, the user can turn that item off and prevent errors like this in the logs.

[Chris]

Hi,

 

Do the error stop if you delete Pulseway from your system? Pulseway only checks for hardware sensors if you request this information from the mobile device.

 

Regards,

Chris

Pulseway Support

[CrazyC]

The errors stop if I stop Pulseway from running, yes.  I should have mentioned that in my first post.

[CrazyC]

Nothing more on this?  It's definitely related to Pulseway.  If I stop Pulseway on either Mac Mini, the errors go away.  There are no SMC errors on my Mac Pro.

[Chris]

Hi,

 

Sorry for the delayed follow up. We confirmed this behaviour with our development team and it will be fixed in a future release.

 

Thank you for your report.

 

Regards,

Chris

Pulseway Support