Repository navigation
Logitech G Pro X 2 LIGHTSPEED cannot be detected #477
Description
Activity
- changed the title
[-]Logitech Pro X 2 LIGHTSPEED cannot be detected[/-][+]Logitech G Pro X 2 LIGHTSPEED cannot be detected[/+]on Jan 29, 2026 #478
I added the new deviceID - I get some output - the battery is not working though.
And I think the headset suppots equalizer as well - it does not report the capability.
Can U help capturing data ? I got mine last week it had already the updated firmware.
Never had the "firmware update breaks it" issue in the past ...So I also updated the deviceID into the OLD implementation to make sure the firmware update broke it.
And I confirm the firmware is responsible not the cpp-rewrite.{ "name": "HeadsetControl", "version": "3.1.0-36-gabe3ac8", "api_version": "1.3", "hidapi_version": "0.14.0", "device_count": 1, "devices": [ { "status": "partial", "device": "Logitech G PRO Series", "vendor": "Logitech", "product": "PRO X 2 LIGHTSPEED", "id_vendor": "0x046d", "id_product": "0x0af7", "capabilities": [ "CAP_SIDETONE", "CAP_BATTERY_STATUS", "CAP_INACTIVE_TIME" ], "capabilities_str": [ "sidetone", "battery", "inactive time" ], "errors": { "battery": "Battery status request timed out" } } ] }This should work now when you use current master branch and compile it yourself. #478 was merged yesterday.
@funforums try it and close this issue when it also wrks for you ...Hi @ChrisLauinger77 thank you for merging and apologies for testing it so late. The headset is now properly detected, but it seems to me it does not really produce a sidetone...? Is there a reliable way you can suggest to test this on Linux/KDE ?
CheersI have sidetone disabled - did also not really test it tbh . From the docs:
Set sidetone level (0-128)
headsetcontrol -s 64
Oh yeah sorry @ChrisLauinger77 - I was not precise with my answer. I did indeed set different levels of sidetone (even 128) but I don´t seem to be able to tell any difference.
It could be that instead of 0-128 it is just
0 off
1 low
2 medium
3 high
4 max
if not - they changed something else and it needs more work.In #501 some changes where done for G522 - I overtook them in our variant but seems not to work either.
Then I started the win11 VM and tested it with logitech original software.
This did also not work for me - so I am confused. Maybe firmware bug ?If you wanna test on your side #503
It's meanwhile already merged
I rebuilt from git commit 5136f7a - set different values for sidetone such as 60, 128, 0, 2, 3 - can´t tell any difference in hearing my own voice in the headset. Can´t tell if I am missing something in the way I am testing, since I am just setting the value, I get confirmation that the sidetone was set successfully, but then I can´t tell any change.
It does not work on win11 with the org logitech software. Seems broken no matter which tool used
Hi @ChrisLauinger77 , that seems to be incorrect imho, at least for my versions of Logi software/headset firmware.
Here is why:
I have switched to a dualbooted W11, and enabled sidetone. Admittedly any value below 65 on this headset seems to be just like off (sidetone issues seem to be bad and known on this model when googling) but setting it to 70 or 100 definitely had an effect (i.e. i could hear the sidetone clearly).My steps to test:
- in Logi software set sidetone > 70
- switch to microphone tab
- run a microphone test
- while microphone is being recorded, you can hear the sidetone
After doing that test, and switching to linux, it seems the headset kept the sidetone setting from windows, and any value set by
headsetcontrol -sis ignored, although being reported as set successfully (i.e. if I set it to 0, it is still active).How I test it being still active on linux:
- Open discord voice settings
- Start a microphone test: this will activate the sidetone on the headset if the sidetone setting allows for it
- Speak (hear the sidetone)
- Stop microphone test and close Discord settings
- (Sidetone on the headset stays on and you can still hear it for about 5-10 seconds then it stops working)
Long story short, it looks to me like
headsetcontrolis failing to set a sidetone setting on Linux, the headset sidetone functionality is not broken (albeit having issues which, in some scenarios, might look like broken on windows too).I hope this can help!
The recording in the windows software worked for me as well.
But settings the sidetone to any value - even 100 did not work in windows. Wonder why it did in your case ...
I expect it to be working just be setting the slider to a value - and then talk and I can here myself. Recording should not be needed. Recording I tested as well on windows - this worked for me.
The detection issue is solved and the battery is shown. Thats good enough for me for now.
Sidetone does not work for me anywhere.Reacted by funforumsApparently sidetone will be activated only when the headset detects that the microphone is being used, otherwise it will not activate the sidetone at all.
@ChrisLauinger77 I'm gonna move this discussion to this issue instead of the G522 implementation.
I've tested my G522 on Linux using this version of HeadsetControl as well as Windows in my VM using G Hub. For both cases, the sidetone setting works as expected for me:
- In Windows, I can hear the mic output immediately after setting the sidetone level.
- In Linux (CachyOS with KDE in my case), I sometimes have to manually open the sound settings for the sidetone to start working. This issue has been present since I got this Headset so I suspect this is a KDE or Linux issue.
I've also updated my headset and Lightspeed receiver to the latest firmware versions as well. Still no issues for me on both OSs.
Did any of you try to collect some data using Wireshark so far? To see if there is any message at all, on setting the sidetone or only after use in something like Discord.
I did collect some wireshark data in my PR - but I was not sure what is what.
I try with opening GNOME sound settings when I have time, maybe @funforums can also test it.
For me sidetone is not really important as it distracts me.
I checked also the firmware and everything is up-to-date.Apologies for the delay - life happened and I hope I will have time to test this again in the weekend. I will need to check if my headset got a new update in the meantime - my last update is indeed quite a few months ago, and it could also be you guys are on a newer firmware version than mine.
@funforums when its not working wireshark logs are needed - see documentation.
Hi, in the meantime I verified that my Firmware is up to date. I confirm that in the GNOME sound settings the sidetone is enabled for me too, if previously set. Analogously, I can hear the sidetone if I execute
wiremix.The problem is, the sidetone seems to work only if I have it set from Windows and then switch to linux. Any setting set from the Logi software in Windows will stay set in Linux, and setting new values with
headsetcontrol -sseems to have no effect for me. I suppose this means that I will need to gather more info with wireshark - will try to do that soon.Hi @ChrisLauinger77 , I was able today to do a capture of the sidetone setting for my PRO X 2 LIGHTSPEED.
I will attach it here, I believe I have managed to precisely filter the packets.
The capture represents me setting sidetone values, going from 0 upwards for each sidetone value in the Logi Software.@funforums look at my new attached PR - I found a reference implementation of the new logitech protocol called centurion.
I could also test side tone - it works now - after review I guess you can close this.
The previous driver was some kind of raw data approach which worked, but I think the new one is better.
I also added equalizer support ...Hi @ChrisLauinger77 thank you. I could test it now that it has been merged, and sidetone setting and battery reading seem to work! Haven´t tried the new equalizer support though, since I wouldn't know how to use it properly and what to really expect.
Reacted by Christian LauingerHi @ChrisLauinger77 thank you. I could test it now that it has been merged, and sidetone setting and battery reading seem to work! Haven´t tried the new equalizer support though, since I wouldn't know how to use it properly and what to really expect.
i implemented the 5 presets which are shown in GHUB from logitech.
you can see the names from the -o json input.
headsetcontrol -p 0- would select flat
headsetcontrol -p 1- would select bass boost
...if you are on gnome . there is an UI https://github.com/ChrisLauinger77/gnome-shell-extension-HeadsetControl
Description
Hi, I would like to report that my Logitech G Pro X 2 LIGHTSPEED is not detected:
headsetcontrol --capabilitiesNo supported device foundI installed it through AUR: https://aur.archlinux.org/packages/headsetcontrol-git
headsetcontrol used to work with this headset, but over time i installed a firmware update and headsetcontrol itself had new versions. I am not entirely sure at which point it stopped detecting it.
Might be related to #471 .
Cheers
Headset Name
Logitech G PRO X 2 LIGHTSPEED
On which OS does the problem happen?
Linux
Device information
Detailed Device Information