similar to: Constant "on battery" and "on line power" status changes

Hello all, About a month ago Peter and Charles were kind enough to try to help me with getting a Tripp Lite USB UPS to work with NUT. I reported quite a bit of initial success, and then other things here fell apart. Between work, fence building and a week-long out of town business trip, I have had to drop this from my list of things to do lately. I am back at it, and I believe I will have

The 2.0.2+ tripplitesu drivers do not recognize SmartOnLine SU2200XL and possibly other SmartOnLine UPSes. Here is a one-line fix. Lee --- ../nut-2.0.2/drivers/tripplitesu.c Thu Jan 27 08:33:21 2005 +++ drivers/tripplitesu.c Sat Oct 1 13:38:51 2005 @@ -227,7 +227,7 @@ buffer[4] = '\0'; if (!strcmp(buffer, "~00D")) { - if (ser_get_buf_len(upsfd, buffer, 4, 3, 0) <=

Hi Al, I'm currently not much available, so I've fwded your mail to the nut list... You might get more reactivity this way... 2007/11/20, Al Grimstad <al at grimstad.mv.com>: > Hi. I don't have the energy or time to subscribe to one of the nut > mailing lists, but this brief FYI may be useful. > > I believe there has been a regression with respect to nut and the

To all, I attempted to configure the UPS tools for the Tripp-Lite SmartOnline 1500VA 2U rackmount UPS. I followed the instructions from the 'upsdrvctl start' output and posted the diagnostic information below. Is my UPS using an unknown product ID as reported? From the mailing list archive, I have found another posting for the same UPS with device model '09AE/4003', whereas

I'm having trouble with a TrippLite SU3000XLCD. I'm using a Raspberry Pi running Raspbian (wheezy) with NUT 2.6.4. I can monitor my older TrippLite UPSs, mostly SU1000RT2Us, with this Pi and a USB to serial adapter. My first thought with the SU3000XLCD was to use the USB port instead of the serial port as that's the "modern" thing to do. When I plugged the USB cable in

I have several Tripplite SU2200RMXL2U and SU3000RM2U units that I would like to monitor using Nut. I have tried to attach to the units using a serial cable with the tripplite and tripplitesu drivers with no success. The drivers simply seem to not recognize the UPS. I then tried using the tripplite_usb driver with the usb cable. It definitely sees the UPS but I am getting errors which told me

I have a new SMART1050SLT Tripp Lite UPS that both tripplite and tripplitesu drivers hate. Both simply time out with a "can't find" message. Does anyone know about the SmartPro series?

Can anyone help getting a Tripplite SU2200XL to work with nut 2.0.3 using the supplied serial cable? Starting the ups service yields: Starting tripplitesu: Network UPS Tools - Tripp Lite SmartOnline driver 0.02 (2.0.3) Unable to detect Tripp Lite SmartOnline UPS on port /dev/ttyS0 I also have Tripplite's PowerAlert 12 software installed and when run it finds the UPS without a problem. So

I have tried to support a TrippLite Internet350SER UPS using a serial cable (The only connection on this model) using the 2.4 code branch. It uses the Protocol 1004 from the tripplite specification that can be use either used on serial or USB device. Since my device was only serial, I worked only on the serial integration. Since I found nothing in tripplite.c, tripplite-hid.c, tripplitesu.c to

On Mon, 4 Mar 2024, Alan C. Bonnici via Nut-upsuser wrote: > Platform: Proxmox VE 8.1.4 > NUT version: Network UPS Tools upsstats 2.8.0 > > I configured Proxmox and I can pull up the UPS stats. > Typing in `upsrw -l cyberpower at localhost` I get the following: > > [battery.charge.low] > Remaining battery level when UPS switches to LB (percent) > Type: STRING >

Thanks Charles for the clarification. If NUT cannot control it then removing it would, IMO add value. On Sun, 10 Mar 2024 at 00:14, Charles Lepple < clepple_at_gmail.com_chribonn at duck.com> wrote: > On Mar 9, 2024, at 5:16?PM, chribonn at duck.com wrote: > > > > The posting at > https://github.com/networkupstools/nut/issues/432#issuecomment-405371395 > references

Very good point. I hope to write a beginners guide -- more like adopting my notes --on NUT. I could summarise your point that technically one should only override settings that NUT can act upon (like those settings that control Low Battery or, as stated in the documentation if the reported value is known to be incorrect. Overriding a variable that is out of scope for NUT (as with

Wow :-) I'll have a read through it. On Sun, 10 Mar 2024 at 15:54, Roger Price < roger_at_rogerprice.org_chribonn at duck.com> wrote: > On Sun, 10 Mar 2024, Alan via Nut-upsuser wrote: > > > Very good point. I hope to write a beginners guide -- more like > adopting my > > notes --on NUT. > > I did the same thing, 131 pages, at >

On Mar 9, 2024, at 5:16?PM, chribonn at duck.com wrote: > > The posting at https://github.com/networkupstools/nut/issues/432#issuecomment-405371395 references ups.delay.start and suggests setting it to -1. > > upsrw -l pve1 at localhost listed this as modifiable but any attempt at modifying the value failed. I used the override.ups.delay.start = -1 in nut.conf and this is now being

Nut Developers, I have unsuccessfully tried to solve a problem with the voltage value on my Cyber Power UPS CP1000AVRLCD. Something is wrong with the battery voltage calculation. It always reads around 20 volts with that's nuts (pardon the pun). Right now: battery.voltage : 20.3 You can take a look for yourself at http://www.3111skyline.com/nutindex.html Is there a parameter I can check

*Platform: Proxmox VE 8.1.4NUT version: Network UPS Tools upsstats 2.8.0* I configured Proxmox and I can pull up the UPS stats. Typing in `*upsrw -l cyberpower at localhost*` I get the following: *[battery.charge.low]Remaining battery level when UPS switches to LB (percent)Type: STRINGMaximum length: 10Value: 10[battery.runtime.low]Remaining battery runtime

Hi everyone, I've been using nut 2.0.3 for more than a year on a Unitek iZi UPS 525 (which is a rebadged Mustek). Everything worked fine and last week, when pressed by RENEL :-) I ran a battery test which showed the system to have 17min of back-up power (yes, still haven't figured out how to use upssched...) The system used for testing was an old PIII/500MHz/512KB cache, 256MB RAM (3 x

Hi Charles, The posting at https://github.com/networkupstools/nut/issues/432#issuecomment-405371395 references ups.delay.start and suggests setting it to -1. upsrw -l pve1 at localhost listed this as modifiable but any attempt at modifying the value failed. I used the *override.ups.delay.start = -1* in nut.conf and this is now being reported. Two observations are that once a variable setting

Citeren "David C. Rankin" <drankinatty at suddenlinkmail.com>: > Discharged battery.voltage: > > 17.4 Volts - (indicated on shutdown, discharging battery.charge 77%) > 16.9 Volts - (indicated on shutdown, discharging battery.charge 51%%) > 16.6 Volts - (indicated on shutdown, discharging battery.charge 33%) > > -- Shutdown Occurred at < 3% -- Battery

tags 441342 upstream thanks Hi Robert, thanks for your report and investigation. We will check to fix this and give you news back. 2007/9/9, Robert Woodcock <rcw at debian.org>: > Package: nut > Version: 2.2.0-2 > Severity: important > > I recently set up nut at work to monitor the 15 APC Smart-UPS 1500s we have > in our server room. Since we currently only have one