eneru 4.11

Intelligent UPS Monitoring & Shutdown Orchestration for NUT

⚡ Eneru

UPS monitoring and shutdown orchestration for NUT

A Python-based UPS monitoring daemon that watches UPS status via Network UPS Tools (NUT) and executes configurable shutdown sequences during power events.

Documentation • Getting Started • Configuration • Changelog

---

Why Eneru?

Most UPS shutdown solutions handle a single system. Eneru handles multiple systems:

Challenge	Eneru Solution
Multiple servers need coordinated shutdown	✅ Orchestrated multi-server shutdown via SSH
VMs and containers need graceful stop	✅ Libvirt VM and Docker/Podman container handling
Network mounts hang during power loss	✅ Timeout-protected unmounting
No visibility during power events	✅ Notifications via 100+ services
Different systems need different commands	✅ Per-server custom shutdown commands
Hypervisors need VM shutdown before host	✅ Pre-shutdown actions (Proxmox, ESXi, XCP-ng, libvirt)
Battery estimates are unreliable	✅ Multi-vector shutdown triggers
Network down during outage	✅ Non-blocking notifications with persistent retry

---

Use cases

Homelabs, virtualization hosts (Proxmox, ESXi, libvirt), Docker/Podman container hosts, NAS systems (Synology, QNAP, TrueNAS), multi-server environments on a single UPS, and mixed physical/virtual setups.

---

Quick start

Installation

PyPI:

pip install eneru[notifications]

Debian/Ubuntu:

curl -fsSL https://m4r1k.github.io/Eneru/KEY.gpg | sudo gpg --dearmor -o /usr/share/keyrings/eneru.gpg
echo "deb [arch=all signed-by=/usr/share/keyrings/eneru.gpg] https://m4r1k.github.io/Eneru/deb stable main" | sudo tee /etc/apt/sources.list.d/eneru.list
sudo apt update && sudo apt install eneru

RHEL/Fedora:

sudo dnf install -y epel-release
sudo curl -o /etc/yum.repos.d/eneru.repo https://m4r1k.github.io/Eneru/rpm/eneru.repo
sudo dnf install eneru

Configuration

# Edit configuration
sudo nano /etc/ups-monitor/config.yaml

# Validate and start
sudo python3 /opt/ups-monitor/eneru.py --validate-config
sudo systemctl enable --now eneru.service

Minimal Config

ups:
  name: "UPS@192.168.1.100"

triggers:
  low_battery_threshold: 20
  critical_runtime_threshold: 600

local_shutdown:
  enabled: true

See the full documentation for complete configuration options.

---

Features

• Multiple shutdown triggers: battery %, runtime, depletion rate, time on battery, FSD flag
• Orchestrated shutdown of VMs, containers, remote servers, filesystems, and the local system
• Notifications to 100+ services (Discord, Slack, Telegram, ntfy, email) via Apprise, with non-blocking persistent retry
• Power quality monitoring: voltage, AVR, bypass, and overload detection
• Dry-run mode for safe configuration testing
• Unit tests, integration tests across 7 Linux distros, and E2E tests with real NUT/SSH/Docker services on every commit

---

Why a systemd daemon? (No Docker)

Eneru runs as a systemd daemon, not a container. It shuts down Docker/Podman containers during power events, so running inside a container would mean getting killed during its own shutdown sequence.

See the documentation for the full explanation.

---

The name

Named after Eneru (エネル) from One Piece, the self-proclaimed God of Skypiea who ate the Goro Goro no Mi (Rumble-Rumble Fruit) and can control electricity. When the power from the grid fails, this tool takes over and shuts everything down safely. Unlimited power... management!

---

Documentation

Full documentation at eneru.readthedocs.io:

• Getting Started - installation and basic setup
• Configuration - full config reference
• Shutdown Triggers - how shutdown decisions work
• Notifications - Discord, Slack, Telegram, etc.
• Remote Servers - SSH setup for NAS and other servers
• Testing - testing strategy and coverage
• Troubleshooting - common issues and solutions

---

License

MIT License - See LICENSE file for details.