Tonight at 2:14 a.m., our shiny BLE keypad tried to negotiate with a 30-year-old mortise deadbolt and threw a firmware tantrum — four beeps, purple LED, then a demand for an integration it clearly doesn’t need. If anyone has a graceful way to make legacy hardware stop ghosting modern readers without replacing the whole cylinder, I’m all ears before my migration plan turns into couples therapy.
I’ve had a BLE keypad do the same “four beeps, purple LED” on a cranky mortise when the bolt had too much drag; a 1 mm strike shim and a puff of dry graphite, then re-running auto-calibration, stopped the ghosting without touching the cylinder… If shimming’s off-limits, bump the torque during calibration once, but don’t let it hide a misaligned door.
Quick fix that saved me once: the reader’s tailpiece was a hair too long and bottoming in the mortise cam — trimmed about 1 mm and eased the top through‑bolt a quarter turn during auto-cal, and the purple diva stopped sulking. @jessica_b88’s shim tip is solid; if you’d rather not cut metal, a thin nylon washer behind the escutcheon can relieve the twist enough to pass calibration — worth a 2‑minute try?
Ended a similar standoff by setting the reader to ‘short throw’ rotation in the app; once it wasn’t trying to over‑travel the mortise cam, the purple sulk vanished. If your firmware doesn’t expose that, clock the tailpiece one tooth on the cam as a stopgap, but only if the case return spring feels crisp.