List Fans/Capabilities Empty

[dresslerc]

I am running the Postman collections, Login and Bond Hubs work fine. However when I try to GET the list of fans/capabilities, all that is returned is [] (status 200).

The URL I am hitting is this:
https://osprey.appbond.com/api/v1/cloud_device/BD22897/

The BD22897 is what is returned from the Bond Hubs request.

From the Bond app, that is the correct bond id and works.

Just to clarify, the Authorization header should be "Bearer " + "key" from the login request correct?

Thanks for your efforts on this!

[danmandle]

Thanks for trying this out! Are you trying to do this in Postman or from code/another tool? Yes, you have the right authorization header. When I had auth issues, it normally returns a 403.

My only guess is that your BOND hub doesn't have any devices attached to it which seems likely.
Can you reply with a screenshot from the bond app like this?

When you get it working, I'd be interested in seeing the output to make sure I can cover more options that just what I have to test with. Just curious, what are you integrating your BOND with? I'm working on a component for Home Assistant.

[dresslerc]

Here is the screenshots:

Long story short, a few years ago I reverse engineered a universal fan remote kit from Amazon and built my own transmitter using a Particle Photon and a 303Mhz transmitter chip (see http://www.fanremote.io). The entire thing was built on Firebase with a NodeJS backend that would basically do what Bond Home is doing. Here is the front end I have:

I liked this interface better because you can control all your device in 1 go, rather than having to click each room and then controlling it. Plus I had some neat extra stuff built in (scheduling system, Nest Integration (air circulation when heat/ac is running etc).

So what I wanted to do is replace my hardware with Bond Home, but then use my UI and my scheduler/nest integration.

[danmandle]

That's a pretty cool project. I'm not sure why you're seeing the issues you're seeing. I tried changing some things on my end to test and I got a 403 anytime I change a param that I think could replicate your result. Maybe you're on a different app server? Don't think that's the case either as there wasn't anything in the API responses to indicate which app server a BOND would be on.

Your best bet would be to do what I did: use Charles to sniff the API traffic to see how the app receives it. I ended up using an older Android tablet because newer versions of Android (7+ I think) require an exception in the app manifest to allow sniffing of HTTPS traffic. I'd be happy to work with you on this as I'm also curious what is different for your setup so that my solution can be more robust.

[dresslerc]

Do you still have your debugging environment setup? I could just give you my username/pwd.

[danmandle]

Yeah, I can do that. Send me an email at firstname@lastname.me (split my username).

[danmandle]

Good news @pakmanwg and @dresslerc ! Bond has released official docs: http://docs-local.appbond.com/ . Looks like it only supports V2 firmware. My guess is that the firmware difference is why we were experiencing different API behavior.

[dresslerc]

Good stuff. My bond is on 1.138.1. Cant force upgrade to 2 I guess. Must wait I suppose.

…

On Wed, Feb 27, 2019 at 2:35 PM Dan Mandle ***@***.***> wrote: Good news @pakmanwg <https://github.com/pakmanwg> and @dresslerc <https://github.com/dresslerc> ! Bond has released official docs: http://docs-local.appbond.com/ . Looks like it only supports V2 firmware. My guess is that the firmware difference is why we were experiencing different API behavior. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAW5KL8Gj0MBt78wVp8ykSy8D4xWTpT-ks5vRt35gaJpZM4Xi9-E> .

[pakmanwg]

Yes, I am at the same version 1.138.1 which is the latest. The api is not working yet. From: Carsten Dressler [mailto:notifications@github.com] Sent: Wednesday, February 27, 2019 6:42 PM To: danmandle/bond Cc: pakmanwg; Mention Subject: Re: [danmandle/bond] List Fans/Capabilities Empty (#1) Good stuff. My bond is on 1.138.1. Cant force upgrade to 2 I guess. Must wait I suppose.

On Wed, Feb 27, 2019 at 2:35 PM Dan Mandle ***@***.***> wrote: Good news @pakmanwg <https://github.com/pakmanwg> and @dresslerc <https://github.com/dresslerc> ! Bond has released official docs: http://docs-local.appbond.com/ . Looks like it only supports V2 firmware. My guess is that the firmware difference is why we were experiencing different API behavior. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAW5KL8Gj0MBt78wVp8ykSy8D4xWTpT-ks5vRt35gaJpZM4Xi9-E> .

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AV84TCVxHhK_OmkdX8ieE4wIR5yU1p7qks5vR0HkgaJpZM4Xi9-E> . <https://github.com/notifications/beacon/AV84TK2v5u3C4uW_xo5LQk2MJB51ERVCks5vR0HkgaJpZM4Xi9-E.gif>

[danmandle]

There are sign-ups for the v2 beta here: https://forum.bondhome.io/t/bond-local-api-beta-sign-up/250