Auto-Shutdown with APC UPS Does Not Work on M1 Mac Mini (Monterey 12.2.1)

Question

Level 1

11 points

Auto-Shutdown with APC UPS Does Not Work on M1 Mac Mini (Monterey 12.2.1)

Energy Saver Auto-Shutdown options with an UPS are not working on my M1 Mac Mini running Monterey 12.2.1 with APC Back-UPS BE860HG2.

We need the M1 Mac Mini to shutdown after 60 seconds when UPS loses power. I have set this option in the energy saver settings under UPS, but the Mac Mini never shuts down. No matter what I set, it never shuts down or gives any indication of shutting down.

This M1 mac mini has had its data migrated from a Time Machine

backup of an Intel Mac Mini running OS X El Capitan 10.11.6.

The only thing that does work is a warning when the Mac Mini is drawing from the UPS.

Does anyone have any suggestions? Nothing in the previous threads have worked.

Here are the relevant settings:

pmset -g

System-wide power settings:
Currently in use:
 disksleep            10
 powernap             1
 womp                 1
 networkoversleep     0
 sleep                0 (sleep prevented by coreaudiod, bluetoothd, powerd)
 Sleep On Power Button 1
 ttyskeepawake        1
 tcpkeepalive         1
 autorestart          1
 standby              0

pmset -g ups

UPS settings:
  haltlevel on  100
  haltafter on  1
  haltremain    on  15

When UPS plugged in:

Now drawing from 'AC Power'
 -Back-UPS ES 850G2 FW:931.a10.D USB FW:a10 (id=25296896)   74%; charging present: true

When UPS unplugged:

Now drawing from 'UPS Power'
 -Back-UPS ES 850G2 FW:931.a10.D USB FW:a10 (id=25296896)   74%; discharging; 4:14 remaining present: true

This is so frustrating to have a machine that does not do what it is clearly set to do.

Does anyone have any suggestions? I can find zero information on anything that might be causing this.

Mac mini 2018 or later

Posted on Feb 22, 2022 9:29 AM

Reply

Answer 1

Top-ranking reply

jaybeuff Author

Level 1

11 points

Feb 22, 2022 4:59 PM in response to etresoft

This is a Mac Mini, which does not have battery options. (It is not a portable).

I have attached images of the Energy Saver menu at the end of the post. Also, 100% this issue is not with the energy saver preferences. It is guaranteed something deeper with the Monterey.

I dug deeper with Monterey in the activity logs and found these few items:

When the UPS disconnects from AC power I get this dispatch event:

dispatchEvent: {
    "Current Capacity" = 97;
    "Delayed Remove Power" = "-1";
    "Enable Audible Alarm" = 2;
    "Is Charging" = 0;
    "Max Capacity" = 100;
    "Power Source State" = "Battery Power";
    "Set Required Voltage" = 120;
    "Time to Empty" = 333;
    Voltage = 0;
}

Followed by this series of console logs that show the machine detects power has been turned off, and appears to have started a timer. Apologies for the image, its not clear how I can copy all these logs out easily. If you right click "open in new tab" you can see the full res log image for diagnostics.

Reply

Answer 2

Dogcow-Moof

Level 8

36,665 points

Feb 22, 2022 7:52 PM in response to jaybeuff

The fact that your

pmset -g ups

output shows all three options as being on when only one is set means there's a disconnect between the preference pane and your system's actual settings.

Try toggling them all on, setting parameters, and clicking Done, then going back and setting the parameters the way you prefer and see if the state is then reported accurately.

For example, I have this:

and my

pmset -g ups

properly reports:

UPS settings:
  haltlevel	on	25
  haltafter	off	0
  haltremain	off	0

Reply

Answer 3

jaybeuff Author

Level 1

11 points

Feb 22, 2022 8:03 PM in response to etresoft

I've tried playing with settings in multiple configurations but nothing seems to affect it.

Just ran logs in another UPS disconnect. This is the closest to exact 1 minute mark (after disconnect messages as seen in previous image). Technically 6-12 milliseconds after.

Image posted below. (Again right click, open image in tab for full res image)

Log errors in order of appearance:

powerd     disableAppSleep: Setting app nap state to true for 359

Acquiring assertion targeting [daemon<com.apple.metadata.mds.index>:359] from originator [daemon<com.apple.powerd>:99] with description <RBSAssertionDescriptor| "App is holding power assertion" ID:190-99-999 target:359 attributes:[
	<RBSDomainAttribute| domain:"com.apple.appnap" name:"PowerAssertion" sourceEnvironment:"(null)">,
	<RBSAcquisitionCompletionAttribute| policy:AfterApplication>
	]>

updateAppSleepStates: Setting app nap state to false for 359 because all assertions are released

Invalidating assertion 190-99-999 (target:[daemon<com.apple.metadata.mds.index>:359]) from originator [daemon<com.apple.powerd>:99]

Reply

Answer 4

etresoft

Level 9

52,654 points

Feb 22, 2022 4:39 PM in response to jaybeuff

What do your settings in System Preferences > Battery look like? Apple changed this preference pane in Monterey. I'm not sure what it even looks like anymore. Unfortunately, someone would have to have a desktop Mac with Monterey and a UPS in order to even see it. One or more screenshots would be very helpful.

Reply

Answer 5

etresoft

Level 9

52,654 points

Feb 22, 2022 7:09 PM in response to jaybeuff

jaybeuff wrote:

This is a Mac Mini, which does not have battery options. (It is not a portable).

Yes. I know. But without having one, I don't know what it looks like. Actually I do have one - a rental - but it's running Big Sur.

I dug deeper with Monterey in the activity logs and found these few items:

It might be interesting to see what happens after 1 minute. Unfortunately, that would be many thousands of log entries. Based on your ~2 sec screenshot, about 3000 entries for 1 minute.

Followed by this series of console logs that show the machine detects power has been turned off, and appears to have started a timer. Apologies for the image, its not clear how I can copy all these logs out easily. If you right click "open in new tab" you can see the full res log image for diagnostics.

There is an "Additional text" button in the toolbar of the forum edit window.

There are two anomalies from your screenshot that you could look at. For one thing, it is set to never shut down the display. But then the machine shutdown is 1 minute. It is possible that confuses things. Maybe set a time for the screen to shutdown.

For the UPS system shutdown, try changing that to 5 minutes. I think the lowest setting might not register correctly. Plus, sometimes you have to physically change a setting to cause it to take effect.

Another thing you might have to try is completely resetting the computer. There is no way to tell what settings from that ancient 10.11 computer could be confusing to the new system. But that is more of a last resort.

Reply

Answer 6

jaybeuff Author

Level 1

11 points

Feb 22, 2022 8:06 PM in response to Dogcow-Moof

Hi Dogcow-Moof. Disregard the discrepancies between the images and the posted code snippets. They are not both from the exact same moment. (I've posted this on other help sites with no advice so far).

The pmset -g command is always in sync with what the settings are at. I took those followup images because the commenter above you asked to see the Energy Saver prefs pane.

Reply

Answer 7

Dogcow-Moof

Level 8

36,665 points

Feb 22, 2022 8:05 PM in response to jaybeuff

If you're comfortable with the command line, try doing a:

sudo pmset -u haltafter 1 haltlevel -1 haltremain -1

and see if that shuts off haltlevel and haltremain as reported by:

pmset -g ups

The man page is a bit confusing, this might also work:

sudo pmset -u haltafter 1 haltlevel -1 haltremain 0

Finally, you may also want to double check you don't have any of APS' applications installed as they may be changing settings behind your back.

Reply

Answer 8

jaybeuff Author

Level 1

11 points

Feb 22, 2022 8:11 PM in response to Dogcow-Moof

Hi Dogcow-Moof,

As mentioned above, the settings always stay in sync with pmset -g ups etc. Disregard the images not matching the pmset -g ups (they were taken at different times with different settings active).

There are zero (0) ups utilities installed on this Mac. It is only using built in OS.

Reply

Answer 9

jaybeuff Author

Level 1

11 points

Feb 22, 2022 8:29 PM in response to etresoft

I dont understand your comment. See my second post of logs. That is exactly what I did. I went through it all. That screen shot and logs messages I included are 1 full minute later after the UPS was disconnected. I scoured them all for anything meaningful.

1 full minute is only about 6,900 logs and its pretty quick to skim find any patterns or messages related to powerd, ioupsd, runningboardd or kernel processes that might relate to power / timing / dispatch of events.

That section is the only real meaningful thing found in the entire log, next to the standard messages that get repeated by the ioupsd and powerd processes.

Reply

Answer 10

4nNtt

Level 1

14 points

Apr 3, 2022 8:48 PM in response to jaybeuff

I'm seeing a similar issue with an M1 iMac on 12.3.1. A Tripp-lite UPS in this case. It doesn't shut down. It might be a slightly different situation. The UPS always shows 0% current charge in energy saver settings regardless of the actual charge on the UPS.

Console is showing this message repeated over and over:

default 23:43:20.246718-0400 powerd Posted notifications for loss of power source id 5136

Despite reporting this, it is connected to power with a full charge and never actually shuts down when configured to shutdown automatically.

Reply

Answer 11

nigelkay

Level 1

19 points

May 26, 2022 10:55 AM in response to jaybeuff

I have the same issue. I have a Mac Studio with the latest Monterey version, and an Eaton 3S 750 UPS with the USB cable attached. It detects when the system is running on the UPS battery, but does not initiate any of the auto-shutdown options. Seems like a bug in Monterey as I've read a few people having issues with different kinds of UPS.

Reply

Answer 12

jaybeuff Author

Level 1

11 points

May 30, 2022 11:08 AM in response to Satkin

Hi @Satkin,

I did not. I even called apple and spoke with their highest tier tech support, collecting diagnosis, only to later find out the technician never submitted any of the info to the engineering team like they were supposed to. They completely dropped the ball.

The second senior technician I spoke to is the one who figured out the first never submitted anything. Unfortunately for me though I had already shipped the M1 Mac off to a museum for an art show so I had no way to gather new diagnostics.

I would highly suggest you cal apples support line and ask for highest level support technician. It’s a process but the best possibility at solving this issue for yourself and others like us.

From talking to the technicians none had any idea about this issue. They were sending all this diagnostics to the engineering team to find out more. This is what they would do with your case as well

Also I’ve spoken with the ups manufacturers and it’s definitely a bug with Monterey or M1 macs somehow.

So yeah definitely reach out to support.