core icon indicating copy to clipboard operation
core copied to clipboard
Published 4 days ago • verified publisher icon home-assistant

Received binary message for non-existing handler [1/2/3/4]

Open adamf83 opened this issue 2 years ago • 11 comments

The problem

When using the assist functionality in HA I’ve noticed that my logs are filling up with the following error:

Logger: homeassistant.components.websocket_api.http.connection Source: components/websocket_api/connection.py:150 Integration: Home Assistant WebSocket API (documentation, issues) First occurred: 21:20:07 (5097 occurrences) Last logged: 21:27:46

[140563455572416] Received binary message for non-existing handler 2 [140563455572416] Received binary message for non-existing handler 3 [140563455572416] Received binary message for non-existing handler 4 [140563007852992] Received binary message for non-existing handler 1 [140563007852992] Received binary message for non-existing handler 2

In the space of running one command I had over 3000 errors. I’m not exactly sure if something isn’t working, but I shouldn’t be getting 3000+ errors.

What version of Home Assistant Core has the issue?

core-2023.11.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

websocket_api

Link to integration documentation on our website

https://www.home-assistant.io/integrations/websocket_api/

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

adamf83 avatar Dec 02 '23 21:12 adamf83

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

Code owner commands

Code owners of websocket_api 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 websocket_api Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)

websocket_api documentation websocket_api source (message by IssueLinks)

home-assistant[bot] avatar Dec 02 '23 21:12 home-assistant[bot]

Seeing the same, only difference being that it's only "1" for me at the end of the error (no "2", "3", etc). Also, this started showing up right after I upgraded core to 2023.11.3 this morning.

Core 2023.11.3

Supervisor 2023.11.6

Operating System 11.2

Frontend 20231030.2

antisane avatar Dec 05 '23 17:12 antisane

not sure if the same issue, but from 2023.12 started with websocket errors like: [140124016572352] Received invalid command: {'access_token': 'eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJmYjg3NmMyNTg5NDI0OGExYWU4NTRjZTVmNGQ4ZmEzOCIsImlhdCI6MTcwMjI4NTk4MywiZXhwIjoxNzAyMjg3NzgzfQ.GLvyfho8wQCOLH0FT-IIqSOqPalz-gMfxBi8FoeuL_Q', 'type': 'auth'}

Core 2023.12.1 Supervisor 2023.11.6 Operating System 11.2 Frontend 20231208.2

Claudio1L avatar Dec 11 '23 09:12 Claudio1L

Bei mir ist der Fehler: [140279515426112] Error handling message: length of value must be at least 1 for dictionary value @ data['statistic_ids']. Got [] (invalid_format) Sven from 192.168.1.22 (Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36)

Herzblut21 avatar Dec 29 '23 07:12 Herzblut21

Détails du journal (ERREUR) Logger: homeassistant.components.websocket_api.http.connection Source: components/websocket_api/connection.py:301 Integration: Home Assistant WebSocket API (documentation, issues) First occurred: 00:30:17 (2 occurrences) Last logged: 00:49:18

[140413019282368] Error handling message: length of value must be at least 1 for dictionary value @ data['statistic_ids']. Got [] (invalid_format) Mario from 10.10.0.78 (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36) [140412007501376] Error handling message: length of value must be at least 1 for dictionary value @ data['statistic_ids']. Got [] (invalid_format) Mario from 10.10.0.78 (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36)

ghost avatar Jan 17 '24 00:01 ghost

I'm also receiving the same, and have actually been for some time...

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: 19:16:04 (50 occurrences)
Last logged: 19:16:10

[139836798769856] Received binary message for non-existing handler 1

celodnb avatar Apr 11 '24 17:04 celodnb

I have the same error, it has to do something when using the companion app on MacOS using the assist functionality. It works when using home assistant assist from a browser, but not from the companion app.

I use nabu casa btw

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: 13:57:57 (850 occurrences)
Last logged: 14:54:27

[139649025566784] Received binary message for non-existing handler 3
[139649002180800] Received binary message for non-existing handler 1
[139649002180800] Received binary message for non-existing handler 2
[139649002715968] Received binary message for non-existing handler 1
[139648868149824] Received binary message for non-existing handler 1

pprazzi avatar May 28 '24 12:05 pprazzi

Same issue here, on 2024.6.1

jhemak avatar Jun 08 '24 04:06 jhemak

Same issue here. This error log occurs when using voice assistant from the Android companion app.

Core 2024.7.4 Supervisor 2024.06.2 Operating System 12.4 Frontend 20240710.0

Homeassistant companion app on Android 13

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: 13:13:32 (1 occurrences)
Last logged: 13:13:32

[547277048704] Received binary message for non-existing handler 1

Might be related to #92307, but it was never resolved.

e3e6 avatar Jul 31 '24 10:07 e3e6

`Logger: homeassistant.components.websocket_api.http.connection Source: components/websocket_api/connection.py:167 integration: Home Assistant WebSocket API (documentation, issues) First occurred: 6:58:49 AM (9 occurrences) Last logged: 7:02:59 AM

[140183798152304] Received binary message for non-existing handler 5
[140183798152304] Received binary message for non-existing handler 6
[140183798152304] Received binary message for non-existing handler 7
[140183798152304] Received binary message for non-existing handler 9
[140183798152304] Received binary message for non-existing handler 11`

unhuzpt avatar Sep 14 '24 05:09 unhuzpt

I am also seeing this issue when using Assist from Firefox on MacOS. I have no issues when using the Android companion app for Assist though.

holysoles avatar Oct 19 '24 21:10 holysoles

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.

issue-triage-workflows[bot] avatar Jan 17 '25 22:01 issue-triage-workflows[bot]

The same for me with Local Voice (Whisper and Piper on separate machine).

The pipeline works but after each sentence (both in/out) I've one row of log below.

I'm trying both from web browser and companion app with iOS.

For connecting in HTTPS and having the mic I'm using Ngnix Proxy Manager ina separate machine.

In configuration.yaml I have:

################################################################################
# HTTP
# https://www.home-assistant.io/integrations/http/
http:
  use_x_forwarded_for: true
  trusted_proxies:
    - 192.168.251.251
###############################################################################

In Ngnix Proxy Manager I've enabled Websockets support and custom locations :

/
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection “upgrade”;

Core: 2025.1.3 Supervisor: 2024.12.3 Operating System: 14.1 Frontend: 20250109.0

2025-01-21 18:30:13.462 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546971177680] Received binary message for non-existing handler 1
2025-01-21 18:30:46.993 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546879266608] Received binary message for non-existing handler 2
2025-01-21 18:30:46.999 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546879266608] Received binary message for non-existing handler 2
2025-01-21 18:30:47.045 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546879266608] Received binary message for non-existing handler 2
2025-01-21 18:33:31.646 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546923654176] Received binary message for non-existing handler 1
2025-01-21 18:33:31.730 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546923654176] Received binary message for non-existing handler 1
2025-01-21 18:33:41.037 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546923654176] Received binary message for non-existing handler 2
2025-01-21 18:33:41.038 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546923654176] Received binary message for non-existing handler 2
2025-01-21 18:33:41.080 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546923654176] Received binary message for non-existing handler 2
2025-01-21 18:33:41.081 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546923654176] Received binary message for non-existing handler 2
2025-01-21 18:36:36.383 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546970406768] Received binary message for non-existing handler 1
2025-01-21 18:36:36.481 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546970406768] Received binary message for non-existing handler 1
2025-01-21 18:36:47.155 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546970406768] Received binary message for non-existing handler 2
2025-01-21 18:36:47.181 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546970406768] Received binary message for non-existing handler 2
2025-01-21 18:36:47.250 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546970406768] Received binary message for non-existing handler 2
2025-01-21 18:36:47.251 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546970406768] Received binary message for non-existing handler 2
2025-01-21 18:42:23.916 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546970218512] Received binary message for non-existing handler 1
2025-01-21 18:42:23.917 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546970218512] Received binary message for non-existing handler 1
2025-01-21 18:42:24.040 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546970218512] Received binary message for non-existing handler 1
2025-01-21 18:42:34.811 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546970218512] Received binary message for non-existing handler 2
2025-01-21 18:42:42.930 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546970218512] Received binary message for non-existing handler 3
2025-01-21 18:42:42.930 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546970218512] Received binary message for non-existing handler 3
2025-01-21 18:42:42.931 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546970218512] Received binary message for non-existing handler 3
2025-01-21 18:42:43.037 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546970218512] Received binary message for non-existing handler 3
2025-01-21 18:42:50.143 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546970218512] Received binary message for non-existing handler 4
2025-01-21 18:42:50.144 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546970218512] Received binary message for non-existing handler 4
2025-01-21 18:42:50.145 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546970218512] Received binary message for non-existing handler 4
2025-01-21 18:42:50.230 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546970218512] Received binary message for non-existing handler 4
2025-01-21 18:42:50.230 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546970218512] Received binary message for non-existing handler 4

coserotondo avatar Jan 21 '25 17:01 coserotondo

I'm getting this error too, using iOS companion app, nabu casa cloud haos 2025.3.3.

Turn on the hallway light - works - no error. Turn off the hallway light - works - logs error! Every time. Here is the log for three on/off operations. Error only logged on the OFF operations.

`Logger: homeassistant.components.websocket_api.http.connection Source: components/websocket_api/connection.py:175 integration: Home Assistant WebSocket API (documentation, issues) First occurred: 3:58:34 PM (3 occurrences) Last logged: 4:05:21 PM

[547489698720] Received binary message for non-existing handler 2 [547508510752] Received binary message for non-existing handler 4 [547508510752] Received binary message for non-existing handler 6`

bdnstn avatar Jun 11 '25 08:06 bdnstn

I just ran into this issue on 2025.6.1 (Container) with Cloud speech-to-text while I was using Assist on my phone. It was working fine and then suddenly it stopped working and got a bunch of "text-to-speech failed" every time I activated the mic. I waited a few minutes and it worked again. Maybe an issue with the cloud server?

pilot51 avatar Jun 18 '25 19:06 pilot51

Android 16 pixel 6a HAOS 2025.7.0 Assist: Home Assistant cloud

Prompt: What's the time Answer: correct answer with current time

Error: Logger: homeassistant.components.websocket_api.http.connection Source: components/websocket_api/connection.py:175 integration: Home Assistant WebSocket API (documentation, issues) First occurred: 06:32:30 (2 occurrences) Last logged: 06:32:30

[548050266976] Received binary message for non-existing handler 15

seanomat avatar Jul 03 '25 04:07 seanomat

I believe I am having this issue as well.

HAOS 2025.7.1

Logger: homeassistant.components.websocket_api.http.connection Source: components/websocket_api/connection.py:175 integration: Home Assistant WebSocket API First occurred: 6:35:19 AM (48 occurrences) Last logged: 6:35:19 AM

[281472087915584] Received binary message for non-existing handler 1

Failure rate is currently 100%, I'll try again soon.

epistax avatar Jul 16 '25 10:07 epistax

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.

issue-triage-workflows[bot] avatar Oct 14 '25 11:10 issue-triage-workflows[bot]

Still an issue 200 occurrences in like 10 min

electricsteve avatar Oct 26 '25 17:10 electricsteve

having the same issue in Home Assistant 2025.11 (docker) when trying to instantiate a voice pipeline.

No issue when using 2025.9

docker compose

services:

  homeassistant:
    container_name: homeassistant
    image: ghcr.io/home-assistant/home-assistant:2025.11
    restart: always
    depends_on:
      - speech-to-phrase
      - wake-words
    ports:
      - 8123:8123
    networks:
      proxy:
      ha-internal:
        ipv4_address: 10.0.0.2
    volumes:
      - /var/docker/homeassistant/config:/config
      - /etc/localtime:/etc/localtime:ro
      - /run/dbus:/run/dbus:ro
    privileged: true
    deploy:
      resources:
        limits:
          cpus: '2'

  speech-to-phrase:
    container_name: homeassistant-stt
    image: rhasspy/wyoming-speech-to-phrase
    restart: always
    networks:
      ha-internal:
        ipv4_address: 10.0.0.3
    environment:
      - TZ=Europe/Rome
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - models:/models
      - /var/docker/homeassistant/speech-to-phrase/train:/train
      - /var/docker/homeassistant/speech-to-phrase/custom-sentences:/custom_sentences
    command:
      - --hass-websocket-uri
      - 'ws://example.com:8123/api/websocket'
      - --hass-token
      - '<my-token>'
      - --retrain-on-start
      - --custom-sentences-dir
      - '/custom_sentences'
    deploy:
      resources:
        limits:
          cpus: '2'

  wake-words:
    container_name: homeassistant-open-wake-words
    image: rhasspy/wyoming-openwakeword
    restart: always
    networks:
      ha-internal:
        ipv4_address: 10.0.0.4
    environment:
      - TZ=Europe/Rome
    volumes:
      - /etc/localtime:/etc/localtime:ro
    deploy:
      resources:
        limits:
          cpus: '1'

networks:
  proxy:
    external: true
  ha-internal:
    name: ha-internal
    ipam:
      config:
        - subnet: 10.0.0.0/29
          gateway: 10.0.0.1

volumes:
  models:
    name: models

andreasntr avatar Nov 23 '25 18:11 andreasntr