core: Using Voice/Assist causes the websocket to get overloaded leading to HAOS stability issues

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