Intermittent discovery issues

[yangm97]

It appears that I'm having some intermittent discovery issues. I have avahi running on the same machine and this pops up on the avahi log:

*** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***

I wonder if that is somehow related?

[brutella]

I wonder if that is somehow related?

Yes, this library uses dnssd to make the accessory discoverable on the local network.

[yangm97]

I see. What would be the cleanest way to solve this issue? Drop avahi and change the dnssd listen method to take a dnssd object, which would be initialized with my other services?

[brutella]

I think that the best way would be to just use Avahi where possible (ex. on Linux).

[brutella]

A random thought just came to my mind, which may resolve this issue.

What about setting the hostname of the announced Bonjour service NOT to the local hostname?
You would have to explicitly set the Host in the dnssd.Config like so:

dnsCfg := dnssd.Config{
    ....
    Host: "Testing",
    ....
}

Does this help?

[brutella]

Could you please test it with the hostname branch?

[yangm97]

Sure!

[yangm97]

Instead of getting a red "Unreachable" message I now get this gray "Unavailable", otherwise it's the same deal as before (reachable from iPhone but not from mac).

I will try disabling avahi so we can isolate that.

[yangm97]

homed log is a bit spammy, do you know what I should be looking for when this happens?

[brutella]

Re: Unavailable What type of accessories are you creating? Looks like they are incompatible with Apple Home.

[yangm97]

Pretty sure they're compatible, since that message comes and goes. I could take some snippets from my code if that helps though, but I guess it is just standard stuff.

We have this issue too, with any configuration, including hklight. The Bridge/Accessory shows up in Discovery under the hap service for anywhere from 5 minutes to a day, but eventually vanishes and only returns when restarting the process - it also turns unavailable in homekit at the same time.

We previously ran homebridge on the same box, but don't anymore, just a single hc instance. Nothing else binding to udp/5353.

Debug logs show nothing about discovery, only the hub and other clients eventually disconnecting.

[brutella]

@schittler Are you using the latest version 1.2.2 of hc?

yes, our go.mod looks like this:

go 1.14

require (
	github.com/brutella/hc v1.2.2
	github.com/miekg/dns v1.1.29 // indirect
	github.com/rs/zerolog v1.18.0
	github.com/spf13/cobra v1.0.0
	github.com/spf13/viper v1.4.0
	github.com/xiam/to v0.0.0-20200126224905-d60d31e03561 // indirect
	golang.org/x/crypto v0.0.0-20200510223506-06a226fb4e37 // indirect
	golang.org/x/net v0.0.0-20200513185701-a91f0712d120 // indirect
	golang.org/x/sys v0.0.0-20200515095857-1151b9dac4a9 // indirect
)

[brutella]

On what hardware are you running it?