Unable to find avahi daemon with default options

[gauntface]

I have a raspberry pi on my network that I can ping with it's local domain and can discover with avahi-browse -all, but spread-the-word doesn't seem to work.

I assume I'm doing something wrong:

 stw
  .on("up", (remoteService, res, referrer) => {
    console.log(`${remoteService.name} is up! (from ${referrer.address})`);
  })
  .on("down", (remoteService, res, referrer) => {
    console.log(`${remoteService.name} is down! (from ${referrer.address})`);
  });

  stw.listen();

I was able to find another device on the network, so something is working. Any ideas / tips for debugging this?

[ardean]

Hello @gauntface

Thank you for your interest in stw.
I compared Avahi's search results with stw and found out that certain devices do not always send all necessary information to detect a service. In v0.7.0 I have now improved the finding of services by searching and querying for unresolved entries in an interval.

Also, I fixed a bug where only one service per host was found.

If you still have trouble finding services, you can debug stw:

> DEBUG=SpreadTheWord:* npm start

Let me know how it is with v0.7.0.