From 6f6c5cdd85e96251c399f71a36f376845281353d Mon Sep 17 00:00:00 2001 From: tdfountain <174762217+tdfountain@users.noreply.github.com> Date: Sat, 19 Apr 2025 02:10:23 -0700 Subject: [PATCH] Add known limitations to NUT (#38388) Co-authored-by: J. Nick Koston --- source/_integrations/nut.markdown | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/source/_integrations/nut.markdown b/source/_integrations/nut.markdown index 0f7d6448ed5..1e1579043c9 100644 --- a/source/_integrations/nut.markdown +++ b/source/_integrations/nut.markdown @@ -28,6 +28,10 @@ related: The **Network UPS Tools (NUT)** {% term integration %} allows you to monitor and manage an Uninterruptible Power Supply (UPS) for battery backup, a Power Distribution Unit (PDU), or other similar power device using a [NUT](https://networkupstools.org/) server. It lets you view the status, receive notifications about important events, and execute commands as device actions for one or more such devices. +This integration cannot communicate directly with a UPS or power device. +For this reason, a NUT server is required. The integration talks to the +NUT server using the NUT protocol to retrieve data and status information. + ## Supported devices This integration supports hardware devices compatible with @@ -332,6 +336,18 @@ automation: message: "The UPS lost power and is now on battery" ``` +## Known limitations + +Not all NUT functionality is available through this integration. The +following are known limitations: + +- This NUT integration only supports a subset of NUT "variables" and +"commands". +- This NUT integration only supports retrieving, but not setting, NUT +"variables". +- This NUT integration does not support NUT "commands" that require +parameters. + ## Troubleshooting ### Using NUT to list all variables