I followed the how-to regarding the install of contrib-homekit-bridged but it doesn't seem like it installed correctly.
I am unable to edit/add an accessory
Attached is a image on my issue

Please advise on what I should do to fix it
Thanks a lot!
I am using a raspberry pi
Hello @TristanMW I am happy you are here :)
Indeed it looks like you did not installed our module properly.
Go to your node-red root folder (possibly ~/.node-red/)
Go to node_modules and look what node-red-contrib modules you got there. I assume you have something else installed called homekit aswell.
You can install module from root of node-red using:
npm i node-red-contrib-homekit-bridged
Or just install it via node-red panel.
Remember you need avahi too:
sudo apt-get install libavahi-compat-libdnssd-dev
I used to have the original contrib-homekit node until I found that this version which is active.
Removed it then tried installing this version ... is it possible that the old files are still there?
_Remember you need avahi too:
sudo apt-get install libavahi-compat-libdnssd-dev_ - Did this aswell


Is the homekit-bridge node supposed to be greyed out?
Apologies for all the images - easier to explain then trying to describe with words
Images are completly fine!!
Okay so let's do this:
Are you creating new nodes in node-red or trying to modify the old one?
Grey color is fine as it is config node - not possible to add manualy from sidebar.
Have you restarted node-red?
Have you refreshed your page where you acces node-red?
package.json:

_uninstall node-red-contrib-homekit-bridged, make sure folder is removed_ - Will do this now
I am creating a new one and double checked that all old accessories were removed from the "configuration node" tab next to debug
I have not restarted node-red and come to think of it I should have tried that first haha
Agggg TRISTAN!
So restarting nodered-service and pi reboot (just incase) fixed the issue ...
Thanks a lot Shaquu
hahahahaha
Good for you @TristanMW !!
Closing :)
Most helpful comment
Agggg TRISTAN!
So restarting nodered-service and pi reboot (just incase) fixed the issue ...
Thanks a lot Shaquu