visitor cannot hear voice from doorbell

Is anyone have a problem with the microphone on their E340 doorbell?

I can hear the person just fine but no matter what the person that’s at the doorbell cannot hear me

I contacted support and all the settings were correct a microphone was enabled informations and the microphone volume was all the way up

Support was unwilling to replace the doorbell so if it can’t be made to work then I’ll have to return it to Amazon for a refund.

I would like to get it to work because the video quality is outstanding

1 Like

You’re not alone — I’ve been troubleshooting this exact issue on an E340 with a HomeBase S380, and after extensive testing, I’m confident it’s not user error or basic network quality.
My symptoms are identical: I can hear visitors perfectly, but my voice comes through broken, clipped, or only partially — sometimes only ~20–30% of what I say.
What I’ve already ruled out:

  • Multiple phones and tablets (same behavior)
  • Wi-Fi vs cellular on the phone (same behavior)
  • Different APs and signal strengths
  • VLAN misconfiguration (camera + HomeBase on same VLAN)
  • Power saving features (UAPSD off)
  • IDS/IPS / firewall inspection disabled for IoT
  • UPnP enabled
  • HomeBase rebooted after every change
  • Tested the doorbell both with and without the HomeBase
    Result:
  • Removing the HomeBase slightly improves audio, but does not fix it
  • That strongly suggests the issue is **Eufy’s upstream two-way audio pipeline (codec + cloud relay), not Wi-Fi, microphone settings, or local network quality

What makes this clearer is that:

  • Recordings sound fine
  • Incoming audio sounds fine
  • Only live upstream talk is unreliable

That points to a limitation in how Eufy handles real-time audio (small UDP packets, minimal jitter buffering). The network can be perfectly stable and still expose this issue.

At this point, it appears to be a firmware / cloud-side limitation affecting the E340, not something end users can fully fix with settings. Hopefully, Eufy addresses this in a future update, because replacing hardware doesn’t seem to resolve it.