On Jun 26, 2017, at 7:03 AM, Andrea de Lutti <adelutti at gmail.com> wrote:> > Are there no warnings for battery test?not sure if you saw my reply on 2016-06-17: Do you mean a notification that a test is in progress, or something for the results? There is the REPLBATT message in upsmon when the battery test fails, but I don't think the generic Qx protocol supports the RB status flag. You could possibly trigger on the OB status and look for the CAL flag in ups.status as well, but I haven't tried to automate that. ^^^ If you run "upsc $UPSNAME ups.status", do you see CAL in the status string during a battery test? If not, your UPS is not reporting this the way that the driver expects.
Sorry, I didn't received it... I don't have any REPLBATT message, but when in battery test I have OL CAL status: it would be good to have the result. Anyway I still not receive any email on any test (power cord disconnected and/or reconnected for example) Does the runtime calibration test alter the values of ups.conf? Or do I have to change it manually? Which would be the right procedure for changing the battery for calibrating NUT (over the manufacturer's suggestions)? Thank you lots, Andrea 2017-06-27 14:50 GMT+02:00 Charles Lepple <clepple at gmail.com>:> On Jun 26, 2017, at 7:03 AM, Andrea de Lutti <adelutti at gmail.com> wrote: > > > > Are there no warnings for battery test? > > not sure if you saw my reply on 2016-06-17: > > Do you mean a notification that a test is in progress, or something for > the results? > > There is the REPLBATT message in upsmon when the battery test fails, but I > don't think the generic Qx protocol supports the RB status flag. > > You could possibly trigger on the OB status and look for the CAL flag in > ups.status as well, but I haven't tried to automate that. > > ^^^ If you run "upsc $UPSNAME ups.status", do you see CAL in the status > string during a battery test? If not, your UPS is not reporting this the > way that the driver expects.-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170627/b2cb5771/attachment.html>
On Jun 27, 2017, at 9:23 AM, Andrea de Lutti <adelutti at gmail.com> wrote:> > Sorry, I didn't received it...You should be subscribed to the list now.> I don't have any REPLBATT messageRight, you would only get REPLBATT messages when the UPS reports that the battery *needs to be replaced* (and then at regular intervals per the upsmon.conf parameters).> , but when in battery test I have OL CAL status: it would be good to have the result."OL CAL" or "OB CAL"? If the UPS is powering the load from the battery during calibration, it should report "OB CAL". The ONBATT handler in NOTIFYCMD can check for CAL at that point. I don't think we considered the case where CAL is paired with OL.> Anyway I still not receive any email on any test (power cord disconnected and/or reconnected for example)Oh, I misinterpreted "working script" as a script that was sending email, rather than work-in-progress. Does that same command work from the command line? Can you add something like "logger" before the mailx line to be sure that the script is executing properly? Be sure to "chmod a+x" the script. I forget if I mentioned this earlier, but for testing notifications, you can use the dummy-ups driver: http://networkupstools.org/docs/man/dummy-ups.html The timer example will simulate the OL-OB-LB transition.> Does the runtime calibration test alter the values of ups.conf? Or do I have to change it manually? Which would be the right procedure for changing the battery for calibrating NUT (over the manufacturer's suggestions)?The automatic calibration/battery test invoked by upscmd (or the UPS front panel button, if any) is for the UPS low battery warning. The manual calibration ups.conf parameters are necessary (and need to be maintained separately) because Qx-based protocols do not all report the state-of-charge as calculated by the UPS. I would recommend both forms of calibration after replacing the battery.> _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser at lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser