I just set up Mopidy on a Raspberry Pi running OSMC (Debian Jessie based distribution with preconfigured Kodi).
Everything is working fine, except zeroconf.
The published services, _mopidy-http._tcp and _mpd._tcp are announced but can’t be resolved.
It turns out this is caused by self.host being set to localhost6.localdomain6.local when calling:
I would check what the hostname command on the machine thinks, and what the /etc/hostname file and possibly /etc/hosts is setup with. As for “solving” this in mopidy, we could a config to override the host name used in zeroconf, but likely the better fix is to make sure that socket.getfqdn() does the right thing on your system.
I just realized that I forgot to report back that passing an empty string to AddService, as suggested in the official avahi documentation, results in the backend succesfully publishing the service.
The change, around line 60 in zeroconf.py, changed from:
Should I file a bug report in the mopidy issue tracker?
This probably affects more users than myself seeing that the existing code will cause publishing of the mopidy service on localhost6.localdomain6 if it is present in /etc/hosts as described in my previous posts.