# Issues with homekit module after node-red update

**URL:** <https://discourse.nodered.org/t/issues-with-homekit-module-after-node-red-update/12716>\
**Category:** General\
**Created:** [29 June 2019 07:38 UTC](https://discourse.nodered.org/t/issues-with-homekit-module-after-node-red-update/12716 "2019-06-29T07:38:44Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [29 June 2019 10:36 UTC](https://discourse.nodered.org/t/issues-with-homekit-module-after-node-red-update/12716/2 "2019-06-29T10:36:27Z")

</div>

If you have the same issue with several nodes the chances are there's an issue with the underlying library.

But one thing to check...  
Have you re-installed the library following the instructions node-red-contrib-homekit-bridged?  
Have you rebooted your device? There was an issue with the avahi module not resetting properly a while ago, which a reboot would clear.

If you have done the above I'd suggest opening an issue against the node-red-contrib-homekit-bridged node as it is still appears to be being actively developed.

---

_[View the full topic](https://discourse.nodered.org/t/issues-with-homekit-module-after-node-red-update/12716)._