search

NRCHKB / node-red-contrib-homekit-bridged

Node-RED Contribution - HomeKit Bridged : Node-RED nodes to simulate Apple HomeKit devices.
https://nrchkb.github.io
MIT License
418 stars 52 forks source link

[PROBLEM SOLVED] Could not pair with a Bridge in Home.app #300

Closed Shaquu closed 4 years ago

Shaquu commented 4 years ago

Problem

If you cannot pair with a Bridge in Home.app and node-red/NRCHKB logs are not indicationg a problem then it might be a solution for you.

Running node-red in DEBUG mode:

DEBUG=NRCHKB*,HAP* node-red

In my case it was an error which showed in DEBUG mode:

Error while decrypting and verifying M5 subTlv

Solution?

Update your machine packages:

sudo apt-get update
sudo apt-get upgrade

Update node-red (for other then PI head to node-red site)

ash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered)

Update node

If node-red did not updated node to latest make sure to have latest LTS installed. Easiest way is using nvm (node version manager)

nvm install --lts
nvm use --lts

Now start node-red and try to pair!

deon-dup commented 4 years ago

Hi @Shaquu. Success at last! So what I did, was to precede your steps outlined above with a deletion of not only the Bridge on both both NR and Homekit App, but I also deleted all the Homekit nodes. I then completely removed V0.08, rebooted, and then proceeded with the upgrade to 1.1.2. Thereafter I proceeded to do the updates as above, and then only I added Homekit nodes with the associated Bridge. After that, adding the Bridge in Homekit App, with the right pin, was a breeze, and everything is working and stable now. Now for the next challenge to figure out NO_RESPONSE as per #277.