[Nut-upsuser] MACOSX-UPS Client/Server Communications Issues

[AIYL]

I’ve already completed the tests,  setting up NUT in FreeBSD running in a Parallels virtual machine.

Results:
a.- Can you try 'upsc ups at 10.0.2.151 <mailto:ups at 10.0.2.151>' from another system on the network?
NUT Client running in FreeBSD connects to NUT server in OSX, upsc at 10.0.2.151, output:
battery.charge: 100
battery.runtime: 480
battery.voltage: 13.500
device.mfr: (unknown)
device.model: Back-UPS ES 550 FW:843.K2 .D USB FW:K2
device.type: ups
driver.name: macosx-ups
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.synchronous: no
driver.version: 2.7.3
driver.version.internal: 1.1
ups.status: OL CHRG

b.- NUT Server setup in FreeBSD to test NAS’es NUT client connection to a server monitoring a “real “ UPS device
Both NAS’es ReadyNas and Synology have succesfully connected to the NUT server and correctly recognized the UPS device

Conclusions:
a.- The OSX firewall is correctly setup to allow communications between the NUT server and the NUT clients
b.- The NAS’es NUT clients connection to a NUT Server in FreeBSD monitoring a “real” UPS device successfully identify the UPS device connected to the NUT server.

See FreeBSD NUT server setup messages and NAS’es UPS screens attached.

The NUT software running the driver MACOSX-UPS is a great and unique tool (I’ve found no other option able to manage my setup while using the OSX Power Management services), any further development effort will be of great value. For example to manage several networked Mac computers, while using the OSX Power Management Services in all of them.

Thank you.

Adolfo Yanes





> On Jul 28, 2015, at 10:10 PM, Charles Lepple <clepple at gmail.com> wrote:
> 
> On Jul 28, 2015, at 12:13 PM, AIYL <adliyanes at gmail.com <mailto:adliyanes at gmail.com>> wrote:
> 
>> Before contacting Synology and Netgear/Readynas, I’d prefer to make sure that the NUT UPS Server has been setup correctly and that the “experimental” MACOSX-UPS driver is equivalent to a standard “usb” driver in terms of server/client communications.
> 
> I flagged it "experimental" because the UPS-to-driver interface is not as robust as USB or serial, but that shouldn't affect the upsd-to-NAS connection. Once the driver starts, and assuming the UPS is not disconnected, things should work similarly to other drivers.
> 
> Gracefully handling disconnection is a known issue for the macosx-ups driver, and it is also known that the information provided by OS X is less detailed than what you would get from usbhid-ups on a non-OSX system. Hopefully the latter is not causing an issue: the NAS should not be relying on anything other than "ups.status" and possibly a few other variables.
> 
> -- 
> Charles Lepple
> clepple at gmail
> 
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150801/48af47c9/attachment-0006.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: FreeBSD NUT Server upsc 20150801.txt
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150801/48af47c9/attachment-0003.txt>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150801/48af47c9/attachment-0007.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: FreeBSD NUT Server upsdrvctl 20150801.txt
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150801/48af47c9/attachment-0004.txt>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150801/48af47c9/attachment-0008.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: FreeUPD NUT Client OSX NUT Server MACOSX upsc from client 20150801.txt
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150801/48af47c9/attachment-0005.txt>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150801/48af47c9/attachment-0009.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ReadyNAS Nut Client FreeBSD NUT Server Connection 3 20150801.png
Type: image/png
Size: 8412 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150801/48af47c9/attachment-0002.png>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150801/48af47c9/attachment-0010.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Synology NUT Client FreeBSD NUT Server Connection 3 20150801.png
Type: image/png
Size: 16473 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150801/48af47c9/attachment-0003.png>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150801/48af47c9/attachment-0011.html>