Device: Eufy C30 Wireless Video Doorbell (Black)
Issue: Alexa routine is no longer triggered when doorbell is pressed
Hi Eufy Community,
Since June 19, 2025, my Eufy C30 doorbell has stopped triggering my Alexa routine when someone presses the doorbell. This function used to work perfectly before.
Here are the facts:
Doorbell still records events and sends push notifications to the Eufy app (working normally)
Doorbell is visible in the Alexa app, and live view works
Routine is configured: Doorbell‑2 is pressed → play sound on Echo Dot
However, Alexa never triggers the routine (no activity logged)
Troubleshooting already done:
Disabled/re‑enabled EufySecurity Alexa Skill multiple times
Removed and re‑added the doorbell in both Eufy and Alexa apps
Recreated Alexa routines from scratch
Restarted both the doorbell and Echo Dot
Checked Wi-Fi (2.4GHz, strong signal)
I’ve also opened a support ticket with logs and screenshots but want to check here:
Is anyone else facing the same issue since mid‑June 2025?
Has anyone received a fix from Eufy or Alexa?
Can Eufy engineers review the cloud logs beginning before June 18, 2025, when it was last working?
I appreciate any help or confirmation from the community and Eufy engineers.
I’m having the exact same issue and have went through the same trouble shooting steps as you. My hub (where I plug the micro SD card) still rings, but that’s hidden away and I relied on the echo devices for notifications.
I have the E340 wireless doorbell, and relied on the built-in Alexa “announce” feature rather than a routine, but mine has also stopped working in roughly the same timescale. (I say roughly, because I noticed it a couple of weeks ago, but didn’t note the date and have only just had time to try and troubleshoot.)
Copying the format of your info
Doorbell still records events and sends push notifications to the Eufy app (working normally).
Doorbell is visible in the Alexa app, and live view works.
Announcements are enabled in the Alexa app, and both an Echo Dot and Echo Pop are configured for announcements.
However, Alexa never announces when the doorbell is pressed.
Removed and re‑added the doorbell in both Eufy and Alexa apps.
Factory reset and re-added the doorbell to both Eufy and Alexa apps.
Restarted both the doorbell and Echo Dot.
Checked Wi-Fi (2.4GHz, doorbell is <10’ from wireless router).
Rebooted router, ensured that doorbell has a DHCP reservation and is not affected by any filtering rules on the router.
I haven’t opened a support ticket yet, but am just about to.
It’s frustrating, as I bought the Echo Pop instead of a Minibase Chime due to the Alexa integration. There’s always been a few seconds lag with Alexa, but it worked fine for 4-5 months, and then just suddenly stopped.
I also have the e340 doorbell cam and it has stopped triggering any of our household Alexa’s in the last couple of weeks. We also have missed deliveries due to this. Tried all the usual resets and even fresh install from scratch…still nothing. Ive had enough of eufy to be honest. I moved from a ring cam to avoid the subscription, but the delay on the eufy to the Echos has always been terrible. The Ring was immediate, and reliable. There have been times when\if the Eufy actually triggered on the Echo’s that the person had already left before the notification came through. I have just ordered a Tapo D235 now to try that out. Should arrive today. Even though Ive been enduring with the Eufy since late last year, I think I’ll see if Costco will take it back, as it’s not fit for purpose.
Exactly the same issue here, not exactly sure when my E340 stopped triggering Alexa announcements but within the last week or two.
I’ve done all the steps as per the original post as well. We had this nonsense a year or so ago, gutted to be back to this as it basically means I have no doorbell other than a notification from
the eufy app on my phone (which I don’t always have under my nose to catch it)
Come on Eufy this is useless! Support ticket done too.
I don’t know whether to be relieved or depressed that other people are having the same issue…
I’ve been swapping emails with what is presumably an AI on their tech support address. And I’ve been on with Alexa support as well. The Eufy support email asked me to remove the Alexa Skill and re-add it, re-entering credentials, but for some reason Alexa had cached the credentials and I had to contact Amazon to be able to re-enter them. (Even though live feed was working, so I assumed the credentials are correct, it’s still necessary to perform the steps tech support ask me to carry out.)
To be honest, even the app notifications are slow to arrive, but that’s probably expected, since I assume it’s using cloud service to push the notifications. It also takes a long time to open live view on the app in response to a doorbell press event, which means people have sometimes gone by the time the app shows me the live feed.
The doorbell is less than 6 months old, so under UK consumer law I think I should be entitled to a refund if tech support can’t help, but obviously I’d rather keep it. I liked the extra camera to monitor left parcels. And obviously being able to use Echo speakers as extra “chimes” was a selling point.
Yeah I gave up. Eufy support just seem to be following a tree chart for every call. I have fixed the issue tho. Just installed the new Tapo D235 doorbell. Amazing. I now press it and within a second, all my echo’s chirp up that someone is at the front door. It also alerts me when the cats are at the front door individually. Why Eufy can’t sort out their software is beyond me.
the Tapo gets half our doorstep in. But I only have it mounted on the side wedge. It also comes with a downward wedge which if I fitted it, I’m assuming it would cover the whole doorstep. It is much more fisheye than the Eufy so covers a wide area. Ours is mounted on the frame of the door, and with the wedge, the actual door is also partly in view. So it’s not got the designated parcel cams, but depending how you mount it, it could definitely cover your full doorstep
Having the issue do getting motion notifications on Alexa dot but no ring notification tried all suggestions but no luck! Only bought it for door bel chime! Whole system useless if i cant hear it ringing! Any one got a contact no for them?
I’m in exactly the same position, stopped announcing a few days ago. I actually contacted Eufy who just suggested all the steps you’ve listed. None of them worked of course.
I suspect it’s an issue on Eufy’s end since the doorbell had been working fine for months and notifying via my Alexa the whole time.
Eufy claims that my the device is not currently bound in their system.
With no resolution offered, they only concluded it may be a device issue and offered me a 70% discount coupon for a replacement purchase.
They did not confirm any software or cloud issue, despite the device working in every other way.
Key Questions
If multiple users on the forum are experiencing similar issues, could this be a problem with Eufy’s Alexa Skill or backend service, not the device itself?
Why is my device reported as “not bound” when it clearly functions, shows up in the app, and is still connected to Alexa live view?
Question about Tapo D235 Doorbell – What Exactly Happens on Echo Dot When Pressed?
Hi everyone,
I’m thinking of switching from my Eufy C30 (which recently stopped triggering Alexa routines) to the Tapo D235, and I need some clarification from current users.
When someone presses the Tapo D235 doorbell, what exactly happens on the Echo Dot?
Does the Echo Dot play a chime sound (like a real doorbell)?
Or does it only announce “Someone is at the front door” as a voice notification?
Also, can Tapo D235 be used to trigger an Alexa routine, similar to how Eufy used to work before?
I’d appreciate any confirmation from those who’ve tested this. Thanks!
I’ve also been asked to send in my device logs — not once, but 2–3 times. I uploaded them immediately after support requested, so they were definitely fresh and within the 24-hour window. However, later they told me the logs had “expired” because they were more than 3 days old… which only happened because their technical team didn’t review them on time.
After going back few times, their final response was that it might be a device quality issue and offered me a discount voucher to buy a new one.
When I checked the Alexa skill reviews for Eufy Security, there are many of 1-star ratings recently — all saying the Alexa integration is broken. So honestly, I believe this is more of a Skill/backend issue, not a device hardware problem.
In the end, I decided to buy the Tapo D235 instead — hopefully it works better. I used the Eufy voucher they gave to buy something else, because I no longer trust their doorbell products.
Weirdly, I could swear I heard Alexa announce the doorbell earlier today, but I was in a different part of the house, so it was faint.
This was at around the same time as I received an email from support advising me that my doorbell was not bound to my account properly, and asking me to delete it from the app and re-add it. This is despite having mentioned that I’d done this several times already.
I’ll re-test the doorbell shortly, at the moment I’d wake an elderly relative from much needed sleep. (Looking after that relative is also why I wanted the doorbell in the first place.) I’ll test before deleting the device from the app, and will update here if it seems to be working.
All this makes me wonder if they have fixed something in the back-end, but perhaps that’s just wishful thinking.
Update: Yep, it’s started working again. Announcements and routines both worked okay, without me deleting it from the app and re-adding. However I decided to trust them (!) that the device wasn’t bound to my account properly, so deleted the doorbell from the app, re-added it, and everything still works. I just wonder whether it will go wrong again at some point, and it was out of action for a couple of weeks, which was pretty problematic when caring for an elderly person.
Plus there are other problems with the speed of opening the live feed in the app, but for now at least Alexa is working again.
Curious to know if it has started working for anyone else? Since it started working on its own, before I tried the provided steps, I suspect if they might have either fixed something on my account or updated the back-end code. Or perhaps it’s just magic…
