I have two original wired video doorbells v1. They work perfectly so do the chimes. I need more chimes. Chimes for this model are no longer available so I purchased a Universal Chime which is supposed to work for all model doorbells. It sets up beautifully and when tested rings the chime I had selected. But when the doorbell is actually pushed, it reverts to the default ding dong. I have deleted and reinstalled it many times, the result is always the same. It works perfectly when tested and plays my requested chime. Just not when the doorbell is pushed and I have specifically requested that particular chime to play when the doorbell is pushed - it always defaults back to ding dong. What is going on?? How do I get one of those original chimes that worked perfectly and were easy to set up. I have found them cheaper other ways but not the chime separately.
I’ll note first of all that I have neither the original Video Doorbell nor the Wi-Fi Chime, but your post reminds me of what another community member is describing in a different topic:
In that case, I think the user was speculating that this is a bug related to the use of beta software/firmware, but I didn’t see a mention of that in your post, so I imagine you’re using production products; however, sharing things like your Wyze app version and the firmware version of your Wi-Fi Chime might be helpful.
If you know that you have the Wi-Fi Chime properly configured with the sound you’ve chosen but it’s still playing only the default sound with the doorbell button press action, then that definitely seems like a case where I’d generate a log and open a Support ticket referencing the Log ID. What did Support say when you contacted them?
everything is said correctly I believe I am a beta tester there’s the version there’s the signal strength there’s the settings you can see it’s supposed to do the “reverb bell“ not the doorbell but every motion triggers the doorbell sound.
Right. I get that from reading your posts elsewhere describing this problem with beta firmware. What I was trying to do above was elicit more detail from @mparegian, because the problem description originating this topic didn’t mention the use of the beta app or firmware, and I think having those kinds of details might help to flesh out the scope of this issue.
I think the screenshots showing your Automation and Chime Tune selections are helpful. 
I am not a beta tester and my firmware is identical to nikrib’s post. I suspect the problem may be with the older original version of the video doorbell. It is no longer available nor the chime that came with it which is why I purchased the universal chime. It tests perfectly playing the correct chime until the actual action requested which is pushing the doorbell - then it defaults back to the stock ding dong. Very frustrating.
I didn’t figure you were, but now I’m seeing part of my own confusion: @nikrib has been posting to a Beta topic from last month, but Wi-Fi Chime firmware update 1.0.0.43 was more recently announced as a production update in a Wyze News topic earlier this month:
Thank you for clearing that up! Has your Wi-Fi Chime always behaved this way with a button press on your Video Doorbell v1, ever since you added the Wi-Fi Chime, or did it work as expected initially but then change at some point? I’m trying to get a sense of whether or not the timing of your issue coincides with the release of this firmware version.
The Wi-Fi Chime that came with the old original version has always worked perfectly. I just this week tried to add the new Universal Chime and while it set up easily and connects with my old version doorbell and tests perfectly - when someone uses the doorbbell, the old one works perfectly but the new one just ding dongs (I am using two because my home is two story and I can’t hear it if I am not on the ground floor and I am usually upstairs). Interestingly enough today, when someone pushed the doorbell, the original chime downstairs worked perfectly with my desired chime, but the new Universal Chime upstairs didn’t chime at all, instead I got a notification on my phone that someone was there - I don’t want that. This is getting crazy!! I’ll probably just go find an old complete set of this on-line just to get another original chime which seems to work perfectly with the old original chime V1. But I shouldn’t have to since Wyze states it works with all of their videro doorbells. Apparently not their original V1 model if you want to change it from the default chime. I am using the dog bark chime and it has been great in warding off unwanted callers - it even scared off a relative because they knew I didn’t have a dog, so figured they were at the wrong house. I has to run out and bring them back!!
Yeah, I get that you’re talking about two different things:
- Wyze Chime came with the original Video Doorbell (“v1”) and communicates directly with that doorbell wirelessly in the ~900 MHz range but doesn’t use Wi-Fi. That’s what you’d like to add to your existing doorbell, but it appears that it’s no longer available.
- Wi-Fi Chime (also called Universal Wi-Fi Chime) was introduced with Duo Cam Doorbell last year and then later made available for sale as a separate accessory. That one does use 2.4 GHz Wi-Fi, which is what allows it to attach to your LAN as an independent device and be triggered by other Wyze Video Doorbells and Cams.
That’s one solution. Looking at the Wyze Web site right now, I’m seeing this:
- Wyze Video Doorbell (Wired) shows as “Out of stock” but has a “Notify me when back in stock!” button; however, a note on the product page also says, “Item is no longer available.”
- Wyze Chime shows as “Out of stock” but has a “Notify me when back in stock!” button.
- (Refurbished) Wyze Video Doorbell (Wired) shows as “Out of stock” but has a “Notify me when back in stock!” button.
If you’re looking third-party, then an eBay store appears to be affiliated with Wyze and has a listing for “Wyze - Video Doorbell Wired 1080p HD Video with 2-Way Audio - White” which appears to include the Chime.
Based on what you and @nikrib are describing, I still wonder if there’s a problem with Wi-Fi Chime (Universal Wi-Fi Chime) itself and its most recent firmware, as I imagine the Wyze app immediately prompted you for a firmware update when you set it up this week. That seems to be one common thread in your experiences.
Thank you for your reply. I have already asked to be notified if and when the old chime becomes available but I doubt it will. Yes, I have already located several used complete V1 doorbells which do include the chime. I know it will work as I have two old chimes installed with a V1 doorbell and they work correctly at another home. I got the additional chime before they quit selling them. It is just becoming expensive and frustrating which I should not be required to endure had they just not said the universal doorbell was compatible with all versions of their doorbell. Guess they forgot about their old Version 1. I have been using Wyze products since they first started so many years ago and I think I have almost everything they sell and they all still work well so I have been very loyal to Wyze and am quite disappointed when I could not get a new chime for my old doorbell. Guess I’ll just have to bite the bullet and buy a new/used setup to get that old chime. Thank you for your help.
You’re welcome. For whatever it’s worth, I’ve already asked other volunteers to try to replicate the issue that’s being described here and in the Beta topic I linked in an earlier post above, since I don’t have this particular product. Hopefully we can get some feedback on that and have a better idea of the root of this issue, whether it’s the Wi-Fi Chime’s firmware or not.
If it can be determined that the issue is related to the Wi-Fi Chime’s 1.0.0.43 firmware, then I’d expect Wyze to resolve that with a future firmware update. This is where replicating the issue, submitting a log, and then opening a ticket with Support that references the Log ID can also help to get this problem to the developers’ attention.
Just as an FYI, I am on 1.0.0.43 and still get failures which cause the default doorbell sound to come out when I assign other sounds to events.
This is hilarious! My wife and I used to imitate dogs barking when we saw people or cars passing by our driveway before we got this Chime. When I first set it up, I set it to sound the doorbell when the button was pushed, and the Dog Barking upon Motion Detect. When she came home, and the first person walked by the house and the Chime started barking, we were crying we laughed so hard! 
I am using the Wyze DoorBell v2 v 4.52.2.4190 with the Wyze Wi-Fi Chime v 1.0.0.43. Chimes associated with the Doorbell seem to work consistently fine, and one of my V4 Cams always chirps the Bird sound when detecting motion at my BirdBath. But, when I tried to assign sounds to any other v4 cams they trigger the default doorbell most of the time, and will occasionally ring out with the assigned sounds. It’s inconsistent, and inconsistent results are the most difficult to troubleshoot.
IS WYZE EVER GOING TO RESPOND TO ANY OF US ABOUT THIS ISSUE?
AND WHY IS THIS TOPIC MARKED AS SOLVED?
I’m not sure that SHOUTING is necessary. I mentioned this above:
These things take time, and it’s important to remember that you’re not communicating directly with Wyze when posting here. This is primarily a user-to-user support community.
Whoever creates a given topic (in most categories) has that privilege, and @mparegian apparently chose to exercise it at some point. That person also has the ability to change that decision.
Sorry, it is getting frustrating when we are helping out by providing test results, without an acknowledgment that anyone even saw them.
Then to close it, without any reason kinda makes us feel like our concerns are not even being considered. Something like. “We are aware and looking into this” would be fantastic, even. But to close it out without a reason, or any explanation is really pretty inconsiderate. We are all just trying to help to find bugs, so that WYZE will be aware and able to look at it, perhaps to make their products even better. We are not expecting to be paid, or compensated in anyway for our support in troubleshooting. It is a very valuable contribution as I have worked most of my career in IT and Telecom, when someone brings an issue to the attention of those responsible for the quality of the product, it is valuable and a little recognition would be in order.
Just my opinion… for what it’s worth. (if anything)
I don’t know what you mean by this. Some additional context might be helpful.
they just closed the topic but never gave us any feedback as to whether they even heard our issues. This topic is feedback on the latest release, with issues that we are all experiencing. I have seen no response that they even acknowledge the fact that they’ve heard our findings. A simple acknowledgment that they are aware of what we are experiencing and that they’re working on it would be sufficient. But I don’t even see that.
I’m still struggling to understand what you mean by this. Without a link to a source or reference, it’s difficult to ascertain what you’re referring to. For whatever it’s worth, the announcement topic for the latest Wi-Fi Chime production firmware release from 20 August 2025 is still open. It’s one that I linked above in a previous post, and it’s my understanding that topics created by Wyze in categories like Wyze News tend to remain open indefinitely, unlike most user-created topics, which are set to automatically close after 90 days of no activity.
Also, I’m not sure that this particular discussion is relevant to the subject of this topic, which @mparegian created to describe a problem with Wi-Fi Chime (which you also seem to be experiencing). I haven’t yet seen definitive evidence that the latest production firmware release is the root of the problem with Wi-Fi Chime’s behavior of playing the default sound when triggered by some cameras, though, as I noted above, I’ve asked other volunteers to try to replicate this. Bear in mind that this is all happening on a holiday weekend.
when I made my first comment it showed this topic as closed resolved, now it’s showing that ITS will close in three months. This chat room is absolutely insane. I replied to a comment which stated that the topic was resolved. Now it’s rollback looking forward to do a screenshot for you, and it’s not there. I don’t know what to say
No, it was marked as “solved”, as I explained previously:
It has never been closed to this point, as far as I know.