Do you see a hostname when you go to the hassio panel>system tab?
Hi, yes it’s hassio
, I’ve just left it at default, I should have included more info in my original post. Here’s the info from my system tab:
Host system
Hostname |
hassio |
System |
HassOS 1.12 |
Deployment |
production |
Version |
139 |
Latest version |
139 |
I’m not installed any extra addons yet, as I’m just trying to get Home Assistant to talk to my MQTT broker first. I’m running it on a Raspberry Pi 3, good PSU, good quality SD card, etc.
I can access the Raspberry Pi fine using another machine on the network using it’s hostname: ssh [email protected] -p 22222
It’s when I try to connect the other way, from the HA docker container to another machine on my network with a *.local
hostname I get connection error.
To use my MQTT example, if I set my configuration.yaml to access using the hostname:
mqtt:
broker: mqtt_broker.local
port: 8883
keepalive: 60
certificate: cert.crt
I get a connection failed
error in my Home Assistant log, and the MQTT broker doesn’t even log a connection attempt.
If I set my configuration.yaml to access using the IP address:
mqtt:
broker: 192.168.1.99
port: 8883
keepalive: 60
certificate: cert.crt
Then it does actually try and connect to my MQTT broker as it logs a connection attempt, but then the auth fails as my MQTT broker only allows connections to the hostname mqtt_broker.local
I’d like to fix this if possible, as I was able to connect to my MQTT broker without issue when running Home Assistant under VirtualEnv
on Raspbian but under HassIO / HassOS
it just will not connect.