[Device]: Logitech G700S not detected

[reyqn]

Pre-flight checklist

• I quit Logi Options+ before testing.
• I searched existing issues for my device.

Device model

Logitech G700S

Connection

Wired (USB cable)

What's the problem?

Device is not detected at all

openlogi list output

2026-08-21T13:07:17.410093Z  WARN openlogi_hid::inventory: node probe keeps failing — retiring its channel before reopen
2026-08-21T13:07:17.410234Z  WARN openlogi_hid::inventory: node probe keeps failing — retiring its channel before reopen
2026-08-21T13:07:23.773185Z  WARN openlogi_hid::inventory: node probe keeps failing — retiring its channel before reopen
2026-08-21T13:07:23.773304Z  WARN openlogi_hid::inventory: node probe keeps failing — retiring its channel before reopen
G513 RGB MECHANICAL GAMING KEYBOARD (—, vid=046d pid=c33c)
  └─ slot 255 ● G513 RGB MECHANICAL GAMING KEYBOARD (keyboard, wpid=?, battery=—)
          model_ids=[c33c,0000,0000] ext=05 serial=— unit_id=35394713 transports=usb

openlogi diag features output

2026-08-21T13:10:03.820683Z  WARN openlogi_hid::inventory: node probe keeps failing — retiring its channel before reopen
2026-08-21T13:10:03.820810Z  WARN openlogi_hid::inventory: node probe keeps failing — retiring its channel before reopen
2026-08-21T13:10:10.206561Z  WARN openlogi_hid::inventory: node probe keeps failing — retiring its channel before reopen
2026-08-21T13:10:10.206668Z  WARN openlogi_hid::inventory: node probe keeps failing — retiring its channel before reopen
device: G513 RGB MECHANICAL GAMING KEYBOARD (direct 046d:c33c)
   idx      id  ver
     0  0x0000  v1
     1  0x0001  v1
     2  0x0003  v2
     3  0x4522  v0
     4  0x0005  v0
     5  0x1e00  v0
     6  0x4540  v0
     7  0x1eb0  v0
     8  0x8060  v0
     9  0x00c2  v0
    10  0x1801  v0
    11  0x1802  v0
    12  0x8080  v2
    13  0x8070  v7
    14  0x1821  v0
    15  0x1bc0  v0
    16  0x1806  v3
    17  0x40a2  v0
    18  0x1b04  v3
    19  0x0020  v0
  (20 feature entries)

Details

Windows 11 Version 25H2 (OS Build 26200.9168)
openlogi 0.7.4 from msi.
I don't use Logi Options+
The mouse also has a 1000hz receiver, the mouse still isn't detected over the receiver (doesn't work either wired from USB or wireless)

[linear-code]

OLG-279

[4ni1ak]

The diagnostics pasted here are for a different device (a G513 keyboard, 046d:c33c) — the G700S itself never shows up anywhere in this report, so there's no PID/WPID to check against crates/openlogi-device-registry/src/receiver.rs's known-receiver table or any device-identity list.

The G700S is also a fairly old (2011-era) gaming mouse, and it's plausible it predates HID++ 2.0 the same way the G602 did in #1058 — in which case this wouldn't be a one-line PID-table gap at all, but a genuine HID++1.0 support gap needing real protocol work, not guessable from a PID alone.

Could you run openlogi list and openlogi diag features (or diag controls if diag features comes back empty, which would itself be a strong signal it's HID++1.0-only) specifically while the G700S is connected — wired first, since that's the simpler path, then via its own receiver if that still doesn't detect it? That would tell us whether this is a registry gap we can fix directly or a deeper protocol-support question for a maintainer.

[reyqn]

openlogi list didn't change since report (I'm now using openlogi 0.8.5)

The output for openlogi diag features and openlogi diag controls is the same, wired or wireless:

❯ openlogi diag features
2026-09-17T08:20:38.638190Z  WARN openlogi_device::inventory: node probe keeps failing — retiring its channel before reopen
2026-09-17T08:20:38.638329Z  WARN openlogi_device::inventory: node probe keeps failing — retiring its channel before reopen
device: G513 RGB MECHANICAL GAMING KEYBOARD (direct 046d:c33c)
   idx      id  ver   flags
     0  0x0000  v1
     1  0x0001  v1
     2  0x0003  v2
     3  0x4522  v0
     4  0x0005  v0
     5  0x1e00  v0    hidden
     6  0x4540  v0
     7  0x1eb0  v0    hidden,engineering
     8  0x8060  v0
     9  0x00c2  v0
    10  0x1801  v0    hidden,engineering
    11  0x1802  v0    hidden,engineering
    12  0x8080  v2
    13  0x8070  v7
    14  0x1821  v0
    15  0x1bc0  v0
    16  0x1806  v3    hidden,engineering
    17  0x40a2  v0
    18  0x1b04  v3
    19  0x0020  v0
  (20 feature entries)

  fw 0: MainApplication U1 19.01_B0014 pid=c33c [active]
  fw 1: Bootloader BOT65.00_B6060 pid=aadc

❯ openlogi diag controls
2026-09-17T08:21:18.641728Z  WARN openlogi_device::inventory: node probe keeps failing — retiring its channel before reopen
2026-09-17T08:21:18.641834Z  WARN openlogi_device::inventory: node probe keeps failing — retiring its channel before reopen
device: G513 RGB MECHANICAL GAMING KEYBOARD (direct 046d:c33c)
     cid    task   flags  capabilities
  0x00f7  0x00cc  0x007a  divertable
  0x00f9  0x00ce  0x007a  divertable
  0x00f8  0x00cd  0x007a  divertable
  0x00fa  0x00cf  0x007a  divertable

[4ni1ak]

Thanks for the quick follow-up, but this is still the G513 keyboard's output (046d:c33c, MainApplication firmware, keyboard feature table) — the G700S itself doesn't appear anywhere in either dump. Can you run openlogi diag features/diag controls while only the G700S is connected (unplug/disconnect the G513 first if they're both attached at once, since diag without a target picks whichever device answers)?

Separately — the "node probe keeps failing — retiring its channel before reopen" warning you're seeing is a real, unrelated bug we just root-caused and fixed tonight (#1128, PR #1451): a shared HID++ channel correlation-id collision between inventory probing and input capture. Not likely related to the G700S detection question, but worth knowing it's fixed if you rebuild from current master.