You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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:
In my case it was an error which showed in DEBUG mode:
Solution?
Update your machine packages:
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)
Now start node-red and try to pair!
The text was updated successfully, but these errors were encountered: