similar to: unexpected UPS status

On Tue, 7 Jan 2020, Eyal Lebedinsky wrote: > On 2020-01-07 23:01, Roger Price wrote: >> There is no report for variable "ups.delay.start" in your upsc output. >> What does command "upsc <ups> ups.delay.start" report? > > $ upsc eaton ups.delay.start > Init SSL without certificate database > Error: Variable not supported by UPS I am surprised

On Tue, 7 Jan 2020, Eyal Lebedinsky wrote: > I had a (intentional) power outage. The UPS/nut properly shut the system down > when battery was down to 20%. > It ran for only 18 minutes rather than the expected 40 (see later). > After it charged to 37% I removed power from the UPS. After 4-5 minutes the > system shut down. > However, when I restored power to the UPS the machine

Maybe a kernel USB issue, but people on this list may have encountered this issue. I am testing a new UPS (EATON 5E 1500iUSB) and am having a problem with the USB connection failing. My old UPS (EATON Ellipse MAX 1500) works just fine with the latest f30. Both devices identify as ID 0463:ffff MGE UPS Systems UPS To narrow the focus I booted recent live CDs on a PC that has no other USB devices

Hi BACKGROUND INFO:I have a new Eaton 5E 1100i USB UPS which their website claims is supported on Linux. They don't provide software for it for Linux, only for Windows.Referring links: https://www.eaton.com/za/en-gb/catalog/backup-power-ups-surge-it-power-distribution/Eaton_5E_UPS.html https://www.eaton.com/za/en-gb/skuPage.5E1100IUSB.specifications.html It was manufactured in May 2020

This UPS is already listed in the compatibility list. But I wanted to add the instant commands supported by upscmd: ============================ Instant commands supported on UPS [PW5125]: beeper.disable - Disable the UPS beeper beeper.enable - Enable the UPS beeper beeper.mute - Temporarily mute the UPS beeper load.on - Turn on the load immediately outlet.1.load.off - Turn off the load on

I got around to unplugging my UPS and I found it doesn't last nearly as long as estimated. Is the "upsmon[1446]: UPS desktop_ups at localhost battery is low" logged when "battery.runtime:" = "battery.runtime.low: 120"? Does any make better batteries that don't go down faster when they get old? battery.charge: 100 battery.charge.low: 10

Hi Manuel 2017-06-07 14:40 GMT+02:00 Charles Lepple <clepple at gmail.com>: > On Jun 7, 2017, at 5:47 AM, Manuel Wolfshant <wolfy at nobugconsulting.ro> > wrote: > > > > If that matters, the OS is a fully updated CentOS 6.9 and this > (latest stable ) version of nut was packaged by me. The problem appears on > any of the USB ports ( well, I tried the 2 in

On Wednesday 08 January 2020 06:44:03 Roger Price wrote: > On Tue, 7 Jan 2020, Eyal Lebedinsky wrote: > > On 2020-01-07 23:01, Roger Price wrote: > >> There is no report for variable "ups.delay.start" in your upsc > >> output. What does command "upsc <ups> ups.delay.start" report? > > > > $ upsc eaton ups.delay.start > > Init

Hello Charles, Thank you so much for your help. Just run upsc and it is possible that input.transfer.low is the one because we used power regulator to bring down the power around 84v and then the ups sent the power loss message to PC. Do you think some others may take effect for the low voltage? Just have the upsc result attached. Then I retried input.transfer.low, default.input.transfer.low,

Hey Charles, Latest update. Looks like in ups.conf I setup default.input.transfer.low = 84. After I took that line out, restart upsdrvctl, upsmon, and upsd, the command of sudo upsrw -s input.transfer.low=70 -u * -p * ups return OK. Still need to verify if it works by using voltage regulator and will keep you updated. Thank you for your help Regards Shen On Thu, Jun 5, 2014 at 8:54 AM,

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

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

On up-to-date f36, with latest kernel 6.1.7-100.fc36.x86_64. After receiving a few of these messages Broadcast message from nut at e7.eyal.emu.id.au (somewhere) UPS ups at ups is unavailable I noticed and ran sudo systemctl restart nut-driver at ups.service which triggered Broadcast message from nut at e7.eyal.emu.id.au (somewhere) Communications with UPS ups at ups established I now added

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

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:

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

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

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

Hi guys, I'm very new to NUT, and power monitoring in general, so please forgive me if this question is dumb. I'd like to write a Linux app that will know, in approximate real-time, how much power is being drawn by a computer plugged into an outlet. Is NUT well-suited to this usage? And if so, can anyone recommend relatively cheap monitoring hardware (ideally less than $200 US) that