similar to: Setting UPS values can be confusing

Hello all, I think I've found the "regression" in Belkin/Liebert USB HID support which worked for NUT v2.7.4 and reports zero voltages in 2.8.0 -- it was actually caused by a bug fix: practically the only functional difference per `git diff v2.7.4..v2.8.0 drivers/belkin-hid.c` is a change from `abs()` to `fabs()` in order-of-magnitude comparisons like `if( abs(value - 1e-7) <

Hello all, I think I've found the "regression" in Belkin/Liebert USB HID support which worked for NUT v2.7.4 and reports zero voltages in 2.8.0 -- it was actually caused by a bug fix: practically the only functional difference per `git diff v2.7.4..v2.8.0 drivers/belkin-hid.c` is a change from `abs()` to `fabs()` in order-of-magnitude comparisons like `if( abs(value - 1e-7) <

Hi On 10/06/2014 03:04 PM, Charles Lepple wrote:> I think I see what is going on. > >???? 0.368670??? Report[buf]: (5 bytes) => 05 4e 00 48 00 >???? 0.368698??? PhyMax = 0, PhyMin = 0, LogMax = 1, LogMin = 0 >???? 0.368723??? Unit = 00000000, UnitExp = 0 >???? 0.368747??? Exponent = 0 >???? 0.368776??? Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID: 0x05, Offset:

On May 11, 2017, at 1:51 PM, Jesse Molina <jmolina at swoncology.net> wrote: > > I suspect this is a driver problem because while NUT claims the battery isn't plugged in, it's giving me battery runtime/charge info. Both can't be valid at the same time. > > I am at a remote location from the computer and UPS, so I can't physically go over and check. I asked a

[please keep the list CC'd. thanks!] On Mar 13, 2015, at 10:53 AM, Philip Taylor <philip at kelsotowers.co.uk> wrote: > I?ve set up UPSMON to simply execute ?shutdown -h now? and my system shuts down when I type ?upsmon -c fsd?. The problem is that the OpenUPS doesn?t shut down as a result; and therefore when the power comes back on, unless the battery has totally run out, the

I'm testing a Powercom UPS (branded as Control System 2 STD80S: http://www.cs2.it/home.php?goto=prodotti&cat=0&idp=2&subid=0) with NUT. It is a USB HID device, with ID 0d9f:0004. I configured nut-server to use driver usbhid-ups and it works almost correctly: upsd communicates right with the device, upsmon catches its events... But when I try to perform a Forced Shutdown, UPS pauses

On Sat, May 28, 2016 at 11:05 AM, abi <abi at abinet.ru> wrote: > However I was unable to shutdown.return it. Maybe protocol is not fully > compatible? > > 0.145757 Initiating UPS shutdown > 0.145760 upsdrv_shutdown... > 0.145763 instcmd(shutdown.return, [NULL]) > 0.145767 powercom_shutdown_nuf: value = (null), command = 5400 > 0.145770

On 28.05.2016 19:46, Larry Fahnoe wrote: > On Sat, May 28, 2016 at 11:05 AM, abi <abi at abinet.ru > <mailto:abi at abinet.ru>> wrote: > > However I was unable to shutdown.return it. Maybe protocol is not > fully compatible? > > 0.145757 Initiating UPS shutdown > 0.145760 upsdrv_shutdown... > 0.145763

Hello! I left this line uncommented in powercom-hid.c for battery voltage: { "battery.voltage", 0, 0, "UPS.Battery.Voltage", NULL, "%.2f", 0, NULL }, and got some data different from the input voltage values The Powercom support staff gave the following response to my question: Dear Alex, First of all , thank you for purchasing PCM MRT-3000 ups. Regarding of your

Hello. Not listed as supported, so here is some info, [root at vhost ~]# /usr/sbin/usbhid-ups -DD -a powercom Network UPS Tools - Generic HID driver 0.38 (2.7.2) USB communication driver 0.32 0.000000 debug level is '2' 0.001318 upsdrv_initups... 0.074753 Checking device (0529/0001) (003/002) 0.074835 Failed to open device, skipping. (Permission denied)

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:

Hello i tried to connect my netys 2000 pr ups to ubuntu 11.10 and i have a problem connecting it. After readin a few post i realized to dianosse the connection. I need help resolving the connextion issue So here is the response to??/lib/nut/usbhid-ups -u root -DDDDD -a netys: Network UPS Tools - Generic HID driver 0.35 (2.6.1) USB communication driver 0.31 ? ?0.000000 ? ? send_to_all: SETINFO

I have a new-ish APC Back-UPS XS 1500G connected via USB. It's giving me a "ups.alarm: No battery installed!" error. I also installed and configured apcupsd to give that a try and it's giving me the same error. I suspect this is a driver problem because while NUT claims the battery isn't plugged in, it's giving me battery runtime/charge info. Both can't be valid

Hi On 10/03/2014 03:42 PM, Charles Lepple wrote:> On Oct 3, 2014, at 7:50 AM, paul.chavent at fnac.net wrote: > > > This is what I was referring to (from the belkin-hid log): > >???? 1.325782??? Report[buf]: (5 bytes) => 05 53 00 48 00 >???? 1.325799??? Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID: 0x05, Offset: 16, Size: 16, Value: 0 >????

I?m a new user of NUT and the OpenUPS - in the past I?ve used APC hardware and apcupsd on Centos 6. I?ve built NUT 2.7.2 from source but used the OpenUPS HID driver v0.4 that?s in github. I?m using firmware version 1.5 on the openups which is the latest published version; I?ve also tried 1.7 which Mini-box sent to me but reverted to the published version. Their support seems a bit slow! I?ve got

Hello. So as my english is not so good, i'll try to write my story in bash commands :o) miwa@zork3$ uname -mrs FreeBSD 5.5-STABLE i386 miwa@zork3$ su root@zork3# cd /usr/ports/sysutils/nat root@zork3# make && make install root@zork3# cd ../nut-usb root@zork3# make && make install root@zork3# cd /usr/local/etc/nut root@zork3# cat ups.conf user=root [MGE-Ellipse]

Hello, Got PowerCOM BNT-1000AP, usb id 0d9f:00a6, firmware FW4.A6 nut 2.4.3 on debian stable shows only two instant commands: beeper.toggle - Toggle the UPS beeper -- not working test.battery.start.quick - Start a quick battery test -- works ok. No load and shutdown commands. Trying svn trunk version, with the same results. Debug output shows the problem: 0.035558

Good Evening, I recently purchased an EPYC quantum UPS. I installed NUT on the home assistant by connecting the UPS via USB and tried all the various drivers in the list, the only one that seems to work is: usbhid-ups with this log: s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service base-addon-banner: starting

Hi all, Yesterday, I bought a UPS for the first time in my life, and was eager to dive into NUT. But not all is working as expected... I saw a similar thread started on 18 October, but it didn't help me. (I also spent a handful of hours searching the web for solutions, and of course read the manual and FAQ - "queequeg".) I tried shutting my UPS (APC "Back-UPS BX750MI

Have recently purchased a MGE Nova 1100 UPS and am trying to get running on netBSD. Configuration netBSD 3.0 amd64 libusb 0.1.10a nut 2.0.3 Built & installed libusb Built kernel with ugen device and uhid removed Build & install nut-2.0.3 with usb Chmod /dev/ugen1 etc to allow access by nut user. Ups.conf [MGENova] driver = newhidups port = auto