-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
List Fans/Capabilities Empty #1
Comments
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. |
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. |
Do you still have your debugging environment setup? I could just give you my username/pwd. |
Yeah, I can do that. Send me an email at [email protected] (split my username). |
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. |
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>
.
|
Yes, I am at the same version 1.138.1 which is the latest. The api is not working yet.
From: Carsten Dressler [mailto:[email protected]]
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>
|
There are sign-ups for the v2 beta here: https://forum.bondhome.io/t/bond-local-api-beta-sign-up/250 |
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!
The text was updated successfully, but these errors were encountered: