Ironclaw - iCue keeps thinking mouse is disconnected

[flankr]

iCue Version 4.11.274

Ironclaw RGB Wireless - Whatever the latest version is

Ironclaw RGB Wireless Dongle - 5.0.84

 

I think I was pushed the 4.11 update a few weeks ago. Ever since then, from time to time(I think after I wake the mouse up from power saving mode), I get this red circle (power) icon on top of the mouse in the dashboard.

 

When that happens, my mouse turns into a "dumb" mouse. Neither SW profiles nor the hardware ones are working. Basically just left, right and middle buttons and browser forward and backward buttons. Nothing else.

 

When this happens, sometimes turning the mouse off and on again solves it. Sometimes it doesn't.

 

Sometimes removing the dongle and re-inserting it works, sometimes it doesn't.

 

I tried the "restart icue service" thing too, doesn't look like it's doing anything.

 

I think I'll just find a version of iCue from last year and use that. But if anyone has any ideas, I'm all ears.

[jpconques]

I have the same issue. Don't suppose you ever got any answers?

[Ares0286]

Bump. I had an Ironclaw Wireless replaced under RMA for the same issue. Here I am back with the same issue as you two on a brand new mouse.

[JoernMS]

. Having the exact same issue with my new Ironclaw Wirelss. Hoping for some news on this. Been lurking the formus for 2 days in hopes of an answer.

[Jean_pl]

Got the same issue here and a fix would help a lot!

[Nayoh]

got the same issue, in the middle of every Apex legends game my mouse becomes unavailable and i lose all my presets... just asked for a replacement... i guess i'm just going to have to forget it and find an other mouse, this one clearly has something very wrong that they don't seem to care fixing.

[bloi]

same issue here ...
earliest thread I found where this problem occurs is from two years ago ...
Can't believe there's still no fix 😒

 

I already tried reinstalling, resetting device, clean reinstall, changing USB-ports, using another cable, use dongle direct in PC, using another keyboard, deactivated selective usb energy settings, etc. 

really tired of it. Why i've bought a wireless mouse when it stop working after less than an hour in wireless mode ...

First picture was at 13:16 2nd & 3rd picture 40 minutes later at 13:56

[bloi]

Did a test today and recorded time and iCue with OBS to exactly define the time when the problem occurs...
Exported logs and found this:

....

2022-11-07 08:11:10.139 I cue.plugin: 08:11:10.139 [ 76 ] attempt to initialize MysticLight_SDK "MSI/CueMsiPlugin.dll"
2022-11-07 08:11:20.280 W cue.plugin: 08:11:20.280 MLAPI_Initialize() failed with status code -3: "MSI Application not found or installed version not supported." "MSI/CueMsiPlugin.dll"
2022-11-07 08:11:20.280 W cue.plugin: 08:11:20.280 [ 76 ] Failed initialization of MysticLight_SDK "MSI/CueMsiPlugin.dll"
2022-11-07 08:12:36.275 I cue.plugin: 08:12:36.274 [ 77 ] attempt to initialize MysticLight_SDK "MSI/CueMsiPlugin.dll"
2022-11-07 08:12:46.377 W cue.plugin: 08:12:46.377 MLAPI_Initialize() failed with status code -3: "MSI Application not found or installed version not supported." "MSI/CueMsiPlugin.dll"
2022-11-07 08:12:46.377 W cue.plugin: 08:12:46.377 [ 77 ] Failed initialization of MysticLight_SDK "MSI/CueMsiPlugin.dll"
❌2022-11-07 08:13:25.717 W cue.devices.enum.subdevice: Fail counter for "IRONCLAW RGB WIRELESS" reached zero, removing subdevice
2022-11-07 08:13:25.717 I cue.devices.bragi.command_queue: Command cancelled bragiprotocol::CommandId::WriteBufferBegin
2022-11-07 08:13:25.717 I cue.devices.bragi.command_queue: Command cancelled bragiprotocol::CommandId::Ping
2022-11-07 08:13:25.717 I cue.devices.bragi.command_queue: Command cancelled bragiprotocol::CommandId::Ping
2022-11-07 08:13:25.717 I cue.devices.bragi.command_queue: Command cancelled bragiprotocol::CommandId::Ping
2022-11-07 08:13:25.717 I cue.devices.bragi.command_queue: Command cancelled bragiprotocol::CommandId::Ping
2022-11-07 08:13:25.717 W cue.pairing.direct: Pairing context not ready or transactions not empty
2022-11-07 08:13:25.717 W cue.devices.enum.subdevice: Fail counter for "IRONCLAW RGB WIRELESS" reached zero, removing subdevice
2022-11-07 08:13:25.717 C cue.devices: Write hunk failed. Device: "IRONCLAW RGB WIRELESS"
2022-11-07 08:13:25.717 C cue.devices: Exception:  Timeout (6210ms) while receiving reply.

2022-11-07 08:13:25.718 C cue.devices: Exception while runCommand on device  IRONCLAW RGB WIRELESS : 
  Timeout (6210ms) while receiving reply.

2022-11-07 08:13:25.719 W cue.legacyproto: Conversion for notification type is not implemented 57
2022-11-07 08:13:31.931 W cue.devices.enum.subdevice:  Get property UsbVid failed.
  Timeout (6210ms) while receiving reply.

2022-11-07 08:13:31.931 C cue.devices.abstact_protocol: stopWorker wasn't called correctly for "IRONCLAW WIRELESS RECEIVER"
2022-11-07 08:13:31.932 C cue.devices: Cannot create subdevice for: "IRONCLAW RGB WIRELESS DONGLE"
2022-11-07 08:13:31.933 C cue.devices:  Failed to get vid, pid from subdevice id: 1

2022-11-07 08:13:43.142 W cue.devices.enum.subdevice:  Get property UsbVid failed.
  Timeout (6209ms) while receiving reply.

2022-11-07 08:13:43.142 C cue.devices.abstact_protocol: stopWorker wasn't called correctly for "IRONCLAW WIRELESS RECEIVER"
2022-11-07 08:13:43.143 C cue.devices: Cannot create subdevice for: "IRONCLAW RGB WIRELESS DONGLE"
2022-11-07 08:13:43.143 C cue.devices:  Failed to get vid, pid from subdevice id: 1
....

the ❌ marks the time.
 

However, I don't know what to do with this.     >.>