Logitech Keyboard Backlight Not Working: G HUB, Battery Save, and Fn Shortcuts Explained

Published on 2026-11-08 ยท 7 min read ยท By MiniTestLab Engineering Team ยท Category: Keyboards

Launch Companion Diagnostic Tool

Test your hardware right now in your browser with zero install:

Open Keyboard Tester

Your Logitech keyboard backlight is off because G HUB has either pushed a blank lighting profile to the onboard memory, the battery save threshold has cut power to the LEDs, or the Fn+F5 shortcut toggled illumination off at the firmware level. On wireless models like the G915 and G915 TKL, the onboard ARM Cortex-M4 controller stores up to five lighting profiles in 1 MB of flash; if the active slot contains a profile with brightness set to zero, the keyboard broadcasts that state even after G HUB is uninstalled. Wired boards like the G213 and G413 hit a different failure mode: the USB port's 500 mA budget gets split between the hub controller and the LED matrix driver, and a low-power USB 2.0 port on a cheap hub can starve the backlight entirely.

Check the Fn Shortcut and Onboard Brightness Before Touching Software

Hold Fn and press F5 once. On every current G-series keyboard this cycles the backlight through its brightness steps and back to off. If you have been pressing it accidentally, the board stores that zero-brightness state in volatile RAM and applies it on every wake. On the G915 specifically, the shortcut is Fn + F5 for brightness and Fn + F6 for effect cycle. Press Fn+F5 four times to confirm you have passed through all brightness levels; the LEDs should pulse visibly at the highest step even if they were at zero.

Also check the Game Mode key (top-left on most G boards). Holding it for three seconds resets the lighting to the default rainbow wave at 50% brightness. This is the fastest hardware-level reset available without touching G HUB.

While you are at the keyboard, run a quick input check with the Keyboard Test tool. It will confirm that keystrokes are registering, which rules out a full USB enumeration failure that could also kill the backlight.

Fix Lighting Profiles in G HUB

G HUB version 2021.9 and later separates onboard profiles from desktop profiles. A common mistake is editing a desktop profile while the keyboard's active onboard slot holds a different, all-black profile. Here is the exact path to fix it:

  1. Open G HUB. Click your keyboard thumbnail on the home screen.
  2. Click Lighting in the left rail. Confirm the dropdown at the top reads Desktop, not Onboard Memory.
  3. Select your active profile. Click the lighting layer. Set Brightness to 100% using the slider (numeric field on the right; type 100 directly).
  4. Now switch the dropdown to Onboard Memory. You will see up to five slots. Click each one and check its brightness value. Set any zero-value slots to at least 50.
  5. Click Save to Device. G HUB will write to the keyboard's flash over HID. The LEDs should respond within two seconds.

If G HUB shows the keyboard as offline (grey thumbnail), the board is not enumerating correctly. Unplug, hold the Fn + Esc combination, replug while holding, then release after three seconds. This forces a USB re-enumeration and clears the HID descriptor cache on the host side.

Logitech G915 Backlight Not Working: Battery Save and Wireless-Specific Fixes

The G915 and G915 TKL run a dedicated battery management IC that throttles LED current when charge drops below a configurable threshold. By default, G HUB sets this cutoff at 20% battery, at which point brightness drops to 0% automatically. If your G915 backlight is not working and the battery is between 10โ€“25%, this is almost certainly the cause.

To adjust the threshold: G HUB > G915 thumbnail > Settings gear (top right) > Power Management > Battery Save. Change the Lighting Off slider from 20% to 5%. Apply. The keyboard acknowledges over the 2.4 GHz LIGHTSPEED link within one polling cycle (1 ms).

On Bluetooth mode specifically, the G915 reduces LED refresh rate to conserve power, which can make certain effects look off or absent. Switch the toggle on the back of the board from BT to LS (LIGHTSPEED dongle) and retest. Bluetooth mode is not recommended for backlight-intensive use on this board.

USB Power, Driver Stack, and Last-Resort Firmware Reflash

Wired keyboards pulling backlight power through a passive USB hub or a front-panel port on a desktop case often get less than the 500 mA the USB 2.0 spec guarantees. The LED matrix on the G213 draws up to 420 mA at full white brightness. Move the cable directly to a rear motherboard USB-A port and retest before assuming a software fault.

Model LED Driver Max Draw (full white) Common Failure Mode
G213 IS31FL3733 matrix driver ~420 mA Underpowered USB hub kills backlight
G413 SE Per-key PWM, no dedicated IC ~180 mA G HUB blank profile overwrites onboard
G915 / G915 TKL IS31FL3741 + battery IC ~310 mA (wired charging) Battery save threshold cuts LEDs at 20%
G Pro X IS31FL3733 ~260 mA Fn lock state stored in onboard flash

If none of the above resolves it, reflash the keyboard firmware. In G HUB go to Settings (gear icon, top right of the main window) > My Gear > find your keyboard > click the three-dot menu > Firmware Update. Force it even if G HUB says the firmware is current by clicking Update rather than skipping. The reflash takes about 90 seconds and rewrites the bootloader partition, which clears corrupted lighting state that profile edits cannot reach.

After the reflash, use the Keyboard Test again to verify all keys scan correctly, then reconfigure your lighting from scratch in G HUB rather than restoring a backup profile, since a corrupted profile file will re-corrupt the onboard memory.

If you use a second input device alongside the keyboard, the Mouse Test tool can confirm that the USB controller handling both devices is not dropping connections, which occasionally manifests as intermittent backlight loss on the keyboard side.

Frequently Asked Questions

Why does my Logitech keyboard backlight turn off after a few seconds?

G HUB's idle timeout is set to 3 minutes by default. Go to G HUB > your keyboard > Settings gear > Power Management > set Lighting Timeout to Never or your preferred interval. This is separate from the battery save threshold on wireless models.

My G915 backlight is not working even at full battery. What now?

Check the onboard memory slots in G HUB as described above. If all five slots show zero brightness, the onboard flash may have been written with a blank profile during a G HUB crash. Use Fn+Esc re-enumeration, then do a firmware reflash. If the LEDs still do not respond, the IS31FL3741 driver IC may have failed, which requires board-level repair.

Does uninstalling G HUB fix backlight problems?

Sometimes, but only if G HUB is actively pushing a zero-brightness profile. The keyboard's onboard memory retains whatever was last written, so uninstalling G HUB without first correcting the profile leaves the problem in place. Use the Fn+Game Mode three-second reset to restore hardware defaults without touching software.

Can a Windows update break Logitech keyboard lighting?

Yes. Windows updates occasionally reset USB selective suspend settings. Go to Device Manager > Universal Serial Bus controllers > right-click your USB Root Hub > Properties > Power Management > uncheck Allow the computer to turn off this device to save power. Do this for every root hub listed. Also check Power Options > Change plan settings > Change advanced power settings > USB settings > USB selective suspend setting > set to Disabled.

Logitech keyboard lights not working on Mac. Is it the same fix?

Mostly. G HUB for macOS uses the same profile structure, but the Fn key behavior differs. On macOS, go to System Settings > Keyboard > set Use F1, F2, etc. keys as standard function keys to On, then test the Fn+F5 shortcut again. Also run the Mac Keyboard Test to confirm the Fn key itself is registering before assuming a lighting fault.

Why are only some keys lit and others dark?

This is a per-key lighting layer issue in G HUB, not a hardware fault. In G HUB > Lighting, check for a secondary layer sitting above your base layer with specific keys set to opacity zero or color black. Delete any unexpected layers. If the dark keys are physically adjacent (e.g., an entire column), the LED matrix row driver for that segment may have failed, which is a hardware fault.

Launch Companion Diagnostic Tool

Test your hardware right now in your browser with zero install:

Open Keyboard Tester