<html><head></head><body><div class="ydp3b749da2yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;"><div></div>
<div><div><div>Hello,</div><div><br></div><div>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?</div><div><br></div><div>root@omv:~# systemctl status nut-driver.service</div><div>● nut-driver.service - Network UPS Tools - power device driver controller</div><div> Loaded: loaded (/lib/systemd/system/nut-driver.service; static; vendor preset: enabled)</div><div> Active: active (running) since Sun 2019-11-03 12:41:51 EET; 10min ago</div><div> Main PID: 3569 (nutdrv_qx)</div><div> Tasks: 1 (limit: 9830)</div><div> CGroup: /system.slice/nut-driver.service</div><div> └─3569 /lib/nut/nutdrv_qx -a ups</div><div><br></div><div>Nov 03 12:41:49 omv systemd[1]: Starting Network UPS Tools - power device driver controller...</div><div>Nov 03 12:41:50 omv upsdrvctl[3561]: Using protocol: Voltronic-QS-Hex 0.10</div><div>Nov 03 12:41:51 omv upsdrvctl[3561]: Can't autodetect number of battery packs [-1/27.29]</div><div>Nov 03 12:41:51 omv upsdrvctl[3561]: Battery runtime will not be calculated (runtimecal not set)</div><div>Nov 03 12:41:51 omv upsdrvctl[3561]: Network UPS Tools - UPS driver controller 2.7.4</div><div>Nov 03 12:41:51 omv systemd[1]: Started Network UPS Tools - power device driver controller.</div><div>Nov 03 12:41:51 omv nutdrv_qx[3569]: Startup successful</div><div>============================</div><div><br></div><div>root@omv:~# systemctl status nut-monitor.service</div><div>● nut-monitor.service - Network UPS Tools - power device monitor and shutdown controller</div><div> Loaded: loaded (/lib/systemd/system/nut-monitor.service; enabled; vendor preset: enabled)</div><div> Active: active (running) since Sun 2019-11-03 12:41:53 EET; 11min ago</div><div> Main PID: 3602 (upsmon)</div><div> Tasks: 2 (limit: 9830)</div><div> CGroup: /system.slice/nut-monitor.service</div><div> ├─3601 /lib/nut/upsmon</div><div> └─3602 /lib/nut/upsmon</div><div><br></div><div>Nov 03 12:41:53 omv upsmon[3600]: fopen /var/run/nut/upsmon.pid: No such file or directory</div><div>Nov 03 12:41:53 omv upsmon[3600]: UPS: ups@localhost (master) (power value 1)</div><div>Nov 03 12:41:53 omv upsmon[3600]: Using power down flag file /etc/killpower</div><div>Nov 03 12:41:53 omv upsmon[3601]: Startup successful</div><div>Nov 03 12:41:53 omv upsmon[3602]: Init SSL without certificate database</div><div>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.</div><div>Nov 03 12:41:53 omv systemd[1]: Started Network UPS Tools - power device monitor and shutdown controller.</div><div>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.</div><div>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.</div><div>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.</div><div>==========================</div><div><br></div><div>root@omv:~# systemctl status nut-server.service</div><div>● nut-server.service - Network UPS Tools - power devices information server</div><div> Loaded: loaded (/lib/systemd/system/nut-server.service; enabled; vendor preset: enabled)</div><div> Active: active (running) since Sun 2019-11-03 12:41:51 EET; 13min ago</div><div> Main PID: 3571 (upsd)</div><div> Tasks: 1 (limit: 9830)</div><div> CGroup: /system.slice/nut-server.service</div><div> └─3571 /lib/nut/upsd</div><div><br></div><div>Nov 03 12:41:51 omv systemd[1]: Starting Network UPS Tools - power devices information server...</div><div>Nov 03 12:41:51 omv upsd[3570]: fopen /var/run/nut/upsd.pid: No such file or directory</div><div>Nov 03 12:41:51 omv upsd[3570]: listening on 0.0.0.0 port 3493</div><div>Nov 03 12:41:51 omv upsd[3570]: listening on 0.0.0.0 port 3493</div><div>Nov 03 12:41:51 omv upsd[3570]: Connected to UPS [ups]: nutdrv_qx-ups</div><div>Nov 03 12:41:51 omv systemd[1]: Started Network UPS Tools - power devices information server.</div><div>Nov 03 12:41:51 omv upsd[3571]: Startup successful</div><div>Nov 03 12:41:53 omv upsd[3571]: User ups@10.0.3.4 logged into UPS [ups]</div><div>Nov 03 12:41:53 omv upsd[3571]: User monmaster@127.0.0.1 logged into UPS [ups]</div><div>Nov 03 12:41:54 omv upsd[3571]: User ups@10.0.3.5 logged into UPS [ups]</div><div>============================</div><div><br></div><div>root@omv:~# upscmd -l ups</div><div>Instant commands supported on UPS [ups]:</div><div><br></div><div>beeper.toggle - Toggle the UPS beeper</div><div>load.off - Turn off the load immediately</div><div>load.on - Turn on the load immediately</div><div>shutdown.return - Turn off the load and return when power is back</div><div>shutdown.stayoff - Turn off the load and remain off</div><div>shutdown.stop - Stop a shutdown in progress</div><div>==========================</div><div><br></div><div>root@omv:~# upsc -l ups</div><div>Error: Unknown error</div><div>==========================</div><div><br></div><div>USB cable disconnect and reconnect:</div><div><br></div><div>Nov 04 13:09:09 omv kernel: usb 1-1.6: USB disconnect, device number 8</div><div>Nov 04 13:09:17 omv kernel: usb 1-1.6: new low-speed USB device number 9 using ehci-pci</div><div>Nov 04 13:09:17 omv kernel: usb 1-1.6: New USB device found, idVendor=0665, idProduct=5161, bcdDevice= 0.02</div><div>Nov 04 13:09:17 omv kernel: usb 1-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0</div><div>Nov 04 13:09:17 omv kernel: usb 1-1.6: Product: USB to Serial</div><div>Nov 04 13:09:17 omv kernel: usb 1-1.6: Manufacturer: INNO TECH</div><div>Nov 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</div><div>===========================</div><div><br></div><div><br></div><div>Thank you.</div><div>Dragos</div><div><br></div></div><br></div><div><br></div>
</div><div id="ydp73bcc7bdyahoo_quoted_3452753022" class="ydp73bcc7bdyahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Sunday, November 3, 2019, 01:09:54 AM GMT+2, Charles Lepple <clepple@gmail.com> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr">On Sep 27, 2019, at 9:19 AM, Dragos Leahu wrote:<br clear="none">> <br clear="none">> Hello,<br clear="none">> <br clear="none">> Replaced UPS Kstar Micropower Micro 1200 (managed via blazer_usb) with <a shape="rect" href="https://www.njoy.ro/UPS/horus-plus-2000. " rel="nofollow" target="_blank">https://www.njoy.ro/UPS/horus-plus-2000. </a>The latter doesn't seem to be supported.<br clear="none">> <br clear="none">> 1. I tried blazer_usb and usbhid-ups. Any other suggestions? <br clear="none"><br clear="none">blazer_usb is no longer maintained - try nutdrv_qx instead. You may need some additional flags: <a shape="rect" href="https://networkupstools.org/docs/man/nutdrv_qx.html" rel="nofollow" target="_blank">https://networkupstools.org/docs/man/nutdrv_qx.html</a><div class="ydp73bcc7bdyqt7089419725" id="ydp73bcc7bdyqtfd29664"><br clear="none"><br clear="none">> <a shape="rect" href="mailto:root@omv" rel="nofollow" target="_blank">root@omv</a>:~# lsusb<br clear="none">> <br clear="none">> Bus 001 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial</div><br clear="none"><br clear="none">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)</div></div>
</div>
</div></body></html>