ConfigTBRZ

Yep still good. Since the NZXT hub is kind of sparsely stocked I ordered and installed this: https://www.amazon.com/gp/product/B07QHQF92K/ref=ppx_yo_dt_b_asin_title_o05_s00?ie=UTF8&psc=1 I was apprehensive about installing it but its actually made quite well and uses SATA power rather than molex (NZXT). I have just the commander pro connected to it, and the RBG hub connected to lighting channel 1 of the CoPro. Four LL120 fans connected to CoPro as well. Also, I did not even have to connect the USB header hub to sata power, it seems to be functioning fine without it and drawing power from the motherboard since installation. That being said, if more devices were added i'd imagine power supplementation would be required. Yes, CoPro is controllable through iCue. Just to reiterate, only the copro is connected to teh hub. my H100i is connected to the mainboard USB header. So both 2.0 headers on the board itself are occupied. I dont know why this is working, it doesnt make a whole lot of sense to me. But it does work. I've been up and working with zero disconnect events for almost a week.

Hey, shame we have to deal with this eh? I went ahead and ordered this since the NZXT hub is hard to get; Micro Connectors S08-303-IA - Acrylic Internal USB 2.0 Hub with Magnetic Base. It was actually a nice piece of hardware and it uses sata power not molex like NZXT. It’s been working in my machine for more than 72hrs uptime with no issue. Just a thought if you’re struggling to find the NXZT device. I actually ordered both and that one got here first. I was worried it would be off brand garbage but the build quality and sata connection surprised me so much I went ahead and used it.

After installing a usb 2.0 header hub and connecting my CoPro to it I’ve had 72hrs system uptime with zero disconnects. Using USBLogView to monitor usb events and reviewing icue logs daily for CoPro insertion and initialization. All clear on my end.

72hrs uptime with no usb events logged using USBLogView tool. No additional instances of CoPro insertion\initialization in iCUE logs. Satisfied to say that the hub did resolve my issue. Not sure how or why, it boggles my mind, but hey, its working

48hrs uptime with no issues. I’ll post again tomorrow. If all clear likely be my final update.

No further drops overnight. iCue logs look good and USB event viewer is clear. Im really curious how and why this works.. But it does.

No USB events logged overnight, iCUE logs show no drop of CoPro either. Looks like an internal USB hub IS the fix. But that begs the questions; why and how? Ive been in C.S. my entire adult life, primarily network engineering and the only thing I can think of is that maybe the USB traffic through the hub is somehow encapsulated or something? Just really struggling to understand at a layer I, layer II level how this is working. ***Update*** 24hrs uptime with no drops. confirmed via USB event viewer tool and reviewing iCue logs.

Bumping my comment from a sister thread: The NZXT hub has not arrived but its equivalent did: https://www.amazon.com/gp/product/B0...?ie=UTF8&psc=1 Preliminary results: No disconnects yet; see iCue log excerpt: 2020-04-27T16:15:11 I cue.devices: Device insertion processing complete for Commander Pro (vid=1b1c, pid=c10) The above is the initialization completing. Prior to using the hub, you could search the log file for device insertion and see it re-initializing repeatedly. So far so good as this event has not re-occurred in the 30 mins I've been gaming. Albeit, more testing is required, but prior disconnects were pretty frequent. Notes: This hub uses SATA power while NZXT apparently uses molex\4-pin. which is nice. Also, power is not really required if just running CoPro off it, it will draw sufficient power from MB USB head. I will connect SATA power if perhaps drops occur again just to rule that out. Also, build quality on this did far exceed what I expected. I was apprehensive about putting it into my build with thousands of dollars worth of gear until I saw how decently it was made. Notes** after five hours uptime I’ve seen no other instances of device insertion in icue logs nor has my usb event monitor triggered am unplug/plug event. Will continue to monitor overnight.

Still stable after five hours uptime. iCue logs only show initial insertion listed in above post. USB logger left running shows no unplug/plug events. Will continue to monitor overnight

The NZXT hub has not arrived but its equivalent did: https://www.amazon.com/gp/product/B07QHQF92K/ref=ppx_yo_dt_b_asin_title_o05_s00?ie=UTF8&psc=1 Preliminary results: No disconnects yet; see iCue log excerpt: 2020-04-27T16:15:11 I cue.devices: Device insertion processing complete for Commander Pro (vid=1b1c, pid=c10) The above is the initialization completing. Prior to using the hub, you could search the log file for device insertion and see it re-initializing repeatedly. So far so good as this event has not re-occurred in the 30 mins I've been gaming. Albeit, more testing is required, but prior disconnects were pretty frequent. Notes: This hub uses SATA power while NZXT apparently uses molex\4-pin. which is nice. Also, power is not really required if just running CoPro off it, it will draw sufficient power from MB USB head. I will connect SATA power if perhaps drops occur again just to rule that out. Also, build quality on this did far exceed what I expected. I was apprehensive about putting it into my build with thousands of dollars worth of gear until I saw how decently it was made. I will update later this week if issue has fully resolved after I've had more time to test real use.

Registered to comment that I also have this issue. Using an Asus Prime X570 PRO I am experiencing disconnects from my CoPro that is causing USB bus reset issues. Most annoying being the loss of my USB audio that requires that device to be reset. I stumbled on this thread doing some googlin' and have ordered the NZXT USB hub (actually in stock at amazon as of this post) and another manufacturer as well. I want to use the NZXT one but we'll see which arrives first. I have confirmed the disconnects a few ways, firstly, the RGB goes out on just one fan (of four) and I can see the CoPro drop from iCUE home panel. I simultaneously ran a usb even logger that also coincides its events w\ the aforementioned symptoms. Im annoyed that I invested so heavily in this ecosystem and corsair seems to ahve not been able to resolve this in the many months/years this thread and others have been active. Just to be sure, I made sure my chipset drivers were up to date and even updated to most recent BIOS. I will reply back with results after my hubs arrive. Good luck everyone.