Additionally, when querying the individual devices, I’m not getting any usable list of commands, however, things like name and location seem accurate. I’d post a screenshot of that too, but as a new user, I can only post 1 image.
That’s real interesting. I like others don’t yet know what would make something a cloud or legacy device but I have 2 normal, plain Jane ceiling fans and a single “hacky” device that thinks it is a fan but is actually just an RF remote for a Christmas tree setup I have tied to IFTTT and a SmartThings custom device.
1 of the fans is in the list and the hacky device is the other. I’d expect maybe both fans to be the ones that show up instead of the hacky device if I was only going to see 2. Must be how they were paired I guess. Either way, Bond sees them as 3 fans.
Also, I actually don’t see anything in the command list. It’s just empty. Here’s an example of the 1st one 00000003 but they both look the same:
Could this have to do with the fact that I didn’t actually re-pair anything after upgrading to the beta firmware? I know we were told we’d have to but everything remained and works still so I figured I’d be fine.
Obviously not all that useful unless I reverse engineer each one. I guess it’s probably in order?
I’m all for tinkering and trying to figure this out, but if this is some issue they are working to fix, I also don’t want to waste my time and appreciate the Local API, even though it’s a WIP. Maybe my feedback can help the devs.
You generally want to limit API calls, not artificially inflate them for some hierarchy on the backend. I’ll defer to them though for now as they know their software better than I of course.
The documentation is somewhat contradictory though as in one spot it seems like a single API call will retrieve everything I’d need and then this hash-tree / one layer bit you linked.
As far as the “order”, it’s a simple id, it’s going to go based on creation so the order will be the order you added commands during pairing I imagine. I just added them like a sane person so they are in ascending order for me.
As I’m digging into this, they are offering quite a bit of detail down to the binary data that will get sent in the RF signal. Woah. I know I’d never need this level of detail but it’s cool that it’s available.
Oh I can agree it’s definitely alpha more than beta right now.
But I’ve been wrestling with it and getting good results (with some trial and error initially, for sure).
I wish the commands were organized in a sane manner, just to play nicely with OCD haha.
Here are two examples of fans where I initially pushed two buttons and the BOND servers auto recognized and completed the remainder of the commands. No rhyme or reason I can see for the order of the commands:
I’ve never had the luxury of auto-recognized commands I don’t think. Or maybe I did on the one device I can’t see
Still haven’t quite worked out how to actually send a command through the API. /tx with a PUT is resulting in no response for me and the documentation doesn’t list a 200 has a response code so maybe they aren’t done with it?