Fatal error browsing for DACP services \ {"code":-3008 #10
Comments
|
Any more info? Any other plugins running? WiFi or Ethernet? What system? I haven't seen this and don't know what could cause it. |
|
Hi Other plugins run just fine (like homematic etc). Home app discovers all devices. Fatal error browsing for DACP services: |
|
Hi Unfortunately problem remains. Any specific port DACP must be able to use? 2018-1-5 22:37:17] [DACP] Found accessory in config: "Apple TV (Living room)" |
|
It needs MDNS to work. But it wouldn’t have paired without it in the first place. Did you make any changes after/during pairing? |
|
Just found this: agnat/node_mdns#130 I guess there’s a patch to be made to the MDNS browsing code. |
|
Hi Thx for helping! |
|
I just pushed 0.7.6 to npm. I'm not sure if that fixes it as I already had a custom resolver sequence in there. Could you please verify? |
|
Will do asap.. will let you know! Thx a million! |
|
No luck.. upgraded and restarted homebridge. Same error occurs. |
|
Hmm. If it's not too much to ask, could you reset your homebridge configuration and run the plugin with a new remote without pairing key? I don't really think that makes a difference due to the code structure, but who knows. |
|
Okay.. so removed the other plug in I used and cleared the config. [2018-1-6 20:00:46] [homebridge-config-ui-x] Logs cleared by Administrator. |
|
Now changed config to reflect: } After restart, this is the log [2018-1-6 20:09:52] Loading 1 platforms... |
|
Let me know what to do next... |
|
Does it start now without the error you reported?
|
|
Yes, it‘s here..:-( 2018-1-6 20:11:52] [DACP] Starting DACP browser... |
|
:( |
|
If it helps at all. 2018-1-6 20:24:46] Got SIGTERM, shutting down Homebridge... [2018-1-6 20:24:55] [DACP] Starting DACP browser... |
|
So.. remote is made visible to apple tv, pairing also.. but everything after that fails.. |
|
Deactivated any bonjour service running on the Synology and rebooted the NAS.. still no luck.. |
|
Hey, I just saw that you're using Node JS 4.8.4 - could you upgrade to 8.9.3? That's the version that I develop upon and it seems as if the low level interface between the mdns library and node.js may have changed. |
|
Also what's the version of homebridge in the docker container? 1.0.4 is not the homebridge version, the current one is 0.4.33. |
|
Hi Guess I‘ll have to wait until the release 8.9.3 |
|
Just realized that homebridge is running within docker (sorry, new to docker so I did not think about it earlier). |
|
So, figured out that nodeJS in the container I use to run Homebrigde uses NodeJS 8.9.3. If it helps, this is the docker container I use to run Homebridge: https://hub.docker.com/r/oznu/homebridge/ |
|
I've updated homebridge-dacp to use the bonjour package instead of the previously used mdns package. Since I plan to release 0.8.0 next week I'm looking for early feedback if this also solves the docker issues you all have been seeing. Could you please verify by:
and running it again? Feedback appreciated. |
|
Hey thanks for the update. I installed from GitHub, and when start homebridge I get the same error, followed by a type error. Also I think the 3008 error is coming from src/dacp/DacpBrowser.js, but the code still seems to reference mdns (unless the lib was changed somewhere higher up the chain haha). |
|
You're still using the old version. Please use the latest code from github - see the instructions above. If needed, please uninstall the old version first using |
|
Thanks! I actually did do that, and have the same results.. I confirmed I have the latest version by confirming the new example and changelog entries are present in the installed version. Is there another branch? The code I was referencing is not from my machine, its still live on GitHub https://github.com/grover/homebridge-dacp/blob/master/src/dacp/DacpBrowser.js Sorry if I've missed something.. |
|
Turns out I missed to push the change. Please try again. Sorry. |
|
Alright got the new version installed. Definitely using bonjour instead of the mdns package now, but sadly it looks like bonjour still makes a call to getaddrinfo. |
|
I assume you're running homebridge in a container as the others? |
|
That's the issue! I can't believe I didn't think to check that. I looked into it more and it seems like the Alpine OS does not support search domains (like local). Ugh. I had only tried to ping the IP before (which works fine as you can see below). https://github.com/gliderlabs/docker-alpine/blob/master/docs/caveats.md Would it be possible to have an optional setting for manual IP? If not I could probably just roll my own Ubuntu container to avoid the issue. |
|
Ha! We're getting closer - at least for Alpine Linux. The name resolution of .local domains is not run through regular DNS, but rather through Avahi with the help of nsswitch.conf. Alpine however doesn't have this facility and the configuration file was removed there. As such Alpine will never be able to resolve .local domains at all. I guess I'll have to include an IP option to resolve the Apple TV and hope that the DACP port doesn't change randomly. Thanks @quacktacular, this is clearer now. |
|
Just to add: The proper solution would be to enable resolution of .local domains through Avahi inside the container, but I can't help with that as I have no experience with Alpine. |
|
I've just pushed another update with some changes from @oznu - specifically the use-referer feature was added. @quacktacular could you enable that in your config.json and try again? I'm a bit curious as @oznu also reported pairing issues that you didn't seem to have. |
|
Hey @grover I only had a couple minutes to test this morning, but it looks like the control portion is working. Only tried the modified play plays control in Home so far. I did not try to re-pair (using a pairing code generated from the mDNS version) this morning, but I did last night. It didn’t work with Bomjour. Asked for my pairing code onscreen the Apple TV and got stuck there. Can try more after work. |
|
Hey @grover Thx very much for trying to get a fix here. Highly appreciate it. |
|
It's not a question of trouble, but rather: Does the version already do what it should do? As such there's only one remaining issue and that's getting feedback if this is working. Apparently the bonjour stuff does help a bit, but breaks the pairing... :( |
|
If someone could try to pair again with the latest version and capture a tcpdump of all udp and tcp traffic in their docker container, that would help me tremendously to figure out the pairing problem with bonjour. |
|
@grover confirmed the pairing issue is still present. Here's a tcpdump during the pairing request. Lots of garbage from other services though haha (they are running on other machines). |
|
Hi @grover, If you can't get Bonjour working correctly without to much effort, then perhaps this solution will work (based on your master branch before you swapped to use bonjour): https://github.com/oznu/homebridge-dacp/commit/ed998cd670707e24cf8587096d8cf64ee366895a
|
|
@oznu Nice! There's just too many MDNS implementations for JS. Let me ponder over this a bit as I really wanted to get rid of the |
|
I've applied the branch @oznu gave in a slightly different manner adding IPv6 support for those few that are IPv6 only. This keeps the MDNS library around for now, but I'll plan to get rid of it in a release or two. If you could verify it again? |
|
Works for me. |
|
Also pairing? If so, then I'll release this version. |
|
Pairing works for me as well. Nice work! |
Added support to start preconfigured playlists Bugfixes for issue #10 (getaddrinfo fails to resolve Bonjour .local addresses)
|
Hi |
|
@grover I think I have a similar problem with mdns as of today. DACP plugin v0.9.1, Homebridge v0.4.38, node v9.9.0:
|
Hi.. Happy new year to you and thx for developing on this project.
Hope I‘m not raising a duplicate to another issue, but encountered this tonight when trying to setup my apple tv 4gen for homebridge.
Was able to successfully pair the apple tv but then it always would end in error saying Apple TV is down.
Thx for looking into it!
[2018-1-3 00:47:08] [DACP]
[2018-1-3 00:49:08] [DACP] Starting DACP browser...
[2018-1-3 00:49:08] [DACP] Fatal error browsing for DACP services:
[2018-1-3 00:49:08] [DACP]
[2018-1-3 00:49:08] [DACP] Error: {"code":-3008,"errno":-3008,"syscall":"getaddrinfo"}
[2018-1-3 00:49:08] [DACP]
[2018-1-3 00:49:08] [DACP] Restarting MDNS browser for DACP in 120 seconds
The text was updated successfully, but these errors were encountered: