<div dir="ltr"><div>Hello,</div><div><br></div><div> Not sure from this log what exactly needs to be helped with? It ends with logging into the data server to monitor "EPYC" and does not claim any inability to do so. Does some HA console report UPS information?<br><br></div><div> Note that earlier "could not find PID" messages are just that: no earlier running (or crashed) daemon instance was found, so this one does not have to clean up before work.</div><div><br></div><div> The ones about fixing up invalid USB vendor HID reports... well, some coders can't read the spec right, it seems; life is life - so we do what we can about it. If you suspect this fix introduces some problems, that logic can be disabled with an UPS config flag `disable_fix_report_desc` (no idea how to set that with HA).<br></div><div><br></div><div>Jim</div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Nov 4, 2023 at 6:06 PM Raul Milan via Nut-upsdev <<a href="mailto:nut-upsdev@alioth-lists.debian.net">nut-upsdev@alioth-lists.debian.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Good Evening, I recently purchased an EPYC quantum UPS. I installed<br>
NUT on the home assistant by connecting the UPS via USB and tried all<br>
the various drivers in the list, the only one that seems to work is:<br>
usbhid-ups<br>
with this log:<br>
<br>
s6-rc: info: service s6rc-oneshot-runner: starting<br>
s6-rc: info: service s6rc-oneshot-runner successfully started<br>
s6-rc: info: service base-addon-banner: starting<br>
<br>
-----------------------------------------------------------<br>
Add-on: Network UPS Tools<br>
Manage battery backup (UPS) devices<br>
-----------------------------------------------------------<br>
Add-on version: 0.12.2<br>
You are running the latest version of this add-on.<br>
System: Home Assistant OS 11.0 (aarch64 / raspberrypi3-64)<br>
Home Assistant Core: 2023.10.5<br>
Home Assistant Supervisor: 2023.10.1<br>
-----------------------------------------------------------<br>
Please, share the above information when looking for help<br>
or support in, e.g., GitHub, forums or the Discord chat.<br>
-----------------------------------------------------------<br>
s6-rc: info: service base-addon-banner successfully started<br>
s6-rc: info: service fix-attrs: starting<br>
s6-rc: info: service base-addon-timezone: starting<br>
s6-rc: info: service base-addon-log-level: starting<br>
s6-rc: info: service fix-attrs successfully started<br>
[17:19:09] INFO: Configuring timezone (Europe/Rome)...<br>
s6-rc: info: service base-addon-log-level successfully started<br>
s6-rc: info: service base-addon-timezone successfully started<br>
s6-rc: info: service legacy-cont-init: starting<br>
cont-init: info: running /etc/cont-init.d/nut.sh<br>
[17:19:13] INFO: Setting mode to netserver...<br>
[17:19:13] INFO: Generating /etc/nut/upsd.users...<br>
[17:19:14] INFO: Configuring user: Raul<br>
[17:19:17] INFO: Password is NOT in the Have I Been Pwned database! Nice!<br>
[17:19:20] INFO: Configuring Device named EPYC...<br>
[17:19:21] INFO: Starting the UPS drivers...<br>
HIDParse: LogMax is less than LogMin. Vendor HID report descriptor may<br>
be incorrect; interpreting LogMax -1 as 65535 in ReportID: 0x0f<br>
Network UPS Tools - Generic HID driver 0.47 (2.8.0)<br>
HIDParse: LogMax is less than LogMin. Vendor HID report descriptor may<br>
be incorrect; interpreting LogMax -1 as 255 in ReportID: 0x12<br>
HIDParse: LogMax is less than LogMin. Vendor HID report descriptor may<br>
be incorrect; interpreting LogMax -1 as 255 in ReportID: 0x13<br>
USB communication driver (libusb 1.0) 0.43<br>
Using subdriver: CyberPower HID 0.6<br>
Network UPS Tools - UPS driver controller 2.8.0<br>
cont-init: info: /etc/cont-init.d/nut.sh exited 0<br>
cont-init: info: running /etc/cont-init.d/nutclient.sh<br>
cont-init: info: /etc/cont-init.d/nutclient.sh exited 0<br>
s6-rc: info: service legacy-cont-init successfully started<br>
s6-rc: info: service legacy-services: starting<br>
services-up: info: copying legacy longrun upsd (no readiness notification)<br>
services-up: info: copying legacy longrun upsmon (no readiness notification)<br>
s6-rc: info: service legacy-services successfully started<br>
[17:19:23] INFO: Starting the UPS information server...<br>
0.000000 fopen /run/nut/upsd.pid: No such file or directory<br>
0.000112 Could not find PID file '/run/nut/upsd.pid' to see if<br>
previous upsd instance is already running!<br>
<br>
0.001586 [D1] debug level is '1'<br>
0.002585 listening on 0.0.0.0 port 3493<br>
0.004322 Connected to UPS [EPYC]: usbhid-ups-EPYC<br>
0.012424 Running as foreground process, not saving a PID file<br>
[17:19:23] INFO: Starting the UPS monitor and shutdown controller...<br>
0.000000 fopen /run/nut/upsmon.pid: No such file or directory<br>
0.000110 Could not find PID file to see if previous upsmon instance<br>
is already running!<br>
<br>
0.001042 Using power down flag file /etc/killpower<br>
0.001609 UPS: EPYC@localhost (primary) (power value 1)<br>
0.001763 [D1] debug level is '1'<br>
0.001939 [D1] debug level is '1'<br>
0.001977 Warning: running as one big root process by request (upsmon -p)<br>
0.002388 [D1] Saving PID 459 into /run/nut/upsmon.pid<br>
Init SSL without certificate database<br>
0.158135 [D1] Trying to connect to UPS [EPYC@localhost]<br>
0.628063 User <a href="mailto:upsmonmaster@127.0.0.1" target="_blank">upsmonmaster@127.0.0.1</a> logged into UPS [EPYC]<br>
0.165988 [D1] Logged into UPS EPYC@localhost<br>
<br>
You can help me?<br>
Thanks Raul Milan<br>
<br>
_______________________________________________<br>
Nut-upsdev mailing list<br>
<a href="mailto:Nut-upsdev@alioth-lists.debian.net" target="_blank">Nut-upsdev@alioth-lists.debian.net</a><br>
<a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev" rel="noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev</a><br>
</blockquote></div>