Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

usbhid-ups does not disable beeper with Eaton 3S550 #9

Closed
aquette opened this issue Feb 15, 2013 · 4 comments
Closed

usbhid-ups does not disable beeper with Eaton 3S550 #9

aquette opened this issue Feb 15, 2013 · 4 comments
Assignees
Milestone

Comments

@aquette
Copy link
Member

aquette commented Feb 15, 2013

Alioth bug #313884
http://lists.alioth.debian.org/pipermail/nut-upsuser/2012-October/007994.html

@aquette aquette added the Eaton label May 20, 2015
@stalchuk
Copy link

stalchuk commented Nov 14, 2016

Hi Arnaud,
any news on the issue?

Have being using Eaton 3S700 facing the same issue:

  • nut-2.7.4 (compiled from source)
  • linux-2.4.28 (uClibc 0.9.27)
  • libusb-0.1.12 (compiled from source)

Please let me know, if any debugging info is required. So far OK is returned, but beeper is not disabled:
1) upsc 3s ups.beeper.status
enabled
2) upscmd -uMyUser -pMyPassword 3s beeper.disable
OK
3) upsc 3s ups.beeper.status
enabled

@aquette
Copy link
Member Author

aquette commented Nov 16, 2016

Hi Sergey / @stalchuk
just to say that I'm looking at it and think I've found the issue. However, I'll need a bit more time to test my findings and implement it in a way that does not generate regression for other units.
This will have to happen by the end of this (busy) week, since I'm on training next one and part of the following...
For the sake of completion, here are some details:
historically, we were using the HID Path "UPS.PowerSummary.AudibleAlarmControl" for "ups.beeper.status" and related commands (beeper.{enable,disable,mute,on,off}
However, some recent and/or smaller units use a different path ("UPS.BatterySystem.Battery.AudibleAlarmControl"), while still providing the historic one (which however doesn't act as expected).

I've tested successfully this new HID Path with a 3S 550, but still have to check for non regression on older units.

Still, since you compile nut from source, while waiting for the proper fix in NUT, you can simply replace the above mentioned path.

@aquette aquette self-assigned this Nov 16, 2016
@aquette aquette added this to the 2.7.5 milestone Nov 16, 2016
@aquette
Copy link
Member Author

aquette commented Nov 16, 2016

Thanks for your patience Sergey!

@stalchuk
Copy link

Thanks for the fix, Arnaud!

Now it works as expected)

jimklimov pushed a commit to 42ity/nut that referenced this issue Jan 28, 2017
Two HID Paths exists for handling beeper status and commands. However, only one
historic was implement, which was not actually suitable for issuing the commands
on newer units (such as 3S, 5P*, ...) (reported by Sergey Talchuk)

Closes: networkupstools#9
jimklimov added a commit to jimklimov/nut that referenced this issue Apr 12, 2017
FTY update from recent upstream/master
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants