Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Error: Service name is already in use on the network
See original GitHub issuenode --version => v10.5.0 homebridge --version =>0.4.44 avahi-daemon =>avahi-daemon 0.6.31 pfSense is also running avahi-daemon 0.6.31 to reflect across multiple subnets
Usage: I’m working on a plugin and stop/starting Homebridge from CLI on a pi3b. /usr/bin/homebridge --debug --plugin-path /home/homebridge/npm/ Everything works as it should except:
Problem:
Every time I stop with SIGINT and restart, I get:
### events.js:167 throw er; // Unhandled 'error' event ^
Error: Service name is already in use on the network at Registry._onProbeComplete (/usr/lib/node_modules/homebridge/node_modules/bonjour-hap/lib/Registry.js:106:27)
This never happened on my old installation and I can’t figure out what’s changed. If I stop/start avahi-daemon on pfSense it will work again. So, this may not be a problem with Homebridge but that’s the only time it manifests itself.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I am still getting same error. I even uninstalled libavahi-compat-libdnssd-dev
i tried different things and couldn’t fix it, so for now i update my local server.js code to use following line in _createBridge to get random number added to name
(bridgeConfig.name || ‘Homebridge’) + “-” + Math.floor((Math.random() * 1000) + 1)
Make sure only one avahi is running in your network. I’m using OpenWRT and had 2 instances running.