🔔 ESPHome Full-Duplex Audio Intercom - Because I Was Bored on Vacation

[meconiotech (n-IA-hane)]

Project Update: ESPHome Intercom Has Evolved Into A Complete VoIP Stack

Hi everyone!

A quick update for anyone following this older ESPHome Intercom thread.

The project has evolved considerably and is no longer based on the original custom intercom transport.

It is now a complete local SIP/SDP/RTP VoIP stack for Home Assistant and ESPHome.

Home Assistant can now act as:

• a real SIP softphone;
• a local SIP registrar;
• a SIP call router and B2BUA;
• an RTP bridge and audio resampler;
• a central phonebook and dial plan;
• an optional SIP trunk endpoint;
• a telephone gateway to Home Assistant Assist.

ESPHome devices are now real SIP endpoints and can:

• call Home Assistant;
• receive calls from Home Assistant;
• call other ESP devices;
• call registered clients such as Zoiper or Linphone;
• participate in ring groups and conference rooms;
• call external mobile or landline numbers through an optional trunk;
• coexist with Voice Assistant, Micro Wake Word, TTS, media playback, Sendspin and AEC/AFE audio processing.

Home Assistant Assist Can Now Be Called By Phone

A Home Assistant Assist pipeline can be exposed as a normal destination in the shared VoIP phonebook.

It can be called:

• from an ESPHome VoIP device;
• from Home Assistant’s softphone;
• from a registered SIP client;
• by name or numeric extension;
• from an external telephone through an optional SIP trunk.

The assistant receives the caller identity, can greet the caller first and then continues with a normal multi-turn spoken conversation using the selected native Home
Assistant STT, conversation and TTS pipeline.

https://raw.githubusercontent.com/n-IA-hane/esphome-intercom/v2026.7.1/docs/images/call-from-esp-to-homeassistant.gif(image larger than 3 MB)

Ring Groups, Conferences And A Shared Dial Plan

The current stack includes:

• extensions for HA, ESP devices and registered SIP phones;
• shared phonebook-driven routing;
• simultaneous ring groups where the first endpoint to answer wins;
• Home Assistant-hosted SIP conference rooms;
• DND and Auto Answer;
• optional external SIP trunk routing;
• standard DTMF extension selection;
• experimental in-call DTMF events for Home Assistant automations.

The Lovelace card can operate as:

• the Home Assistant softphone;
• an ESP phone mirror and controller;
• a manual keypad;
• a shared phonebook view.

The maintained Waveshare P4 Touch profile also includes an on-device Contacts/Keyboard telephone interface.

The Full-Duplex Audio Work Continues

The original full-duplex ESPHome audio goal is still an important part of the project.

The reusable audio stack now provides:

• official ESP-IDF I²S ownership;
• codec-backed and codec-free audio paths;
• lightweight AEC and full Espressif AFE profiles;
• single-microphone and dual-microphone processing;
• speaker-reference echo cancellation;
• Voice Assistant barge-in;
• shared media, TTS and VoIP playback;
• real-time audio paths without arbitrary loop delays.

Follow The New VoIP Stack Thread

This older thread remains useful as project history, but future announcements, release information, new features and VoIP-specific discussion will be published in
the new thread:

https://community.home-assistant.io/t/voip-stack-for-home-assistant-and-esphome/

Main repository:

GitHub - n-IA-hane/esphome-intercom: VoIP Stack for ESPHome and Home Assistant - local SIP phones, HA softphone/router, phonebook, softphone accounts and optional trunk calls · GitHub

Current stable release:

Release 2026.7.1: Assist By Phone, Groups And A Stronger VoIP Stack · n-IA-hane/esphome-intercom · GitHub

If you were using one of the older Intercom Native versions, please refer to the current documentation and maintained YAML profiles before upgrading: the project has
migrated from its original custom call transport to standards-based SIP/SDP/RTP.

What started as an ESPHome full-duplex intercom is now a local telephone system built around Home Assistant.

[IOT7712]

I lazily watched the friends neighbours kids set up a similar thing yesterday, between their cubby houses adjacent to the fence, high up in the old gum trees. Australia in the summer - I love to visit my mate near the beach, kookaburras and magpies singing, BBQ sizzling, doing the occasional Aussie salute, the beach flies being less friendly than the ones out bush in the paddocks in the channel country up north.

Two tin cans and a piece of string.

Right next to their refrigerated Eskies hanging on the end of a few joined power extension cables snaking out of the open kitchen window, covered with flyscreen and a broken gum branch to swat the flies off their lemonade and jelly. They still have their flashing LED lights going, entwined around the huge trunk and branches, a leftover from Christmas day, and probably going to be left on till they go back to school in a month’s time. In their cozzies, squirting each other with heavy duty water cannons over the fence, as the garden hose was banned, no waterproofing on the extension cable joints and nobody wanting to do first aid without a AED machine close by. They take helf-n-safty real seriously too mate!

Two way communication. Simultaneous if needed. Visual too. Extremely low power. Adjustable volume. Natural intelligence - took all of two seconds to ask their dad for his used beer cans (they didn’t need to ask him to scoff the second - he had already downed a few) and a piece of fishing line they had to untangle. No echo. Full duplex. Standby backup - their cell phones and Instagram. Auto hangup too - just put it down. Absolutely no Chinese components. Multiprotocol support - supports Pig Latin and sign language too. Privacy too - they whisper.

It got an update overnight, their mum (note the Aussie spelling) suggesting they use string instead of fishing line, the audio characteristics being superior.

Downtime to upgrade was was about five minutes, as they had to find scissors to cut the fishing line knot to remove it before installing the string and tying two knots.

With the social media ban downunder, children are forced to actually TALK to each other. Face-to-face. Shock, horror! A novelty.

An emerging trend? Cutting edge? No changes to the Matter standard required. My neighbours’ grandma swears they used the very same technology when the cubby house was HERS half a century ago!

Thinking aloud whether should add an extension to make it three way for the cubby house on the other side. Do we do point to point, duplicating the setup to the other tree? Three lots of string and six cans? Do we join it in the middle for a party line and only three cans? My mate offers to drink the extra beers. Where to tie the knot for optimum audio response, string tightness, etc? My mate is giggling, a little pickled, suggesting we ask AI. With earnest seriousness only a few beers can bring on.

Should we, or just experiment?

We’re not posting on on GitHub. The kids in the yard on the other side have hanged their elbows over the fence, bored, also curious. Can they do the same thing? Can they climb the fence and check it out themselves? Their dad offers to drink a beer, for scientific research purposes of course, so they can have another node. My mate obliges, carrfully tossing it overhand over the fence with accuracy only an experienced beach and backyard cricketer can master.

I’m asking grandma if she has any old windup telephones in the old shed, and if my mate has a spare 48v power supply and a lot of two core wire. We might be onto something here…

I know, it’s the hot sun and pineapple juice talking… The kids are laughing, conjuring up some scheme, asking if we can go to the movies tomorrow after the sun on the beach gets too hot, already bored.

Life is good!

[heinz86]

@meconiotech this is absolutely awesome. I think, there are multiple people waiting for this for implementing an in-house communication system, a doorbell or a baby phone.

Can you please create a Pull Request for esphome to upstream your intercom component?

[TokarevSergey]

Good morning. This is a really great project. Could you please tell me how the connection will work if there are multiple users? For example, someone stands at the door and calls Mayach v3, and there are two or three users in HomeAssistant, and they all receive a call notification at the same time. Will they all be able to hear the person who just arrived, and will they all be able to talk to the person who just arrived? Thank you.

[stevemann (Stephen Mann (YAML-challenged))]

@meconiotech

Xiaozhi Ball V3

Link? It doesn’t show on a search.

[meconiotech (n-IA-hane)]

@TokarevSergey

Good morning. This is a really great project. Could you please tell me how the connection will work if there are multiple users? For example, someone stands at the door and calls Mayach v3, and there are two or three users in HomeAssistant, and they all receive a call notification at the same time. Will they all be able to hear the person who just arrived, and will they all be able to talk to the person who just arrived? Thank you.

Hi, there are still a lot of things that need to be tested. I’m testing from a PC and Android app, and everyone who connects seems to be able to talk to the other person. The component itself creates a driver for using the microphone and speaker together. You can then manage the call logic yourself via the esphome yaml or through home assistant automations. I’ll be doing some testing soon to see if I can implement something for multicast. Take a look at my git. I’ve also published two example yamls that I use daily. You can use them as a starting point for your own tests. And please, if you find anything that doesn’t work or that you’d like to see improved, please let me know.

[meconiotech (n-IA-hane)]

Hi you can find it on AliExpress

[stevemann (Stephen Mann (YAML-challenged))]

Just the link, please. “This image could not be loaded”.

[meconiotech (n-IA-hane)]

https://a.aliexpress.com/_ExTLgrm

[TokarevSergey]

Could you please tell me? Is it possible to use both HomeAssistant and P2P simultaneously? So that if the HA server is down for some reason, I can still receive a call?

[meconiotech (n-IA-hane)]

Hi! Yes, it’s absolutely possible.
The component itself is just a bidirectional audio bridge - it opens a stream to whatever destination you configure. The actual behavior and logic are entirely up to you through automations.
By default, you set a static IP/port, but since remote_ip and remote_port accept templates, you can dynamically switch between HA and P2P targets based on any condition you want.
For example, you could create an automation that:
Tries to reach HA first
If HA is unavailable (timeout or no response), switches remote_ip to another ESP device
Starts the stream
The component doesn’t care where the audio goes - it just streams to whatever IP:port you tell it to. So yes, you can build a fallback system where P2P kicks in when HA is down.

[heinz86]

@meconiotech It feels a bit like your great feature in the GitHub discussion does not get the appropriate attention from the Esphome maintainers. Would be great to get their feedback to understand the best way to integrate full-duplex audio in Esphome.
Maybe it gets more attention if you create an additional Pull Request?

[meconiotech (n-IA-hane)]

Quick update:
In the last days I’ve been doing a full refactor of the component.
It has now evolved into a pseudo phone-like system, with:

• Static contacts
• Dynamically auto-discovered contacts via mDNS
• The ability to scroll through contacts and call a selected peer

At the moment I’m finishing testing and cleaning things up.
Stay tuned, because soon I’ll publish a proper release with all the involved components and documentation.

The refactor also focuses on maximizing reuse of existing ESPHome components, keeping the system modular and maintainable.
Depending on the hardware, the audio path automatically adapts to dual-bus or single-bus I2S setups, transparently enabling full-duplex operation without requiring additional user configuration.

From a functional point of view, the system now supports two distinct call flows:

• Calling Home Assistant
  When an ESP calls Home Assistant, it behaves like a classic intercom:
  • An event is generated in Home Assistant
  • HA can handle user notifications
  • The user can answer the call and establish two-way audio with the device
  • HA can also arbitrarily open audio streams toward devices (useful for remote two-way communication with a room, ambient audio monitoring, or announcements)
• ESP ↔ ESP calls
  Calls between ESP devices behave like internal calls in a phone system:
  • The caller initiates a call to the selected peer
  • If the receiver does not have auto-answer enabled, it enters a ringing state and can be answered manually
  • If the receiver is in auto-answer mode, the full-duplex communication is established automatically

Home Assistant is entirely optional and not part of the core architecture:
discovery, signaling, and audio streaming all work ESP-to-ESP without HA in the loop.

TODO / future exploration:

• Experiment with multicast audio
• One-to-many calls (e.g. announcements to multiple ESPs at once), similar to store or public-address systems

[TokarevSergey]

Good afternoon. I don’t understand why my post was banned.

[meconiotech (n-IA-hane)]

I dont know, it wasn’t me

[TokarevSergey]

Please add information about which pins it connects to. GPIO was previously missing, but now it’s gone. Thank you.

[TokarevSergey]

You used to have a great description. It was clear where everything was connected. Please bring it back. And as far as I understand, you redesigned everything for a different microphone. Can I use the old one you had, or should I order a new one? Thank you.

[meconiotech (n-IA-hane)]

Yes, the documentation is currently outdated due to a major refactor.

The pinout and hardware section will be restored to avoid further confusion.

Regarding the microphone: the INMP441 is still supported.
In general, any standard I2S microphone should work, as the audio path is generic and not bound to a specific microphone model.

[TokarevSergey]

Can you please tell me if I can run the EPROM device on an esp32-s3 (wroom-1) with any GPIO? Thank you.

[hansons83 (Jakub)]

@meconiotech Hi. I’m playing a bit with your components, great work with that. I have one question, i’m using ring buffer speaker reference and i have good echo cancelation results when aec filter lenght is 8, this adds to much load in my project. If i understand correctly there is a need to buffer speaker samples to be aligned with mic data, but it looks like there is some kind requirement for filter length to. This is not correct in my opinion.
Br
Jakub