Closed taw123 closed 3 weeks ago
FYI- I also verified the socket and location of the Avahi-daemon on the host
[~] # ls -la /var/run/dbus
lrwxrwxrwx 1 admin administrators 35 2024-03-06 04:31 /var/run/dbus -> /mnt/ext/opt/avahi0630/var/run/dbus/
[~] # ls -la /var/run/avahi-daemon/socket
srwxrwxrwx 1 guest guest 0 2024-03-06 04:32 /var/run/avahi-daemon/socket=
And of course verified NON HomeBridge based, QNAP-hosted mDNS (avahi-daemon) Network service discovery continues to work fine (SMB, etc).
Not a dig against the devs here, and I would help if they wanted but...
It seems like mDNS support here STILL is an issue and the best approach for ME.... Despite not making sense from a performance or network arch strategy... is to go back to approach I took years ago and implement an entire second network stack using MACLAN then run HomeBridge's mDNS advertising via avahi on it's own MAC address.
As I said I am still willing to help with diagnostics/dev/etc if you have the cycles to engage otherwise I'll assume that it's just not a good time for you and will implement as I mentioned in a week. Thanks again for all your work on HB I understand one doesn't always have cycles to respond/update.
All the best. --T
@taw123 I’m currently on vacation and don’t have access to look at this. I will be back in a few weeks and can look at this then. If you want to start a pull request, can look at it then.
PS GitHub needs a ‘out of office’ function
Just a friendly/respectful ping SOLELY to ensure that a Bot doesn't prematurely close this before you get cycles "back in the office" ;)
I have the exact same issue, avahi daemon works on host, links are there but still that
[Homebridge] The selected advertiser, "avahi", isn't available on this platform. Reverting to "bonjour-hap"
during startup
Actually, was able to resolve this. In my case it turned out that the host's avahi wasn't running with dbus. Installing (apt-get update && apt-get install avahi-utils iputils-ping -y
) and running avahi-browse -a
on the guest (homebridge) with docker exec -it homebridge bash made it clear that the issue wasn't with homebridge itself. I had to properly setup dbus on the host and then restart avahi with enable-dbus=yes
set in /etc/avahi/avahi-daemon.conf
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been closed as no further activity has occurred.
Current Situation
To be concise I am going to leave out some history regarding PRIOR use (5 or so years ago when I did have things working, then later broke in an update and changes to service advertising).....
Compose:
Per wiki
I am still seeing msgs in the console indicating what I expectted to be that HB calls from it's AVHI implementation being passed to the system daemon are in fact it appears CONFLICTING with the system service.
Clearly I must be missing something here.... Just not sure what... as I CAN see the HB controller IS being advertised on the network, and can add it to iOS due to it reverting to advertising via bonjour-hap
Logs
Configuration
clean container for testing purposes. No default/generated config
Environment
Docker Image: HOMEBRIDGE_PKG_VERSION=1.1.6 FFMPEG_VERSION=v2.1.1 Hosted on QNAP Hero: 5.1.x (with avhi service advertising active) Home Assistant: (2024.3), also running in Docker Host mode (without issue) running both HK Bridge & HK Device (need to use HB for legacy AMP integration (Onkyo) and potentially for extended TV support (Tizen Samsung) I both working perviously.
Process Supervisor
Docker (Mention image name in
Additional Context
)Additional Context
homebridge/homebridge:latest Container pulled: 2024-03-11