Disconnected: Did not receive auth message within 10 seconds

Configuration
22

I have the same problem as well

23

For anyone else using AppDaemon and docker-compose, the current docker-compose looks like this:

# docker-compose.yaml
version: '3.8'

services:
  appdaemon:
    container_name: appdaemon
    image: acockburn/appdaemon:latest
    restart: unless-stopped
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /opt/homeassistant/config/appdaemon:/conf # Set which local directory will contain all your app daemon configuration
    ports:
      - "${PORT_APP_DAEMON}:${PORT_APP_DAEMON}"
    environment:
      - TZ=${TZ}
      - HA_URL=http://${HA_IP}:${PORT_HA}
      - HA_TOKEN=${HA_APPDAEMON_KEY}
      - DASH_URL=http://${HA_IP}:${PORT_APP_DAEMON}
    depends_on:
      - homeassistant
    labels: 
      autoheal: "true"

    # this section is completely optional
    healthcheck:
      test: curl -fSs http://127.0.0.1:${PORT_APP_DAEMON} || exit 1
      start_period: 90s
      timeout: 10s
      interval: 5s
      retries: 3

All the following variables live in a .env file:

  • PORT_APP_DAEMON ā†’ default: 5050
  • TZ ā†’ example: Europe/Berlin
  • HA_IP ā†’ IP address to your Home Assistant instance
  • PORT_HA ā†’ default: 8123
  • HA_APPDAEMON_KEY ā†’ generate a Long Lived Access Token in Home Assistant

And then, you need to edit (as mentioned by @DobriyS) the /opt/homeassistant/config/appdaemon/appdaemon.yaml file to make sure the Long Lived Access Token is added there too as well as the Home Assistant IP address:

# appdaemon.yaml
appdaemon:
  time_zone: CET
  latitude: 51.725
  longitude: 14.3434
  elevation: 0
  time_zone: Europe/Berlin
  plugins:
    HASS:
      type: hass
      ha_url: <HA_IP>:<PORT_HA>
      token: <HA_APPDAEMON_KEY>
      cert_verify: True
http:
  url: <HOST_IP>:<PORT_APP_DAEMON>
admin:
api:
hadashboard:
24

Neither do I, and it has started for me as well. I am on 2023.7.3, but it references 2023.4ā€¦

Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/http.py:51 
Integration: Home Assistant WebSocket API (documentation, issues) 
First occurred: 3 August 2023 at 20:47:29 (3 occurrences) 
Last logged: 3 August 2023 at 22:58:50

[547300399440] from 127.0.0.1 (Home Assistant/2023.4 (io.robbie.HomeAssistant; build:2023.460; iOS 16.6.0)): Disconnected: Did not receive auth message within 10 seconds
[547270845264] from 127.0.0.1 (Home Assistant/2023.4 (io.robbie.HomeAssistant; build:2023.460; iOS 16.6.0)): Disconnected: Did not receive auth message within 10 seconds
[547138817424] from 127.0.0.1 (Home Assistant/2023.4 (io.robbie.HomeAssistant; build:2023.460; iOS 16.6.0)): Disconnected: Did not receive auth message within 10 seconds
25

Same hereā€¦

No clue as to why or where this comes fromā€¦

Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/http.py:50
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 09:42:37 (1 occurrences)
Last logged: 09:42:37

[140386469862208] from 192.168.50.151 (Home Assistant/2023.4 (io.robbie.HomeAssistant; build:2023.460; iOS 15.6.0)): 
Disconnected: Did not receive auth message within 10 seconds
26

Same, not sure if this is caused by upgrading my docker or pfsense haproxy package. But before both, I had zero issues accessing it remotely or via dns. I can still access it via ip:port.

27

Same Problems. Recently updated to RPI Docker Version 2023.9.3 for home assistant/home-assistant.

SOLVED for my situation. HA was running but not frontend was loading. From the iPad and iPhone, I was only seeing a blank screen with a Gear for the (ā€œSettingsā€) ā€œCompanion Appā€ Settings. Go to ā€œDebuggingā€ and ā€œRESET FRONTEND CACHEā€. Close and restart the HA app and it works!

28

My android companion app would not load and finally show 3 options on-screen including ā€˜waitā€™. Diving into the HAOS LogViewer, I found this

Disconnected: Did not receive auth message within 10 seconds

Anyways, the issue was I had two wifi SSIDs (same network) at home, and in the companion app, I had added just one ā€˜knownā€™ wifi SSID. My issue happens when Iā€™m connected to the 2nd wifi SSID.

The solution for me was to add the second home SSID to the known network inside the companion app settings in the app.

2 Likes
29

how did you add another wifi ssid in the companion app? thanks