[Bug]: Logitech MX Master 3S Thumb Wheel only works in one direction
- Dominant language
- Rust
- Stars
- 21k
- Forks
- 675
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 174
Description
### Pre-flight checklist
- [x] I searched [existing issues](https://github.com/AprilNEA/OpenLogi/issues?q=is%3Aissue) and this is not a duplicate.
- [x] I am on the [latest release](https://github.com/AprilNEA/OpenLogi/releases/latest) or a recent `master` build.
- [x] I quit **Logi Options+** before running OpenLogi (the two apps fight over HID++ access and only one can own a receiver at a time).
### Which part of OpenLogi?
GUI (desktop app)
### OpenLogi version
0.4.1
### Operating system
macOS
### OS version & architecture
macOS Tahoe 26.5, Apple Silicon
### Device model
MX Master 3S - 0b034
### How is the device connected?
Bluetooth (direct, no receiver)
### Affected area(s)
- [ ] Device discovery / detection
- [x] Button remapping
- [ ] DPI control
- [ ] SmartShift
- [ ] Per-application profiles
- [ ] Battery status
- [x] Settings / configuration (TOML)
- [ ] Auto-update
- [ ] Menu bar / tray
- [ ] Other
### What happened?
Thumb Wheel only works in one direction
### Steps to reproduce
1. configure thumb wheel to "Next Tab"
2. scroll up -> next tab
3. scroll down -> I expect "previous tab" action
### `openlogi list` output
```text
```
### Logs
```shell
```
### macOS permissions (if applicable)
- [x] OpenLogi has **Accessibility** permission (needed to remap buttons via the event tap).
- [x] OpenLogi has **Input Monitoring** permission (needed for Bluetooth-direct devices and capture).
Contributor guide
No contributing guide indexed for this repository
Research direction
No source files or tests are named in the report. Start by reproducing the MX Master 3S Bluetooth issue on macOS with the thumb wheel mapped to “Next Tab,” then compare the up and down event paths and inspect the resulting TOML configuration. Done means the configured behavior triggers next and previous tab actions in the two directions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100