Wife had a weird experience with her 22 RDX today. The unlock on the keyfob didn't work, and Acuralink unlock kept giving an error and wouldn't connect.

Strangely, the remote start on the keyfob worked fine.

Wife had to use the physical key to get in the car and then it started fine with the regular pushbutton. Then the remote unlock began to work again.

Anyone see this before? Thoughts on what might have happenned?

 

I had the same happen to me a few months ago. Mine also was running at the time. Thank god for the actual key in the fob. Has not happened again. Keeping my fingers crossed….

 

It has happened to me at least 3 times after remote starting the car and trying to get on while car was running. If I recall correctly, I postedy experience here the first time. I haven't been able to find an answer.

 

This has happened to me a couple of times with my '22. Both times was when it was running after remote start. I was able to unlock it after canceling the remote start, then pressing lock, then unlock.

 

This is a problem only on Advance models? My '23 Tech key fob doesn't have remote start.

 

Keyfob remote start was added to the Advance and the A-Spec Advance models in the '22 model year. My '20 Advance does not have keyfob remote. Otherwise, it was a dealer installed option or available with an AcuraLink subscription.

Ron