Pebble M350 and M350s Bluetooth Pairing: Why the 3-Second Button Hold Is Everything

Published on 2026-11-08 · 7 min read · By MiniTestLab Engineering Team · Category: Mouse Hardware

Launch Companion Diagnostic Tool

Test your hardware right now in your browser with zero install:

Open Mouse Tester

If your Logitech Pebble M350 or M350s is not connecting, you are almost certainly on the wrong pairing channel. The M350 stores two separate device profiles on a single button, and a tap cycles through them without entering pairing mode — only a held press triggers the active pairing broadcast. The root cause is a low-cost tactile switch behind the channel button that registers both short taps and long holds, so the firmware distinguishes intent purely by hold duration, and most users never hold long enough.

Understanding the Channel Architecture Before You Touch Anything

The M350 (original) supports one Bluetooth channel plus one USB receiver slot. The M350s expands that to two Bluetooth channels plus one USB receiver slot, cycling through all three with the same button. Each channel slot stores a complete pairing record in the mouse's onboard flash. When you switch channels, the mouse immediately tries to reconnect to whatever device was last paired on that slot. If nothing is stored, the LED blinks amber rapidly — that is the unpaired state. If something is stored but out of range or powered off, the LED blinks amber slowly. These two blink patterns are different and tell you exactly what you are dealing with.

The button itself is a small dome tactile rated for roughly 500,000 actuations — not a named Omron or Kailh part, just a generic SMD dome. It will not fail on a new mouse. If you are getting no LED response at all when pressing it, the battery is the first suspect, not the switch.

Step-by-Step Pairing Procedure for Both Models

  1. Install one AA battery. The M350 uses a single AA; the M350s uses a single AA as well. Confirm polarity against the embossed diagram in the battery bay. A reversed battery gives zero LED activity and is the most common out-of-box failure.
  2. Slide the power switch on the underside to ON. The green indicator window next to the switch should show green, not red.
  3. Press the channel button (top rear of the mouse, small circular button) once to confirm which channel is active. The LED will blink the channel number in white: one blink for channel 1, two blinks for channel 2 (M350s only), three blinks for the USB receiver channel.
  4. Hold the channel button for exactly 3 seconds. The LED shifts to rapid white blinking — this is active pairing mode. The window is 3 minutes.
  5. On your host device, open Bluetooth settings and select "Pebble M350" or "Pebble Mouse 2" from the discovered devices list. Do not click anything on the mouse during this step.
  6. Connection confirms with a solid white LED for 2 seconds, then off.

If you are pairing to an iPad and the Logitech Pebble mouse is not connecting, go to Settings > Bluetooth, make sure Bluetooth is toggled on, and verify the iPad is not already connected to a different Bluetooth mouse consuming the HID slot. iPadOS limits simultaneous Bluetooth HID devices. Forget any old M350 entry in the iPad's device list before attempting a fresh pair.

M350 vs M350s: Hardware and Pairing Differences

Feature Pebble M350 (Original) Pebble Mouse 2 M350s
Bluetooth channels 1 2
USB receiver support Yes (Logi Bolt or Unifying) Yes (Logi Bolt only)
Battery 1x AA 1x AA
Reported battery life Up to 18 months Up to 24 months
Scroll wheel encoder Mechanical incremental encoder Mechanical incremental encoder
Main switches Generic low-force dome, not user-serviceable Generic low-force dome, not user-serviceable
Logi Options+ support Limited Full
Pairing button hold time 3 seconds 3 seconds

The M350s dropped Unifying receiver compatibility entirely. If you own a Unifying receiver (nano, identified by the orange star logo), it will not pair with an M350s under any circumstances. You need a Logi Bolt receiver, which uses a different 2.4 GHz protocol stack.

Diagnosing Clicks and Cursor After Pairing Succeeds

Once the mouse is connected, run a quick functional check before assuming software is the problem. Use the Mouse Test to confirm all three buttons register, that cursor movement tracks in all directions, and that there is no dead zone at low speed. The M350 uses a basic optical sensor — no acceleration tuning, no lift-off distance adjustment in firmware. If the cursor skips, the sensor window on the underside is dirty; wipe it with a dry microfiber cloth. Do not use compressed air directly into the sensor aperture.

If left or right click is registering as a double event, that is the dome switch beginning to fail or a firmware debounce issue. Check it with the Double Click Test — hold each button and watch for unintended double registration. On the M350, the main switches are soldered to the PCB under a snap-fit top shell secured by two Phillips screws under the rear label. Replacement domes are available but the shell is thin and flexes easily; use a spudger, not a flat screwdriver.

Scroll wheel stuttering or missing steps points to the mechanical incremental encoder getting contaminated. The M350 encoder is a standard 2-pin + common through-hole part, replaceable with a generic 11mm or 13mm scroll encoder under $5. Verify scroll behavior first with the Scroll Wheel Test to count missed pulses before opening the mouse.

Frequently Asked Questions

Why does my Logitech Pebble M350 keep disconnecting after a few minutes?

The M350 enters a deep sleep after 5 minutes of inactivity to preserve battery. The first click after sleep wakes it, which takes roughly 200ms — this is normal behavior, not a disconnect. If it is dropping mid-use, the battery voltage is sagging under load. Replace the AA battery even if a voltage meter reads 1.4V static; under-load voltage on a partially depleted alkaline can drop below the radio module's minimum threshold.

My Logitech Pebble mouse is not connecting to my iPad even though Bluetooth is on. What is wrong?

Go to Settings > Bluetooth on the iPad, find any previous "Pebble M350" or "Pebble Mouse 2" entry, tap the info icon, and select Forget This Device. Then put the mouse into pairing mode with the 3-second hold and re-pair fresh. iPadOS caches stale pairing records and will refuse to reconnect to a mouse that was previously paired on a different channel slot.

Can I use the M350s with a Unifying receiver I already own?

No. The M350s is Logi Bolt only. The Bolt protocol is not backward-compatible with Unifying hardware. You need a Bolt receiver, sold separately or included in the M350s box depending on the retail SKU you purchased.

The channel button LED does not light up at all. Is the button broken?

Almost always a dead or reversed battery. Confirm the AA is installed with the positive terminal toward the spring contact, not the flat plate. If a fresh battery in correct orientation still gives no LED, check for corrosion on the battery contacts — white or green residue from a previous leaking battery. Clean contacts with a cotton swab and isopropyl alcohol (90% or higher).

Does Logi Options+ change anything about Bluetooth pairing behavior?

No. Logi Options+ does not control the pairing process or channel switching. It reads device status after connection is established. Install it at options.logitech.com only after the mouse is already paired and showing as connected in your OS Bluetooth settings.

How do I know which channel the M350s is currently on?

Press the channel button once without holding. Count the white LED blinks: one blink is channel 1, two blinks is channel 2, three blinks is the USB receiver channel. The blink sequence completes in under 2 seconds. If you see rapid amber blinking after a single press, that channel has no stored pairing record and is ready to pair without the 3-second hold — though holding 3 seconds still works.

Launch Companion Diagnostic Tool

Test your hardware right now in your browser with zero install:

Open Mouse Tester