[Device]: Logitech G502 Hero SE

[eGOoOGle]

Pre-flight checklist

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

Device model

Logitech G502 Hero SE

Connection

Wired (USB cable)

What's the problem?

Device is detected but a feature doesn't work

openlogi list output

Unable to configure the mouse like others

openlogi diag features output

Details

No response

[linear-code]

OLG-144

[exico91]

I have the same problem but with the G502 Hero (no SE).
I can adjust the DPI and RGB but I cannot bind any button

[pxlnvdr]

Not issue related but does it connect via bolt or wired only?

[exico91]

Mine is a G502 Hero, is wire only, not detachable. (maybe is an SE after all after reading the lsusb output)

Some infos from lsusb, maybe are useful:

 lsusb -v -d 046d:c08b

Bus 005 Device 005: ID 046d:c08b Logitech, Inc. G502 SE HERO Gaming Mouse
Negotiated speed: Full Speed (12Mbps)
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 [unknown]
  bDeviceSubClass         0 [unknown]
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x046d Logitech, Inc.
  idProduct          0xc08b G502 SE HERO Gaming Mouse
  bcdDevice           27.03
  iManufacturer           1 Logitech
  iProduct                2 G502 HERO Gaming Mouse
  iSerial                 3 1660396F3931
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x003b
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          4 U127.03_B0010           
    bmAttributes         0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower              300mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      1 Boot Interface Subclass
      bInterfaceProtocol      2 Mouse
      iInterface              0 
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.11
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength      67
          Report Descriptors: 
            ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval               1
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      0 [unknown]
      bInterfaceProtocol      0 
      iInterface              0 
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.11
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength     151
          Report Descriptors: 
            ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0014  1x 20 bytes
        bInterval               1
Device Status:     0x0000
  (Bus Powered)

[madmalkav]

I can confirm this happens also to me both in MacOS and Linux

[yuzi-co]

Data point that may explain this one, though from a different G502 variant — mine is a G502 LIGHTSPEED (wireless, Lightspeed receiver 046d:c539, wpid 407f), not the wired Hero SE. Same family, different bus, so treat the details as indicative rather than authoritative for your unit.

The short version: the G502 exposes no ReprogControls feature at all, so "unable to configure the mouse like others" is structural, not a detection failure.

openlogi diag controls:

device: G502 (slot 1 on receiver 82839805)
Error: dump HID++ 0x1b04 reprogrammable controls

Caused by:
    device does not expose HID++ feature 0x1b04

None of 0x1b00-0x1b04 are present. The full table openlogi diag features returns (names resolved against crates/openlogi-hidpp/src/feature/registry.rs):

 idx  id       ver  name (registry.rs)     impl
   0  0x0000   v1   Root                   yes
   1  0x0001   v1   FeatureSet             yes
   2  0x0003   v2   DeviceInformation      yes
   3  0x0005   v0   DeviceTypeAndName      yes
   4  0x1d4b   v0   WirelessDeviceStatus   yes
   5  0x0020   v0   ConfigChange           no
   6  0x1001   v2   BatteryVoltage         yes
   7  0x8070   v4   ColorLedEffects        yes
   8  0x1300   v0   LedControl             no
   9  0x8100   v0   OnboardProfiles        no
  10  0x8110   v0   MouseButtonFilter      no
  11  0x8060   v0   AdjustableReportRate   yes
  12  0x2201   v1   AdjustableDpi          yes
  13  0x1802   v0   DeviceReset            no
  14  0x1803   v0   (not in registry.rs)   no
  15  0x1805   v0   OobState               no
  16  0x1806   v4   ConfigDeviceProps      no
  17  0x1811   v0   (not in registry.rs)   no
  18  0x1830   v0   (not in registry.rs)   no
  19  0x1890   v4   (not in registry.rs)   no
  20  0x1891   v4   (not in registry.rs)   no
  21  0x18a1   v0   (not in registry.rs)   no
  22  0x1801   v0   (not in registry.rs)   no
  23  0x18b1   v0   (not in registry.rs)   no
  24  0x1df3   v0   (not in registry.rs)   no
  25  0x1e00   v0   (not in registry.rs)   no
  26  0x1eb0   v0   (not in registry.rs)   no
  27  0x1863   v0   (not in registry.rs)   no
  28  0x1e22   v0   (not in registry.rs)   no
  29  0x2121   v0   HiResWheel             yes

So Capabilities::from_feature_ids in crates/openlogi-core/src/device.rs correctly derives buttons = false — my cached identity in config.toml reads:

[devices."receiver:...:slot:1".identity.capabilities]
buttons = false
pointer = true
lighting = true
scroll_inversion = true
hires_wheel = true

That is the mouse telling the truth. G-series keep their button map in onboard profile flash (0x8100), not in a divertable control table, so the HID++ remapping path this app is built around has nothing to attach to on a G502.

What the device does offer, and what already works today:

• 0x2201 AdjustableDpi — DPI control works
• 0x8070 ColorLedEffects — RGB works
• 0x1001 BatteryVoltage — battery works
• 0x2121 HiResWheel — wheel resolution / inversion
• 0x8060 AdjustableReportRate — implemented in registry.rs as ReportRateFeature, but I see no UI surfacing it

And two the device advertises that registry.rs names but does not implement:

• 0x8100 OnboardProfiles — the subject of feat: onboard profiles (0x8100) support for G-series mice #459
• 0x8110 MouseButtonFilter

Worth noting for anyone else landing here: the 13 features above marked (not in registry.rs) are mostly Logitech-internal/manufacturing ones; I have deliberately not guessed at names for them.

If it helps, I am happy to run any further diag you want against this unit.

(Aside: if you were on Windows, the empty diag features block in the report above is not your fault — the Windows artifacts ship no openlogi binary at all. Filed as #658, fix in #659.)

[yuzi-co]

Follow-up: I have now tested this on the wired path, so the hedge in my comment above can come off.

I connected the same G502 LIGHTSPEED by USB cable with the receiver unplugged. It enumerates as a direct device (046d:c08d, slot 255) rather than through the receiver:

> openlogi list
G502 LIGHTSPEED Wireless Gaming Mouse (—, vid=046d pid=c08d)
  └─ slot 255 ● G502 LIGHTSPEED Wireless Gaming Mouse (mouse, wpid=?, battery=100% full (charging))
          model_ids=[407f,c08d,0000] ext=00 serial=— unit_id=6be9d300 transports=usb+equad

ReprogControls is still absent over USB — same error, stable across three consecutive probes:

> openlogi diag controls
device: G502 LIGHTSPEED Wireless Gaming Mouse (direct 046d:c08d)
Error: dump HID++ 0x1b04 reprogrammable controls

Caused by:
    device does not expose HID++ feature 0x1b04

None of 0x1b00-0x1b04 appear in the wired feature table either. So this is not a wireless-transport artifact: the G502 exposes no reprogrammable-controls feature on either bus, and button remapping through the HID++ divert path cannot work on this family regardless of how it is connected.

DPI does work over the cable, for what it is worth:

> openlogi diag dpi
  current DPI: 800
  supported DPI: 100..25600 (step ≈ 50, 511 values)
  writing DPI: 850 → read-back DPI: 850 → restoring DPI: 800
✓ DPI round-trip OK

Caveat that still stands: mine is a G502 LIGHTSPEED, yours is a G502 HERO SE. Same family and I would expect the same answer, but I cannot confirm your exact unit — if you can get openlogi diag features and openlogi diag controls off it, that would settle it. (On Windows that needs #659 to land first, or a local cargo build --release -p openlogi.)

Separately, the wired probe turned up one difference worth its own report: 0x2121 HiResWheel is present over the receiver but absent over USB on this device. Filed as #660.

[Duggle]

I have the wired G502 hero with the same issue. DPI and lighting works but no button options.

❯ openlogi list
Logitech G502 HERO Gaming Mouse (—, vid=046d pid=c08b)
  └─ slot 255 ● G502 HERO Gaming Mouse (mouse, wpid=?, battery=—)
          model_ids=[c08b,0000,0000] ext=00 serial=— unit_id=32314707 transports=usb

❯ openlogi diag features
device: G502 HERO Gaming Mouse (direct 046d:c08b)
   idx      id  ver    
     0  0x0000  v1
     1  0x0001  v1
     2  0x8070  v3
     3  0x0003  v2
     4  0x0005  v0
     5  0x1300  v0
     6  0x18a1  v0
     7  0x1e00  v0
     8  0x1e22  v0
     9  0x1eb0  v0
    10  0x2201  v1
    11  0x8060  v0
    12  0x8100  v0
    13  0x8110  v0
    14  0x00c2  v0
    15  0x1801  v0
    16  0x1802  v0
    17  0x1806  v5
    18  0x18b1  v0
  (19 feature entries)

❯ openlogi diag controls
device: G502 HERO Gaming Mouse (direct 046d:c08b)
Error: dump HID++ 0x1b04 reprogrammable controls

Caused by:
    device does not expose HID++ feature 0x1b04