-
Notifications
You must be signed in to change notification settings - Fork 512
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possible mDNS conflict? #2
Comments
Thank you for submitting an issue. This add-on is not tested on a generic Linux Hass.io installation, but it "should" not be a problem. Nevertheless, you have a valid issue on your hands. Could you be so kind and try stopping the mDNS on the docker host, just for the sake of checking if this is actually causing the issue? |
Interesting.. If I disable avahi-daemon on the host it settles on hassio-2 and then continues on to start. Mind you the Home app refuses to accept the pin it generated. I've deleted the entire home bridge folder and restarted so that it would generate a new code but that didn't help. Nothing in the logs about the Home app trying to connect (even with debug on).
|
BTW, I noticed the pins are always generated as 290--22-311 (with the double dash.. Is this s bug? |
That last one looks like a bug, could you please create a separate issue for this? |
Getting something similar when adding plugins. *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** |
@frenck many thanks. is it fixable? |
I've moved this issue to the dedicated GitHub repository of the Homebridge addon. For more information and the tracking of the progress of this issue, please see: |
This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread. |
I am witnessing the below behaviour on a generic linux hassio install:
It just keeps going and incrementing the host name.
It may be relevant that the docker host itself is running mDNS on 192.168.1.123 (for the purposes of mosquitto container auto discovery as that's not built into the add-on).
The text was updated successfully, but these errors were encountered: