Community Solution

Use NUT and PeaNUT with ZimaOS UPS

A community user reported that enabling ZimaOS UPS power-loss protection allowed a GoldenMate Pro UPS to be recognized and then exposed to a PeaNUT dashboard.

What Solved GoldenMate UPS Detection in ZimaOS

The community update reported that enabling and configuring ZimaOS UPS power-loss protection caused a GoldenMate Pro UPS to be recognized. The same post also clarified an important distinction: PeaNUT is a dashboard for NUT data, while Network UPS Tools provides the backend services that communicate with the UPS.

For sizing and deployment context, UPS monitoring is a lightweight service compared with the broader workloads on ZimaBoard 2 or ZimaCube 2.

NUT Backend vs PeaNUT Dashboard

Component Role
NUT drivers / upsd Communicate with the UPS and expose UPS data to clients
upsmon Monitors UPS state and can coordinate shutdown behavior
PeaNUT Displays NUT server information in a web interface

The current NUT documentation describes upsmon as the monitor and shutdown controller and supports monitoring remote systems through an upsd server. See NUT upsmon documentation and NUT upsd documentation.

Verify ZimaOS Before Installing Duplicate NUT Services

The community poster reported that ZimaOS 1.5.3 and later included NUT tooling in their environment. Before adding a separate NUT container, enable the built-in UPS protection feature and inspect the terminal for available NUT commands. Running two independent backends against the same USB UPS can complicate device ownership and monitoring.

Connect PeaNUT After the Backend Works

  1. Confirm ZimaOS detects the UPS and reports power state.
  2. Identify the NUT server name, host, port and credentials used by the local configuration.
  3. Add that NUT server to PeaNUT.
  4. Verify battery percentage, line status and load values update correctly.
  5. Simulate a safe test condition before relying on automatic shutdown.

Coordinating Shutdown of Other Devices

The next question in the thread was how to notify a Synology NAS and Mac mini during an outage. NUT supports a primary/secondary monitoring model, so other systems can run a compatible monitoring client against the NUT server and initiate their own shutdown policy. Do not copy shutdown commands blindly: each OS needs its own tested service, credentials and timing policy.

FAQ

Does installing PeaNUT automatically install NUT?

No. PeaNUT is a dashboard and expects access to a functioning NUT backend.

Should I run another NUT container if ZimaOS already detects the UPS?

Usually not as the first step. Verify the built-in service and expose its data cleanly before adding another backend.

Can one UPS shut down multiple machines?

Yes, NUT is designed for network monitoring, but each secondary machine needs a tested monitoring and shutdown configuration.