No logs, no problem!
What the heck has occurred here, looks like some of my threads have been merged? No wonder this is confusing.
Will fix when I get home
Exactly what command are you running to make HA run in docker?
It’s all covered better in this thread.
The command is
docker run -d
Surprisingly it works fine, HA starts ok - it seems like it should work, however the ability of HA to perform a ‘detection’ against the entire network, appears to be unfortunately failing.
Again to be clear, I’m running under a tailored version of linux, found here.
It used to be mentioned in the documentation, but if you want DISCOVERY to work, net has to be host, and you don’t specify a port.
You may need to open some more ports in docker for detection to work, try opening ports 53, or 5353, or even all ports to test detection.
You need to have network mode host…
That’s DNS. Home Assistant isn’t running a DNS server
Those threads should be merged.
I don’t know why you are surprised it works. However see the other comments for the reason why discovery isn’t working.
I do realise that, but unfortunately it spits out errors.
The following components and platforms could not be set up:
I am indeed already using --net=host
I was looking at this yesterday. Maybe it is because zeroconf is already running on libreelec?
That’s totally possible? Is this a service which is not possible to take input from 2 applications?
I don’t suppose you or someone here has a spare R.Pi, VM etc to run LibreElec on?
It, it’s actually a fairly fast install
I have 6 libreelec boxes. I am on team Kodi and a moderator on the le forum. I don’t have any on a pi.
I was trying this out with various incarnations of the docker command line without a lot of success. I am getting zeroconf errors.
I am not a docker expert. I am not a zeroconf expert. I imagine zeroconf needs to use a set of ports that will already be allocated to Kodi. Just guessing here.
A port can only be in use by ONE service/application, so it’s not about taking input from 2 applications, it’s about listening on a port.
100% likely. I guess turning off zeroconf will render discovery useless.
This is my home assistant log for one run. I think the solution will be to exclude default_config from configuration.yaml and include what is needed as a minimum.
2019-08-16 19:27:11 ERROR (MainThread) [homeassistant.setup] Error during setup of component zeroconf
Traceback (most recent call last):
File “/usr/src/app/homeassistant/setup.py”, line 172, in _async_setup_component
component.setup, hass, processed_config # type: ignore
File “/usr/local/lib/python3.7/concurrent/futures/thread.py”, line 57, in run
result = self.fn(*self.args, **self.kwargs)
File “/usr/src/app/homeassistant/components/zeroconf/init.py”, line 61, in setup
zeroconf = Zeroconf()
File “/usr/local/lib/python3.7/site-packages/zeroconf.py”, line 1807, in init
self._listen_socket = new_socket()
File “/usr/local/lib/python3.7/site-packages/zeroconf.py”, line 1778, in new_socket
OSError: [Errno 98] Address already in use
2019-08-16 19:27:11 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of default_config. Setup failed for dependencies: zeroconf
2019-08-16 19:27:11 ERROR (MainThread) [homeassistant.setup] Setup failed for default_config: Could not set up all dependencies.
In case anyone is following this, these are the ports running on libreelec (without the hass docker running)
MasterBedroom:~ netstat -tanp|grep LISTEN tcp 0 0 127.0.0.1:36573 0.0.0.0:* LISTEN 1008/kodi.bin tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 978/smbd tcp 0 0 127.0.0.1:9090 0.0.0.0:* LISTEN 1008/kodi.bin tcp 0 0 127.0.0.1:39301 0.0.0.0:* LISTEN 1008/kodi.bin tcp 0 0 0.0.0.0:4713 0.0.0.0:* LISTEN 270/pulseaudio tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 978/smbd tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1/systemd tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 1008/kodi.bin tcp 0 0 127.0.0.1:52307 0.0.0.0:* LISTEN 1008/kodi.bin tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 337/sshd tcp 0 0 0.0.0.0:36666 0.0.0.0:* LISTEN 1008/kodi.bin tcp 0 0 :::445 :::* LISTEN 978/smbd tcp 0 0 :::4713 :::* LISTEN 270/pulseaudio tcp 0 0 :::139 :::* LISTEN 978/smbd tcp 0 0 :::111 :::* LISTEN 1/systemd tcp 0 0 :::8080 :::* LISTEN 1008/kodi.bin tcp 0 0 :::22 :::* LISTEN 337/sshd tcp 0 0 :::36666 :::* LISTEN 1008/kodi.bin
Oh wow, ok geez! Ok thanks man. Well that’s definitely going to be super helpful with my problem.
I can’t for the life of me, recall WHY I need zeroconf for kodi but I’m fairly sure it’s quite important (might be using my Kodi Android / iOS remote app?)