You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Need help testing Automation as dialplan: share your working automations
#123
We could use your help testing Automation as dialplan, and building a collection of useful call automations together.
The idea is simple: define what happens to a call in Home Assistant's normal automation editor. Play a greeting, wait, forward to a phone or Assist, choose a destination by time or presence, or let the caller press a key. The native VoIP trigger selects the call automatically, so ordinary examples do not need Call-ID templates or blueprint imports.
The phonebook remains the default dialplan. Automations add the behavior you choose; existing event and state automations remain available.
Get the preview and follow the guide
Install or redownload 2026.9.3-dev through HACS, enabling prerelease versions if necessary. Redownload even if that version is already installed, because the preview package has been updated.
Restart Home Assistant and refresh the frontend. In the Companion app, use Reset frontend cache. In Chrome/Edge, open F12, right-click the reload button and choose Empty cache and hard reload if old controls remain.
This is a development preview. 2026.9.2 remains the stable release, and this HA integration update does not require new ESP firmware.
A small example to get started
In VoIP Stack, choose Add contact > Automation, name the contact Welcome, and optionally give it an unused extension. Then create this ordinary automation. Replace tts.piper with your own TTS entity, and 1666 with your configured assistant's name or extension.
alias: Welcome greeting then assistantmode: paralleltriggers:
- trigger: voip_stack.call_receivedoptions:
destination: Welcomeactions:
- action: voip_stack.tts_saydata:
tts_entity_id: tts.pipermessage: "Welcome. I will connect you to the assistant now."
- action: voip_stack.forwarddata:
destination: "1666"
Call Welcome to test it. The greeting runs before the forward and the caller stays on the same call. Remove the forward for an information line that speaks and ends the call, or insert HA's Delay action between the steps to wait before connecting.
What would be useful to test?
Is the complete greeting audible, including its first and last words? After forwarding, can both sides hear each other?
Do keypad menus choose the correct destination? Are repeated digits received separately?
Do no-answer, presence and time rules choose the expected route, while ordinary phonebook calls still work?
What happens if the caller hangs up during a greeting, delay or keypad wait? Can you immediately call again?
Do your existing automations still behave correctly?
For a browser-to-browser test, keep both cards loaded in running browser tabs or devices. Auto-answer needs the receiving card and microphone permission. Opening a previously unloaded receiving card can be the moment it answers the waiting call.
We are testing real calls and audio as well as the automated checks, but we are not claiming that every installation and combination has been validated. Different TTS providers, conversation agents and SIP phones make your feedback valuable.
Share an automation that others can use
If you build something working and useful, please paste it here in a YAML code block and include:
What it does, in plain language.
What needs to exist first: contacts, groups, TTS provider or other HA entities.
The full automation, with example names in place of personal details and no passwords or tokens.
Which devices and Home Assistant/VoIP Stack versions you tested, and any limitations you found.
Ideas include opening-hours information, a visitor menu, a quiet-hours ring group, a greeting before Assist, or a notification showing received keypad digits. For gate or lock examples, first test the key and sender filters with a notification action.
If something fails, describe the call direction and expected result, mention the TTS provider or SIP client involved, and share the relevant automation trace with private details removed. Working recipes and reproducible problems are both welcome. Thank you for helping make this useful in everyday installations.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
We could use your help testing Automation as dialplan, and building a collection of useful call automations together.
The idea is simple: define what happens to a call in Home Assistant's normal automation editor. Play a greeting, wait, forward to a phone or Assist, choose a destination by time or presence, or let the caller press a key. The native VoIP trigger selects the call automatically, so ordinary examples do not need Call-ID templates or blueprint imports.
The phonebook remains the default dialplan. Automations add the behavior you choose; existing event and state automations remain available.
Get the preview and follow the guide
This is a development preview. 2026.9.2 remains the stable release, and this HA integration update does not require new ESP firmware.
A small example to get started
In VoIP Stack, choose Add contact > Automation, name the contact Welcome, and optionally give it an unused extension. Then create this ordinary automation. Replace
tts.piperwith your own TTS entity, and1666with your configured assistant's name or extension.Call Welcome to test it. The greeting runs before the forward and the caller stays on the same call. Remove the forward for an information line that speaks and ends the call, or insert HA's Delay action between the steps to wait before connecting.
What would be useful to test?
For a browser-to-browser test, keep both cards loaded in running browser tabs or devices. Auto-answer needs the receiving card and microphone permission. Opening a previously unloaded receiving card can be the moment it answers the waiting call.
We are testing real calls and audio as well as the automated checks, but we are not claiming that every installation and combination has been validated. Different TTS providers, conversation agents and SIP phones make your feedback valuable.
Share an automation that others can use
If you build something working and useful, please paste it here in a YAML code block and include:
Ideas include opening-hours information, a visitor menu, a quiet-hours ring group, a greeting before Assist, or a notification showing received keypad digits. For gate or lock examples, first test the key and sender filters with a notification action.
If something fails, describe the call direction and expected result, mention the TTS provider or SIP client involved, and share the relevant automation trace with private details removed. Working recipes and reproducible problems are both welcome. Thank you for helping make this useful in everyday installations.
All reactions