cancel
Showing results for 
Search instead for 
Did you mean: 
Replies are disabled for this topic. Start a new one or visit our Help Center.

Persistent False Tamper Alarms – Nest x Yale Lock – No Real Fix or Support

ArsenG
Community Member

Hi everyone,

I wanted to share my experience and see if anyone has found a true solution for the persistent false tamper alarm issue with the Nest x Yale Lock.

I’ve been a loyal Yale user for over 4 years. From the beginning, my lock has constantly triggered tamper alarms for no reason — even when the door is untouched. I have tried every fix suggested here and by Google/Yale support:

  • Multiple factory resets

  • Checking/reseating the internal cable

  • Tightening screws

  • Replacing batteries countless times

  • Updating firmware whenever possible

Nothing permanently solves the problem.

Yale support finally admitted that this is likely a manufacturing defect but refused a replacement because my lock is technically out of warranty. They offered me a 20% discount code for a new lock — but then said they ran out of codes and put me on a waitlist.

It’s extremely disappointing that a security product with a known defect can’t be replaced or properly supported — especially considering how many others have posted about the same issue.

Has anyone found a true long-term fix for the tamper alarm? Or has anyone been able to get a proper replacement through Google Nest or Yale?

I’m considering sharing this more widely so other customers know before buying. Any advice on next steps is appreciated.

Thanks for reading — hope this helps others too.

Arsen

2 REPLIES 2

Mrpopun
Community Member

I'm in the same boat considering they have been denying any fault  for years it's likely they will not offer a replacement.

Who did you contact nest yale ot google?

ArsenG
Community Member

Actually, both were involved—Google initially referred me to Yale, and the entire conversation continued with Yale. The strange part is that they offered a discount on a new product, only to retract it in a follow-up email. I’ve never encountered anything like this before.