Description of problem:
  UPS Eaton 5E 1100iUSB is recognized and immediately disconnected: 
# journalctl -fe
 kernel: usb 1-8: USB disconnect, device number 85
 kernel: usb 1-8: new low-speed USB device number 86 using xhci_hcd
 kernel: usb 1-8: New USB device found, idVendor=0463, idProduct=ffff, bcdDevice= 0.01
 kernel: usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=0
 kernel: usb 1-8: Product: 5E
 kernel: usb 1-8: Manufacturer: EATON
 kernel: hid-generic 0003:0463:FFFF.0055: hiddev97,hidraw1: USB HID v1.10 Device [EATON 5E] on usb-0000:00:14.0-8/input0
 mtp-probe[15330]: checking bus 1, device 86: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-8"
 mtp-probe[15330]: bus: 1, device: 86 was not an MTP device
 mtp-probe[15336]: checking bus 1, device 86: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-8"
 mtp-probe[15336]: bus: 1, device: 86 was not an MTP device
 kernel: hid-generic 0003:0463:FFFF.0055: usb_submit_urb(ctrl) failed: -1
 kernel: hid-generic 0003:0463:FFFF.0055: timeout initializing reports
 kernel: usb 1-8: USB disconnect, device number 86
  And device ID goes 86 - 86 and so on.

  lsusb shows UPS for a while, then device disappears (probably because it is disconnected) and then shows UPS with incremented device number (reconnected):
# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 09da:c10a A4Tech Co., Ltd.
Bus 001 Device 086: ID 0463:ffff MGE UPS Systems UPS
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
----
# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 09da:c10a A4Tech Co., Ltd.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
----
# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 09da:c10a A4Tech Co., Ltd.
Bus 001 Device 092: ID 0463:ffff MGE UPS Systems UPS
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

   NUT scanners shows this:   nut-scanner -U
Scanning USB bus.
[nutdev1]
	driver = "usbhid-ups"
	port = "auto"
	vendorid = "0463"
	productid = "FFFF"
	bus = "001"

# cat ups.conf  contains section:
[ups]
	driver = "usbhid-ups"
	port = "auto"
	vendorid = "0463"
	productid = "FFFF"

   blazer_usb is not the appropriate driver:
# blazer_usb -DD -u root -x vendorid=0463 -a ups
Network UPS Tools - Megatec/Q1 protocol USB driver 0.12 (2.7.4)
   0.000000     Error: UPS [ups] is for driver usbhid-ups, but I'm blazer_usb!
   
   usbhid-ups should be the correct driver (detects USB mouse and USB UPS):
# usbhid-ups -DD -u root -x vendorid=0463 -a ups
Network UPS Tools - Generic HID driver 0.41 (2.7.4)
USB communication driver 0.33
   0.000000     debug level is '2'
   0.001211     upsdrv_initups...
   0.002192     Checking device (1D6B/0003) (002/001)
   0.002292     - VendorID: 1d6b
   0.002298     - ProductID: 0003
   0.002309     - Manufacturer: Linux 5.0.4-200.fc29.x86_64 xhci-hcd
   0.002313     - Product: xHCI Host Controller
   0.002316     - Serial Number: 0000:00:14.0
   0.002320     - Bus: 002
   0.002325     - Device release number: 0500
   0.002329     Trying to match device
   0.002349     Device does not match - skipping
   0.002396     Checking device (09DA/C10A) (001/002)
   0.004630     - VendorID: 09da
   0.004637     - ProductID: c10a
   0.004640     - Manufacturer: A4Tech
   0.004642     - Product: USB Mouse
   0.004644     - Serial Number: unknown
   0.004646     - Bus: 001
   0.004648     - Device release number: 1032
   0.004650     Trying to match device
   0.004653     Device does not match - skipping
   0.004659     Checking device (0463/FFFF) (001/078)
   2.005157     - VendorID: 0463
   2.005196     - ProductID: ffff
   2.005205     - Manufacturer: unknown
   2.005214     - Product: unknown
   2.005222     - Serial Number: unknown
   2.005234     - Bus: 001
   2.005244     - Device release number: 0001
   2.005263     Trying to match device
   2.005366     Device matches
   2.005411     failed to claim USB device: Device or resource busy
   9.837128     detached kernel driver from USB device...
  14.837390     Unable to get HID descriptor (Connection timed out)
  14.837423     HID descriptor length 549
  14.837877     Unable to get Report descriptor: Broken pipe
  14.837976     Checking device (1D6B/0002) (001/001)
  14.838237     - VendorID: 1d6b
  14.838258     - ProductID: 0002
  14.838274     - Manufacturer: Linux 5.0.4-200.fc29.x86_64 xhci-hcd
  14.838286     - Product: xHCI Host Controller
  14.838296     - Serial Number: 0000:00:14.0
  14.838307     - Bus: 001
  14.838321     - Device release number: 0500
  14.838331     Trying to match device
  14.838348     Device does not match - skipping
  14.838367     No appropriate HID device found
  14.838379     No matching HID UPS found

  Same UPS device with same cable is working properly when connected to different machines with OS  Fedora 23, Fedora 26, Fedora 29 4.18.16-300.fc29.x86_64 and Windows 10 (with the bundled Win UPS soft).
  The problem is observed when the UPS is connected to 3 different machines with later Fedora 29 kernel (f.e. 5.0.4-200.fc29.x86_64) and all Fedora 30 versions available at the moment. Connecting the UPS through USB hub does not help. Another UPS Eaton 5E 2000iUSB shows the same problem when connected to OS Fedora 29 and works fine on Debian 9.5 (stretch) - 4.9.110-1  amd64.  
  
Version-Release number of selected component (if applicable): Fedora 29 5.0.4-200.fc29.x86_64 and later, all Fedora 30 kernels

How reproducible: Any time Eaton 5E UPS is connected.

Steps to Reproduce:
1. Connect Eaton 5E ****iUSB device to USB port
2.
3.

Actual results:
1. Log shows that the device is constantly connecting & disconnecting. 
2. lsusb shows constantly incrementing Device number.
3. NUT shows:   upsdrvctl start
Network UPS Tools - UPS driver controller 2.7.4
Network UPS Tools - Generic HID driver 0.41 (2.7.4)
USB communication driver 0.33
No matching HID UPS found
Driver failed to start (exit status=1)

Expected results:
No error messages in log, consistent Device number

Additional info:
  Fiddling with /etc/udev/rules.d/69-libmtp.rules to exclude this device from MTP rules does not help:
ATTR{idVendor}=="0463", GOTO="libmtp_rules_end"
  Google search does not point to a work around.
I am a user, not professional. I am puzzled by "hid-generic" record in the log, I expected "usbhid-ups" to handle this device.