[Nut-upsuser] Belkin 800VA Universal AVR doesn't warn about battery
gasper.kozak at gmail.com
Sun Jul 12 12:10:48 UTC 2009
I've installed the mentioned packages and LB event still doesn't get
Just to make sure, if values displayed with upsc are set to these values
Then the driver should report LB when battery.charge is below
battery.charge.low (30)? What does battery.charge.warning have to do here?
On Sun, Jul 12, 2009 at 1:12 AM, Gasper Kozak <gasper.kozak at gmail.com>wrote:
> thanks, sort of what I expected. So it's very probable that it's driver's
> fault for not receiving LB message, even though OL, OB, DISCHRG work well,
> including when more than one is set.
> I found the Centos packages I'm refering to here on the list:
> This mailing list appears to be the only "official" source of information
> about them. I'm having problems installing them, but I'm aware this is not
> the place to ask about that -- I'll contact he packager directly. I just
> wanted to make sure, whether my USP is supposed to report LB in status field
> or not.
> When I succeed in upgrading nut, I'll post the results here.
> Thanks and best regards,
> On Sat, Jul 11, 2009 at 11:21 PM, Arjen de Korte <nut+users at de-korte.org<nut%2Busers at de-korte.org>
> > wrote:
>> Citeren Gasper Kozak <gasper.kozak at gmail.com>:
>> Since battery.charge.low and battery.charge.warning settings are
>>> and LB doesn't get reported via ups.status, I'm guessing the latter two
>>> these are just advisory -- rather silly, but I guess that's it. Maybe
>>> 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
>> 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?
>> 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
>> 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
>> Nut-upsuser mailing list
>> Nut-upsuser at lists.alioth.debian.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Nut-upsuser