Trouble connecting to Home Assistant


  • IP Address
  • Rhasspy version 2.4.14
  • Docker
  • Rpi 3B+, Jabra 410 USB Speaker/microphone
  • Raspbian Buster
  • Other software details (e.g., python 3.7)


  • IP Address
  • Rhasspy version 2.4.14
  • Docker
  • Intel NUC i3
  • Debian Buster Server
  • in Docker

rhasspyListener with Jabra 410 USB speaker/microphone is running on RPi 3B at Home Assistant is running on an Intel NUC i3 at inside a docker container. This is the home_assistant section of my profile YAML on rhasspyListener:

    "home_assistant": {
        "access_token": "abcDEFghiJKLmnoPQRstuVWXyz",
        "url": ""

but all I see back from the Problems tab is:

HomeAssistantIntentHandler	Can't contact server	Unable to reach your Home Assistant server at Is it running?

Am I missing something else in my profile YAML definition? I’ve tried many, many different combinations of http: or https: and physical IP addresses as well as docker container IP addresses, and still Rhasspy fails to connect. :frowning:

have you simply tried to curl your NUC ? :


Not yet but I certainly will - Thank you! :slight_smile:

The SSL security certificate on Home Assistant is using a DNS node name.
Trying to hit the server via IP address was failing. :frowning:

Solution: Update /etc/hosts on the host Raspbian system to include the proper IP address and DNS node name matching.

Updating the host Raspbian system did not resolve the issue. :frowning: Somehow, I need to add my IP/name combination to the /etc/hosts file in the docker container. I’ve tried that, and it will not allow replacing the file (says it’s busy / in use) and echoing >>/etc/hosts does not update the file. :frowning:

When starting the Docker container for Rhasspy, the secret magick incantation is as follows:

        --add-host "hassio-node-name:" \

Further tip: If configuring separate Rhasspy listener and server nodes, you’ll need to add the --add-host command to both docker start/run commands.