this is the error i get when i try to load it up, obtaining the ip adress and the token from the app. what do i need to do?
BOND
Unexpected Error
An unexpected error has occurred trying to load the app. Check Logs for more information.
Error: No signature of method: org.apache.http.conn.ConnectTimeoutException.getResponse() is applicable for argument types: () values: [] Possible solutions: getMessage()
I'd suggest double checking the IP. It is saying it can't connect to it. Can you ping that IP from a command line in windows?
i cannot, so how do i find the correct ip address?
In the BOND app when you click on the bridge there is a line that says Bond ID. For example, BB18038 if you take that name, append .local and ping it you should see the IP:
ping BB18038.local
ping bb18038.local (192.100.0.61): 56 data bytes
now that did give me an entirely diffrent ip address and gets me past the first page, but will not pull up any devices
Ok well that's good. When you're in the BOND app, what number is shown next to Devices Associated? If it's zero it sounds like you have cloud devices which might be the problem.
maybe, it doesnt give a number just blank space. i just updated to the latest bond firmware and app earlier today to try to get this to work....maybe let the cloud settle for a little while, restart the device and see if anything changes
Nope, there is a process you need to follow to convert them to local devices. I believe you need to remove the device(s) from the hub and readd them. If that doesn't work I am sure @bond-jacob can lend a hand!
@agallowaymd
At this point pretty much all* devices have offline versions. Here's a quick test: tap the device, find its settings (top right), does it have a "local token"? If it has one, you should be good to go, and your problem lies elsewhere.
If it doesn't have this "local token", try re-recording it, you should* get a local version now. If re-recording isn't convenient for you, or if you get stuck elsewhere PM me and I can help out.
*(Note: There are still some "cloud-only devices" out there that are still without a local version, but they represent less than 0.5% of all devices)
FYI, in the next versions (v2.15) of the mobile app, this IP will be visible in-app. Should be a little quality-of-life improvement for getting this set up.
1 Like
Strange... Do you see any devices on your dashboard? Try swiping down from the top of the screen to refresh.
nope, no new devices. i am trying to figure out how to do a static ip address for bond as i thought that might be my issue. if i try the ip the bond home app gives me it wont go through at all...and if i try the ip that the ping gives me to the device name the app starts in hubitat, but i do not see any devices. like wise if i just put in the numbers without the dots in the ip adress it will start up the app but give me the same thing i get with the ping
A couple troubleshooting steps: First, everything here is on the same network, right? If so, does the Bond respond on either of those IP addresses to any curl? I'd try curl -i http://192.100.0.61/v2/sys/version
with your address substituted in, do you get a response?
There's currently no way in the app to set it, but there's a couple ways to go about this. I do recommend you try out the above troubleshooting steps first, this doesn't sound like a problem static IP is going to resolve.
- Use the local API. A couple relevant articles: Getting Started & WiFi station
- Use the web GUI. This is the tiny webapp that the Bond exposes. Simply visit the IP that ping is giving you in a web browser and you should see a page that allows you to configure advanced WiFi settings. If you're having trouble with the IP still, get the Bond into "green flashing" WiFi setup mode by holding down the pinhole reset button, connect to its config network and visit
10.7.42.1
.
the only thing that gives a response is when i ping BH35970.local, the curl-i does not respond on the ip address i get from that, the local api does not respond, and not getting any luck from the web gui either. maybe i will try a factory reset and set it all up again? the fans are working through the bond home app, very strange
This just seems like some odd networking behavior, maybe try a power cycle? I wouldn't recommend a factory reset at this time, as I don't think it's likely to accomplish anything that a simple power cycle wouldn't.
It times out with a "can't find host" error?
it responds to the curl but doesnt report any of the information it is supposed to based on the local api article, cant get it to give me version number or the local token when asked based on the instructions in that article. i have those things from the app mind you just was using that as a test
So what does it respond with?
C:\Users\fetas>Curl -i and the rest of the command
HTTP/1.1 200 OK
Date: Sun, 03 Nov 2019 18:25:43 GMT
Content-Length: 0
Connection: close
is what i get, did the factory reset and added back in my fans and getting the same issues still
Very strange. Well, I'd guess you're somehow hitting the wrong endpoint but I don't know what endpoint would return OK with 0 Content-Length...