Re: [Nut-upsuser] Help with Elite 800VA usb UPS
> Starting the driver with debug level 5 seems happier, but continue to cycle It is meant to 'cycle', it's working correctly. When you run the driver normally (i.e. not in debug mode), you don't see all that output (plus, after having established a connection with the device, the driver goes into the background), but it's doing exactly the same thing. > nutdrv_qx > > rroot@artu:~# upsdrvctl start > Network UPS Tools - UPS driver controller 2.7.2 > Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2) > Can't chdir to /var/run/nut: No such file or directory > Driver failed to start (exit status=1) > > but with blazer_usb seems better > > root@artu:~# upsdrvctl start > Network UPS Tools - UPS driver controller 2.7.2 > Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2) > Supported UPS detected with megatec protocol > Rating information unavailable > Vendor information unavailable > No values provided for battery high/low voltages in ups.conf > > Using 'guestimation' (low: -0.87, high: -1.08)! > Battery runtime will not be calculated (runtimecal not set) > > but > > root@artu:~# upsc Elit@artu > Error: Connection failure: Connection refused Also, remember that, if you launch upsd and then you change the content of ups.conf (for example, changing the driver of your UPS from 'nutdrv_qx' to 'blazer_usb'), you need to reload its configuration (upsd -c reload) or restart it (mandatory, if it's running in debug mode). So, let's try this: 1. stop all NUT-related services, 2. make sure to have the right things in your ups.conf (i.e. your UPS configured for driver 'blazer_usb'), 3. launch upsd, 4. launch the driver, 5. now check the values with upsc: what happens? ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Help with Elite 800VA usb UPS
> > hmm, apparently the UPS doesn't close the replies to our queries with > the expected CR and we (I) did not consider that case in nutdrv_qx -- > noted: > https://github.com/networkupstools/nut/issues/441 > > But blazer_usb, being less strict on the terminating CR of Q1 replies, > should work with your device. > > > root@artu:~# upsc Elit@artu > > Init SSL without certificate database > > Error: Driver not connected > > aehm, was the blazer_usb driver running? > This was tested with nutdrv_qx rroot@artu:~# upsdrvctl start Network UPS Tools - UPS driver controller 2.7.2 Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2) Can't chdir to /var/run/nut: No such file or directory Driver failed to start (exit status=1) but with blazer_usb seems better root@artu:~# upsdrvctl start Network UPS Tools - UPS driver controller 2.7.2 Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2) Supported UPS detected with megatec protocol Rating information unavailable Vendor information unavailable No values provided for battery high/low voltages in ups.conf Using 'guestimation' (low: -0.87, high: -1.08)! Battery runtime will not be calculated (runtimecal not set) but root@artu:~# upsc Elit@artu Error: Connection failure: Connection refused Starting the driver with debug level 5 seems happier, but continue to cycle root@artu:~# /lib/nut/blazer_usb -a Elit -u nut -D Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2) 0.00 debug level is '5' 0.415024 Checking device (1D6B/0001) (006/001) 0.478033 - VendorID: 1d6b 0.478074 - ProductID: 0001 0.478081 - Manufacturer: unknown 0.478089 - Product: unknown 0.478096 - Serial Number: unknown 0.478103 - Bus: 006 0.478109 Trying to match device 0.478120 Device does not match - skipping 0.478193 Checking device (1D6B/0001) (005/001) 0.541928 - VendorID: 1d6b 0.542215 - ProductID: 0001 0.542370 - Manufacturer: unknown 0.542525 - Product: unknown 0.542673 - Serial Number: unknown 0.542818 - Bus: 005 0.542959 Trying to match device 0.543981 Device does not match - skipping 0.544060 Checking device (/) (004/004) 0.560313 - VendorID: 0.560574 - ProductID: 0.560700 - Manufacturer: 0.560833 - Product: 010937 0.560958 - Serial Number: 0.561081 - Bus: 004 0.561205 Trying to match device 0.561332 Device matches 0.793308 send_to_all: SETINFO ups.vendorid "" 0.793568 send_to_all: SETINFO ups.productid "" 0.793711 send_to_all: SETINFO device.type "ups" 0.793897 send_to_all: SETINFO driver.version "2.7.2" 0.794035 send_to_all: SETINFO driver.version.internal "0.11" 0.794164 send_to_all: SETINFO driver.name "blazer_usb" 0.794289 Trying megatec protocol... 0.794402 send: Q1 1.027417 received 46 (40) 1.027475 read: (221.8 140.0 220.6 015 50.0 13.8 30.0 1001 1.027758 send_to_all: SETINFO input.voltage "221.8" 1.027796 send_to_all: SETINFO input.voltage.fault "140.0" 1.027839 send_to_all: SETINFO output.voltage "220.6" 1.027903 send_to_all: SETINFO ups.load "15" 1.027944 send_to_all: SETINFO input.frequency "50.0" 1.027970 send_to_all: SETINFO battery.voltage "13.80" 1.027990 send_to_all: SETINFO ups.temperature "30.0" 1.028011 send_to_all: SETINFO ups.beeper.status "enabled" 1.028031 send_to_all: SETINFO ups.type "offline / line interactive" 1.028049 send_to_all: SETINFO ups.status "OL" 1.028058 Status read in 1 tries 1.028067 Supported UPS detected with megatec protocol 1.028077 send: F 1.150426 received 21 (35) 1.150482 read: #220.0 000 012.0 50.0 1.150492 blazer_rating: short reply 1.150510 Rating read 1 failed 1.150520 send: F 1.273356 received 21 (35) 1.273397 read: #220.0 000 012.0 50.0 1.273402 blazer_rating: short reply 1.273407 Rating read 2 failed 1.273418 send: F 1.396336 received 21 (35) 1.396380 read: #220.0 000 012.0 50.0 1.396386 blazer_rating: short reply 1.396392 Rating read 3 failed 1.396403 Rating information unavailable 1.396411 send: I 1.591274 received 38 (35) 1.591622 read: # TR00094S 1.591816 blazer_vendor: short reply 1.591925 Vendor information read 1 failed 1.591938 send: I 1.785267 received 38 (35) 1.785641 read: # TR00094S 1.785879 blazer_vendor: short reply 1.786077 Vendor information read 2 failed 1.786275 send: I 1.980336 received 38 (35) 1.980814 read: # TR00094S 1.981136 blazer_vendor: short reply 1.981417 Vendor information read 3
Re: [Nut-upsuser] Apple Mac slave
On Fri, 9 Jun 2017, Robbie van der Walle wrote: ... and also still open is the notification on the Mac. If notify-send is available on the Mac, then perhaps this will work: In upsmon.conf on the Mac you need NOTIFYCMD /usr/sbin/upssched(or wherever this goes on a Mac) NOTIFYFLAG ONBATT SYSLOG+EXEC In upssched.conf you need CMDSCRIPT /usr/sbin/upssched-cmd(or wherever this goes on a Mac) AT ONBATT UPS@NAS EXECUTE on-battery In upssched-cmd you need case $1 in (on-battery) MSG="Power failure. Save your work!" notify-send -a nut -u critical -t 60 $MSG ;; (*) logger -i -t upssched-cmd "Unrecognized command: \"$1\"." ;; esac Roger ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
