• 17 Posts
  • 341 Comments
Joined 4 months ago
cake
Cake day: May 14th, 2026

help-circle

















  • As a follow up, I’m curious to hear from lurkers here or those who are thinking about self-hosting (but haven’t started yet); which approach appeals (using the “media at home” example in OP) and why? We’re all pretty much damned souls here but it might be interesting to hear from someone just starting out.


  • I can dig it…but surely the simple option is to have the PC wake up on power restoration, right?

    Set the BIOS to “restore last state after AC loss” and let the UPS do its basic job. If power returns before the battery dies, the PC never shuts down. If the battery does die, the PC loses AC while running, then powers back up when AC returns.

    Does that not achieve the same outcome?

    I get the idea of Pi + NUT + WoL setup (especially if you want a clean shutdown). It just seems…a lot for a single machine.

    (He said, conspicuously hiding the shopping cart of solar panels and marine batteries)


  • I’m not sure if there’s a fundamental misunderstanding but I felt a need to clarify that NUT works with a UPS. It isn’t either or. Whether you’ve got a homelab or a single desktop PC, you need some piece of software which can see when the UPS goes “Oh shit, power is gone” and instruct the machine(s) to shut down cleanly. NUT is that software.

    Could be. In context, the respondent was discussing the use of a raspberry pi - between their UPS and their single Lenovo minipc - as a stand-alone home device. Why? Don’t know.

    To my understanding, the sequence is (or should be)

    Mains fails -> UPS supplies battery power -> UPS reports its battery state over USB -> software on the PC shuts the OS down.

    Using a Pi as a dedicated NUT server makes sense when several machines need the same UPS…for one PC, it seems like an extra machine in the chain (for the sake of an extra machine in the chain).

    That’s sort of what I meant: things get overbuilt. Maybe for fun.