Using Voice/Assist causes the websocket to get overloaded leading to HAOS stability issues #92307

Anto79-ops · 2023-04-30T20:05:41Z

The problem

Hi,

Running HAOS (2023.5.0b4) on RPi4 4Gb on 500GB SSD (usb boot) and using HA in Chrome (Windows 10 computer) to use Assist.

Working with @bdraco, what we did:

The profiler service was started, and then the Assist dialogue box was opened and I voiced my command by pressing the microphone key "Turn on the Kitchen Light", it responded and then replied back did the action, then I said "Turn off the kitchen light" and likewise it responded and did the action. Both commands were successful. Shown here:

However, the logs would indicate otherwise. During this time, errors were logged in the thousands (over a few minutes) during the above dialogue:

Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/connection.py:125
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 10:16:00 AM (4291 occurrences)
Last logged: 1:27:51 PM

[547285121440] Received binary message for non-existing handler 8
[547285121440] Received binary message for non-existing handler 9
[547285121440] Received binary message for non-existing handler 10
[547297052992] Received binary message for non-existing handler 1
[547297052992] Received binary message for non-existing handler 2

My voice assistant settings are:

And the callgrind files here:

callgrind.out.1682882817681.txt
profile.1682882817681262.cprof.txt

Reveal some issues:

Where "20% of the event loop time is logging 1000x of the messages"

   index = handler_id - 1
        if (
            index < 0
            or index >= len(self.binary_handlers)
            or (handler := self.binary_handlers[index]) is None
        ):
            self.logger.error(
                "Received binary message for non-existing handler %s", handler_id
            )
            return

During this time, memory usage increased and CPU usage spiked (see the end of the traces):

In other separate callgrinds, similar issues are also seen:

This may also be related to this issue.

What version of Home Assistant Core has the issue?

2023.5.0b4

What was the last working version of Home Assistant Core?

not sure

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Assist

Link to integration documentation on our website

No response

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

The text was updated successfully, but these errors were encountered:

Anto79-ops · 2023-05-03T14:38:18Z

just wanted to add more information on this, when I use Home Assistant cloud with these settings (running b8):

asking the voice assistant same command for the kitchen lights as above, it works amazingly well and fast (unbelievably fast, wow!), but It still throws the logs, but not as much as when using local voice.

Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/connection.py:125
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 8:33:14 AM (38 occurrences)
Last logged: 8:33:14 AM

[546834613872] Received binary message for non-existing handler 2

Using the local voice and it will log in the thousands as mentioned above.

micium · 2023-05-05T07:06:08Z

Same problem with my HA (2023.5.1) using assist on RPI4, before Whisper the STT was ok .. now this feature is unusable !

gfn256 · 2023-05-05T11:10:17Z

Same experience on Home Assistant 2023.5.1, Voice Assist works properly (on Nabu Casa Cloud from phone) but logged some 260 Received binary message for non-existing handler... after 3 queries to voice. By the way the voice worked amazingly! Can't say it caused any hit in HA stability - I'm running in VM (2 cores - 4GB ram - 32 GB disk) in proxmox on an i5 6500T (16GB ram - 128gb NVME).

Anto79-ops · 2023-05-10T18:15:02Z

Hi,

Just an update on this. It still does it when I use Frontend (i.e. the microphone in the browser), however, when I use VOIP: no issues and no error messages in the core logs as above.

So, this is probably something related to frontend.

paulius2k · 2023-05-15T17:15:16Z

I am getting a lot of these messages every time I try using Voice Assistant via the Android App.
This happens in both cases - when the request is processed successfully and when it fails.


2023-05-15 20:11:53.509 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [547333730032] Received binary message for non-existing handler 3
2023-05-15 20:11:53.512 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [547333730032] Received binary message for non-existing handler 3
2023-05-15 20:11:53.515 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [547333730032] Received binary message for non-existing handler 3
2023-05-15 20:11:53.607 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [547333730032] Received binary message for non-existing handler 3
2023-05-15 20:11:53.611 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [547333730032] Received binary message for non-existing handler 3
2023-05-15 20:11:53.644 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [547333730032] Received binary message for non-existing handler 3
2023-05-15 20:11:53.658 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [547333730032] Received binary message for non-existing handler 3
2023-05-15 20:11:53.668 ERROR (MainThread) [snitun.multiplexer.core] Ping fails, no response from peer
2023-05-15 20:11:53.693 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [547333730032] Received binary message for non-existing handler 3
2023-05-15 20:11:53.706 INFO (MainThread) [homeassistant.components.websocket_api.http.connection] [546893645280] Connection closed by client

balloob · 2023-05-15T18:32:18Z

For people experiencing this, what browser and platform are you using? And are you browsing the website via Nabu Casa Cloud or local or proxy?

paulius2k · 2023-05-15T18:41:05Z

This is happening to me when I use Voice Assistant in my HA Android App on my Samsung phone with Android 13.
The App is connecting via Nabu Casa Cloud in my case.

Anto79-ops · 2023-05-15T21:54:46Z

Since my posts are kind of scattered I can provide some more information in a summary here.

It does not happen when I use VoIP (via grandstream and a phone) and it does not happen when using the Atom5 Echo (via ESPHome). And this is true for both local and cloud-based setups, no issues and no errors.

The problem occurs when using frontend ways such as (Windows OS and Chrome browser) and app (Android).

In these two cases, the error messages approach the thousands when I use local-based processing and the hundreds when I use home assistant cloud.

Hope that provides more information.

paulius2k · 2023-07-07T10:46:16Z

Can anything be done about this? I have the same errors flowing in my v2023.7.0.
Thank you.

stephack · 2023-07-08T14:20:40Z

I just started playing with this on v2023.7.1 and I'm getting these errors in my log as well....when using the Android mobile app. Also connecting via Nabu Casa.

joostlek · 2023-07-17T12:26:40Z

Can you share the logs?

paulius2k · 2023-07-19T16:42:32Z

I have much less of these errors in v2023.7.5-full Android App - just couple of entries per successful or unsuccessful attempt to understand a spoken command:


2023-07-19 19:32:52.078 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546671609552] Received binary message for non-existing handler 1
2023-07-19 19:32:52.190 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546671609552] Received binary message for non-existing handler 1
2023-07-19 19:33:02.507 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546671609552] Received binary message for non-existing handler 2
2023-07-19 19:33:02.583 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546671609552] Received binary message for non-existing handler 2
2023-07-19 19:33:02.677 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546671609552] Received binary message for non-existing handler 2
2023-07-19 19:33:12.499 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546671609552] Received binary message for non-existing handler 3
2023-07-19 19:33:12.555 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546671609552] Received binary message for non-existing handler 3
2023-07-19 19:33:29.795 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546671609552] Received binary message for non-existing handler 4
2023-07-19 19:33:29.864 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546671609552] Received binary message for non-existing handler 4
2023-07-19 19:33:36.006 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546671609552] Received binary message for non-existing handler 5
2023-07-19 19:33:36.095 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546671609552] Received binary message for non-existing handler 5
2023-07-19 19:33:43.541 INFO (MainThread) [homeassistant.helpers.intent] Triggering intent handler <OnOffIntentHandler - HassTurnOn>
2023-07-19 19:33:43.627 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546671609552] Received binary message for non-existing handler 6
2023-07-19 19:33:43.673 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546671609552] Received binary message for non-existing handler 6
2023-07-19 19:33:52.349 INFO (MainThread) [homeassistant.helpers.intent] Triggering intent handler <OnOffIntentHandler - HassTurnOff>
2023-07-19 19:33:52.429 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546671609552] Received binary message for non-existing handler 7
2023-07-19 19:33:52.541 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546671609552] Received binary message for non-existing handler 7
2023-07-19 19:33:59.666 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546671609552] Received binary message for non-existing handler 8
2023-07-19 19:33:59.688 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546671609552] Received binary message for non-existing handler 8
2023-07-19 19:34:14.791 INFO (MainThread) [homeassistant.helpers.intent] Triggering intent handler <OnOffIntentHandler - HassTurnOff>
2023-07-19 19:34:14.914 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546671609552] Received binary message for non-existing handler 9
2023-07-19 19:34:26.133 INFO (MainThread) [homeassistant.helpers.intent] Triggering intent handler <OnOffIntentHandler - HassTurnOff>
2023-07-19 19:34:26.201 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546671609552] Received binary message for non-existing handler 10
2023-07-19 19:34:26.261 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546671609552] Received binary message for non-existing handler 10
2023-07-19 19:34:34.905 INFO (MainThread) [homeassistant.helpers.intent] Triggering intent handler <OnOffIntentHandler - HassTurnOff>
2023-07-19 19:34:34.976 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546671609552] Received binary message for non-existing handler 11
2023-07-19 19:34:35.011 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546671609552] Received binary message for non-existing handler 11
2023-07-19 19:34:43.609 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546671609552] Received binary message for non-existing handler 12
2023-07-19 19:34:43.640 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546671609552] Received binary message for non-existing handler 12
2023-07-19 19:34:43.695 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546671609552] Received binary message for non-existing handler 12
2023-07-19 19:34:43.756 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546671609552] Received binary message for non-existing handler 12

bbrendon · 2023-10-13T05:26:04Z

For me, running this project (https://github.com/synesthesiam/homeassistant-satellite) triggers a constant stream of these in the logs:

ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [139694421748928] Received binary message for non-existing handler 1

HASS v2023.10.2

TB-SE · 2023-10-14T15:30:07Z

For me, running this project (https://github.com/synesthesiam/homeassistant-satellite) triggers a constant stream of these in the logs:
ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [139694421748928] Received binary message for non-existing handler 1
HASS v2023.10.2

+1

home-assistant · 2023-10-23T17:03:35Z

Hey there @home-assistant/core, @synesthesiam, mind taking a look at this issue as it has been labeled with an integration (conversation) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of conversation 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 conversation Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

conversation documentation
conversation source
_{^{(message by IssueLinks)}}

Emile86 · 2023-10-24T22:54:11Z

For me, running this project (https://github.com/synesthesiam/homeassistant-satellite) triggers a constant stream of these in the logs:
ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [139694421748928] Received binary message for non-existing handler 1
HASS v2023.10.2
+1

Same issue here with satellite

`Logger: homeassistant.components.assist_pipeline.pipeline
Source: components/assist_pipeline/pipeline.py:929
Integration: Assist pipeline (documentation, issues)
First occurred: 00:44:32 (6 occurrences)
Last logged: 00:58:43

Unexpected error during intent recognition
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/assist_pipeline/pipeline.py", line 929, in recognize_intent
conversation_result = await conversation.async_converse(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/conversation/init.py", line 467, in async_converse
result = await agent.async_process(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/conversation/default_agent.py", line 202, in async_process
if trigger_result := await self._match_triggers(user_input.text):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/conversation/default_agent.py", line 697, in _match_triggers
self._rebuild_trigger_intents()
File "/usr/src/homeassistant/homeassistant/components/conversation/default_agent.py", line 670, in _rebuild_trigger_intents
for sentence in intent_data.sentences:
^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/functools.py", line 1001, in get
val = self.func(instance)
^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/hassil/intents.py", line 52, in sentences
return [parse_sentence(text, keep_text=True) for text in self.sentence_texts]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/hassil/intents.py", line 52, in
return [parse_sentence(text, keep_text=True) for text in self.sentence_texts]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/hassil/parse_expression.py", line 207, in parse_sentence
seq = parse_expression(chunk, metadata=metadata)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/hassil/parse_expression.py", line 159, in parse_expression
return parse_group_or_alt_or_perm(chunk, metadata=metadata)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/hassil/parse_expression.py", line 82, in parse_group_or_alt_or_perm
seq_text = remove_delimiters(seq_chunk.text, GROUP_START, GROUP_END)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/hassil/parser.py", line 302, in remove_delimiters
assert len(text) > 2, "Text is too short"
^^^^^^^^^^^^^
AssertionError: Text is too short`

error on satellite side:
ERROR:homeassistant_satellite.remote:Unexpected error during intent recognition

elmillero · 2023-10-25T19:40:40Z

Here too, when stopping the 'homeassistant-satellite' service on all satellites, the error subsides.

sdholden28 · 2023-11-04T21:18:43Z

For me, running this project (https://github.com/synesthesiam/homeassistant-satellite) triggers a constant stream of these in the logs:
ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [139694421748928] Received binary message for non-existing handler 1
HASS v2023.10.2
+1
Same issue here with satellite
`Logger: homeassistant.components.assist_pipeline.pipeline Source: components/assist_pipeline/pipeline.py:929 Integration: Assist pipeline (documentation, issues) First occurred: 00:44:32 (6 occurrences) Last logged: 00:58:43
Unexpected error during intent recognition Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/assist_pipeline/pipeline.py", line 929, in recognize_intent conversation_result = await conversation.async_converse( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/conversation/init.py", line 467, in async_converse result = await agent.async_process( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/conversation/default_agent.py", line 202, in async_process if trigger_result := await self._match_triggers(user_input.text): ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/conversation/default_agent.py", line 697, in _match_triggers self._rebuild_trigger_intents() File "/usr/src/homeassistant/homeassistant/components/conversation/default_agent.py", line 670, in _rebuild_trigger_intents for sentence in intent_data.sentences: ^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/functools.py", line 1001, in get val = self.func(instance) ^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/hassil/intents.py", line 52, in sentences return [parse_sentence(text, keep_text=True) for text in self.sentence_texts] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/hassil/intents.py", line 52, in return [parse_sentence(text, keep_text=True) for text in self.sentence_texts] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/hassil/parse_expression.py", line 207, in parse_sentence seq = parse_expression(chunk, metadata=metadata) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/hassil/parse_expression.py", line 159, in parse_expression return parse_group_or_alt_or_perm(chunk, metadata=metadata) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/hassil/parse_expression.py", line 82, in parse_group_or_alt_or_perm seq_text = remove_delimiters(seq_chunk.text, GROUP_START, GROUP_END) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/hassil/parser.py", line 302, in remove_delimiters assert len(text) > 2, "Text is too short" ^^^^^^^^^^^^^ AssertionError: Text is too short`

error on satellite side: ERROR:homeassistant_satellite.remote:Unexpected error during intent recognition

+1

jenniferlee1818 · 2023-11-09T21:36:01Z

Came here to see what's up with the logs after installing wake word.
This is in my logs less than one minute after restarting home assistant. 20000?!!

Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/connection.py:150
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 2:30:08 PM (20144 occurrences)
Last logged: 2:31:01 PM

[140034822700480] Received binary message for non-existing handler 3

Home Assistant container running in docker with separate containers piper, whisper and porcupine (rhasspy/wyoming-piper, rhasspy/wyoming-whisper, rhasspy/wyoming-porcupine1)

OzGav · 2024-01-02T00:14:04Z

Keeping this alive in 2024!

Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/connection.py:167
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 1:45:30 AM (4232 occurrences)
Last logged: 10:03:00 AM

[547681309888] Received binary message for non-existing handler 1
[547681309888] Received binary message for non-existing handler 2
[547681309888] Received binary message for non-existing handler 3
[545834808128] Received binary message for non-existing handler 1

fantnhu · 2024-01-14T15:03:37Z

I have the same problem:

`Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/connection.py:167
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 15:57:20 (210 occurrences)
Last logged: 15:57:20

[140195976403264] Received binary message for non-existing handler 9`

Frontend + microphone. ESPHome + micronoffal does not work for me at all. :(

Core
2024.1.3
Supervisor
2023.12.0
Operating System
11.4
Kezelőfelület
20240104.0

issue-triage-workflows · 2024-04-15T03:58:17Z

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.

PiotrMachowski · 2024-04-21T14:33:40Z

The problem is still there.

HA Core: 2024.4.3
Supervisor: 2024.04.0
OS: 12.2
Assist used from Android App: 2024.4.1-full

Errors

2024-04-21 13:54:13.721 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140088671119040] Received binary message for non-existing handler 1
2024-04-21 13:54:13.745 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140088671119040] Received binary message for non-existing handler 1
2024-04-21 13:54:13.814 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140088671119040] Received binary message for non-existing handler 1
2024-04-21 13:54:14.224 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140088671119040] Received binary message for non-existing handler 1
2024-04-21 13:54:14.224 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140088671119040] Received binary message for non-existing handler 1
2024-04-21 13:54:20.051 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140088671121472] Received binary message for non-existing handler 1
2024-04-21 13:54:20.590 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140088671121472] Received binary message for non-existing handler 1
2024-04-21 13:56:29.106 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140088638387904] Received binary message for non-existing handler 1
2024-04-21 13:56:29.156 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140088638387904] Received binary message for non-existing handler 1
2024-04-21 13:56:29.170 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140088638387904] Received binary message for non-existing handler 1
2024-04-21 13:56:29.187 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140088638387904] Received binary message for non-existing handler 1
2024-04-21 13:56:29.200 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140088638387904] Received binary message for non-existing handler 1
2024-04-21 13:56:29.278 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140088638387904] Received binary message for non-existing handler 1
2024-04-21 13:56:29.291 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140088638387904] Received binary message for non-existing handler 1
2024-04-21 13:56:29.419 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140088638387904] Received binary message for non-existing handler 1
2024-04-21 13:56:29.432 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140088638387904] Received binary message for non-existing handler 1
2024-04-21 13:56:29.449 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140088638387904] Received binary message for non-existing handler 1
2024-04-21 13:56:29.462 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140088638387904] Received binary message for non-existing handler 1
2024-04-21 13:56:29.479 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140088638387904] Received binary message for non-existing handler 1
2024-04-21 13:56:30.043 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140088638387904] Received binary message for non-existing handler 1
2024-04-21 13:56:30.060 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140088638387904] Received binary message for non-existing handler 1
2024-04-21 13:56:30.077 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140088638387904] Received binary message for non-existing handler 1
2024-04-21 13:56:30.090 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140088638387904] Received binary message for non-existing handler 1
2024-04-21 13:56:30.103 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140088638387904] Received binary message for non-existing handler 1
2024-04-21 13:56:30.112 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140088638387904] Received binary message for non-existing handler 1
2024-04-21 13:56:30.701 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140088638387904] Received binary message for non-existing handler 1
2024-04-21 13:56:30.719 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140088638387904] Received binary message for non-existing handler 1
2024-04-21 13:56:30.739 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140088638387904] Received binary message for non-existing handler 1
2024-04-21 13:56:30.773 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140088638387904] Received binary message for non-existing handler 1
2024-04-21 13:56:30.790 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140088638387904] Received binary message for non-existing handler 1
2024-04-21 13:56:30.803 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140088638387904] Received binary message for non-existing handler 1
2024-04-21 13:56:30.825 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140088638387904] Received binary message for non-existing handler 1
2024-04-21 13:56:30.825 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140088638387904] Received binary message for non-existing handler 1

frenck added this to the 2023.5.0 milestone Apr 30, 2023

Anto79-ops mentioned this issue May 1, 2023

Standard Text Queries to Assist Makes HA Unresponsive and causing unwanted reboot of Core #92181

Closed

balloob mentioned this issue May 3, 2023

Received Binary Message for non-existing handler #92280

Closed

paulius2k mentioned this issue May 15, 2023

Voice Assistant: assistants missing in the Android App #93122

Closed

joostlek added the integration: conversation label Oct 23, 2023

home-assistant bot assigned synesthesiam Oct 23, 2023

issue-triage-workflows bot added the stale label Apr 15, 2024

issue-triage-workflows bot removed the stale label Apr 21, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Using Voice/Assist causes the websocket to get overloaded leading to HAOS stability issues #92307

Using Voice/Assist causes the websocket to get overloaded leading to HAOS stability issues #92307

Anto79-ops commented Apr 30, 2023 •

edited

Anto79-ops commented May 3, 2023

micium commented May 5, 2023

gfn256 commented May 5, 2023 •

edited

Anto79-ops commented May 10, 2023 •

edited

paulius2k commented May 15, 2023

balloob commented May 15, 2023

paulius2k commented May 15, 2023

Anto79-ops commented May 15, 2023

paulius2k commented Jul 7, 2023

stephack commented Jul 8, 2023

joostlek commented Jul 17, 2023

paulius2k commented Jul 19, 2023

bbrendon commented Oct 13, 2023 •

edited

TB-SE commented Oct 14, 2023

home-assistant bot commented Oct 23, 2023

Emile86 commented Oct 24, 2023 •

edited

elmillero commented Oct 25, 2023

sdholden28 commented Nov 4, 2023

jenniferlee1818 commented Nov 9, 2023

OzGav commented Jan 2, 2024

fantnhu commented Jan 14, 2024

issue-triage-workflows bot commented Apr 15, 2024

PiotrMachowski commented Apr 21, 2024

Using Voice/Assist causes the websocket to get overloaded leading to HAOS stability issues #92307

Using Voice/Assist causes the websocket to get overloaded leading to HAOS stability issues #92307

Comments

Anto79-ops commented Apr 30, 2023 • edited

The problem

What version of Home Assistant Core has the issue?

What was the last working version of Home Assistant Core?

What type of installation are you running?

Integration causing the issue

Link to integration documentation on our website

Diagnostics information

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

Anto79-ops commented May 3, 2023

micium commented May 5, 2023

gfn256 commented May 5, 2023 • edited

Anto79-ops commented May 10, 2023 • edited

paulius2k commented May 15, 2023

balloob commented May 15, 2023

paulius2k commented May 15, 2023

Anto79-ops commented May 15, 2023

paulius2k commented Jul 7, 2023

stephack commented Jul 8, 2023

joostlek commented Jul 17, 2023

paulius2k commented Jul 19, 2023

bbrendon commented Oct 13, 2023 • edited

TB-SE commented Oct 14, 2023

home-assistant bot commented Oct 23, 2023

Emile86 commented Oct 24, 2023 • edited

elmillero commented Oct 25, 2023

sdholden28 commented Nov 4, 2023

jenniferlee1818 commented Nov 9, 2023

OzGav commented Jan 2, 2024

fantnhu commented Jan 14, 2024

issue-triage-workflows bot commented Apr 15, 2024

PiotrMachowski commented Apr 21, 2024

Anto79-ops commented Apr 30, 2023 •

edited

gfn256 commented May 5, 2023 •

edited

Anto79-ops commented May 10, 2023 •

edited

bbrendon commented Oct 13, 2023 •

edited

Emile86 commented Oct 24, 2023 •

edited