[Nut-upsdev] USB comms dropout not detected

[Arjen de Korte]

Citeren Arjen de Korte <nut+devel op de-korte.org>:

> The usbhid-ups driver doesn't know the 'Device not connected' error  
> message means that the UPS is no longer connected. The libusb  
> library is fairly verbose with error messages and not all of them  
> are a sign of trouble. Therefor, we only assume the UPS is gone for  
> specific ones and by default, they are disregarded.
>
> If you add this error in the case statement around line 1350 in  
> usbhid-ups.c that lists the conditions for reconnecting, you'll  
> probably be fine. The driver will then tell the server that the data  
> is stale after a couple of tries and reconnect once it is attached  
> again.

OK, I just found this error code (ENXIO) and added it to the list. If  
you checkout the latest version from the trunk, this should work.

Best regards, Arjen
-- 
Please keep list traffic on the list