Home Assistant running Docker with bridge network, all entities showing "No response"

Tags: #<Tag:0x00007f328211b8e8> #<Tag:0x00007f3282119c00>

Hi all,

I’m attempting to move my Home assistant container from a Docker “host” network to a Docker “bridge” network. Everything has gone smoothly so far, except my HomeKit integration (not HomeKit controller, that also works well!).

I initially had the problem where I was unable to discover the HomeKit bridge and pair. This was fixed by using avahi-daemon to reflect the mDNS between my host network interface and docker network interface and also by modifying the Home Assistant HomeKit config to include “advertise_ip” and “safe_mode” (which was switched off after pairing) as suggested in the Home Assistant HomeKit documentation. This allowed me to successfully discover, pair and add all of my Home Assistant entities to HomeKit.

Having added all of the Home Assistant entities to HomeKit, my next problem was that all of the entities are display as “No response”. If I change my Docker network back to “host”, it all works as expected. However in bridge mode, everything shows as “No response” in HomeKit. This is where I’ve become stuck.

Before attempting the move from “host” network mode to “bridge” network mode, Home Assistant and the HomeKit integration have been pretty much flawless throughout the ~2 years I’ve been using it!

I’m running 0.117.5 and Docker version 19.03.13 on a Centos 7 VM running on a QNAP NAS in Virtualisation Station.

Has anyone come across this issue before, or have any ideas of what to start checking?

Thanks in advance!

Fixed. The host network interface had changed names, meaning allow-interfaces my avahi-daemon.conf was incorrect

All working well now!