similar to: newhidups output for Geek Squad GS1285U

On Jun 10, 2019, at 2:32 PM, Marc Finns wrote: > > Hello, I read all FAQ and other sources but I could not find this situation, so I thought of asking the experts. > I successfully configured a Raspberry NUT server to control my UPS that powers several devices (NUC with ESXI VMs, Synology NAS etc). > All works well in principle, but I have the following behaviours that I could not

I tested your fix (newhidups -DDD /dev/null) using both and APC Back-UPS 350 an APC Smart-UPS RT 2000 XL. No more segmentation fault due to the fixed-size array. ~Jacob -----Original Message----- From: nut-upsdev-bounces@lists.alioth.debian.org [mailto:nut-upsdev-bounces@lists.alioth.debian.org] On Behalf Of Peter Selinger Sent: Monday, October 16, 2006 12:12 PM To: Schmier, Jacob Cc: NUT

Hello, I'm using the stable amd64 port of Debian Linux. I installed (the latest) nut-2.0.1-4 and nut-usb packages for utilizing an APC Smart-UPS 1500 USB. I tried "apcupsd" first but "nut" makes an even more sophisticated impression on me and has more security options. I had problems with the newhidups driver. It didn't find a device with matching VendorID. And

Hello everyone! If this message was posted twice, my apologies. I'm having issues with my webmail today... I am using the testing version of NUT from SVN at changeset 582. I have successfully created a stub for newhidups driver for my Dynex DX-800U UPS, but I am completely lost on the customization of it. I've followed the hid-subdrivers.txt instructions and I understand I need to

Charles Lepple wrote: > > would you mind forwarding (to either me, or the list) the .txt file > showing the hidparser bug? I am trying to revamp libhid's hidparser, > and it would be helpful to have the descriptor. The text file is contained in the tarball on the patch tracker, at

Charles Lepple wrote: > On 8/2/06, Didrik Pinte <dpinte@itae.be> wrote: > > Le mercredi 02 ao=FBt 2006 =E0 08:08 -0400, Charles Lepple a =E9crit : > > > On 8/2/06, Didrik Pinte <dpinte@itae.be> wrote: > > > > Can you start the driver like this: "/sw/bin/newhidups -u root -DDD" > > > and paste some of the output? > > > > Here

Thanks for the reply. However these two FAQ are unfortunately not describing the situation. - The first issue is that NUT switches off the UPS upon reboot on low battery (not that it dies because of low battery) - The second issue is that the UPS does not recognise being online again (not that the PC does not restart) Sent from my iPhone > On 11 Jun 2019, at 02:03, Charles Lepple <clepple

Gentlemen, I have a new HID USB device, that seems to be quite similar to the currently supported APC HID UPS. I append the dump-tree output, and would much appreciate advice on how to proceed. Certain entries for the current device are not available, but maybe there are some replacements that could be used. This may of course require a new table in apc-hid.h, and I would prefer not to do this

Gentlemen, Please note that what follows pre-dates the latest changes from Arnaud (just thought someone might want to look at these before I can test the latest!). When running newhidups with -D -D -D I saw messages that looked like errors, and it took me a while to understand that they were not really errors. I therefore added two new entries in apc-hid.h, and I modified a couple of diagnistic

Hello, I have been using NUT for a short period of time and have some questions regarding the UPS reboot signal that I can't figure out. Have tried some googling and reading the DOCs but I am struggling to understand how some variables / things are supposed to work, so would appreciate any help with any of the following questions. I am running NUT on standalone mode on a linux machine

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

I've acquired and installed NUT 2.4.1 on a D-Link DNS323 NAS. With exception of Load and Battery Temp readings all works well. A upsc ups at localhost command returns; battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 50 battery.date: 2001/09/25 battery.mfr.date: 2008/06/05 battery.runtime: 2122 battery.runtime.low: 120 battery.temperature: 3022999999999998800 battery.type:

I have a Tripp-Lite BCPERS450, connected to a system running Ubuntu 16.04.3 LTS and NUT 2.7.2-4ubuntu1.2. I had to make my own /lib/systemd/system-shutdown/nutshutdown, but now everything is working except for powering on and off the UPS. Regardless of the settings of offdelay and ondelay in upsconf, and regardless of whether the AC power is on, when I say "upsdrvctl shutdown" the UPS

Hello, I am having difficulty using NUT to shut down my Netgate SG-1100 (a pfSense router) when the power level of the UPS gets critically low. Here is some relevant information: - OS: pfSense 2.4.5-RELEASE-p1 (FreeBSD 11.3-STABLE) - NUT version: 2.7.4 - Installed from: pfSense package 2.7.4_7 - UPS: AVR750U (Device release number 2) - I have included my config files, output from `upsc`, and

Hello Nutters, I'm running nut 2.7.2 on FreeBSD 10-stable (via the FreeBSD port) with an APC Back-UPS CS 350 connected via USB. I get persistent (every few minutes) messages logged "battery is low" but I don't understand why. I don't think it's for the reason described in the FAQ (but I'm not 100% sure). In the trace output I can see that

I am having an issue running NUT and using an TrippLite OMNI900LCD. When I run ./upsdrvctl start I get : [player@V0002-S002 bin]$./upsdrvctl start Network UPS Tools - UPS driver controller 2.1.0 Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.1.0) Detected a UPS: Tripp Lite /TRIPP LITE UPS Using subdriver: TrippLite HID 0.1 (experimental) dstate_setflags: base variable

Peter Selinger wrote: > Hm. I need more information, as NUT seems to garble the values even > before I can see them. I am not so worried about the date and > temperatures (although, strangely, the battery replacement date > appears to be Sept 25, 2001, which makes no sense). But the voltage is > definitely important. > > [...] > Thanks Peter - I'll send the new

Hello I recently switched from apcupsd to NUT2.2.2 without any troubles. I tried to figure out how I can configure the self-test intervall. The command upsrw lists only the variables battery.charge.low battery.runtime.low ups.delay.shutdown ups.delay.start The command usbhid-ups -D and the listing under http://obsvermes.org/cgi-bin/nut/upsstats.cgi?host=apcsmart at localhost&treemode

Nut will monitor the ups and shutdown Linux when the ups goes to low battery as it should. But the UPS is not shut down so the system will restart when the power is restored. If I switch the UPS off , restore power and switch the UPS on the system will restart. I have not been able to get nut to switch the UPS off after it brings the system down. I can get the UPS to switch off with upscmd

I posted earlier on this list about getting an Arduino Pro Micro using https://github.com/abratchik/HIDPowerDevice in a simple sketch to monitor a DIY UPS I have built. With the changes from that thread (I had a PR merged), I was able to get usbhid-ups to recognize my device and could setup NUT the rest of the way. My intended configuration is to run NUT on a Raspberry Pi, have that device be