CAMARO6 - View Single Post - Passive Door Unlock Driver's Side not Responding

vaeron · 02-18-2026, 01:45 PM

Okay I've searched everywhere and decided to wait to post about it until today. I've got my 2016 2SS, the passive door UNLOCK (edited, mistyped) works fine on the passenger side when attempting to enter the vehicle, but the driver side does not. Has anyone run into this issue? what was the fix? My first thought was the button not making contact or having a torn lead (haven't torn into it yet) but wanted to rule out anything else before I started pulling door trims to get into the door. Every other aspect of the locking / unlocking mechanism works. It locks fine automatically when I walk away, car starts normally every time. I have multiple fobs and replaced batteries in both. It is only the driver's side passive unlock that's not working.

02-18-2026, 01:45 PM	#1
vaeron Drives: 2016 Camaro 2SS Join Date: May 2025 Location: Washington State Posts: 54	Passive Door Unlock Driver's Side not Responding Okay I've searched everywhere and decided to wait to post about it until today. I've got my 2016 2SS, the passive door UNLOCK (edited, mistyped) works fine on the passenger side when attempting to enter the vehicle, but the driver side does not. Has anyone run into this issue? what was the fix? My first thought was the button not making contact or having a torn lead (haven't torn into it yet) but wanted to rule out anything else before I started pulling door trims to get into the door. Every other aspect of the locking / unlocking mechanism works. It locks fine automatically when I walk away, car starts normally every time. I have multiple fobs and replaced batteries in both. It is only the driver's side passive unlock that's not working. __________________ 2016 Black 2SS purchased in May 2025, 6 Spd. GM Performance Strut Tower Brace, Mishimoto Oil Catch Can, MRR M017 wheels, powder coated in satin black, Continental Extreme Contact DSW06 285/30R20 in the front and 305/30R20 in the rear. Last edited by vaeron; 02-20-2026 at 12:39 AM. Reason: mistyped and put lock instead of unlock.