Hello, Some Unifying-ready Logitech devices, such as the M305 mouse, come with a non-Unifying receiver. It looks the same, but instead of the Unifying logo it has 'NANO RECEIVER' written on the case. The device ID of the nano receiver is 0xc52f. I have M305 and M175 mice. Both of them come with one of these Nano receivers.

I added the ID to the code and your pairing tool worked, both mice pair successfully. All it needs is a new define in line 29: define USB_DEVICE_ID_M305_NANO_RECEIVER (__s16)0xc52f and including this new ID in the comparison in line 59: info.product!= USB_DEVICE_ID_M305_NANO_RECEIVER && I'm posting this here in case you want to add it to the code. It does support battery information, although the granularity depends on the device.

The original VX’s receiver was. Kcn Serial Mac Booster here. I had with the VX Nano: Logitech’s Mac. When I tested these third-party mouse drivers.) The Nano requires 2. Download and Update Logitech VX Nano Cordless Laser Mouse Drivers for your Windows XP, Vista, 7, 8 and 10 32 bit and 64 bit. Here you can download Logitech VX Nano.

For example, an Anywhere MX can report battery with a precision of 1%, but a M525 mouse can only report 'critical' (5%), 'low' (20%), 'high' (50%) or 'full' (90%). For just battery information, you can also rely on UPower 0.9.22 or later (earlier versions were buggy). Example: $ upower -d. Device: /org/freedesktop/UPower/devices/keyboard_0003o046DoC52Bx001B native-path: /sys/devices/pci00:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.2/0003:046D:C52B.0016/0003:046D:C52B.001B vendor: Logitech, Inc. Model: K800 serial: FB841B86 power supply: no updated: Tue 05 Nov 2013 07:15:32 PM CET (11 seconds ago) has history: yes has statistics: no keyboard present: yes rechargeable: yes state: discharging percentage: 55%. (if you know the path, you can also use upower -i /org/freedesktop/UPower/devices/keyboard_0003o046DoC52Bx001B to restrict the output to a single device).