From LedHed's Wiki
(Created page with "== Overview == I ran into some issues with NUT and my new Tripp Lite SMART1500LCDXL and wanted to post me notes so others can benefit. == Issue == MUT would post a wall messa...") |
|||
| Line 1: | Line 1: | ||
== Overview == | == Overview == | ||
I ran into some issues with NUT and my new Tripp Lite SMART1500LCDXL and wanted to post me notes so others can benefit. | I ran into some issues with NUT and my new Tripp Lite SMART1500LCDXL and wanted to post me notes so others can benefit. | ||
| + | |||
== Issue == | == Issue == | ||
Latest revision as of 09:38, 14 April 2021
Contents
Overview
I ran into some issues with NUT and my new Tripp Lite SMART1500LCDXL and wanted to post me notes so others can benefit.
Issue
MUT would post a wall message stating that it lost connection with the UPS and then post that the data was stale.
Resolution
I initially set the pollinterval to 15 seconds, but started getting the disconnect issue. It turns out that the UPS likes to be polled by the driver every 1/2 second. NUT by default sets a 'pollinterval' of 2 seconds which seems to be frequent enough to prevent the disconnect. So I just commented out the pollinterval line in ups.conf, you could set it to a value of 1 but 2 seems to be enough.
ups.conf
[ups1]
driver = "usbhid-ups"
port = "auto"
desc = "Tripp Lite SMART1500LCDXL"
vendor = "Tripp Lite"
vendorid = "09ae"
productid = "2012"
# pollinterval = 1
bus = "001"
Reference
https://alioth-lists.debian.net/pipermail/nut-upsdev/2019-June/007440.html