Synology: Host name conflict #35
Comments
|
I have tried to test this by installing Plex (which also uses Avahi) on DSM (6.1.3 Update 6) then launching the homebridge container, but haven't been able to replicate this error. I also tried adding a second network interface but was still unable to replicate the issue. A few things you could try. 1. Try disabling IPv6.
2. Try with Bonjour services both on and off.
|
|
Thank you @oznu ! IPv6 was off from the beginning (yes, really). I tried it with IPv6 set to Auto, but the same thing happens. My router has IPv6 disabled as well and the Synology does not get a local IPv6 address. I believe the IPv6 address is applied by the Docker daemon. Bonjour services were on. I tried it with Bonjour off, but again, the same thing happens. When Plex is not running, again the same thing happens. I'm a bit confused because your image was working fine! I merely reinstalled all packages because I migrated my volume to btrfs. Just to try it, i ran it with an empty |
|
I'm not sure if it will fix the problem, but I've pushed up a change to the Avahi config. You can test it out by downloading the latest image. I also came across these:
Other people have experienced the same |
|
Thank you, I will try. Interestingly enough, if I run the docker image manually, there are no errors:
|
|
Here is the relevant output if I run your newly pushed image manually, using the command above: There are no errors. I deleted the container created by the Docker UI in Synology and created it through the command line. Now it appears to work! I can stop and start the container through the UI as well. Just for testing, I recreated the same container again through the UI and again it fails. I'm not sure what the UI is doing differently, but something seems to be messing up the configuration. I have to wait until I'm home to pair the iOS device with homebridge. Will update in a couple of hours! |
|
Thanks for testing this. Would you be able to provide the json output from a |
|
Sure, and I did that already as one of the first things. There are no notable differences as far as I can see: Created through UI: [
{
"Id": "ca178ef672c15c2e3a2162edb5e7263ba9846bd95b82dd75a6209059df64661d",
"Created": "2017-11-14T14:18:57.934229642Z",
"Path": "/init",
"Args": [],
"State": {
"Status": "running",
"Running": true,
"Paused": false,
"Restarting": false,
"OOMKilled": false,
"Dead": false,
"Pid": 16433,
"ExitCode": 0,
"Error": "",
"StartedAt": "2017-11-14T14:19:24.802324475Z",
"FinishedAt": "0001-01-01T00:00:00Z",
"StartedTs": 1510669164,
"FinishedTs": -62135596800
},
"Image": "sha256:830673d6749e9dc4bf859c43f50247506e31799c3fc1a7938ee5a5c9e60a8acb",
"ResolvConfPath": "/volume1/@docker/containers/ca178ef672c15c2e3a2162edb5e7263ba9846bd95b82dd75a6209059df64661d/resolv.conf",
"HostnamePath": "/volume1/@docker/containers/ca178ef672c15c2e3a2162edb5e7263ba9846bd95b82dd75a6209059df64661d/hostname",
"HostsPath": "/volume1/@docker/containers/ca178ef672c15c2e3a2162edb5e7263ba9846bd95b82dd75a6209059df64661d/hosts",
"LogPath": "/volume1/@docker/containers/ca178ef672c15c2e3a2162edb5e7263ba9846bd95b82dd75a6209059df64661d/log.db",
"Name": "/homebridge-test",
"RestartCount": 0,
"Driver": "btrfs",
"MountLabel": "",
"ProcessLabel": "",
"AppArmorProfile": "docker-default",
"ExecIDs": null,
"HostConfig": {
"Binds": [],
"ContainerIDFile": "",
"LogConfig": {
"Type": "db",
"Config": {}
},
"NetworkMode": "host",
"PortBindings": null,
"RestartPolicy": {
"Name": "no",
"MaximumRetryCount": 0
},
"AutoRemove": false,
"VolumeDriver": "",
"VolumesFrom": null,
"CapAdd": [],
"CapDrop": [],
"Dns": null,
"DnsOptions": null,
"DnsSearch": null,
"ExtraHosts": null,
"GroupAdd": null,
"IpcMode": "",
"Cgroup": "",
"Links": null,
"OomScoreAdj": 0,
"PidMode": "",
"Privileged": false,
"PublishAllPorts": false,
"ReadonlyRootfs": false,
"SecurityOpt": null,
"UTSMode": "",
"UsernsMode": "",
"ShmSize": 67108864,
"Runtime": "runc",
"Env": [
"PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
"ARCH=amd64",
"NPM_CONFIG_LOGLEVEL=info",
"NODE_VERSION=8.9.0",
"YARN_VERSION=1.2.1",
"HOMEBRIDGE_VERSION=0.4.31",
"S6_KEEP_ENV=1",
"PUID=1024",
"GUID=100"
],
"ConsoleSize": [
0,
0
],
"Isolation": "",
"CpuShares": 50,
"Memory": 0,
"NanoCpus": 0,
"CgroupParent": "",
"BlkioWeight": 0,
"BlkioWeightDevice": null,
"BlkioDeviceReadBps": null,
"BlkioDeviceWriteBps": null,
"BlkioDeviceReadIOps": null,
"BlkioDeviceWriteIOps": null,
"CpuPeriod": 0,
"CpuQuota": 0,
"CpuRealtimePeriod": 0,
"CpuRealtimeRuntime": 0,
"CpusetCpus": "",
"CpusetMems": "",
"Devices": [],
"DeviceCgroupRules": null,
"DiskQuota": 0,
"KernelMemory": 0,
"MemoryReservation": 0,
"MemorySwap": -1,
"MemorySwappiness": -1,
"OomKillDisable": false,
"PidsLimit": 0,
"Ulimits": null,
"CpuCount": 0,
"CpuPercent": 0,
"IOMaximumIOps": 0,
"IOMaximumBandwidth": 0
},
"GraphDriver": {
"Data": null,
"Name": "btrfs"
},
"SynoStatus": "running",
"Mounts": [
{
"Type": "volume",
"Name": "e2fbcca290011f69116bd85f5cc73b0e84151bfb31084065acd82839d9eea904",
"Source": "/volume1/@docker/volumes/e2fbcca290011f69116bd85f5cc73b0e84151bfb31084065acd82839d9eea904/_data",
"Destination": "/homebridge",
"Driver": "local",
"Mode": "",
"RW": true,
"Propagation": ""
}
],
"Config": {
"Hostname": "homebridge-test",
"Domainname": "",
"User": "",
"AttachStdin": false,
"AttachStdout": false,
"AttachStderr": false,
"Tty": true,
"OpenStdin": true,
"StdinOnce": false,
"Env": [
"PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
"ARCH=amd64",
"NPM_CONFIG_LOGLEVEL=info",
"NODE_VERSION=8.9.0",
"YARN_VERSION=1.2.1",
"HOMEBRIDGE_VERSION=0.4.31",
"S6_KEEP_ENV=1",
"PUID=1024",
"GUID=100"
],
"Cmd": null,
"ArgsEscaped": true,
"Image": "oznu/homebridge",
"Volumes": {
"/homebridge": {}
},
"WorkingDir": "/homebridge",
"Entrypoint": [
"/init"
],
"OnBuild": null,
"Labels": {},
"DDSM": false
},
"NetworkSettings": {
"Bridge": "",
"SandboxID": "61f698d57085823b6b8affa3f26900209151073bcca89cc2077ec5eb9eb89afa",
"HairpinMode": false,
"LinkLocalIPv6Address": "",
"LinkLocalIPv6PrefixLen": 0,
"Ports": {},
"SandboxKey": "/var/run/docker/netns/default",
"SecondaryIPAddresses": null,
"SecondaryIPv6Addresses": null,
"EndpointID": "",
"Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"IPAddress": "",
"IPPrefixLen": 0,
"IPv6Gateway": "",
"MacAddress": "",
"Networks": {
"host": {
"IPAMConfig": null,
"Links": null,
"Aliases": null,
"NetworkID": "344b9c826297c6049a17d076fada038cde076711de3fa5f7a37d56fd52c88ff2",
"EndpointID": "a5a1de3160ae1a14747303f0118e7a8547c5d2ee6799db536112d8d8fa61724f",
"Gateway": "",
"IPAddress": "",
"IPPrefixLen": 0,
"IPv6Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"MacAddress": ""
}
}
}
}
]Created via CLI: [
{
"Id": "08a9b420362ce322c0f075bfe86ee40c29a81e3b16a4ff355b01fa9565b09b18",
"Created": "2017-11-13T12:32:09.734074861Z",
"Path": "/init",
"Args": [],
"State": {
"Status": "running",
"Running": true,
"Paused": false,
"Restarting": false,
"OOMKilled": false,
"Dead": false,
"Pid": 32183,
"ExitCode": 0,
"Error": "",
"StartedAt": "2017-11-13T13:48:02.695941573Z",
"FinishedAt": "2017-11-13T13:47:22.960600849Z",
"StartedTs": 1510580882,
"FinishedTs": 1510580842
},
"Image": "sha256:830673d6749e9dc4bf859c43f50247506e31799c3fc1a7938ee5a5c9e60a8acb",
"ResolvConfPath": "/volume1/@docker/containers/08a9b420362ce322c0f075bfe86ee40c29a81e3b16a4ff355b01fa9565b09b18/resolv.conf",
"HostnamePath": "/volume1/@docker/containers/08a9b420362ce322c0f075bfe86ee40c29a81e3b16a4ff355b01fa9565b09b18/hostname",
"HostsPath": "/volume1/@docker/containers/08a9b420362ce322c0f075bfe86ee40c29a81e3b16a4ff355b01fa9565b09b18/hosts",
"LogPath": "/volume1/@docker/containers/08a9b420362ce322c0f075bfe86ee40c29a81e3b16a4ff355b01fa9565b09b18/log.db",
"Name": "/homebridge",
"RestartCount": 0,
"Driver": "btrfs",
"MountLabel": "",
"ProcessLabel": "",
"AppArmorProfile": "docker-default",
"ExecIDs": null,
"HostConfig": {
"Binds": [
"/volume1/docker/homebridge/:/homebridge"
],
"ContainerIDFile": "",
"LogConfig": {
"Type": "db",
"Config": {}
},
"NetworkMode": "host",
"PortBindings": {},
"RestartPolicy": {
"Name": "no",
"MaximumRetryCount": 0
},
"AutoRemove": false,
"VolumeDriver": "",
"VolumesFrom": null,
"CapAdd": null,
"CapDrop": null,
"Dns": [],
"DnsOptions": [],
"DnsSearch": [],
"ExtraHosts": null,
"GroupAdd": null,
"IpcMode": "",
"Cgroup": "",
"Links": null,
"OomScoreAdj": 0,
"PidMode": "",
"Privileged": false,
"PublishAllPorts": false,
"ReadonlyRootfs": false,
"SecurityOpt": null,
"UTSMode": "",
"UsernsMode": "",
"ShmSize": 67108864,
"Runtime": "runc",
"Env": [
"PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
"ARCH=amd64",
"NPM_CONFIG_LOGLEVEL=info",
"NODE_VERSION=8.9.0",
"YARN_VERSION=1.2.1",
"HOMEBRIDGE_VERSION=0.4.31",
"S6_KEEP_ENV=1",
"PUID=1024",
"GUID=100"
],
"ConsoleSize": [
0,
0
],
"Isolation": "",
"CpuShares": 0,
"Memory": 0,
"NanoCpus": 0,
"CgroupParent": "",
"BlkioWeight": 0,
"BlkioWeightDevice": null,
"BlkioDeviceReadBps": null,
"BlkioDeviceWriteBps": null,
"BlkioDeviceReadIOps": null,
"BlkioDeviceWriteIOps": null,
"CpuPeriod": 0,
"CpuQuota": 0,
"CpuRealtimePeriod": 0,
"CpuRealtimeRuntime": 0,
"CpusetCpus": "",
"CpusetMems": "",
"Devices": [],
"DeviceCgroupRules": null,
"DiskQuota": 0,
"KernelMemory": 0,
"MemoryReservation": 0,
"MemorySwap": 0,
"MemorySwappiness": -1,
"OomKillDisable": false,
"PidsLimit": 0,
"Ulimits": null,
"CpuCount": 0,
"CpuPercent": 0,
"IOMaximumIOps": 0,
"IOMaximumBandwidth": 0
},
"GraphDriver": {
"Data": null,
"Name": "btrfs"
},
"SynoStatus": "running",
"Mounts": [
{
"Type": "bind",
"Source": "/volume1/docker/homebridge",
"Destination": "/homebridge",
"Mode": "",
"RW": true,
"Propagation": ""
}
],
"Config": {
"Hostname": "stark",
"Domainname": "",
"User": "",
"AttachStdin": true,
"AttachStdout": true,
"AttachStderr": true,
"Tty": true,
"OpenStdin": true,
"StdinOnce": true,
"Env": [
"PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
"ARCH=amd64",
"NPM_CONFIG_LOGLEVEL=info",
"NODE_VERSION=8.9.0",
"YARN_VERSION=1.2.1",
"HOMEBRIDGE_VERSION=0.4.31",
"S6_KEEP_ENV=1",
"PUID=1024",
"GUID=100"
],
"Cmd": null,
"ArgsEscaped": true,
"Image": "oznu/homebridge",
"Volumes": {
"/homebridge": {}
},
"WorkingDir": "/homebridge",
"Entrypoint": [
"/init"
],
"OnBuild": null,
"Labels": {},
"DDSM": false
},
"NetworkSettings": {
"Bridge": "",
"SandboxID": "e43dada53caceb9ebf716e1724cbbcb05b2a507587efca7b36753f393d0c1065",
"HairpinMode": false,
"LinkLocalIPv6Address": "",
"LinkLocalIPv6PrefixLen": 0,
"Ports": {},
"SandboxKey": "/var/run/docker/netns/default",
"SecondaryIPAddresses": null,
"SecondaryIPv6Addresses": null,
"EndpointID": "",
"Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"IPAddress": "",
"IPPrefixLen": 0,
"IPv6Gateway": "",
"MacAddress": "",
"Networks": {
"host": {
"IPAMConfig": null,
"Links": null,
"Aliases": null,
"NetworkID": "344b9c826297c6049a17d076fada038cde076711de3fa5f7a37d56fd52c88ff2",
"EndpointID": "975ebab85567088a6c5178857651086f0fa8d9a2b9c1380a147823f2264ef48b",
"Gateway": "",
"IPAddress": "",
"IPPrefixLen": 0,
"IPv6Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"MacAddress": ""
}
}
}
}
]Binds are empty because I haven't mapped a config for the GUI-created test container. Other than that, I see no major differences! |
|
The only difference that I can see is the When using For some reason the hostname of the container created from the GUI is I tested this by creating a new container on the latest DSM (DSM 6.1.4-15217 Update 1) with the latest Docker package and checked the I tried overriding the hostname using I'm not sure how the container you are creating via the GUI, with host networking, is picking up a different hostname. |
|
Good catch! Yes, Interestingly, the hostname also changes to So I'm guessing it's an issue with the Docker package or my installation of said package, and not with the Thank you for helping me troubleshoot! Running it from the CLI is perfectly fine for me. |
|
I also have the same issue after upgrading the image. Turning IPv6 didn't change anything (I turned it on just before the upgrade). |
|
@iRonin What versions of DSM and the Synology Docker package are you using? |
|
@oznu Docker 17.05.0-0349 (latest) and DSM 6.1.4-15217 Update 1 (latest) |
|
Good news, well sort of, I have been able to replicate the issue using the latest Docker package - this was not showing up a few days ago. I'll try and figure out a solution. |
|
When creating a container the Synology GUI is more or less sending the equivalent of this command: Support for One potential solution, which I have tested and works, is to override the hostname in the Avahi config. This is set in I'll work on making it so the |
|
FYI, DSM 6.2 (rc) has Docker 17.09.0! |
|
See:
This hostname must match what DSM is using exactly or else it will still fail.
Let me know if this does not work for you. |
|
Right now I'm battling another issue with |
|
Sorry, I haven't pulled the latest image. |
|
Worked after I disabled the bonjour service… |
|
Works, even with enabled bonjour service! Thank you! ❤️ |
|
In trying to solve this problem, and keep it simple to install Homebridge on a Synology, I have put together a Synology Package that will manage the oznu/homebridge container lifecycle. If you two would like to test it out it's available here: https://github.com/oznu/homebridge-syno-spk The package will pull down the latest oznu/homebridge docker image, configure the volume mount for you, and set the Updating to the latest version of homebridge is also much easier, you just have to go into Package Center and execute the |
|
Works for me with Bonjour now too... |
|
@oznu alright, I will try it out! |
|
|
|
It'd be nice if the manager asked for existing homebridge config, not only the share and would allow to specify the share and config folder. |
|
Thanks for testing it out and providing feedback! 😄
It's a bit of a pain to get setup for building from source. The Synology Docs have a mostly correct guide. I'm using Travis CI to build the SPK for each release, you can see the scripts in the
Yes. The current way of upgrading the image using the Synology Docker GUI is tedious and not very reliable, the SPK will check for updates each time it's started, and if an update is available re-create the container with the same settings. I'm using the bundled
As you figured out, the container is just managed by the SPK, you can still view the logs, access the terminal, start and stop the container, and do everything else you normally would using the Synology Docker GUI.
I agree. I can't figure out a way to get a folder selection dialog box to appear in the install wizard, this might not even be possible and is certainly not mentioned in the Synology Docs. I'm thinking of having two options:
This should keep it simple for people who just want to get it up and running, but also satsify those who want more control around where they store their config. |
|
Hello everybody, I'm new in this products and I want to try homebridge on my Synology (1517+). I've a LACP connection with my 4 wire (no IPV6). I try to break my LACP, disconnect 3 of my 4 ports and already nothing on mu iPhone. I add other sources (Fibaro HC2, MelCloud) already nothing. I 've a firewall between my wifi and my internal network (Fortigate 60E with 2 internal and a wan)) I xhek my rules and everything seams to be my fine. (I add a wifi router on my swith directly to exclude the fire wall problema). If someone have an idea ? |
|
Hi Everyone, It seems like the best solution to this problem would be to remove Avahi from the container entirely, doing so will prevent any possible conflicts with other Avahi/Bonjour stacks running on either the docker host or inside another container. Luckily when the hard work done here https://github.com/KhaosT/HAP-NodeJS/pull/495 is merged in we'll be able to do this. In the meantime, I have created a test image which runs a customised version of Homebridge based on that pull request which will allow you to test running Homebridge without Avahi. Just use the For anyone that is still experiencing problems with Feedback from others who already have it working would be great as well. I was able to do a "drop in replacement" of this image and everything just worked - I didn't need to re-pair with my iPhone or reconfigure accessories. Note 1: If you're running any of the following plugins please be aware these depend on Avahi (mdns) to operate and will not work with the homebridge-controllerlink Note 2: If you run multiple instances of Homebridge, each instance will require a different name in the Note 3: You can't install using the |
|
Just to say that I was seeing the errors when using the default image, but I just switched to the no-avahi image and it works great and fixes the issue for me. Thanks for putting that together! |
|
Hey @oznu, just a quick question: Does this also address grover/homebridge-dacp#10 that people have been reporting in homebridge-dacp? It doesn't look like it, but wanted to confirm. If not: Do you have an idea, what's causing getaddrinfo to fail inside the docker containers? Note that I switched the latest version (not published yet) to make use of Bonjour, but still no dice. |
|
@oznu As the developer behind several of those non-functional plugins homebridge-alexa Any thoughts on how to resolve the issue? In each I'm using MDNS device discovery to identify devices on the network. PS I don't have a synolog, but have some users of my plugins reporting issues. |
|
There are two issues. This issue is more about conflicts with other Bonjour/Avahi stacks running that prevents Homebridge running at all. The The issue you referenced is because Alpine Linux lacks nss-mds, so it can't resolve The homebridge-dacp plugin author got it working using this: grover/homebridge-dacp@63ab4b8 |
|
@oznu
Do you know if mdns-js <https://github.com/mdns-js>/node-mdns-js <https://github.com/mdns-js/node-mdns-js> Has the same issue?
Due to other issues I’m switching to that version, the compiling of mdns on various platforms being the biggest.
Tks
… On Mar 10, 2018, at 7:59 PM, oznu ***@***.***> wrote:
@NorthernMan54 <https://github.com/northernman54>,
There are two issues. This issue is more about conflicts with other Bonjour/Avahi stacks running that prevents Homebridge running at all. The no-avahi variant of the image would have prevented your plugins from installing at all so I don't think the referenced issue is related to that comment.
The issue you referenced is because Alpine Linux lacks nss-mds, so it can't resolve .local domains using the system dns. I wrote a small library that resolves the .local domain in pure javascript which solved the problem: mdns-resolver <https://github.com/oznu/mdns-resolver>.
The homebridge-dacp plugin author got it working using this: ***@***.*** <grover/homebridge-dacp@63ab4b8>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#35 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AS5CmKLoi7njptKbRWtniJ1NyswX-Qalks5tdHcDgaJpZM4QaPL_>.
|
|
Hi @NorthernMan54, This library is a pure-javascript implementation of Bonjour which I would recommend, for just discovering devices the master version should be fine: https://www.npmjs.com/package/bonjour A pending pull request for HAP-NodeJS uses this in place of the mdns library. It works great on Linux, macOS and Windows (you don't even need to install Apple Bonjour). The trick to making any of the mdns libraries work on Alpine Linux is to resolve the |
|
@oznu
Tks for the recommendation. I just tried it, and it worked on first try. Much appreciated
… On Mar 11, 2018, at 9:11 PM, oznu ***@***.***> wrote:
Hi @NorthernMan54 <https://github.com/northernman54>,
This library is a pure-javascript implementation of Bonjour which I would recommend, for just discovering devices the master version should be fine:
https://www.npmjs.com/package/bonjour <https://www.npmjs.com/package/bonjour>
A pending pull request for HAP-NodeJS <https://github.com/KhaosT/HAP-NodeJS/pull/495> uses this in place of the mdns library.
It works great on Linux, macOS and Windows (you don't even need to install Apple Bonjour).
The trick to making any of the mdns libraries work on Alpine Linux is to resolve the .local domain to an IP address in JavaScript.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#35 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AS5CmMecUsdl6_QxISxb-J3-3m5vWW-4ks5tdctHgaJpZM4QaPL_>.
|
|
So I used the https://github.com/oznu/homebridge-syno-spk link and it worked perfectly for about a month. I then turned on Bonjour to enable time machine backup. The container will no longer start and I have documented such on the 'Issues' page of syno-spk. I've also disabled bonjour to see whether that would fix the problem. It did not. It seem my issue may be related with this issue, but I am unsure. |
|
Homebridge 0.4.39 has been released and drops the The |
|
After updating the GUI Plugin for Homebridge today, I'm getting the same error as the OP. Homebridge still works fine, I just can't access the GUI anymore. |
|
I used the command inside the Docker image to update and restarted the container. Everything works fine again now. Thanks a lot! |
Its fixed the hostname problem. :) Thank you! |
|
Hi, hier is a couple exemples out of different logs of HB. with setting DSM_HOSTNAME and without. |
|
@giss69 swap to the https://github.com/oznu/docker-homebridge/wiki#image-variants |
|
sorry i've opened a new issue. |
|
Also been having this issue. I'm a new user so don't have any historical knowledge but just chiming in as well. |
|
@stephenjmcmahon this comment is still up-to date: Or use this package: https://github.com/oznu/homebridge-syno-spk And make sure you select the default option (no-avahi) when prompted. |
|
@oznu appreciate the quick reply! I I've spun up no-avahi and will report back I also tried "DSM_HOSTNAME" and a matching network hostname as well but no dice there. |
|
Hi, the same problem with QNAP container station. The hostname is set to the name of the container. |
A fresh install (latest image, latest Synology DSM, latest iOS 11) of homebridge does not work for me. The logs show this:
As you can see, it's already at
-48and this keeps going on forever.The relevant log messages are:
I have no other Docker images running on the Synology, but there is (native) Plex and a few other services. Is something else running an mDNS service that causes this?
My iOS 11 device is not able to find the homebridge. Entering the code manually just shows a loading spinner that is there forever.
The text was updated successfully, but these errors were encountered: