qDot
Implementation looks good, just waiting on some internal testing before bringing this in. Should happen soon tho.
Ok hmm. I guess we've got some sort of race issue down in btleplug. I'll try to check it out soon.
Not sure why this got closed? It's not fixed yet. I've at least made a followup on btleplug.
A solution for part of the rotate issue in terms of a Client API implementation: The only difference between ScalarCmd Rotate and RotateCmd is that RotateCmd has a 2d direction...
Annnnd 9 months later, finally starting to think through this for implementation, and I have a small tweak that I think should cover everything. Devices will be trees of features,...
@Yoooi0 You're reading slightly too far into my example. The Boost has 2 ways to get the same reading, but that's also currently the *only* toy that does that. So...
> What if the features are its own separate thing but they only include indexes that map to the actuators/sensors lists: Ok having sat with this for a week, I'm...
> Actually if the library implementation is able to use the actuator/sensor UUID then it can be another way to send commands. So you would be able to either send...
Ok, well, tackling this *yet again* in the new year. Good news is, every time I revisit this, the more I'm becoming ok with the simplifications everyone is recommending. Both...
Ok, well, after a year of fucking around trying to do this in a RDBMS and learning a bunch about sqlite then chucking it all, I'm implementing this in the...