MGE-SHUT(8)

✨ mge-shut β€” the SHUT protocol driver bestie πŸ’…

okay so real talk, this is the manual page for mge-shut, and it lives in section 8 of the NUT Manual. It's the driver for SHUT Protocol UPS equipment. She's niche, she's specific, she's iconic. Let's get into it 🫢


🌸 NAME 🌸

mge-shut β€” Driver for SHUT Protocol UPS equipment ⚑


πŸŽ€ SYNOPSIS πŸŽ€

mge-shut -h

mge-shut -a UPS_NAME [OPTIONS]
Note β€” this man page is ONLY about the hardware-specific stuff for the mge-shut driver. The core driver lore lives elsewhere, bestie. For all that, go read nutupsdrv(8). πŸ’–

πŸ¦‹ SUPPORTED HARDWARE πŸ¦‹

mge-shut supports all recent Eaton, MGE and Dell UPS models which use the SHUT protocol. And yes, SHUT stands for Serial HID UPS Transfer, now you know, iykyk ✨

Older MGE models β€” think Pulsar ESV+, Pulsar EX and Pulsar ES+ β€” are on a whole different vibe. They use the U-Talk protocol, so they should use the mge-utalk driver instead. Different era, different protocol, no notes πŸ™ˆ


πŸ’… EXTRA ARGUMENTS πŸ’…

This driver also supports the following optional settings. Yes, "extra" β€” she's giving main character energy and taking bonus config πŸŽ€

  • lowbatt=num β€” sets the low battery warning threshold, aka the moment shutdown gets initiated by upsmon(8). The factory default value is 30 (in percent), and whether you can change it is settable depending on the exact model. Some models just say no, and honestly? respect πŸ’œ
  • offdelay=num β€” sets the timer before the UPS gets turned off after the kill power command is sent (that's the one you send via the -k switch). The default value is 20 (in seconds). Usually this must be lower than ondelay, but lowkey the driver will NOT warn you on startup if it isn't. It's just gonna let you live your truth 😭
  • ondelay=num β€” sets the timer for the UPS to switch on in case the power comes back after the kill power command was sent but before the actual switch off. The whole point is making sure the machines connected to the UPS are, in all cases, rebooted after a power failure. The default value is 30 (in seconds). Usually this must be greater than offdelay, but again, the driver will not warn you upon startup if it isn't. Some UPSes will restart no matter what, even if the power is (still) out at the moment this timer elapses. In that case, you could try if setting ondelay = -1 in ups.conf helps. Fingers crossed bestie 🀞
Warning β€” the ondelay parameter was set in ten-seconds unit in the legacy mge-shut(8) driver (e.g. 3 for 30 seconds). It is now set in seconds (30 for 30 seconds). Make sure you use the correct unit in your configuration. Not me having a units glow-up and forgetting to tell everyone πŸ’€
  • notification=num β€” set notification type to 1 (no), 2 (light) or 3 (yes). This argument is ignored. It is only here for backward compatibility. She's a legacy queen, she stays, she does nothing πŸ‘‘

πŸ’€ KNOWN ISSUES πŸ’€

Repetitive timeout and staleness

Some models tend to be unresponsive with the default polling frequency. The result is that you have some "data stale" errors in your system log. Not the vibe. πŸ™ˆ

In this case, simply modify the general parameter pollinterval to a higher value (like 10 for 10 seconds). This should solve the issue. Slay πŸ’…

Using notification=3 might also help. (Yes, the same one that's otherwise ignored. She's helping from the bench 🫢)


πŸ‘‘ AUTHOR πŸ‘‘

Arnaud Quette


🌈 SEE ALSO 🌈

The core driver

Internet resources


okay that's the whole page, bestie ✨ every flag, every default, every warning, all accounted for, no cap πŸŽ€

this was Network UPS Tools 2.8.5, dated 10/07/2026 β€” mge-shut(8), out πŸ’–πŸ¦‹πŸŒΈ periodt

πŸ“¦ where this page comes from