ERROR Received binary message for non-existing handler 1

[bbrendon]

When I start this, I get a massive amount of these in the hass logs. Is this a HASS problem or the satellite problem? Anyone else?

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

[martin131]

same problem, any solution?

[synesthesiam]

This can happen some times when HA has already closed the pipeline, but a few audio chunks are still send out by the satellite. It shouldn't be hurting anything.

[estiens]

I get a ton of these as well and fairly regularly (about every ten seconds or so no matter what)

[freakshock88]

I get these all the time, and it seems to break my satellite functionality. My satellites no longer respond to the wake word. I have 2 satellites with Raspberry pi's and one M5Stack ESPHome one setup as voice satellites.

Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/connection.py:167
Integration: Home Assistant WebSocket API ([documentation](https://www.home-assistant.io/integrations/websocket_api), [issues](https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+websocket_api%22))
First occurred: 6:09:55 PM (16473 occurrences)
Last logged: 9:49:08 PM

    [140202907642816] Received binary message for non-existing handler 1
    [140202867441088] Received binary message for non-existing handler 253
    [140202867441088] Received binary message for non-existing handler 254
    [140202867441088] Received binary message for non-existing handler 255
    [140202867441088] Received binary message for non-existing handler 1

Any idea how to fix / debug this?