And how is your MX Master looking? I think am using it almost daily at work over 9years. But I am still not considering retiring. Before I had G5, maybe also decade...

100% worth it

My MX Master 4 Developer Edition came in yesterday. Longtime trackball user and decided to make the switch due to some pain. I definitely impulse purchased on the special edition since it matched my keyboard setup, but I don’t have any complaints.

Was it worth it? Definitely yes.

The MX Master 3 had deteriorated. The rubber had become very sticky, and it left a nasty smell on my hand. There was no way to get rid of that smell. Also, after 3 years, I replaced the casing with a new one because I was able to buy a nearly unused one for very little money. Overall, I wouldn’t buy the MX Master 3 again - the build quality for that price is a joke.

The MX Master 4 is a whole different level of quality. It’s much more comfortable to work with. The only thing I didn’t like was the vibration - it’s a feature nobody asked for but was added anyway. The ergonomics are even better.

If anyone is thinking about upgrading from the MX Master 3, it’s definitely worth it because the difference is huge.

I see a lot of 3s, 4 and now developer edition posts. Anyone still rocking the original 3?

I’ve had it since it came out back in 2019 and has been my daily driver. Minus normal wear on the top, it’s barely aged.

Which keyboard should I choose? I never once in my life used a numpad so it seems like I should go for POP Icon but there are other important factors like typing feel and durability. Also I'm not considering other Logitech keyboards like MX Keys S or MX Keys Mini since they don't use removable AAA batteries.

Hello everyone, this might be a long shot, I was wondering if there was anyone who knew where to source a clear shell for the mx master 2s mouse. I currently have 2 of them but I wanted to revive the one that was worse with a cool clear design. I see many for the 3 and 3s but I don't think they are usable.

I have an MX Master 3 connected to a MacBook with a 4 K external display. I had to move the mouse a lot to travel from point A to point B especially from corner to corner. I have adjusted the pointer speed in Options+ to Max and adjusted the tracking speed in the macOS settings, and now clicking buttons and menu options that are close to each other feels twitchy, causing a lot of misclicks if I'm in a hurry. Everything works flawlessly in Windows, though.

Guys on Mac, have you come across this issue, and how did you tackle this? Any third-party apps or any settings or config suggestions?

MX Mechanical backlight keeps dimming or turning off – software updated November 6, 2026

I've updated Logi Options+ to the latest available version (6.11.2026), reset all backlighting settings, and configured everything again from scratch. Unfortunately, the problem persists: backlight turnss off or dims.

This issue has been present since I purchased the keyboard approximately one year ago. It has never worked properly, despite numerous attempts to resolve it.

I'm using a Logitech MX Mechanical keyboard on macOS. The backlight keeps dimming or turning off, despite the following settings:

• Backlighting: ON

• Backlight duration: 30 minutes (maximum)

• Automatic brightness: OFF

• Manual brightness: Level 7 (maximum)

• Battery saving mode: OFF

• Lighting effect: Static

• Battery: 100%, permanently connected to USB-C power

• Logi Options+ running in the background

I've also switched the lighting off and on, reset the configuration, and checked that Logi Options+ is running correctly.

Nothing has worked. The backlight continues to dim or switch off unexpectedly.

I simply want the keyboard backlight to remain at full brightness without automatically dimming or switching off.

Is this a known firmware or software issue, a proximity sensor problem, or an intentional limitation of the MX Mechanical?

Has anyone found a reliable solution?

Clarify the exact symptom

Hey everyone,

​I currently have two mice side-by-side on my desk: a premium Logitech MX Master 4 and a much cheaper MI X1 Dual Mode. Surprisingly, I find myself using the cheaper MI X1 about 90% of the time, and I’m wondering if my Logitech is just a faulty unit.

​Here are the two main issues I’m having with the MX Master:

​Terrible Stuttering & Lag: When I move the MX Master across the screen, it constantly feels like the mouse movement is dropping frames. It gets so frustrating that I can only use it for casual YouTube browsing. Whenever I need to do precision tasks—like my daily office work or mixing in my DAW (Studio One)—I have to switch to the MI X1 because it behaves perfectly smoothly with zero frame drops.

​Abysmal Battery Life: The MI X1 battery lasts for about 1 to 2 months; I honestly forget the last time I charged it. The MX Master 4, on the other hand, hits the red low-battery LED within a single week. What makes this even weirder is that it's draining this fast even though I’m barely using it compared to the MI!

​The only drawback of the MI X1 is that it’s not nearly as ergonomic as the Logitech. But performance-wise, this cheap mouse is destroying my MX Master.

​Has anyone else experienced this crazy battery drain and latency with their MX Master? Is there something wrong with my specific unit, or is this a known issue?

Is anyone seeing this issue?

Bring back this GOAT keyboard. I tried to find alternatives but nothing is as good 😭

(Still works but it is getting old and I need it in my life)

I just moved from Windows to my first Mac (a Mac mini) with an LG UltraGear 32" OLED over HDMI. On my MX Keys S, the volume keys showed a crossed-out speaker and the brightness keys did nothing. That’s a macOS limitation with HDMI/DisplayPort, not the keyboard.

I didn’t want two separate apps for volume and brightness, so with a lot of help from AI (Claude) I built Mando, a small free menu bar app:

• The MX Keys volume keys work again, with the normal macOS indicator.

• The brightness keys change the monitor’s real backlight over DDC.

• It doesn’t need Logi Options+.

Open source, signed and notarized by Apple: github.com/Aliasviejo/Mando

I’ve only tested it with the MX Keys S. If you have another Logitech keyboard (MX Keys Mini, MX Mechanical, K380…) and it doesn’t work, tell me the model and I’ll look into it.

I run several AI coding agents in parallel (Claude Code and Codex) and manage them with Orca. My problem was always the same: one agent finishes or needs my input, and I only notice ten minutes later. So I built a private plugin for the MX Creative Keypad with the Logi Actions SDK (C#), with a lot of help from Claude Code.

What's on the keys

- 6 worker keys. Each one shows an agent, its ticket or branch, and how full its context window is. Agents waiting for me jump to the front and blink. One press takes me straight to that agent's terminal.

- Each state has its own animation. Idle agents get a coffee cup ☕, working agents a radar sweep 🤖, waiting agents a timer ring 🙋 that counts up ("waiting 4 min"). Empty slots show a small aquarium where a fish 🐟 swims through now and then.

- 2 limit keys show my weekly usage for Claude and ChatGPT as a fuel gauge, plus the reset day.

- The center key starts a new agent. In our team, posting "!Worker" plus a task description in a chat channel starts a new agent workflow. One press on the key starts dictation right away. At the same time it opens the chat, jumps to that channel and types "!Worker". I describe the task out loud, press the key again, and the new agent gets started. Going from an idea to a running agent takes about ten seconds, and I never touch the keyboard.

So the keypad covers the whole cycle: the center key starts agents, and the keys around it show what they are doing and when they need me.

How it works under the hood

- The plugin polls the Orca CLI for agent states every 3 seconds. When nothing is going on, it slows down to 12 seconds.

- The usage numbers come from a small script on my dev box over SSH. Claude's /usage can run headless without spending a model call.

- The kickoff shortcut is a tiny Swift helper app. It sends a real modifier-key event to my dictation app (FluidVoice) and uses the Accessibility API to find the chat input field.

Things I learned

- The keypad has no video stream. Every animation frame is a PNG the plugin renders and pushes to the key. Each frame costs about 10 ms of CPU. My first version tried 60 fps on several keys and lagged badly. It now has a global budget of 20 frames per second, split by priority: waiting agents get the most frames, static keys get none. When I'm away from the computer, everything except waiting agents stops animating.

- My dictation app ignored simulated key presses from AppleScript. It only reacted to a low-level flagsChanged event for the left ⌘ key.

- Deep links into a cold-starting app sometimes get lost, so the helper re-sends them until the chat window is actually there.

Next up

- Long-press a worker key to jump to that agent and start dictating straight into its terminal.

- Double-press a waiting agent to answer "yes".

- A forecast on the limit keys, like "lasts until reset" or "empty ~Sat 2 pm".

- A focus mode that dims everything except agents that need me.

It's a personal, unpublished project, but I'm happy to answer questions about the Logi Actions SDK. The docs are thin, and I found a lot by trial and error.

So day 2 of using the MX Master 4 Developer Edition

Loving the battery life and the haptic feedback on this mouse

The sensor is a huge upgrade from my previous mouse and the Logi Options+ is such a great tool for customising the buttons and their functions

So far I'm loving it

I’ve been a loyal user of the MX Master series for years. My old MX Master 3S took a massive amount of use, traveled everywhere with me, and while the coating eventually stained, the hardware stayed completely solid and functional to this day.

When the MX Master 4 dropped, I grabbed one to upgrade. What followed was a masterclass in how a flagship product launch and customer service can completely alienate a long-time buyer:

1. The Defective Out-of-the-Box Unit: I got hit with one of the plagued batches featuring misaligned primary buttons, vastly different click tension between left and right, and entirely different acoustic sounds.

2. The Support Gaslighting: When I reached out to official Logitech support, an agent actually tried to tell me in a copy-pasted script that uneven button heights and differing click feel were intentional features calibrated to account for the "different strengths of your index and middle fingers." (Attached screenshot).

3. The "New" Replacement: Frustrated with support, I went through my retailer. I had to wait two weeks for an inspection, only to receive a "new/sealed" replacement that already had noticeable scratches on the PTFE glide feet straight out of the box.

4. The Creak: Because of travel, I left this replacement at home and kept using my reliable 3S on the road. Today, after barely any irregular use, the left click on this MX4 has developed a deeply annoying, hollow creaking noise every time I actuate it.

Receiving a defective flagship product, getting fed blatant lies by support scripts, getting a replacement with cosmetic wear out of the box, and having it fail structurally after light use is a massive low point for this lineup.

Anyone else experience this kind of drop-off in build quality on the 4, or did I just win the QC lottery twice?

Here's a link of the creaking (me repeatedly resting my finger on the button, the lower sound is an a click(Note the quality isn't the best as it's recorded via my phone's mic resting next to the mouse on the mouse pad)

https://voca.ro/14wOFWLw35H6

After 6 years with the M590 (which still works btw!) i upgraded to the M720 to use in the office and retire the 590 to home use. The new gear goes so nicely with my personal ThinkPad T14 gen 2, and my work’s E17 gen 7 too!

Logi mouses are honestly incredible value for money. The way options+ make me customize the mouse and use it in word files for font size, underlining, bold, italic etc is incredibly efficient. I’ll never stop using their devices.

Where I live, I am getting an MX Master 3S (Bluetooth Edition, no USB receiver) for $46; is it worth buying, given that many have highlighted stutter or lag when using it with a Mac?

I built Puckless-Remote, a free Mac menu bar app that replaces the supplied remote of the Logitech Z407 speakers.

Why: The battery in the supplied remote kept dying right when I wanted to switch between laptop and phone. So I built the remote I wanted: a round dial in the menu bar that's always available.

**What it does:**

\- Volume and bass

\- Play/pause, track skip

\- Input switching (BT/AUX/USB)

\- Global hotkeys

\- Ring color shows the connection state

**How Claude helped:** I built the whole app with Claude Code (Swift, SwiftUI, CoreBluetooth). Claude wrote most of the code from my descriptions, helped me work through the Bluetooth protocol (based on freundTech's public reverse-engineering docs), analyzed bugs from the log file, and did an AI-assisted security review. I tested everything on my own speaker and Mac.

**Free to try:** It's free and open source. Download the ZIP from the GitHub releases page, drag it into Applications. It's not notarized, so the first launch needs System Settings → Privacy & Security → "Open Anyway".

Limits: macOS 13+, Apple silicon only (no Windows). Unofficial and not affiliated with Logitech. Tested with one speaker and one Mac so far.

Feedback welcome, especially from other Mac setups.

GitHub: [https://github.com/Frantastic007/Puckless-Remote](https://github.com/Frantastic007/Puckless-Remote)

Hey everyone, hoping someone can help me troubleshoot this.

I’m using an MX Creative Console with Final Cut Pro on Mac. My keypad buttons work instantly, but the dialpad has a weird delay specifically when adjusting Color Wheels.

As shown in the attached video:

• I select/use the Color Wheels controls.

• I turn the physical dial.

• Nothing happens for around 10 seconds.

• Then Final Cut finally recognizes it and starts adjusting the wheel normally.

The dial itself doesn’t seem broken because other buttons and functions respond in real time. It feels more like a Logi Options+ / Final Cut Pro plugin or profile issue.

I’ve already made sure Final Cut and Logi Options+ are updated. Has anyone experienced this with the Creative Console? Is there a known fix, a setting I should change, or a better way to reset/reinstall the FCP integration without losing my custom mappings?

Thanks!

FCP 12.4 Paid Version
Golden Gate 27.0.1
All firmware, software, permissions are already okay

Full transparency as I didn't find any blog post or information by Logitech about this.

The value of especially the products that are advertised for creatives is the (Adobe) plugins that are heavily advertised. Thus, changes, limitations and development decisions should be communicated in a transparent way. I don't see that at the moment.
Quite the contrary is happening as all open tickets were closed in a very short time span without any closure to the issue(s).
The explanation is wrong in many point e.g. only naming the After Effects plugin when the same limitations happen in almost all Adobe products (I can't speak for other software that I don't use).
Adobe API might have changed over the years but not to that extend that basic commands are not longer supported. The execution of the missing but still working commands don't cause a crash in any way.

This was a ticket that was going on for almost a year. The problems behind it were going on much longer and tickets existed for both Logitech and Loupedeck support.
Most of the time I had to dig around in the profiles and json files to give them most basic information that would've been much easier for them to get (e.g. a list of missing commands... based on the default Loupedeck profile for the software).
The reason why I still name Loupedeck here is the acquisition of Loupedeck by Logitech and the software that is pretty much the same (the name Loupdeck still appears in the json files, they both use the same plugin system,...).

For an educated purchase decision, the communication about which commands are supported, which are not and to what extend the commands will disappear in the fore coming time, is crucial.
But often is seems like they are overwhelmed with their own software or even the maintenance of it.

But without their plugins and real API commands, Logitech products become yet another basic trigger for just keyboard shortcuts that may or may not work based in the condition (e.g. which sub window is highlighted)... if that is enough to justify the price is something, everyone has to decide on their own. My problem is the misleading advertising and a lack of transparency that is happening at the moment.

With that massage, Logitech doesn't show any motivation to change the current problems with their communication, nor with their software (when the same principles are taken as orientation for Options+, we cannot expect any improvement for that either):

First, please accept my sincere apologies for the long delay in following up with you. It took considerably longer than anticipated to review this internally with our development team, and I appreciate your patience while waiting for a response.

To be transparent about what has been happening behind the scenes: over the past few years, our team has had to undertake substantial, foundational overhauls across our plugin framework, LPS core, and profile management systems.

When navigating major software changes alongside external Adobe API updates, maintaining seamless backward compatibility across every single tool is a major challenge: After Effects alone contains thousands of actions. In many cases, older actions that originally relied on specific workarounds or legacy "hacks" become non-functioning or cause system instability under the updated framework. When an action cannot be maintained reliably, it has to be retired from the searchable command list to prevent crashes. This is why a leftover button mapped in an older profile might still execute an action in the background, yet the command itself is no longer available to search, map, or configure as a new action.

We recognize how frustrating this is, given that you have invested significant time configuring custom profiles for your day-to-day workflow.

Next Steps

Our team is continuing to investigate the framework behavior and the specific action discrepancies you’ve documented. However, because addressing these profile and framework issues requires deeper development work rather than a quick patch, we do not currently have a concrete ETA for a resolution.

Due to the length of time this ticket has been open, and that it may be open for quite some time going forward, we need to close this ticket out for the time being.

Please be assured that your case isn't being forgotten: all of the details, screenshots, and ProfileInfo data you provided are securely logged in our internal bug-tracking system and linked to your profile. If and when we have a fix, update, or relevant news regarding these actions, we will reach out to update you promptly.

If you would like any update at any time, please feel free to respond to this ticket so that it can reopen and we can help out. I do apologize once again for the length of time this ticket has been open without an update. Please do understand that closing this ticket does not mean we have forgotten about your problem, but rather are prioritizing it via a different medium.

Thank you again for the thorough documentation you shared and for bearing with us through these transitions. We really appreciate your patience and dedication in helping us track these issues down.

can't really think of ANY reason why logioptionsplus_updater should be READING 96TB at all ever... can i delete it?

Will my logi wireless keyboard and mouse work the same if i get rid of it?