Fix Magic Mouse & Keyboard Not Connecting to Mac — Troubleshoot Fast

Why your Magic Mouse / Apple mouse isn’t connecting (and how to think about the problem)

When an Apple mouse or keyboard refuses to connect, the root cause almost always falls into one of four domains: power & hardware (dead battery, faulty switch), Bluetooth state on the Mac (software, stuck controller), interference or range issues, or pairing/data corruption (device stored but not discovered). Diagnosing efficiently means eliminating the simple causes first and saving the heavier resets for last.

This article assumes you’re troubleshooting common queries such as “magic mouse not connecting,” “apple mouse not working,” “magic keyboard not connecting,” and “reset bluetooth module mac.” I’ll walk you through quick checks, progressive fixes, and advanced resets so you don’t jump straight to the nuclear option (SMC/NVRAM) before you have to.

Throughout the steps below you’ll see instructions for macOS Bluetooth and hardware resets that apply to recent macOS versions (Big Sur, Monterey, Ventura, Sonoma). If you need a script-driven or developer-oriented approach, see this troubleshooting repository on GitHub for collected diagnostic steps and logs: apple mouse not connecting.

Quick checks and fast fixes (do these first)

Before you change settings or reset modules, run this fast checklist to catch the low-hanging fruit. Most connection failures are caused by simple, fixable issues such as drained batteries, switched-off devices, or a device that’s already paired to another host.

• Confirm device power: switch on the Magic Mouse/Keyboard and check the battery or built-in battery charge.
• Make the device discoverable: toggle the device off and on, or press and hold the pairing button (for older models) to enter pairing mode.
• Check macOS Bluetooth: open System Settings → Bluetooth and look for the device; if present but not connecting, choose “Forget Device” and re-pair.

If the device doesn’t appear in Bluetooth settings at all, move the mouse close to the Mac and remove obvious interference (microwave ovens, 2.4 GHz routers in close proximity, USB 3.0 hubs). Try pairing with a different Mac, iPad, or iPhone to confirm the peripheral itself is functional. If it pairs to another host, the problem is with macOS Bluetooth state rather than the device.

Also restart your Mac. Yes, the venerable restart will clear many transient Bluetooth controller states. Restarting will also clear temporary connection caches that block fresh pairing attempts. If restart fails, proceed to the next section for targeted Bluetooth troubleshooting.

Advanced Bluetooth troubleshooting — precise steps and terminal commands

When quick checks don’t work, we move into advanced but safe debugging: remove cached pairings, reset the Bluetooth controller, and check system logs. These steps will not reset your whole Mac; they target the Bluetooth stack and pairing database.

First, remove the device from macOS Bluetooth and delete pairing records. Open Terminal and run these commands to remove Bluetooth plist caches and reload the daemon—this often resolves “device discovered but won’t connect” errors:

sudo rm /Library/Preferences/com.apple.Bluetooth.plist
sudo rm ~/Library/Preferences/com.apple.Bluetooth.plist
sudo pkill bluetoothd

After running the commands, restart the Mac or toggle Bluetooth from the menu bar. If you’re on macOS Ventura or later and don’t have a Bluetooth icon visible, open System Settings → Control Center → Bluetooth and enable the icon in the menu bar for faster access during troubleshooting.

If Bluetooth device names are present but connections repeatedly fail, check Console.app (filter for “bluetoothd”) to see pairing errors, authentication failures, or OS-level messages. Authentication failures often indicate firmware mismatches or a need to unpair the device from another previously paired host.

Reset Bluetooth module, SMC, and NVRAM — when to use each reset

Use the Bluetooth-module reset when the Bluetooth controller behaves oddly (devices oscillate between connected/disconnected, or pairing repeatedly times out). A proper Bluetooth reset clears the controller’s state without touching other system settings.

macOS no longer exposes a one-click “Reset Bluetooth Module” in System Preferences for recent versions, but you can still achieve the equivalent by running the terminal steps above, or by removing Bluetooth PLIST files and restarting. If you prefer a UI-guided approach on older macOS builds, hold Shift+Option and click the Bluetooth menu and choose “Reset the Bluetooth module.”

If Bluetooth-module resets fail, escalate to SMC (System Management Controller) or NVRAM resets—these handle lower-level hardware states and persistent parameter storage. SMC reset is helpful for USB/Bluetooth controllers stuck at the hardware level; NVRAM reset helps with persistent device pairing memory or unusual I/O errors. Follow Apple support’s official guidance for SMC/NVRAM reset steps by model. Apple’s help page for wireless accessory issues is useful: Apple Wireless accessory troubleshooting.

Practical pairing and firmware tips

If your Magic Mouse pairs but stutters, or the Magic Keyboard has missed keystrokes, check firmware and macOS updates. Apple occasionally releases firmware updates for Bluetooth peripherals that resolve pairing and stability problems. Use Software Update in System Settings to ensure your Mac is current; peripherals often receive firmware updates when connected to an updated macOS host.

For rechargeable Magic Mouse or Magic Keyboard, check the battery level. Low power can allow initial pairing but will drop connections under load. Swap to a wired Lightning connection (for Magic Keyboard / Magic Mouse 2) to ensure the device is charged and to force a firmware update where applicable.

If you have multiple Bluetooth devices, avoid heavy simultaneous pairing during troubleshooting. Disconnect or power off other nearby Bluetooth hosts (phones, tablets) so the Mac and target device perform a clean first-time pairing. Interference and auto-joining to previously paired hosts (e.g., iPad) are common causes of “magic mouse not connecting” symptoms.

When to escalate and what to collect before contacting support

If none of the above fixes the issue, collect the following before contacting Apple Support or a repair center: macOS version, Mac model and year, console logs filtered for “bluetoothd”, exact device model (Magic Mouse 1 vs Magic Mouse 2), and the troubleshooting steps you tried (repairs, resets, battery checks). These details significantly speed diagnosis.

If a clean macOS install fixes Bluetooth behavior temporarily, consider hardware diagnostics: run Apple Diagnostics (restart and hold D) to check for hardware faults. Persistent failures after SMC/NVRAM reset and following diagnostics usually point to a failing Bluetooth module on the logic board.

If you want community-driven examples and scripts to capture logs and pairing traces, see this companion repository: magic mouse not connecting diagnostics. It includes commands and structured output to share with support teams.

Preventive tips and best practices

To avoid future connectivity headaches, keep these habits: keep macOS up to date, maintain a charged battery in rechargeable peripherals, and use a single primary host for pairing when possible. Where multiple Macs are used, unpair devices from the idle hosts to prevent automatic re-connection conflicts.

Maintain a tidy Bluetooth device list—remove devices you no longer use so macOS doesn’t attempt to connect to stale pairings. Periodically check for firmware updates and charge your Magic Mouse/Keyboard before major meetings or presentation sessions to reduce the chance of mid-task disconnects.

Finally, if you rely on a Bluetooth mouse for accessibility or precision work, keep a wired backup or a USB/Bluetooth dongle mouse ready. That quick fallback prevents lost productivity while you diagnose and fix Apple Bluetooth issues.

sudo rm /Library/Preferences/com.apple.Bluetooth.plist
sudo rm ~/Library/Preferences/com.apple.Bluetooth.plist
sudo pkill bluetoothd