Replies: 3 comments 6 replies
-
Hi rajohn96. I am having the same issue. It looks like it tries to run an initial "ping" command hitting http://${this.bondIP}/v2/devices and fails. I can hit this address with CURL though so not sure what the problem is. I plan to mess with the code later today to see if I can figure anything out. |
Beta Was this translation helpful? Give feedback.
-
I set Home Bridge to -D and things started working again even when turning of -D. No idea why. Edit: Turning -D back off didn't seem reliable. I set bond to it's own bridge mode and that seems to work every time. I tried isolating the code locally for ping and that worked every time. I think maybe what is happening is HAP (whatever that is) fires up but isn't quite done when bond tries to do its thing? I see the plugin uses HAP and in my logs HAP starting is mentioned right before bond. Everything is working for me now so I don't play to dig into this any more. |
Beta Was this translation helpful? Give feedback.
-
THANK YOU both for this. I was banging my head against the wall trying to figure this out. Ultimately, I also had to put Bond in Bridge Mode and THEN restart the child bridge to get it to connect. I guess it is a timing thing with HAP or whatever that is (my technical knowledge is somewhat lacking there). |
Beta Was this translation helpful? Give feedback.
-
All,
I have a home bridge with fw v3.8.4 that I can see via ping and curl to without issue but cannot connect via the homebridge plug-in. I get the following message in the log:
[Bond] Unable to find Bond for IP Address: 192.168.1.36. Skipping this Bond.
Even if I restart the bridge and then restart the homebridge app within the 10 minute window (during which time no token is required) I have the same results. This seems to be something with the axios library throwing an ECONNABORTED error.
TIA!
Beta Was this translation helpful? Give feedback.
All reactions