similar to: Are all measurements are in seconds?

Linux NUT 2.7.1 Eaton 5PX usbhid-ups It would appear that interrupts are not actually working on my 5PX using the usbhid-ups driver. I will be trying the serial mge-shut driver next. It just seemed like it was working before because of the default pollinterval of 2 seconds. The status update comes in during the pollinterval no matter what I have pollfreq set to. And I can set pollonly and

Hello, is there a way to query from the cmdline if the UPS data is stale? "upsc" outputs a lot of information, but not if the data is stale. Example output from a "stale" UPS on the server: (nut version: nut-2.7.2-3.el7) # upsc apcsmart battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 50 battery.mfr.date: 2014/09/01 battery.runtime: 1320

Hi all, I attached a driver for MiniBox openUPS device ( http://www.mini-box.com/OpenUPS) and a dump of the hid usages. I had the possibility to make a few adjustments to the device firmware for HID usages, and although I haven't managed to produce a good structure many issues from previous firmware were at least fixed and new information added. ATM the driver only shows pertaining

Hi, I've been checking out NUT with an OpenUPS board over the last couple of weekends, and have noticed that it doesn't seem to report sensible values. This lead me to investigate usbhid-ups and delve into various issues. As mentioned in a github issue, one of the problems is with the report descriptor - dumping this from the usbhid-ups debug output and picking through it reveals that

Gentlemen, I think this question is mainly for Arnaud again: When I run my UPS directly with newhidups -D -D -D, with no data changes, and I then observe the interaction with my UPS (still Back-UPS ES 650 FW:818.w1.D USB FW:w1), I see the updateinfo cycle through 3 different forms: (1) a (2 bytes) => 06 08 notification that provides one item: UPS.PowerSummary.APCStatusFlag Note that

Hi folks, I'm having an issue with getting nut-server to start at boot on a freshly installed Fedora 40 desktop. Seems once the machine is up, I can manually start with systemctl start nut-server and everythings fine. dnf info nut Last metadata expiration check: 2:08:11 ago on Sat 27 Jul 2024 03:48:13 PM EDT. Installed Packages Name : nut Version : 2.8.2 Release : 1.fc40

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

Hi Patrick, 2010/11/15 Patrick O'Malley > I've confirmed that the CyberPower CP1350AVRLCD works with nut using > the USB port and the usbhid-ups driver. It is not on your list. > Thanks! > have you checked all variables, and most of all that shutdown works as expected? ie http://new.networkupstools.org/user-manual.html#Testing_shutdowns please also send us an upsc output.

Well, the intention generally is to use it as a driver, so the more abilities the merrier (PR would be welcome) :) Per comments to initial PR that added it, https://github.com/networkupstools/nut/pull/1044 : > The idea of introducing this driver is to enable creation and prototyping of smart UPS based on Arduino, which is inexpensive versatile platform very much suitable for custom fully

oh! Ok, I'll go look at all the HID objects reported by the sample code @abratchik has on top-of-tree of his repo and see what makes sense to add to NUT. PR coming this week. On Sun, Nov 12, 2023 at 2:38?PM Jim Klimov <jimklimov+nut at gmail.com> wrote: > Well, the intention generally is to use it as a driver, so the more > abilities the merrier (PR would be welcome) :) >

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

I was getting: "Can't claim USB device [0764:0501]: could not detach kernel driver from interface 0: Operation not permitted" so I manually installed the udev rules the source (I installed the Gentoo ebuild). I am now getting: # upsdrvctl start Network UPS Tools - UPS driver controller 2.4.3 Network UPS Tools - Generic HID driver 0.34 (2.4.3) USB communication driver 0.31 Using

Arjen de Korte wrote: > > Author: adkorte-guest > Date: Fri Aug 10 20:23:27 2007 > New Revision: 1041 > > Log: > * drivers/usbhid.[ch]: > - Moved the struct & data for ups.status processing to usbhid.c, since this is only used in there. Subdrivers report the status through text messages, they don't set the status bits directly. > - Rewrote (flattened) the

On Tuesday 21 January 2020 19:52:01 Charles Lepple wrote: > sudo lsusb -v -d 0764:0501 copious output, containing this: idVendor 0x0764 Cyber Power System, Inc. idProduct 0x0501 CP1500 AVR UPS bcdDevice 0.01 iManufacturer 3 CPS iProduct 1 CP625HGa I take it that this is evidence they don't follow the spec to the letter.

I bought a new CyberPower CP850AVRLCD ups, connected it to a usb port and I'm trying to use it with hal. I installed [root at phoenix ~]# rpm -q nut nut-client nut-2.2.0-6.1.fc8 nut-client-2.2.0-6.1.fc8 lsusb sees it: [root at phoenix docs]# lsusb Bus 001 Device 001: ID 0000:0000 Bus 005 Device 002: ID 0c45:1050 Microdia Bus 005 Device 001: ID 0000:0000 Bus 004 Device 001: ID 0000:0000

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

All, I have built and installed nut from git on Archlinux. It uses the usbhid driver. Beginning a couple of years ago, nut begin failing to run on Archlinux without 'tweaking' or 'fudging' the install. There are two primary problems: (1) upsdrvctl cannot be launched normally i.e. (/usr/sbin/upsdrvctl start) without failing to connect: Dec 14 02:24:39 phoinix systemd[1]:

Hi, I have an UPS with only the marking D1000 on it and it came with Junda-Tech's UpsMate. Its USB id is 3344:0025, which is apparently a microprocessor. I've could get some of the HID interactions as described on the website, but there are some outstanding. Junda-Tech does not respond to any queries. Does anybody else have the same or a similar UPS with more information? What is the

On Tuesday 14 January 2020 00:03:09 Gene Heskett wrote: > On Monday 13 January 2020 22:42:46 Charles Lepple wrote: > > On Jan 13, 2020, at 10:17 PM, Gene Heskett wrote: > > >>> (I was looking at the hid-subdrivers.txt file in the latest NUT > > >>> tree, which has the command line amended to not generate that > > >>> "too many non-option