# Unable to make homekit-bridged work

**URL:** <https://discourse.nodered.org/t/unable-to-make-homekit-bridged-work/20772>\
**Category:** General\
**Created:** [23 January 2020 13:01 UTC](https://discourse.nodered.org/t/unable-to-make-homekit-bridged-work/20772 "2020-01-23T13:01:16Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![bplatypus](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bplatypus/32/16434_2.png) [@bplatypus](https://discourse.nodered.org/u/bplatypus)\
**Post date:** [23 January 2020 13:01 UTC](https://discourse.nodered.org/t/unable-to-make-homekit-bridged-work/20772/1 "2020-01-23T13:01:16Z")

</div>

Hi everyone!

I installed node-red on docker on my Synology NAS (ds1819+). Installation was really easy and it works perfectly!

I then installed the Philips-Hue stuff and I can control my hue accessories from node-red and receive status change without any issue.

I then installed the homekit-bridge ([https://www.npmjs.com/package/node-red-contrib-homekit-bridged](https://www.npmjs.com/package/node-red-contrib-homekit-bridged)), trying to add a lightbulb accessory (111-11-111), deployed the stuff, went in homekit on my iphone and tried to discover the new accessory by entering 111-11-111 but nothing appears!

I'm using my Apple TV as hub. All my IOS devices are up-to-date.  
I tried some different libraries like [https://flows.nodered.org/node/node-red-contrib-homekit](https://flows.nodered.org/node/node-red-contrib-homekit) or the -preconfigured one but always the same result, I see nothing in homekit.

Does anyone have the same problem?  
Thanks for any help.

---

<div class="post-metadata">

**Author:** ![binary](https://avatars.discourse-cdn.com/v4/letter/b/8c91f0/32.png) [@binary](https://discourse.nodered.org/u/binary)\
**Post date:** [23 January 2020 13:28 UTC](https://discourse.nodered.org/t/unable-to-make-homekit-bridged-work/20772/2 "2020-01-23T13:28:43Z")

</div>

I’m going to take a wild guess, because I don’t know how the Synology installation works... however, I could not get homekit-bridged to work on Docker. It works perfectly on a ‘naked’ RPi (i.e. not dockerised).

I suspect it has something to do with port access; Docker containers run within their own network, so I think I’ll have to open a port to the ‘outside world’ (my network). Perhaps it’s the same issue on Synology.

I haven’t done much research on this, but searching for ‘homekit port’ threw up some potentially useful results.

---

<div class="post-metadata">

**Author:** ![bplatypus](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bplatypus/32/16434_2.png) [@bplatypus](https://discourse.nodered.org/u/bplatypus)\
**Post date:** [23 January 2020 13:34 UTC](https://discourse.nodered.org/t/unable-to-make-homekit-bridged-work/20772/3 "2020-01-23T13:34:49Z")

</div>

This would mean that every library could use some different ports?

Because it's working perfectly for my Hue devices!

So maybe homekit-bridged is using some ports I need to specify in docker. I'm going to ask google about it ;-). Thanks for your reply.

---

<div class="post-metadata">

**Author:** ![bplatypus](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bplatypus/32/16434_2.png) [@bplatypus](https://discourse.nodered.org/u/bplatypus)\
**Post date:** [23 January 2020 13:49 UTC](https://discourse.nodered.org/t/unable-to-make-homekit-bridged-work/20772/4 "2020-01-23T13:49:51Z")

</div>

Just found an interesting thing to test. Add --net=host to the docker run command!

docker run -d --net=host ....

Will try it after work!

edit: found it here: [https://github.com/nfarina/homebridge/issues/309](https://github.com/nfarina/homebridge/issues/309)

---

<div class="post-metadata">

**Author:** ![binary](https://avatars.discourse-cdn.com/v4/letter/b/8c91f0/32.png) [@binary](https://discourse.nodered.org/u/binary)\
**Post date:** [23 January 2020 13:53 UTC](https://discourse.nodered.org/t/unable-to-make-homekit-bridged-work/20772/5 "2020-01-23T13:53:01Z")

</div>

That could be it; homekit needs avahi (bonjour) to work. I’m hoping to have time to test this over the weekend.

---

<div class="post-metadata">

**Author:** ![cflurin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cflurin/32/29_2.png) [@cflurin](https://discourse.nodered.org/u/cflurin)\
**Post date:** [23 January 2020 15:16 UTC](https://discourse.nodered.org/t/unable-to-make-homekit-bridged-work/20772/6 "2020-01-23T15:16:18Z")

</div>

A technology that I like best is MQTT.  
For HomeKit see: [https://github.com/cflurin/homebridge-mqtt](https://github.com/cflurin/homebridge-mqtt)

---

<div class="post-metadata">

**Author:** ![bplatypus](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bplatypus/32/16434_2.png) [@bplatypus](https://discourse.nodered.org/u/bplatypus)\
**Post date:** [23 January 2020 15:30 UTC](https://discourse.nodered.org/t/unable-to-make-homekit-bridged-work/20772/7 "2020-01-23T15:30:44Z")

</div>

why do you prefer it? It seems a bit more complex to configure...

---

<div class="post-metadata">

**Author:** ![cflurin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cflurin/32/29_2.png) [@cflurin](https://discourse.nodered.org/u/cflurin)\
**Post date:** [23 January 2020 15:50 UTC](https://discourse.nodered.org/t/unable-to-make-homekit-bridged-work/20772/8 "2020-01-23T15:50:50Z")

</div>

It's an external app, so it can also be used by other platforms like esp8266. I'm the author therefore I can’t say more 😀

---

<div class="post-metadata">

**Author:** ![bplatypus](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bplatypus/32/16434_2.png) [@bplatypus](https://discourse.nodered.org/u/bplatypus)\
**Post date:** [23 January 2020 16:24 UTC](https://discourse.nodered.org/t/unable-to-make-homekit-bridged-work/20772/9 "2020-01-23T16:24:53Z")

</div>

It's working by adding the --net=host! 😀