UPSCLI_UPSERROR(3)

🎀 UPSCLI_UPSERROR(3) — the NUT Manual, but make it cute 🎀

okay bestie, welcome to the NUT Manual page for upscli_upserror ✨ this one's a lil guy, but he's important, so let's go 💅

---

✨ NAME ✨

upscli_upserror — get the current error number for a connection 🫶

---

🌸 SYNOPSIS 🌸

#include <upsclient.h>

int upscli_upserror(UPSCONN_t *ups);

like, that's the whole vibe. short. iconic. no cap 💖

---

🦋 DESCRIPTION 🦋

so the way this works: upscli_upserror() takes the pointer ups — which points at a UPSCONN_t state structure — and hands you back the value of the internal error number, if there even is one. that's it. that's the function. lowkey obsessed with how simple that is 🍓

you'll typically use this to check for specific error values, like UPSCLI_ERR_UNKCOMMAND. and that specific error? it's literally the glow-up trick for detecting older versions of upsd(8) that might not support a given command. old upsd doesn't know the command, you get UPSCLI_ERR_UNKCOMMAND, and now you know what era you're dealing with. iykyk 😌

also important, bestie: some error messages have extra meanings layered on top, so you should use upscli_strerror(3) to get the readable error messages. the number is the number, but the string is the ✨lore✨.

---

💖 RETURN VALUE 💖

upscli_upserror() returns one of the UPSCLI_ERR_* values from upsclient.h, or 0 if no error has occurred. so 0 is the "we're so back" result, and everything else is a little situation you should probably look into 👑

---

🌈 SEE ALSO 🌈

• upscli_readline(3)
• upscli_sendline(3)
• upscli_strerror(3)

---

bestie reminder 💀: the number tells you what kind of problem, but upscli_strerror(3) tells you what it means. don't skip it, fr fr.

---

okay that's the page!! go forth and handle your errors, main character 🌟

Network UPS Tools 2.8.5 — dated 10/07/2026, and this page is UPSCLI_UPSERROR(3) 💜