Quick Answer: A Windows taskbar battery monitor shows the charge level of your wireless devices beside the clock. Wireless Battery reads the battery directly from mice, headsets, keyboards and controllers, so you don't need G HUB, Synapse or iCUE running. It uses about 2 MB of RAM, refreshes every 60 seconds and warns you at 15%.

Your mouse dies in the middle of a ranked match, or your headset goes quiet during a call. The annoying part is that nothing warned you. Windows surfaces battery levels for some Bluetooth devices, but most 2.4 GHz receivers stay invisible. The vendor suites that do show levels are heavy and only cover their own brand. A Windows taskbar battery monitor closes that gap with one small utility that keeps every device's charge in view.

What the taskbar display actually shows

By default, Wireless Battery draws something like 🎧 30% 🖱 93% beside the notification area, using the Windows icon font. Each number belongs to one device, so you can see your mouse and headset at a glance. The styling carries meaning:

  • Red number: the device is at 15% or below. The same threshold triggers the "Low battery" notification.
  • Blue âš¡: the device is charging.
  • Dimmed text: the device is asleep, and the number is the last value it reported.

The dimmed state is the one people misread. A dim 42% isn't a fresh reading. It's what the device last told the app before it dozed off. Blanking the slot would be worse for a glance-based display, so the app keeps the old value and dims it instead.

The display also follows light and dark mode and DPI scaling. If you use a transparent taskbar theme such as Windhawk's Taskbar Styler, turn on Background behind taskbar text in the menu. Without it, the numbers can disappear into your wallpaper.

Why you don't need vendor software

The common advice is to install your peripheral's suite to see its battery. That advice is incomplete. Vendor suites show battery only for their own hardware, and they run background services to do it. Wireless Battery takes a different route: it talks to the devices directly. G HUB, Synapse, iCUE, GG and NGenuity can stay installed, or even keep running. You don't need to uninstall anything.

Here's the mechanism. Each vendor exposes battery through a HID feature report or input report. Logitech devices use HID++ (versions 1.0 and 2.0), and the app relies on feature discovery. It asks the device which battery features it supports instead of assuming a fixed register map. Razer devices use a feature-report protocol of their own. When a device answers in the expected format, the app decodes the reply. When it doesn't, the device simply doesn't appear.

The trade-off is real. Vendor software absorbs firmware changes and quirks, and a direct protocol read can break after a firmware update. The upside is that the app stays small and independent. Most people will prefer that, but you should know which side of the trade you're on.

Coverage is per model, not per brand

The README lists Logitech, Razer, SteelSeries, Corsair, HyperX, Glorious, PlayStation, Xbox and many smaller brands. Treat "supported brand" as shorthand, though. Support is granted per model, per receiver, and per protocol. A Logitech G435 on its newer 046D:0ADF dongle takes a different path from most Logitech headsets, which is why the table lists it separately.

Here's how to check whether your hardware is covered before you install:

  1. Find your receiver's USB ID (VID:PID) in Device Manager. For example, the Logitech PRO X3 SUPERSTRIKE dongle is 046D:C54F.
  2. Search the repo's supported devices table for that model and ID, not just the brand name.
  3. Check the "tested" flag. Entries such as the Redragon M916 Pro 1K and the Ninjutso Sora V2 are marked as tested on real hardware. Others are supported by protocol but unverified on that exact model.
  4. Read the caveats. The AULA keyboard entry notes that Bluetooth and wired modes are untested, and the DAREU EM901X entry says charging transitions are untested.

The table below shows how the protocol affects what you see on the taskbar:

DeviceProtocolGranularity or quirk
Logitech mice and headsetsHID++ 1.0 / 2.0 with feature discoveryUnified battery, voltage or ADC, depending on what the device supports
Razer BlackShark V3 headsetsVendor protocolQueried every 5 minutes, so readings lag the 60-second cycle
Areson M915RGB-WL17-byte GetPower feature reportLevel in 10% steps, plus a charging flag
VAXEE wireless mouseRead-only feature report 0EBattery in 5% steps
ATK N9 Pro headsetVirtual COM portThe ATK desktop app must be closed

Here's where it gets interesting. Two readings from the same brand can look different on the taskbar because the protocol decides the granularity. A VAXEE mouse will never show 47%, and an Areson mouse will never show 93%. That's a property of the hardware report, not a bug in the app.

Why a supported device can still go missing

Most "my device isn't showing" cases come from one of three causes.

First, the device may be on a receiver or cable the app can't decode. The DAREU EM901X works on the 260D:1074 2.4 GHz receiver, but USB cable mode isn't enabled. Same mouse, different connection, different result. The README says the app requires one unambiguous input/feature pair on the device, so it won't guess when a receiver exposes multiple candidates. You'll see a missing entry rather than a wrong number, which is the safer failure.

Second, another program may already hold the device. The ATK headset entry requires the ATK desktop app to be closed. Think of it as an exclusive-access rule: the app expects the port to itself.

Third, the device may be asleep or outside the tested set. Asleep devices show dimmed values, so check that first.

That said, not every missing device is a failure. The README says the app can switch to tray icons when the taskbar is vertical or can't be found, so a layout problem can look like a missing device when it's really a display-mode issue.

Taskbar text or tray icons: when to use which

The default taskbar text is compact. It fits several devices into a small space and reads well on a horizontal taskbar. Tray icons draw one icon per device, with the number drawn into the icon. They take more space, but they stay legible on a vertical taskbar, and each device gets its own hover tooltip.

Pick the taskbar text when you have a horizontal taskbar and want a single glance. Pick tray icons when you have a vertical taskbar, a crowded tray, or several devices you check separately. You can switch modes from the menu, and the menu also lets you hide individual devices by clicking them.

Refresh timing matters too. Levels update every 60 seconds, and the app refreshes immediately when a device is plugged in or the PC wakes. If you're waiting for a number after a fresh charge, the 60-second cycle is the reason it hasn't moved yet.

Installing it and judging the trust question

The fastest route is the WirelessBattery-Setup installer from the latest release. It installs in seconds and, according to the README, doesn't need admin rights. The README also offers a portable zip for people who want no installer, and it documents building from source with make or build.bat. The app can also start with Windows.

Trust deserves a direct look. Many protocols are read-only. The Bragi GET queries for Corsair devices are read-only, and so are the Cooler Master status reports and the Endgame Gear battery command. The rationale is simple: a read-only query can't change a device's settings, so it's a lower-risk way to get battery data. Still, a protocol reverse-engineered from a device can change with firmware, so check the README's tested flags and the project's issue history before you depend on a device for something critical.

Here's the practical rule. Install it, confirm your device shows up within the first minute, and then leave it alone. If a device is missing, check the receiver ID and the caveats before you assume the app is broken.

Frequently Asked Questions

What is a Windows taskbar battery monitor?

A Windows taskbar battery monitor is a small utility that displays the battery levels of your wireless peripherals in the taskbar or tray. Wireless Battery is one example. It reads battery data from supported mice, headsets, keyboards and controllers and shows it without vendor software. Support depends on each device's protocol and receiver.

How do I see my wireless mouse battery level on Windows 11?

Install Wireless Battery from the latest GitHub release and run it. Your mouse should appear in the taskbar with its percentage within a minute. If it doesn't, confirm the receiver's VID:PID is in the supported devices table, and close any vendor app that might be holding the device.

Why does my wireless mouse battery not show up?

The most common causes are an unsupported receiver or connection mode, a vendor app holding the device, or a device that is asleep. The app only shows devices it can decode, so a device on an untested or disabled connection mode won't appear. Check the device's entry in the README for caveats first.

Do I need Logitech G HUB or Razer Synapse installed?

No. Wireless Battery talks to devices directly, so G HUB, Synapse, iCUE and similar suites are optional. You can keep them installed or running, and they don't conflict with the app.

Start with one device today: install the app, confirm the reading, and see how it compares with your vendor's suite. Pass this to someone whose headset died mid-call, because a Windows taskbar battery monitor catches that before it happens.