Problem w/ assist_satellite.start_conversation & VoIP Phone. Call must connect twice.

[dreamy fjord]

I have a VOIP phone integrated into Home Assistant. When I manually pick up the receiver, it auto-dials my HA instance at 192.168.1.107, and I can talk to the Assist Satellite just fine. Everything works as expected.

The problem occurs when I try to trigger a conversation through automation using assist_satellite.start_conversation. The phone rings like it should, but when I pick up, I just get silence. No message is played.

If I hang up and manually pick up the receiver again (which triggers the auto-dial), I can then hear the message or interact with the assistant.

It seems like the assistant isn’t initializing properly or isn’t ready to speak when the call is initiated from automation.

Anyone run into something similar or have tips on how to ensure the assistant is fully ready to deliver audio once the call is answered?

[warped ore]

I had to add this before triggering the phone answer to make it work reliably.

I also have a 2 second delay after calling this before triggering the conversation.

[dreamy fjord]

Interesting, I’ll give it a try! Thanks for the pointer :)

[dreamy fjord]

Resolved my issue perfectly! Really appreciated!

Such a weird issue. Any idea why this is happening?

[warped ore]

No. I only figured out how to solve he issue because the Network Chuck video described a similar issue. I guessed that the cause might be the same.

@dreamy fjord

[hollow jasper]

Could be related to this? https://github.com/home-assistant/core/pull/150490

[dreamy fjord]

Ahh understood, good catch then!
Sorry for the late reply :)

[dreamy fjord]

Very well looks like it may be, no? @warped ore