AprilNEA / AprilNEA/OpenLogi

[Device]: Logitech MK295 (Nano Receiver, PID_C534) not detected

Open
#866 0 comments 0 reactions 0 assignees View on GitHub
area: hidpp needs: triage
Dominant language
Rust
Stars
21k
Forks
675
Avg merge
2d 5h
Merged PRs (30d)
172

Description

### Pre-flight checklist

- [x] I quit **Logi Options+** before testing.
- [x] I searched existing issues for my device.

### Device model

MK295 Silent Wireless Combo (keyboard + mouse combo)

### Connection

Other / not sure

### What's the problem?

Device is not detected at all

### `openlogi list` output

```text
openlogi.exe list
WARN openlogi_device::inventory: node probe keeps failing — retiring its channel before reopen
WARN openlogi_device::inventory: node probe keeps failing — retiring its channel before reopen

Gaming Mouse G502 (—, vid=046d pid=c07d)
└─ slot 255 ● Tunable FPS Gaming Mouse G502 (mouse, wpid=?, battery=—)
model_ids=[0000,0000,0000] ext=00 serial=— unit_id=00000000 transports=—
```

### `openlogi diag features` output

```text

```

### Details

Device is not detected at all

Receiver hardware IDs (Windows Device Manager, keyboard interface):
HID\VID_046D&PID_C534&REV_2901&MI_00
HID\VID_046D&PID_C534&MI_00

This is a "Nano Receiver" (VID_046D, PID_C534), shared across several
Logitech budget wireless sets (e.g. MK270, MK295), not a Unifying or
Bolt receiver. openlogi list does not show the receiver or the
keyboard/mouse at all — only the wired G502. The two "node probe
keeps failing" warnings may be related to this receiver failing to
respond as expected during probing.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing `openlogi.exe list` and `openlogi diag features` with the MK295 Nano Receiver connected, using the reported VID_046D/PID_C534 identifiers. Trace the receiver inventory path associated with the `node probe keeps failing` warnings. Done means the receiver and its keyboard/mouse appear in `openlogi list` without those probe failures.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
embedded-iot
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.