02-27-2025 02:52 AM
I use the Nest doorbell 2nd Gen in combination with a traditional chime inside. The Nest is the battery-powered version since it's the only version available here in Germany, but I use it with a cable connection. My problem is that the chime's striker vibrates constantly, which is clearly audible and therefore very annoying. I've now read that this is due to a series connection of the two items to power the Google Nest - i.e. the Nest is connected to the doorbell in a closed circuit, which causes the striker to vibrate constantly.
Can anyone confirm this for me? Are there ways to solve this (apart from switching to the Nest Mini instead of the traditional bell)?
Answered! Go to the Recommended Answer.
02-27-2025 08:59 AM
Not sure about "fixing" but I had a very similar issue a few years ago .. where the traditional chime was constantly getting energized slightly, then it proceeded to smoke ! Thick stinky smoke began to pour out of the unit and I had to run to find out how to de-energize it. I did so by shutting circuit breaker the 26vac transformer was on. I have since gone to the Nest App and shut off the chime which had another benefit .. it still chimes thru my home display and my doorbells used to quit after button was hit, and re-boot. Now they don't anymore. My suggestion is to abandon the old chime, change your settings. Sorry.
02-27-2025 08:59 AM
Not sure about "fixing" but I had a very similar issue a few years ago .. where the traditional chime was constantly getting energized slightly, then it proceeded to smoke ! Thick stinky smoke began to pour out of the unit and I had to run to find out how to de-energize it. I did so by shutting circuit breaker the 26vac transformer was on. I have since gone to the Nest App and shut off the chime which had another benefit .. it still chimes thru my home display and my doorbells used to quit after button was hit, and re-boot. Now they don't anymore. My suggestion is to abandon the old chime, change your settings. Sorry.
02-28-2025 05:55 AM
Thanks so much for your detailed answer, highly appreciated. As you said, I'll now work on a workaround, absolutely fine. Happy weekend!