Open Tyne-Bridges opened 1 week ago
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!
(message by CodeOwnersMention)
voip documentation voip source (message by IssueLinks)
Also encountered this issue and had to downgrade to 2024.9.3
Same for me.
The phone does seem to listen, and commands are executed, but no beeps/feedback.
After a restart of home-assistant it will work once, subsequent calls don't work anymore.
I got the following related entries:
Logger: homeassistant.components.voip.assist_satellite
Bron: components/voip/assist_satellite.py:242
integratie: Voice over IP (documentatie, problemen)
Eerst voorgekomen: 13 oktober 2024 om 22:02:46 (4 gebeurtenissen)
Laatst gelogd: 15:55:00
PipelineEvent(type=<PipelineEventType.ERROR: 'error'>, data={'code': 'stt-no-text-recognized', 'message': 'No text recognized'}, timestamp='2024-10-13T20:02:46.801795+00:00')
PipelineEvent(type=<PipelineEventType.ERROR: 'error'>, data={'code': 'stt-no-text-recognized', 'message': 'No text recognized'}, timestamp='2024-10-13T20:02:52.555435+00:00')
PipelineEvent(type=<PipelineEventType.ERROR: 'error'>, data={'code': 'stt-no-text-recognized', 'message': 'No text recognized'}, timestamp='2024-10-13T20:04:09.823681+00:00')
PipelineEvent(type=<PipelineEventType.ERROR: 'error'>, data={'code': 'stt-no-text-recognized', 'message': 'No text recognized'}, timestamp='2024-10-14T13:55:00.110173+00:00')\
\
Logger: homeassistant
Bron: /usr/src/homeassistant/homeassistant/runner.py:147
Eerst voorgekomen: 07:15:00 (2 gebeurtenissen)
Laatst gelogd: 14:23:18
Error doing job: Exception in callback None() (None)
Traceback (most recent call last):
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/local/lib/python3.12/asyncio/selector_events.py", line 1238, in _read_ready
self._protocol.datagram_received(data, addr)
File "/usr/local/lib/python3.12/site-packages/voip_utils/voip.py", line 193, in datagram_received
raise err
File "/usr/local/lib/python3.12/site-packages/voip_utils/voip.py", line 183, in datagram_received
audio_bytes = self._rtp_input.process_packet(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/voip_utils/rtp_audio.py", line 61, in process_packet
raise RtpError(
voip_utils.error.RtpError: Expected payload type 107, got 101
The problem
I’ve been using VOIP to speak to my Home Assistant via a Grandstream Handytone HT801 box and a cordless phone, as on the page World's most private voice assistant - Home Assistant.
This worked fine up to and including 2024.9.3. I’ve now found that installing 2024.10.1 or 10.2 breaks it, even if I don’t apply the repair which is recommended because _binary_sensor.192_xx_xx_xx_call_inprogress is now deprecated. The message about this says the call will work until 2025.4.
After updating to any Home Assistant version from 2024.10.1 I hear the two tone notification (to indicate “call in progress”?) when I press the phone button. However, speaking into the phone doesn’t then give any response - the tone just repeats every few seconds until I hang up. The only way I’ve found to fix the problem is to revert to my backup of 2024.9.3, which means I’m effectively stuck on that version.
I would have included a log extract for VOIP here but can’t find a log.
I’m running HAOS on an Intel NUC and have reverted back to Core 2024.9.3, Supervisor 2024.10.0, Operating System 13.1, Frontend 20240909.1.
Any idea what's going wrong? Thanks.
What version of Home Assistant Core has the issue?
2024.10.2
What was the last working version of Home Assistant Core?
2024.9.3
What type of installation are you running?
Home Assistant OS
Integration causing the issue
VOIP
Link to integration documentation on our website
https://www.home-assistant.io/voice_control/worlds-most-private-voice-assistant
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response