Re: [Nut-upsuser] NUT not recognising Mini-box OpenUPS 2

[Charles Lepple]

On Aug 16, 2017, at 3:27 AM, Song Teck  wrote:
> 
> How do I go about capturing the log?

You might want to discharge the battery most of the way to battery.charge.low 
(5%, if it is similar to the other unit listed in the DDL) before switching to 
debug mode, because it is fairly verbose. Then, stop the NUT components ("sudo 
stop nut-client" and "sudo stop nut-server") and run this:

sudo /lib/nut/usbhid-ups -DD -a name-of-ups 2>&1 | tee 
/tmp/OpenUPS2.low-battery.txt

Please gzip the log before emailing it to the list.
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] NUT not recognising Mini-box OpenUPS 2

[Song Teck]

Hi Charles,

Ok, will try the ignore lb flag later. How do I go about capturing the log?
I might as well do it while testing the flag...

Cheers,
ST

On 15 August 2017 at 20:42, Charles Lepple  wrote:

> On Aug 15, 2017, at 5:24 AM, Song Teck  wrote:
> >
> > Hi Charles,
> >
> > Have managed to make some progress after a fashion. Got the unit to work
> on the jessie version of NUT (2.7.2). upsc does output the unit parameters,
> along with the mis-scaled voltage readings described at
> http://networkupstools.org/ddl/Mini-Box.com/OpenUPS2.html. Am now trying
> to get the shutdown sequence to work properly.
> >
> > Have been following this: http://networkupstools.org/
> docs/user-manual.chunked/ar01s06.html
> > Unit performs as described in the "Testing shutdowns" section.
> >
> > I have another question that I am hoping to get some clarification with.
> >
> > The ups unit does not transit into OB LB even when Battery Charge falls
> below the LB level. The unit does initiate power off properly when Battery
> Charge/Runtime reaches 0.
> > Is this correct? Or should there be an earlier transition and shutdown
> triggered by OB LB?
>
> The driver should recognize one of several standard shutdown notifications:
>
>https://github.com/networkupstools/nut/blob/v2.7.
> 2-signed/drivers/openups-hid.c#L300-L302
>
> However, I don't know which of these is actually implemented in the
> firmware. If you can afford some downtime, you can capture a log as the
> battery discharges - let us know if you want to try that.
>
> To synthesize the OB+LB state, you can use the "ignorelb" flag with
> override.battery.charge.low and/or override.battery.runtime.low as
> described in http://networkupstools.org/docs/man/ups.conf.html
>
> You mentioned that the UPS powers off by itself when the charge reaches 0.
> Note that there does not seem to be a way to tell it to power off early
> with a command from NUT (e.g. "upsdrvctl shutdown", which gets translated
> to "/path/to/driver ... -k").
>
> >
> > I have also not been able to successfully get NOTIFYMSG or NOTIFYFLAG to
> work successfully although I suspect that has to do with my configuration
> of NOTIFYCMD. Will pursue that a little more.
>
> I'd recommend a separate email thread for that, and check Roger Price's
> writeup for further information: http://rogerprice.org/NUT.html
>
>
>
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] NUT not recognising Mini-box OpenUPS 2

[Charles Lepple]

On Aug 15, 2017, at 5:24 AM, Song Teck  wrote:
> 
> Hi Charles,
> 
> Have managed to make some progress after a fashion. Got the unit to work on 
> the jessie version of NUT (2.7.2). upsc does output the unit parameters, 
> along with the mis-scaled voltage readings described at 
> http://networkupstools.org/ddl/Mini-Box.com/OpenUPS2.html. Am now trying to 
> get the shutdown sequence to work properly. 
> 
> Have been following this: 
> http://networkupstools.org/docs/user-manual.chunked/ar01s06.html
> Unit performs as described in the "Testing shutdowns" section.
> 
> I have another question that I am hoping to get some clarification with.
> 
> The ups unit does not transit into OB LB even when Battery Charge falls below 
> the LB level. The unit does initiate power off properly when Battery 
> Charge/Runtime reaches 0. 
> Is this correct? Or should there be an earlier transition and shutdown 
> triggered by OB LB? 

The driver should recognize one of several standard shutdown notifications:

   
https://github.com/networkupstools/nut/blob/v2.7.2-signed/drivers/openups-hid.c#L300-L302

However, I don't know which of these is actually implemented in the firmware. 
If you can afford some downtime, you can capture a log as the battery 
discharges - let us know if you want to try that.

To synthesize the OB+LB state, you can use the "ignorelb" flag with 
override.battery.charge.low and/or override.battery.runtime.low as described in 
http://networkupstools.org/docs/man/ups.conf.html

You mentioned that the UPS powers off by itself when the charge reaches 0. Note 
that there does not seem to be a way to tell it to power off early with a 
command from NUT (e.g. "upsdrvctl shutdown", which gets translated to 
"/path/to/driver ... -k").

> 
> I have also not been able to successfully get NOTIFYMSG or NOTIFYFLAG to work 
> successfully although I suspect that has to do with my configuration of 
> NOTIFYCMD. Will pursue that a little more. 

I'd recommend a separate email thread for that, and check Roger Price's writeup 
for further information: http://rogerprice.org/NUT.html



___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] NUT not recognising Mini-box OpenUPS 2

[Song Teck]

Hi Charles,

Have managed to make some progress after a fashion. Got the unit to work on
the jessie version of NUT (2.7.2). upsc does output the unit parameters,
along with the mis-scaled voltage readings described at
http://networkupstools.org/ddl/Mini-Box.com/OpenUPS2.html. Am now trying to
get the shutdown sequence to work properly.

Have been following this:
http://networkupstools.org/docs/user-manual.chunked/ar01s06.html
Unit performs as described in the "Testing shutdowns" section.

I have another question that I am hoping to get some clarification with.

The ups unit does not transit into OB LB even when Battery Charge falls
below the LB level. The unit does initiate power off properly when Battery
Charge/Runtime reaches 0.
Is this correct? Or should there be an earlier transition and shutdown
triggered by OB LB?

I have also not been able to successfully get NOTIFYMSG or NOTIFYFLAG to
work successfully although I suspect that has to do with my configuration
of NOTIFYCMD. Will pursue that a little more.

Cheers


On 4 August 2017 at 20:09, Song Teck  wrote:

> Hi Charles, Tim,
>
> Ah, thanks for bit about the dependencies. Would have thought them to be
> version specific.
>
> Tried with the client and server debs but it seems too many dependency
> differences between wheezy and jessie. I also tried upgrading from wheezy
> to jessie wholesale to see if that worked and it did solve nut but in the
> process broke something else that's more critical so I'll give the
> following another try:
>
> 1) try Tim's suggestion of searching for the "new" upsdrvctl or failing
> that,
> 2) uninstalling 2.6.5 and then installing 2.7.4 via tar
>
> Cheers
>
> On 3 August 2017 at 19:21, Charles Lepple  wrote:
>
>> On Aug 3, 2017, at 5:35 AM, Song Teck  wrote:
>> >
>> > That package is supposed to install both server and client (according
>> to the description at https://packages.debian.org/stretch/nut anyway).
>> I'll try both server and client individually later and see if that helps.
>> >
>> Right, but only if you install it via apt. If you install the 2.7.4 .deb
>> with dpkg, and you have the 2.6.4 nut-client and nut-server .debs
>> installed, the dependencies are satisfied. (The nut metapackage does not
>> depend on specific versions.)
>
>
>
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] NUT not recognising Mini-box OpenUPS 2

[Song Teck]

Hi Charles, Tim,

Ah, thanks for bit about the dependencies. Would have thought them to be
version specific.

Tried with the client and server debs but it seems too many dependency
differences between wheezy and jessie. I also tried upgrading from wheezy
to jessie wholesale to see if that worked and it did solve nut but in the
process broke something else that's more critical so I'll give the
following another try:

1) try Tim's suggestion of searching for the "new" upsdrvctl or failing
that,
2) uninstalling 2.6.5 and then installing 2.7.4 via tar

Cheers

On 3 August 2017 at 19:21, Charles Lepple  wrote:

> On Aug 3, 2017, at 5:35 AM, Song Teck  wrote:
> >
> > That package is supposed to install both server and client (according to
> the description at https://packages.debian.org/stretch/nut anyway). I'll
> try both server and client individually later and see if that helps.
> >
> Right, but only if you install it via apt. If you install the 2.7.4 .deb
> with dpkg, and you have the 2.6.4 nut-client and nut-server .debs
> installed, the dependencies are satisfied. (The nut metapackage does not
> depend on specific versions.)
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] NUT not recognising Mini-box OpenUPS 2

[Charles Lepple]

On Aug 3, 2017, at 5:35 AM, Song Teck  wrote:
> 
> That package is supposed to install both server and client (according to the 
> description at https://packages.debian.org/stretch/nut anyway). I'll try both 
> server and client individually later and see if that helps.
> 
Right, but only if you install it via apt. If you install the 2.7.4 .deb with 
dpkg, and you have the 2.6.4 nut-client and nut-server .debs installed, the 
dependencies are satisfied. (The nut metapackage does not depend on specific 
versions.)
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] NUT not recognising Mini-box OpenUPS 2

[Song Teck]

Hi Charles,

That package is supposed to install both server and client (according to
the description at https://packages.debian.org/stretch/nut anyway). I'll
try both server and client individually later and see if that helps.

Cheers,
ST

On 3 Aug 2017 7:26 a.m., "Charles Lepple"  wrote:

> On Aug 2, 2017, at 12:09 PM, Song Teck  wrote:
> >
> > sudo dpkg -i nut_2.7.4-5_all.deb
> > (Reading database ... 103447 files and directories currently installed.)
> > Preparing to replace nut 2.6.4-2.3+deb7u1 (using nut_2.7.4-5_all.deb) ...
> > Unpacking replacement nut ...
> > Setting up nut (2.7.4-5) ...
> >
> > which doesn't return an error but starting upsdrvctl after still shows
> v2.6.4 so that didn't work.
> >
> The "nut" package only depends on "nut-client" and "nut-server", so you
> would need .debs for those as well. Those are the ones that I think would
> be likely to have issues.
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] NUT not recognising Mini-box OpenUPS 2

[Charles Lepple]

On Aug 2, 2017, at 12:09 PM, Song Teck  wrote:
> 
> sudo dpkg -i nut_2.7.4-5_all.deb
> (Reading database ... 103447 files and directories currently installed.)
> Preparing to replace nut 2.6.4-2.3+deb7u1 (using nut_2.7.4-5_all.deb) ...
> Unpacking replacement nut ...
> Setting up nut (2.7.4-5) ...
> 
> which doesn't return an error but starting upsdrvctl after still shows v2.6.4 
> so that didn't work.
> 
The "nut" package only depends on "nut-client" and "nut-server", so you would 
need .debs for those as well. Those are the ones that I think would be likely 
to have issues.
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] NUT not recognising Mini-box OpenUPS 2

[Tim Dawson]

This is probably just pathing issues . . . the .deb likely put the 2.7.4 
distro in a different place, and if you can find it and run the newly 
installed "upsdrvctl" instead of the old one, it may well work.  That, 
or deinstall the old version first, then install 2.7.4 cleanly . . .


- TIm

On 08/02/2017 11:09 AM, Song Teck wrote:

Hi Charles,

thanks for the clarification on the libusb. that indeed does work to 
get the value in ./configure.


I've tried installing a .deb

sudo dpkg -i nut_2.7.4-5_all.deb
(Reading database ... 103447 files and directories currently installed.)
Preparing to replace nut 2.6.4-2.3+deb7u1 (using nut_2.7.4-5_all.deb) ...
Unpacking replacement nut ...
Setting up nut (2.7.4-5) ...

which doesn't return an error but starting upsdrvctl after still shows 
v2.6.4 so that didn't work.


Does ./configure, make, sudo make install have to be carried out in a 
particular directory? I've run it from a /usr/local both with and 
without the user/group/usb switches and again it seems to run fine but 
when the upsdrvctl is called, it still remains as 2.6.4 so evidently 
I'm missing something here...


Thanks again for your patience

On 2 August 2017 at 10:02, Charles Lepple > wrote:


On Aug 1, 2017, at 12:01 PM, Song Teck > wrote:
>
> Hi Charles,
>
> Ok, I missed the absence from the backports as well. Again, some
unfamiliarity here, so
>
> 1) I presume I cannot use a metapackage meant for jessie or
stretch on wheezy? Or if I can, is there a way to deploy it from
console?

The "nut" metapackage just depends on "nut-client" and
"nut-server". The drivers are in the server package - you'd need
to find a way to install a newer nut-server package, and I don't
know if I would want to try and mix .deb versions like that (if it
is even possible).

> 2) If not and I use the 2.7.4 tar found at
http://networkupstools.org/download.html
, do i just run the
classical process? i.e.
>
> ./configure
> make
> sudo make install

You could, but the paths would be slightly different from the .deb
version, and it won't necessarily integrate with the system
shutdown. However, the driver-to-upsd interface hasn't changed
between 2.6.5 and 2.7.4, as long as you use the same paths for
./configure that the 2.6.5 Debian package used.

>
> ./configure has a no under "install USB drivers" and when I add
that handle (--with-usb) in, it prompts for libusb.
>
> Does that mean I actually have to do the process referenced in
your link? Or is it fine to go ahead with that as USB drivers as a no?
>

The OpenUPS2 is connected via USB, so you'll need the libusb
dependencies.

> here is some info on that process:

http://lists.alioth.debian.org/pipermail/nut-upsuser/2016-October/010389.html


>
> In your case, you probably don't need the libusb-1.0 branch
snapshot, so you could just use a NUT tarball from the downloads
page: http://networkupstools.org/download.html#_stable_tree_2_7

>
To clarify: that thread was talking about a snapshot of a NUT
branch that uses libusb-1.0, versus the original libusb-0.1
support. If you set things up to do "apt-get build-dep nut", it
will pull in the libusb-dev package (which would cause the
./configure output to say yes for building USB drivers).




___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser


--
Tim Dawson

972-567-9360

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] NUT not recognising Mini-box OpenUPS 2

[Song Teck]

Hi Charles,

thanks for the clarification on the libusb. that indeed does work to get
the value in ./configure.

I've tried installing a .deb

sudo dpkg -i nut_2.7.4-5_all.deb
(Reading database ... 103447 files and directories currently installed.)
Preparing to replace nut 2.6.4-2.3+deb7u1 (using nut_2.7.4-5_all.deb) ...
Unpacking replacement nut ...
Setting up nut (2.7.4-5) ...

which doesn't return an error but starting upsdrvctl after still shows
v2.6.4 so that didn't work.

Does ./configure, make, sudo make install have to be carried out in a
particular directory? I've run it from a /usr/local both with and without
the user/group/usb switches and again it seems to run fine but when the
upsdrvctl is called, it still remains as 2.6.4 so evidently I'm missing
something here...

Thanks again for your patience

On 2 August 2017 at 10:02, Charles Lepple  wrote:

> On Aug 1, 2017, at 12:01 PM, Song Teck  wrote:
> >
> > Hi Charles,
> >
> > Ok, I missed the absence from the backports as well. Again, some
> unfamiliarity here, so
> >
> > 1) I presume I cannot use a metapackage meant for jessie or stretch on
> wheezy? Or if I can, is there a way to deploy it from console?
>
> The "nut" metapackage just depends on "nut-client" and "nut-server". The
> drivers are in the server package - you'd need to find a way to install a
> newer nut-server package, and I don't know if I would want to try and mix
> .deb versions like that (if it is even possible).
>
> > 2) If not and I use the 2.7.4 tar found at http://networkupstools.org/
> download.html, do i just run the classical process? i.e.
> >
> > ./configure
> > make
> > sudo make install
>
> You could, but the paths would be slightly different from the .deb
> version, and it won't necessarily integrate with the system shutdown.
> However, the driver-to-upsd interface hasn't changed between 2.6.5 and
> 2.7.4, as long as you use the same paths for ./configure that the 2.6.5
> Debian package used.
>
> >
> > ./configure has a no under "install USB drivers" and when I add that
> handle (--with-usb) in, it prompts for libusb.
> >
> > Does that mean I actually have to do the process referenced in your
> link? Or is it fine to go ahead with that as USB drivers as a no?
> >
>
> The OpenUPS2 is connected via USB, so you'll need the libusb dependencies.
>
> > here is some info on that process: http://lists.alioth.debian.
> org/pipermail/nut-upsuser/2016-October/010389.html
> >
> > In your case, you probably don't need the libusb-1.0 branch snapshot, so
> you could just use a NUT tarball from the downloads page:
> http://networkupstools.org/download.html#_stable_tree_2_7
> >
> To clarify: that thread was talking about a snapshot of a NUT branch that
> uses libusb-1.0, versus the original libusb-0.1 support. If you set things
> up to do "apt-get build-dep nut", it will pull in the libusb-dev package
> (which would cause the ./configure output to say yes for building USB
> drivers).
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] NUT not recognising Mini-box OpenUPS 2

[Charles Lepple]

On Aug 1, 2017, at 12:01 PM, Song Teck  wrote:
> 
> Hi Charles,
> 
> Ok, I missed the absence from the backports as well. Again, some 
> unfamiliarity here, so 
> 
> 1) I presume I cannot use a metapackage meant for jessie or stretch on 
> wheezy? Or if I can, is there a way to deploy it from console?

The "nut" metapackage just depends on "nut-client" and "nut-server". The 
drivers are in the server package - you'd need to find a way to install a newer 
nut-server package, and I don't know if I would want to try and mix .deb 
versions like that (if it is even possible).

> 2) If not and I use the 2.7.4 tar found at 
> http://networkupstools.org/download.html, do i just run the classical 
> process? i.e.
> 
> ./configure
> make
> sudo make install

You could, but the paths would be slightly different from the .deb version, and 
it won't necessarily integrate with the system shutdown. However, the 
driver-to-upsd interface hasn't changed between 2.6.5 and 2.7.4, as long as you 
use the same paths for ./configure that the 2.6.5 Debian package used.

> 
> ./configure has a no under "install USB drivers" and when I add that handle 
> (--with-usb) in, it prompts for libusb. 
> 
> Does that mean I actually have to do the process referenced in your link? Or 
> is it fine to go ahead with that as USB drivers as a no?
> 

The OpenUPS2 is connected via USB, so you'll need the libusb dependencies.

> here is some info on that process: 
> http://lists.alioth.debian.org/pipermail/nut-upsuser/2016-October/010389.html
> 
> In your case, you probably don't need the libusb-1.0 branch snapshot, so you 
> could just use a NUT tarball from the downloads page: 
> http://networkupstools.org/download.html#_stable_tree_2_7
> 
To clarify: that thread was talking about a snapshot of a NUT branch that uses 
libusb-1.0, versus the original libusb-0.1 support. If you set things up to do 
"apt-get build-dep nut", it will pull in the libusb-dev package (which would 
cause the ./configure output to say yes for building USB drivers).
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] NUT not recognising Mini-box OpenUPS 2

[Song Teck]

Hi Charles,

Ok, I missed the absence from the backports as well. Again, some
unfamiliarity here, so

1) I presume I cannot use a metapackage meant for jessie or stretch on
wheezy? Or if I can, is there a way to deploy it from console?
2) If not and I use the 2.7.4 tar found at
http://networkupstools.org/download.html, do i just run the classical
process? i.e.

./configure
make
sudo make install

./configure has a no under "install USB drivers" and when I add that handle
(--with-usb) in, it prompts for libusb.

Does that mean I actually have to do the process referenced in your link?
Or is it fine to go ahead with that as USB drivers as a no?

Thanks again for the assistance.



On 1 August 2017 at 20:43, Charles Lepple  wrote:

> On Aug 1, 2017, at 7:56 AM, Song Teck Ng  automation.com> wrote:
> >
> > Hi Charles,
> >
> > Thanks for your reply. So the Jessie or stretch versions will work then
> since those are 2.7.2 and 2.7.4...
> >
> > I will have to update my sources.list and follow this?
> >
> > https://backports.debian.org/Instructions/
>
> That was the thought, but I mistakenly thought that there was a NUT
> package in wheezy-backports. https://packages.debian.org/
> search?suite=wheezy-backports=nut-server does not list anything.
> (Debian only does backports by request, and that could take a while -
> especially for something in oldoldstable.)
>
> Agreed that upgrading to jessie or stretch would work.
>
> If you can install build-essential and the NUT build-deps, you could build
> a newer version from source.
>
> here is some info on that process: http://lists.alioth.debian.
> org/pipermail/nut-upsuser/2016-October/010389.html
>
> In your case, you probably don't need the libusb-1.0 branch snapshot, so
> you could just use a NUT tarball from the downloads page:
> http://networkupstools.org/download.html#_stable_tree_2_7
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] NUT not recognising Mini-box OpenUPS 2

[Charles Lepple]

On Aug 1, 2017, at 7:56 AM, Song Teck Ng  
wrote:
> 
> Hi Charles,
> 
> Thanks for your reply. So the Jessie or stretch versions will work then since 
> those are 2.7.2 and 2.7.4...
> 
> I will have to update my sources.list and follow this?
>  
> https://backports.debian.org/Instructions/

That was the thought, but I mistakenly thought that there was a NUT package in 
wheezy-backports. 
https://packages.debian.org/search?suite=wheezy-backports=nut-server 
does not list anything. (Debian only does backports by request, and that could 
take a while - especially for something in oldoldstable.)

Agreed that upgrading to jessie or stretch would work.

If you can install build-essential and the NUT build-deps, you could build a 
newer version from source.

here is some info on that process: 
http://lists.alioth.debian.org/pipermail/nut-upsuser/2016-October/010389.html

In your case, you probably don't need the libusb-1.0 branch snapshot, so you 
could just use a NUT tarball from the downloads page: 
http://networkupstools.org/download.html#_stable_tree_2_7
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] NUT not recognising Mini-box OpenUPS 2

[Song Teck Ng]

Hi Charles,

Thanks for your reply. So the Jessie or stretch versions will work then
since those are 2.7.2 and 2.7.4...

I will have to update my sources.list and follow this?

https://backports.debian.org/Instructions/

Will give it a go later and update either way.

Thanks,
ST
Via mobile

On 1 Aug 2017 19:44, "Charles Lepple"  wrote:

> On Aug 1, 2017, at 3:14 AM, Song Teck Ng  automation.com> wrote:
> > 4) Have edited the ups.conf and nut.conf files with the necessary
> entries but trying to start the driver with upsdrvctl start gives:
> > "Network UPS Tools - UPS driver controller 2.6.4
> >
> > Network UPS Tools - Generic HID driver 0.37 (2.6.4)
> >
> Support for the original OpenUPS was added in NUT v2.7.1. Is there any way
> you can use Debian Backports to get a newer version of NUT?
>
>
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] NUT not recognising Mini-box OpenUPS 2

[Charles Lepple]

On Aug 1, 2017, at 3:14 AM, Song Teck Ng  
wrote:
> 4) Have edited the ups.conf and nut.conf files with the necessary entries but 
> trying to start the driver with upsdrvctl start gives:
> "Network UPS Tools - UPS driver controller 2.6.4
> 
> Network UPS Tools - Generic HID driver 0.37 (2.6.4)
> 
Support for the original OpenUPS was added in NUT v2.7.1. Is there any way you 
can use Debian Backports to get a newer version of NUT?


___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser