Hello, Replaced UPS Kstar Micropower Micro 1200 (managed via blazer_usb) with https://www.njoy.ro/UPS/horus-plus-2000. The latter doesn't seem to be supported. 1. I tried blazer_usb and usbhid-ups. Any other suggestions? 2. What would be needed to get it supported by NUT? ======== HW =======HP Microserver Gen 8 ======== UPS =======Working:Kstar Micropower Micro 1200http://www.kstar.com/Line%20Interactive%20UPS%20OEM/10189.jhtml Software: http://www.kstar.com/download5/index.jhtml Not working:nJoy Horus Plus 2000https://www.njoy.ro/UPS/horus-plus-2000 Software: https://www.power-software-download.com/viewpower.html *** Cable/UPS physically detected: root at omv:~# lsusb Bus 001 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial *** Tried different USB ports on the server to no avail. Cable still visible, UPS not. *** Connected UPS with same usb cable to Windows laptop with ViewPower software installed and it was detected and I was able to manage it. ======= NUT ========ii nut-client 2.7.4-5 amd64 network UPS tools - clientsii nut-server 2.7.4-5 amd64 network UPS tools - core system ======= OS ========No LSB modules are available.Distributor ID: DebianDescription: Debian GNU/Linux 9.11 (stretch)Release: 9.11Codename: stretch ========== Error =========root at omv:~# systemctl status nut-driver.service● nut-driver.service - Network UPS Tools - power device driver controller Loaded: loaded (/lib/systemd/system/nut-driver.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2019-09-27 15:07:49 EEST; 4min 26s ago Process: 6518 ExecStart=/sbin/upsdrvctl start (code=exited, status=1/FAILURE) Sep 27 15:07:47 omv systemd[1]: nut-driver.service: Failed to enqueue stop job, ignoring: Transaction is destructive.Sep 27 15:07:47 omv systemd[1]: Starting Network UPS Tools - power device driver controller...Sep 27 15:07:49 omv upsdrvctl[6518]: No supported UPS detectedSep 27 15:07:49 omv upsdrvctl[6518]: Network UPS Tools - Megatec/Q1 protocol USB driver 0.12 (2.7.4)Sep 27 15:07:49 omv upsdrvctl[6518]: Driver failed to start (exit status=1)Sep 27 15:07:49 omv upsdrvctl[6518]: Network UPS Tools - UPS driver controller 2.7.4Sep 27 15:07:49 omv systemd[1]: nut-driver.service: Control process exited, code=exited status=1Sep 27 15:07:49 omv systemd[1]: Failed to start Network UPS Tools - power device driver controller.Sep 27 15:07:49 omv systemd[1]: nut-driver.service: Unit entered failed state.Sep 27 15:07:49 omv systemd[1]: nut-driver.service: Failed with result 'exit-code'. ========= NUT conf ============root at omv:~# cat /etc/nut/ups.conf[ups]port = autodriver = blazer_usb Thanks.Dragos -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20190927/6e92f7fb/attachment.html>
Hello,
Anyone, any idea?
On Friday, September 27, 2019, 04:19:34 PM GMT+3, Dragos Leahu
<dragos_leahu at yahoo.com> wrote:
Hello,
Replaced UPS Kstar Micropower Micro 1200 (managed via blazer_usb) with
https://www.njoy.ro/UPS/horus-plus-2000. The latter doesn't seem to be
supported.
1. I tried blazer_usb and usbhid-ups. Any other suggestions? 2. What would be
needed to get it supported by NUT?
======== HW =======HP Microserver Gen 8
======== UPS =======Working:Kstar Micropower Micro
1200http://www.kstar.com/Line%20Interactive%20UPS%20OEM/10189.jhtml
Software: http://www.kstar.com/download5/index.jhtml
Not working:nJoy Horus Plus 2000https://www.njoy.ro/UPS/horus-plus-2000
Software: https://www.power-software-download.com/viewpower.html
*** Cable/UPS physically detected:
root at omv:~# lsusb
Bus 001 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial
*** Tried different USB ports on the server to no avail. Cable still visible,
UPS not.
*** Connected UPS with same usb cable to Windows laptop with ViewPower software
installed and it was detected and I was able to manage it.
======= NUT ========ii nut-client 2.7.4-5 amd64 network UPS tools - clientsii
nut-server 2.7.4-5 amd64 network UPS tools - core system
======= OS ========No LSB modules are available.Distributor ID:
DebianDescription: Debian GNU/Linux 9.11 (stretch)Release: 9.11Codename: stretch
========== Error =========root at omv:~# systemctl status nut-driver.service●
nut-driver.service - Network UPS Tools - power device driver controller
Loaded: loaded (/lib/systemd/system/nut-driver.service; static; vendor preset:
enabled) Active: failed (Result: exit-code) since Fri 2019-09-27 15:07:49
EEST; 4min 26s ago Process: 6518 ExecStart=/sbin/upsdrvctl start (code=exited,
status=1/FAILURE)
Sep 27 15:07:47 omv systemd[1]: nut-driver.service: Failed to enqueue stop job,
ignoring: Transaction is destructive.Sep 27 15:07:47 omv systemd[1]: Starting
Network UPS Tools - power device driver controller...Sep 27 15:07:49 omv
upsdrvctl[6518]: No supported UPS detectedSep 27 15:07:49 omv upsdrvctl[6518]:
Network UPS Tools - Megatec/Q1 protocol USB driver 0.12 (2.7.4)Sep 27 15:07:49
omv upsdrvctl[6518]: Driver failed to start (exit status=1)Sep 27 15:07:49 omv
upsdrvctl[6518]: Network UPS Tools - UPS driver controller 2.7.4Sep 27 15:07:49
omv systemd[1]: nut-driver.service: Control process exited, code=exited
status=1Sep 27 15:07:49 omv systemd[1]: Failed to start Network UPS Tools -
power device driver controller.Sep 27 15:07:49 omv systemd[1]:
nut-driver.service: Unit entered failed state.Sep 27 15:07:49 omv systemd[1]:
nut-driver.service: Failed with result 'exit-code'.
========= NUT conf ============root at omv:~# cat /etc/nut/ups.conf[ups]port =
autodriver = blazer_usb
Thanks.Dragos
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20191029/bfe9ab3f/attachment.html>
On Sep 27, 2019, at 9:19 AM, Dragos Leahu wrote:> > Hello, > > Replaced UPS Kstar Micropower Micro 1200 (managed via blazer_usb) with https://www.njoy.ro/UPS/horus-plus-2000. The latter doesn't seem to be supported. > > 1. I tried blazer_usb and usbhid-ups. Any other suggestions?blazer_usb is no longer maintained - try nutdrv_qx instead. You may need some additional flags: https://networkupstools.org/docs/man/nutdrv_qx.html> root at omv:~# lsusb > > Bus 001 Device 005: ID 0665:5161 Cypress Semiconductor USB to SerialDoes this device show up as a USB serial port in /dev? (e.g. /dev/ttyUSB0) You can sometimes see evidence of this in dmesg/journalctl when you plug in the USB cable (useful if the /dev name is different)
Hello,
No ttyUSB* device under /dev however the new driver has detected the UPS, the
nut services are able to start, just "upsc -l ups" sais unknown error
and doesn't return any information. Could be due to the driver unable to
detect number of battery packs as reported by the nut-driver.service startup?
How can I fix that?
root at omv:~# systemctl status nut-driver.service● nut-driver.service - Network
UPS Tools - power device driver controller Loaded: loaded
(/lib/systemd/system/nut-driver.service; static; vendor preset: enabled)
Active: active (running) since Sun 2019-11-03 12:41:51 EET; 10min ago Main PID:
3569 (nutdrv_qx) Tasks: 1 (limit: 9830) CGroup:
/system.slice/nut-driver.service └─3569 /lib/nut/nutdrv_qx -a ups
Nov 03 12:41:49 omv systemd[1]: Starting Network UPS Tools - power device driver
controller...Nov 03 12:41:50 omv upsdrvctl[3561]: Using protocol:
Voltronic-QS-Hex 0.10Nov 03 12:41:51 omv upsdrvctl[3561]: Can't autodetect
number of battery packs [-1/27.29]Nov 03 12:41:51 omv upsdrvctl[3561]: Battery
runtime will not be calculated (runtimecal not set)Nov 03 12:41:51 omv
upsdrvctl[3561]: Network UPS Tools - UPS driver controller 2.7.4Nov 03 12:41:51
omv systemd[1]: Started Network UPS Tools - power device driver controller.Nov
03 12:41:51 omv nutdrv_qx[3569]: Startup
successful===========================root at omv:~# systemctl status
nut-monitor.service● nut-monitor.service - Network UPS Tools - power device
monitor and shutdown controller Loaded: loaded
(/lib/systemd/system/nut-monitor.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2019-11-03 12:41:53 EET; 11min ago Main PID:
3602 (upsmon) Tasks: 2 (limit: 9830) CGroup:
/system.slice/nut-monitor.service ├─3601 /lib/nut/upsmon
└─3602 /lib/nut/upsmon
Nov 03 12:41:53 omv upsmon[3600]: fopen /var/run/nut/upsmon.pid: No such file or
directoryNov 03 12:41:53 omv upsmon[3600]: UPS: ups at localhost (master) (power
value 1)Nov 03 12:41:53 omv upsmon[3600]: Using power down flag file
/etc/killpowerNov 03 12:41:53 omv upsmon[3601]: Startup successfulNov 03
12:41:53 omv upsmon[3602]: Init SSL without certificate databaseNov 03 12:41:53
omv systemd[1]: nut-monitor.service: Supervising process 3602 which is not our
child. We'll most likely not notice when it exits.Nov 03 12:41:53 omv
systemd[1]: Started Network UPS Tools - power device monitor and shutdown
controller.Nov 03 12:41:53 omv systemd[1]: nut-monitor.service: Supervising
process 3602 which is not our child. We'll most likely not notice when it
exits.Nov 03 12:41:53 omv systemd[1]: nut-monitor.service: Supervising process
3602 which is not our child. We'll most likely not notice when it exits.Nov
03 12:41:53 omv systemd[1]: nut-monitor.service: Supervising process 3602 which
is not our child. We'll most likely not notice when it
exits.=========================root at omv:~# systemctl status
nut-server.service● nut-server.service - Network UPS Tools - power devices
information server Loaded: loaded (/lib/systemd/system/nut-server.service;
enabled; vendor preset: enabled) Active: active (running) since Sun 2019-11-03
12:41:51 EET; 13min ago Main PID: 3571 (upsd) Tasks: 1 (limit: 9830)
CGroup: /system.slice/nut-server.service └─3571 /lib/nut/upsd
Nov 03 12:41:51 omv systemd[1]: Starting Network UPS Tools - power devices
information server...Nov 03 12:41:51 omv upsd[3570]: fopen
/var/run/nut/upsd.pid: No such file or directoryNov 03 12:41:51 omv upsd[3570]:
listening on 0.0.0.0 port 3493Nov 03 12:41:51 omv upsd[3570]: listening on
0.0.0.0 port 3493Nov 03 12:41:51 omv upsd[3570]: Connected to UPS [ups]:
nutdrv_qx-upsNov 03 12:41:51 omv systemd[1]: Started Network UPS Tools - power
devices information server.Nov 03 12:41:51 omv upsd[3571]: Startup successfulNov
03 12:41:53 omv upsd[3571]: User ups at 10.0.3.4 logged into UPS [ups]Nov 03
12:41:53 omv upsd[3571]: User monmaster at 127.0.0.1 logged into UPS [ups]Nov 03
12:41:54 omv upsd[3571]: User ups at 10.0.3.5 logged into UPS
[ups]===========================root at omv:~# upscmd -l upsInstant commands
supported on UPS [ups]:
beeper.toggle - Toggle the UPS beeperload.off - Turn off the load
immediatelyload.on - Turn on the load immediatelyshutdown.return - Turn off the
load and return when power is backshutdown.stayoff - Turn off the load and
remain offshutdown.stop - Stop a shutdown in
progress=========================root at omv:~# upsc -l upsError: Unknown
error=========================USB cable disconnect and reconnect:
Nov 04 13:09:09 omv kernel: usb 1-1.6: USB disconnect, device number 8Nov 04
13:09:17 omv kernel: usb 1-1.6: new low-speed USB device number 9 using
ehci-pciNov 04 13:09:17 omv kernel: usb 1-1.6: New USB device found,
idVendor=0665, idProduct=5161, bcdDevice= 0.02Nov 04 13:09:17 omv kernel: usb
1-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0Nov 04 13:09:17
omv kernel: usb 1-1.6: Product: USB to SerialNov 04 13:09:17 omv kernel: usb
1-1.6: Manufacturer: INNO TECHNov 04 13:09:17 omv kernel: hid-generic
0003:0665:5161.0006: hiddev0,hidraw0: USB HID v1.00 Device [INNO TECH USB to
Serial] on usb-0000:00:1a.0-1.6/input0==========================
Thank you.Dragos
On Sunday, November 3, 2019, 01:09:54 AM GMT+2, Charles Lepple <clepple
at gmail.com> wrote:
On Sep 27, 2019, at 9:19 AM, Dragos Leahu wrote:>
> Hello,
>
> Replaced UPS Kstar Micropower Micro 1200 (managed via blazer_usb) with
https://www.njoy.ro/UPS/horus-plus-2000. The latter doesn't seem to be
supported.
>
> 1. I tried blazer_usb and usbhid-ups. Any other suggestions?
blazer_usb is no longer maintained - try nutdrv_qx instead. You may need some
additional flags: https://networkupstools.org/docs/man/nutdrv_qx.html
> root at omv:~# lsusb
>
> Bus 001 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial
Does this device show up as a USB serial port in /dev? (e.g. /dev/ttyUSB0) You
can sometimes see evidence of this in dmesg/journalctl when you plug in the USB
cable (useful if the /dev name is different)
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20191104/74326c53/attachment.html>