[Nut-upsuser] Liebert PSA "On Battery" report

[Charles Lepple]

On Oct 17, 2014, at 8:31 PM, Tim Dawson <tadawson at tpcsvc.com> wrote:

> Likely because 2.6.3 is not a current release. 2.7.2 (or 3?) is rhe current version, and it makes little sense to backport changes.

Tim,

It's possible that these changes didn't make it in. I admit that would be my knee-jerk reaction to seeing an older version number, but the last occurrence of "PSA" in the drivers/ Git log is 2009.

> Nut is a trivial compile . . . 'Use the source, Luke . . .'
> 
> - Tim
> 
On October 17, 2014 6:05:35 PM CDT, Derek Harding <derek at lagham.org.uk> wrote:
> Hi,
> 
> Back in 2011, it was reported that Liebert PSA devices persist in 
> reporting OB (On Battery) when using usbhid-ups regardless of the actual 
> state. Pier Paolo did some work (2011) which reportedly solved the 
> issue. However, that doesn't seem to have reached mainstream and I now 
> face the same problem.

Derek,

Do you have a link to the message where the problem was solved?

> I'm using NUT 2.6.3 with a new Liebert PSA 1500Va that only ever reports 
> OB and hence, when the power fails it doesn't trigger a shutdown (Ubuntu 
> 12.04 servers). Latching power fail through upsc works as it should.

Not sure what you mean by "Latching power fail" - setting FSD through upsd?

> Any advice would be gratefully received but I would prefer not to have 
> to rebuild/build. I don't mind replacing with a different, more up to 
> date usbhid-ups.

It's hard to tell without seeing the results of upsc for the combination of your UPS and NUT version, but if you have a valid battery charge level, you can use the "ignorelb" setting to synthesize a low battery notification.

-- 
Charles Lepple

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?