Re: [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@10.0.2.151' from another system on the network? NUT Client running in FreeBSD connects to NUT server in OSX, upsc@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

battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 50
battery.date: not set
battery.mfr.date: 2010/12/23
battery.runtime: 532
battery.runtime.low: 120
battery.type: PbAc
battery.voltage: 13.5
battery.voltage.nominal: 12.0
device.mfr: APC
device.model: Back-UPS ES 550
device.serial: 3B1052X38339  
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.synchronous: no
driver.version: 2.7.3
driver.version.data: APC HID 0.95
driver.version.internal: 0.39
input.sensitivity: high
input.transfer.high: 139
input.transfer.low: 92
input.voltage: 122.0
input.voltage.nominal: 120
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.firmware: 843.K2 .D
ups.firmware.aux: K2 
ups.load: 38
ups.mfr: APC
ups.mfr.date: 2010/12/23
ups.model: Back-UPS ES 550
ups.productid: 0002
ups.serial: 3B1052X38339  
ups.status: OL
ups.timer.reboot: 0
ups.timer.shutdown: -1
ups.vendorid: 051d

Network UPS Tools - Generic HID driver 0.39 (2.7.3)
USB communication driver 0.32
Network UPS Tools - UPS driver controller 2.7.3

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

On Jul 28, 2015, at 10:10 PM, Charles Lepple <clep...@gmail.com> wrote: On Jul 28, 2015, at 12:13 PM, AIYL <adliya...@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@gmail

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