@JayF wrote:
Hey guys!
Yesterday I’ve been struck by an idea of what would be the probable solution and it turns out it worked for me.
I’m running Home-Assistant on Docker from within an Intel NUC. I’ve never been able to find the Apple TV while I was able to detect it manually from outside the Docker container.
If you are running several Docker containers on the same hardware, chances are that you actually reserved the port 8123 for HA usage. If you did, then the command line in order to create the Docker container would have the
-p 8123:8123
command in it.I figured out that would be the problem as the only to communicate with the container is by going through the port 8123. Therefore, only having 8123 as a communication won’t allow any reliable discovery or anything else outside of the Docker network.
I then decided to stop all containers on my Intel NUC, deleted my HA container and recreated it
--net=host
and voilà, the AppleTV is now being discovered and I can control it remotely no problems!The actual command I typed in was:
sudo docker run -d --name="home-assistant" --net=host --restart=always --device=/dev/ttyACM0 --device=/dev/ttyUSB0 -v /home/jayf/Dockerconf/HomeAssistant:/config -v /var/run/docker.sock:/var/run/docker.sock -e "TZ=America/Montreal" -p 8123:8123 homeassistant/home-assistant
The
--device=/dev/ttyACM0
is being used for my Z-Wave USB dongle. Obviously, the specified port in that command will be ignored as--net=host
is being used.Hopefully it will help others!
Posts: 3
Participants: 2