Both keys are rejected during a weak battery event
Both keys being rejected during a weak-battery event makes common vehicle supply a priority before condemning the keys. Low power can disturb recognition, but persistent access faults after supply is restored still require their own tests.
Preserve the shared timing
Record cranking/no-crank behaviour, exact messages and any simultaneous resets. Save relevant faults before clearing. Compare whether remote unlocking and passive starting fail together or only one function is affected.
Stabilise supply and reassess authorization
A workshop should charge/assess the battery, check loaded delivery/earth connections and verify charging. A correct resting reading does not prove the supply remains suitable during a start request. Avoid repeated attempts that further deplete reserve.
Then evaluate the access/start request and supported backup recognition. If both keys remain rejected with sound supply, investigate the common detection/control path from evidence rather than replace two keys. A separate engine cranks-but-no-start complaint needs its own combustion branch once authorization is established.
Verify a comparable first start
Correct the demonstrated supply or detection fault and use the proper battery/setup procedure if applicable. Keep pre/post scans so voltage effects are distinguishable from remaining key-system defects. Warm recovery immediately after charging is only an initial check.
Outcome & verification
Confirm reliable recognition, start authorization and normal cranking after comparable parking, with stable supply and no renewed relevant fault.
Community discussion
Owner experiences, questions and other possible solutions.
No owner experiences yet. Share what was checked and what happened.
Sign in to share your experienceHelpful votes reflect community experience. Repair outcomes are self-reported.