Nut upsuser - Jul 2009 - Belkin 800VA Universal AVR doesn't warn about battery

Hi,

I'm currently using a Belkin UPS (
http://www.belkin.com/au/IWCatProductPage.process?Product_Id=137904) with
nut, and my notify script doesn't receive a low battery warning. I receive
ONBATT and ONLINE, but not any battery low message.

I've run upsmon -D and I've seen it polls the ups.status property. The
problem seems to be that this UPS doesn't put LB (I guess that should stand
for low battery) in the status. Even when the battery is at 7%, the status
is still OB DISCHRG. If upsmon parses only this property, it's bound to miss
LB message.

Here are the battery variables, reported by upsc:
battery.charge: 53
battery.charge.low: 30
battery.charge.warning: 30

Since battery.charge.low and battery.charge.warning settings are read-only,
and LB doesn't get reported via ups.status, I'm guessing the latter two
of
these are just advisory -- rather silly, but I guess that's it. Maybe upsmon
should watch these as well?

I've bypassed this problem by writing my own monitor that triggers the LB
event and shuts down the somputer. The question is: did I miss something
important? Is it supposed to work this way?

I'm using nut-2.2.0, which is an older version, so this may well be the
problem, but I'm on Centos and the only rpms I've found for 2.4
didn't work.

Best regards,
Gasper
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20090711/84d1609f/attachment.htm>

Citeren Gasper Kozak <gasper.kozak op gmail.com>:
> Since battery.charge.low and battery.charge.warning settings are read-only,
> and LB doesn't get reported via ups.status, I'm guessing the latter
two of
> these are just advisory -- rather silly, but I guess that's it. Maybe
upsmon
> should watch these as well?
No. The very least a driver (UPS) should support are the OL, OB and LB  
flags. If this doesn't work, it's broken and can't be used reliably.
> I've bypassed this problem by writing my own monitor that triggers the
LB
> event and shuts down the somputer. The question is: did I miss something
> important?
Yes, the upgrades that have been released since nut-2.2.0 came out  
(sorry, couldn't resist).
> Is it supposed to work this way?
Yes.
> I'm using nut-2.2.0, which is an older version, so this may well be the
> problem, but I'm on Centos and the only rpms I've found for 2.4
didn't work.
The version you're using is over two years old and no longer  
supported. You need to upgrade to a more recent version before asking  
for help. With the sparse information you're providing here, we can't  
help you as to why the binaries you found don't work. You should also  
check with whoever packaged these RPMS first if you have problems  
installing them, before asking for help here.

Best regards, Arjen
-- 
Please keep list traffic on the list