Re: [Nut-upsdev] On ups.status CHRG/DISCHRG Vs battery.charger.status

2015-04-08 Thread Arnaud Quette
Hi Charles and the list, 2015-03-30 11:05 GMT+02:00 Arnaud Quette arnaud.que...@gmail.com: Hi Charles, 2015-03-29 0:44 GMT+01:00 Charles Lepple clep...@gmail.com: On Mar 25, 2015, at 4:11 AM, Arnaud Quette arnaud.que...@gmail.com wrote: 1) Keep the legacy CHRG / DISCHRG status bits

Re: [Nut-upsdev] On ups.status CHRG/DISCHRG Vs battery.charger.status

2015-03-30 Thread Arnaud Quette
Hi Charles, 2015-03-29 0:44 GMT+01:00 Charles Lepple clep...@gmail.com: On Mar 25, 2015, at 4:11 AM, Arnaud Quette arnaud.que...@gmail.com wrote: 1) Keep the legacy CHRG / DISCHRG status bits for ups.status, along with the complementary ones for battery.charger.status. And advocate

Re: [Nut-upsdev] On ups.status CHRG/DISCHRG Vs battery.charger.status

2015-03-28 Thread Charles Lepple
On Mar 25, 2015, at 4:11 AM, Arnaud Quette arnaud.que...@gmail.com wrote: 1) Keep the legacy CHRG / DISCHRG status bits for ups.status, along with the complementary ones for battery.charger.status. And advocate (document) for the use of / switch to the latter, that is more suitable for

[Nut-upsdev] On ups.status CHRG/DISCHRG Vs battery.charger.status

2015-03-25 Thread Arnaud Quette
Hi NUT developers, part of the 2.7.3 release, we are about to merge the below branch / PR for the bcmxcp drivers family: https://github.com/networkupstools/nut/pull/158 https://github.com/networkupstools/nut/tree/pull_158_bcmxcp_rebased It has introduced the battery.charger.status variable,