core icon indicating copy to clipboard operation
core copied to clipboard

Assist Satellite Announce

Open ChiliJohn opened this issue 10 months ago • 6 comments

The problem

I have noticed that when using the assist_satellite.announce function in Home Assistant with a Grandstream HT801 and an analog phone, an error occurs if the call is not answered within 30 seconds.

This results in scripts and automations failing with the error message:

"User did not pick up in time"

I have not found a way to change the 30-second timeout or even get a simple response indicating that the call was not answered without it causing an error in Home Assistant.

What version of Home Assistant Core has the issue?

core-2025.2.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet


Anything in the logs that might be useful for us?

Logger: homeassistant.helpers.script.websocket_api_script
Kilde: helpers/script.py:526
Første forekomst: 13.50.14 (1 forekomster)
Senest logget: 13.50.14

websocket_api script: Error executing script. Unexpected error for call_service at pos 1: User did not pick up in time
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 526, in _async_step
    await getattr(self, handler)()
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 762, in _async_call_service_step
    response_data = await self._async_run_long_action(
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<9 lines>...
    )
    ^
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 727, in _async_run_long_action
    return await long_task
           ^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2794, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2837, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1007, in entity_service_call
    single_response = await _handle_entity_call(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
        hass, entity, func, data, call.context
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1079, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/assist_satellite/entity.py", line 209, in async_internal_announce
    await self.async_announce(announcement)
  File "/usr/src/homeassistant/homeassistant/components/voip/assist_satellite.py", line 179, in async_announce
    await self._do_announce(announcement, run_pipeline_after=False)
  File "/usr/src/homeassistant/homeassistant/components/voip/assist_satellite.py", line 236, in _do_announce
    await self._announcement_future
TimeoutError: User did not pick up in time

Additional information

No response

ChiliJohn avatar Feb 11 '25 13:02 ChiliJohn

https://github.com/home-assistant/core/blob/31ea2e1714d8bed10b372728de9537bf56edf6b0/homeassistant/components/voip/assist_satellite.py#L268

And

https://github.com/home-assistant/core/blob/31ea2e1714d8bed10b372728de9537bf56edf6b0/homeassistant/components/voip/assist_satellite.py#L54

Would be the two areas to look at changing/allowing to be configured.

CloCkWeRX avatar Feb 11 '25 13:02 CloCkWeRX

Many many thanks, found a workaround to solve the problem

Edit assist_satellite.py and set timeout to desired (eg 600). Save and restart HA (VOIP breaks now). Go to Devices & Integrations → Remove VOIP. Restart HA Install VOIP again.

Now the new timeout works...

It is a mistake that HA gives an error at timeout, I'm sure it will be looked into. A good idea could also be to make the timeout function available in the UI

My reason for the long timeout is that I want to use the old analogue phone as an alarm clock, and there it is not certain that I will be able to answer within the 30 seconds ;-)

Thanks again for the help

ChiliJohn avatar Feb 11 '25 17:02 ChiliJohn

Hey there @balloob, @synesthesiam, mind taking a look at this issue as it has been labeled with an integration (voip) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of voip can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign voip Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


voip documentation voip source (message by IssueLinks)

home-assistant[bot] avatar Feb 11 '25 23:02 home-assistant[bot]

Might be useful to have a way to configure the timeout in the integration per phone. Additionally an option to play an announcement only once and have it hang up from homeassistant automatically would a big improvement. That would also allow a phone configured to accept automatically to play announcements without interactions.

Ultrawipf avatar Feb 16 '25 10:02 Ultrawipf

I hope you will look into this error, every time HA is updated to 2025.x.x you must manually enter the config file and correct the timeout so that the script and automations do not crash... ;-)

ChiliJohn avatar Feb 27 '25 21:02 ChiliJohn

I've found that if I don't set a response with SetResponseOfConversationTo '', in my automations, it will work just fine. It seems the VOIP integration needs a response from Home Assistant before it closes that conversation.

Code-Spinner1 avatar May 12 '25 01:05 Code-Spinner1

So I upgraded to the latest dev build and after the first call from HA, TTS is played it does not hang up, and then when I hang up in the dev console I see the action complete (the green checkmark shows when I hang up) then when I press perform action again, I get a call, I answer no audio, nothing and instantly it shows the action complete.

Another thing,

If I send a announcement I receice thr call but no announcement, i hang up, call home assistant and it plays back the announcement and then silence.

And if I am on the call, and press perform action, it plays the message again but gives an sattelite. Announce unknown error instantly.

Edit 2.

  1. call home assistant from phone. (Ha answers and makes tone)
  2. press announcement tts perform button in dev console
  3. 2nd call incoming and until you answer the active call (which you originated in step 1) plays the TTS in a loop.
  4. answer the call, no audio is played, hang up the call.
  5. call originated in step 1 is still active and is playing TTS in an indefinite loop (I got bored and hang up after about 1.5 minutes)

Th3Specialist avatar Jun 10 '25 01:06 Th3Specialist

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Not fixed at all

Th3Specialist avatar Sep 15 '25 02:09 Th3Specialist