Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Homebridge listens on tcp6 only #1277
I have two HomeBridge instances running. The problematic one is on Debian:
It listens on IPv6 only, but is advertised with IPv4 and IPv6:
Another instance on a Mac works fine:
This one listens on both, IPv4 and IPv6 and is advertised as such.
How can I force hombridge to use both, IPv4 and IPv6 or advertise IPv6 only?
same issue here (raspbian - rasp b+).
This problem has been already discussed before, but, usually they solved it by reinstalling a fresh version of homebridge or disabling tcp6. Both solution doesn't work for me.
Bonjour browser detect Homebridge at x.x.x.x:51824 and also homekit find the accessory, but pairing always fail.
This the result of the way nodejs creates the server socket, see here:
It looks like the behaviour of nodejs on Ubuntu/Debian has changed, it opens only a tcp6 socket.
It is easy to test it, if you start a simple server:
The solution is to modify hap-nodejs to create a tcp4 server socket or both.
A quick fix is to modify eventedhttp.js in /usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util, in line 60:
This issue has been automatically marked as stale because it has not had recent activity, and will be closed if no further activity occurs. If this issue was overlooked, forgotten, or should remain open for any other reason, please reply here to call attention to it and remove the stale status. Thank you for your contributions.
This was referenced
Dec 26, 2018
For everyone running the docker image, adding the following to