similar to: NUT with Eaton 9135 6000

Device Manufacturer: Eaton Device Name: 5S1500LCD ---------------------------------------------------------- upsc output: battery.charge: 100 battery.charge.low: 20 battery.runtime: 3515 battery.type: PbAc device.mfr: EATON device.model: Ellipse PRO 1500 device.serial: 0000000000 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2

Device Manufacturer: Eaton Device Name: 5S1500LCD ---------------------------------------------------------- upsc output: battery.charge: 100 battery.charge.low: 20 battery.runtime: 3515 battery.type: PbAc device.mfr: EATON device.model: Ellipse PRO 1500 device.serial: 0000000000 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2

>> last night we had what looked like a power spike and 3 machines plugged >> into 2 Eaton UPS went down instantly. I heard the click the UPS makes when >> it shuts the load on the ports and then shuts itself down (ie same thing if >> I simulate with upsmon -fsd). The machines instantly came back, there was no >> actual downtime, and the machine next to them which is

Linux-2.4.28 libusb-0.1.8 nut-2.6.5 [+most recent drivers from GIT] - from tarball EATON 3S700DIN [mfr.date 09/28/14] ---------------------------------- ISSUES: I) Too many kernel logs: --- In /var/log/kernel.log usbdevfs: usb_submit_urb returned -28 In /var/log/daemon.log: usbhid-ups[744]: libusb_get_interrupt: No error usbhid-ups[744]: libusb_get_interrupt: error submitting URB: No space left

Hello, we have a MGE Pulsar Evolution 800 connected to a Fedora Core5 Server using a serial cable. Installed and configured properly are RPM versions of nut-2.0.3-0.1.fc5 nut-client-2.0.3-0.1.fc5 nut-cgi-2.0.3-0.1.fc5 which all work (mostly) fine. The server is connected to outlet.0 and properly shuts down when it's loosing power after around 20 minutes. It also boots up whenever the ups

Hi, I have the Eaton 5E850iUSBDIN UPS connected via USB to a Raspberry Pi 3B+. It seems that everything but the ondelay parameter works so far. when I test the setup with this command: upsmon -c fsd The NUT server makes the NUT clients shut down properly and the Raspberry Pi running the NUT server shuts down correctly too. The problem is that after UPS shuts down, it immediatelly brings the

Hi, that's a good point, thanks. I don't see ups.delay.start anywhere. Here is the output of upsrw: upsrw Eaton at localhost [outlet.desc] Outlet description Type: STRING Maximum length: 20 Value: Main Outlet [output.voltage.nominal] Nominal output voltage (V) Type: ENUM Option: "200" Option: "208" Option: "220" Option: "230" SELECTED Option:

Hello I have a remote Dell R310 to which I connected via USB a new UPS, model Eaton 5E1500I USB. Assuming I interpreted correctly the docs, it should normally work using the usbhid-ups driver. However, no matter what I tried, I get an error which you can also is included in the below paste: #usbhid-ups -DDDD -u root -x explore -x vendorid="0463" -a eaton Network UPS Tools

On Jul 26, 2014, at 9:58 AM, Leith Bade <leith at leithalweapon.geek.nz> wrote: > First the beeper is annoying and loud and I worry it will wake everyone up at night. I read that you can mute the beeper temporarily (and this works) but that most UPSs do not allow you to permanently turn it off (I tried using upsrw but it said beeper.status was read only). Can you send the variable list

I have a brand new Eaton 5E UPS purchased in Australia. Details: Eaton 5E Model: 5E650iUSB-AU Date: best I can find is the shipping date to supplier on box label - May 2014 OS: Ubuntu 14.04 Server edition Nut 2.7.1 Installed via apt-get install nut I have two problems I would like to fix. First the beeper is annoying and loud and I worry it will wake everyone up at night. I read that you can

Oops... changing that to --with-user=nut solved one problem. I have the driver, upsd and upsmon running now. Thank you! Now I'm back to another issue, every 2 seconds I get in the logs: May 3 13:45:23 myhost upsd[2587]: Connected to UPS [eaton]: usbhid-ups-eaton It seems happy to do this forever. On Tue, May 3, 2016 at 8:17 AM, Charles Lepple <clepple at gmail.com> wrote: > On

Hi, This might be a simple thing to fix, but I can?t figure it out. We replaced the battery for the first time in our Eaton 5PX a couple of weeks ago, but we haven?t been able to clear the ?ups.alarm: replace battery!? status. Details of our installation are: OS: Debian 6 NUT version: 2.7.4 Installation method: from source tarball UPS device: Eaton 5PX2000IRT, 240V, 1800W, 2000VA, bought in

On Fri, Sep 11, 2020, at 4:05 PM, Bartosz wrote: > Dear All, > > Could you please recommend me a UPS with 100% support of the ondelay parameter and NUT compatibility? > > 850 or 1000 VA > > I have the EATON 5E850iUSBDIN UPS and it does not support this parameter so I would like to buy another UPS that for sure will support it. > > Thank you, > Bart Can you tell

Hi, FINALLY got my UPS working, YEA!!!! But now it brings up even more issues.. (BOOO!!) 1) I'm thinking this is a UPS issue, but when I pull the plug on my UPS, it goes from 100 to 30 in just a short amount of time (Minutes). This causes the machine to shut down. But once it gets to 0, its beeped its little heart out for a few more HOURS providing power to the non-system items perfectly.

On Thu, Sep 24, 2020 at 06:51:23PM +0300, Manuel Wolfshant wrote: > On 9/21/20 9:47 PM, Lionel Élie Mamane wrote: >> We have a HP R/T 3000 G4 UPS; according to the data returned by the >> usbhid-ups driver, it seems to be a "badge engineered" Eaton 5PX >> UPS LI R 3000. >> We have a stubborn "Replace Battery" alarm that stays (...): >> The

Hello, I've installed Nut (2.0.5) on RedHat a week ago, and upsmon seems to generate false alarms every hour: ... Jun 8 06:10:56 nutevalserver upsmon[2849]: UPS usb-mge-evolution at localhost on line power Jun 8 06:35:46 nutevalserver upsmon[2849]: UPS usb-mge-evolution at localhost on battery Jun 8 06:35:51 nutevalserver upsmon[2849]: UPS usb-mge-evolution at localhost on line power

Hi Powermen ;-) I recently came across the Powerman project (http://sourceforge.net/projects/powerman/), pointed by Tony Merenda, from Opengear (thanks Tony). Congrats for your work in this area! I've thought a bit about Powerman and NUT since then... NUT currently supports hosts of UPSs and few PDUs (RPCs), and provides tons of features: http://test.networkupstools.org

But runs normally if started. On a rpi4 running an uptodate raspbian buster, how do I set it to auto start at boot time? Thanks. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D.

Hello, Sorry if any of this is obvious - I'm new to NUT. NUT via upsc is displaying (edited for length): device.model: Eaton 5P 2200 device.type: ups driver.name: usbhid-ups ups.alarm: Fatal EEPROM fault! ups.status: ALARM OL CHRG ups.test.interval: 604800 ups.test.result: Done and passed driver.version: 2.7.2 driver.version.data: MGE HID 1.33 driver.version.internal: 0.38 Is this possibly

Hi, I'm a MGE Evolution 650 owner and, after putting in place a basic configuration for controlling my UPS, I'm going to tune a little bit better NUT for my needs. First of all let me describe my little (SOHO) scenario: I have the ISP modem/switch (providing VoIP too, so it's important to keep it running as much as possible), a small low power home server and a much hungrier PC.