feat: detect any Logitech headset from G HUB (not only PRO X) - #15
Merged
Conversation
Replace the name-based PRO X filter with Test-LogitechHeadsetDevice, which uses the G HUB deviceInfo fields (deviceType + capabilities.hasBatteryStatus) with a name fallback, and excludes mice/keyboards/receivers/dongles. This makes the LogitechGHub mode work with G733, G533, G Pro X, Astro, etc. — any Logitech headset G HUB reports with a battery signal. Runtime fallback lookup, installer option [2] and the cycle-path G HUB filter all use it; prompts/logs generalized to "Logitech headset". Tests added. Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
The release build writes dist/*.zip + .sha256; they are generated and should not be tracked. Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
…d devices The LogitechGHub runtime polls the G HUB battery signal to tell ON from OFF, so a deviceInfo with deviceType=headset/audio but no hasBatteryStatus is not usable in this mode. The matcher now returns $hasBattery for that case (was unconditional true) and falls back to the battery capability before the name heuristic. Tests added for both the reject (headset without battery) and accept (battery with unknown type) cases. Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
Leftover from the English-first migration: the header and the COM comment in Toggle-AudioEnhancements.ps1 mixed Spanish fragments. Now fully English. Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
svcl.exe was replaced by the native Core Audio backend in v1.3.0, but the module kept the old CSV parser and "Svcl" naming as dead weight. - Remove dead functions from AutoSwitchCore.psm1: Get-RenderItemIdFromText, ConvertFrom-SvclCsv, ConvertFrom-CsvLine, Resolve-DetectedState, Test-SvclExportValid, Get-SvclRenderDevice (unused since Core Audio). - Rename the live helpers to match reality: Get-CsvColumn -> Get-DeviceColumn, Get-SvclDeviceLabel -> Get-DeviceLabel, Find-SvclRenderDeviceByIdentity -> Find-RenderDeviceByIdentity (they operate on Core Audio render rows now). - Drop tests for the removed functions and the tests/fixtures/svcl-export.csv; the remaining identity tests build rows inline. - Clean EN/ES mixed comments in Runtime and tests; fix the runtime worker comment (Core Audio, not svcl). - Docs: site (NirSoft download -> Core Audio backend), SOURCES (svcl read -> state read), wiki How-It-Works / Como-funciona (Core Audio + SteelSeries). Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
The cleanup rewrote the files without the BOM; non-ASCII content (em dash in Get-DeviceLabel) requires it. Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
This was referenced Aug 17, 2026
Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
- Add a sectioned table of contents to the README grouped by audience (users, operators, contributors) with working anchors. - Restructure the README: add Supported headsets table, Configuration and Troubleshooting sections, More resources block, and group Installer behavior into sub-sections. Tighten the tagline, link the stable release to the latest release, and refine copy/terminology. - Update the English and Spanish wiki to v1.4.0: reflect the full Logitech PRO X family (not only PRO X 2) and the SteelSeries Arctis Nova 5/5X detection mode. Fill missing Spanish content, recover technical nuances (fail closed, debounce) and unify terminology. Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
The repository quality check (check-repository.py) was still pinned to v1.2.5 while the project is at v1.4.0, so the validate workflow failed. Update CURRENT_VERSION to 1.4.0 and refresh the Pages site badge/tagline to reflect v1.4.0 and the SteelSeries Arctis Nova 5/5X mode. Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Generalizes the
LogitechGHubdetection mode so it works with any Logitech headset G HUB reports, not just PRO X / PRO X 2.Test-LogitechHeadsetDevice(inAutoSwitchCore, exported): decides if a G HUBdeviceInfois a headset by using the structured fields (deviceType+capabilities.hasBatteryStatus) with a name fallback, and excludes mice / keyboards / receivers / dongles.Get-ProX2BatteryPathnow uses it.Test-LogitechProXDeviceNamefor the PRO X-specific tests.This covers G733, G533, G Pro X, Astro, etc. — any Logitech headset whose battery signal G HUB exposes over
/battery/<deviceId>/state.Also
dist/build artifacts accidentally staged from the v1.4.0 publish, and addeddist/to.gitignore.Validation