-
-
Notifications
You must be signed in to change notification settings - Fork 632
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v0.11.0 fails on Synology #993
Comments
For comparison, here's the log output in Homebridge v1.5.9:
|
Reading the logs there are two important lines here:
The last line refers to a feature failing introduced with PR #970 which registers to the Server.StateChanged interface to be notified about avahi server restarts. That's my currently analysis of the problem. I will investigate further. One possibility is to just gracefully continue if the dbus interface is not found, see: HAP-NodeJS/src/lib/Advertiser.ts Lines 416 to 417 in e39faf0
But ideally we find a solution that enables restart detection also for < avahi 0.8 daemons. Thanks for reporting this issue 🚀 |
Looking at the diff between 0.7 and 0.8, there are now changes in regard to the dbus interface used: avahi/avahi@v0.7...v0.8#diff-cda9c20b8570353458c309abfcddcac2c9be7b6fca607ef7b702a7d489ed1648 |
Your test in the PR also uses avahi 0.7? See #970 (comment) |
You are indeed right. I was probably still running ubuntu 20.04 back then. Is there anyway to replicate the synology environment, is there a docker image or something? |
For reference, the error comes from here within dbus-native: It is called by |
You could try to manually debug, by adding a |
I think Synology supports multiple DSM installations on the same DiskStation through virtualisation, but I never looked into that. I doubt DSM will run on non-Synology hardware. In my experience, Synology tends to modify standard software, e.g. they run their own build of So “interface” in the error message refers to the |
Exactly. And the issue also only evolves around the For our other commands we use the |
The result is just a newline. The xml reads:
|
Hm. I mean, we could incorporate a workaround where we just don't care about hooking the |
That's an old one, my Raspberry Pi servers running bullseye report 1.12.24 (with the same 2002, 2003 copyright message).
Nothing here that we didn't already know. |
ping @adriancable, any ideas on this? |
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. |
I installed a workaround in the latest beta release of hap-nodejs 0.11.1 and homebridhe 1.6.1. |
Analysis
Homebridge v1.6.0, or rather HAP-NodeJS v0.11.0 doesn't work on my Synlogy. I'm getting an error
Could not create mDNS advertisement. The HAP-Server won't be discoverable: Error: No such interface found
Haven't changed anything on my config; reverting to Homebridge v1.5.9 / HAP-NodeJS v0.10.4 solves the issue.
Using Avahi as advertiser.
I'm running a DS920+ and a DS918+, both on DSM 7.1.1. Both use link aggregation; the interface name is ovs_bond0. The Homebridge UI does find this interface, and displays the network activity graph.
Expected Behavior
HAP-NodeJS should advertise itself.
Steps To Reproduce
Upgrade Homebridge to v1.6.0 on Synology with
avahi
as advertiser.Logs
Configuration
Environment
Process Supervisor
hb-service
Additional Context
I think the check through
dbus
whether Avahi is running doesn't work on Synology. I do have adbus
process running, though.The text was updated successfully, but these errors were encountered: