qDot
Bluetooth device connections in UWP are managed via what is supposed to be a black boxed RAII situation. Whenever all connection objects (bluetoothLEDevice/Service/GattCharacteristic) are dropped, and .Dispose is called on...
If a computer has multiple bluetooth adapters, Buttplug will choose whatever adapter comes up as "default", even if that adapter isn't on or doesn't support Bluetooth LE. We should iterate...
IButtplugDevice.Disconnect is currently only called from DeviceManager.RemoveAllDevices(), which is never called from anywhere. We should figure out when/how this cleanup needs to happen.
Systems with alternative bluetooth stacks, like the Betula stack, will cause the UWPBluetoothManager to detect a usable radio, but not be able to access it. We need a way to...
Changes in #397 reduced the overall amount of test boilerplate quite a bit. However, there are still quite a few cases of repeated code for single vibrator devices that could...
These patches came in as WIPs, and there's a lot of websocket comments and wrong code scattered around them (for instance, connections were never actually stored to the _connections array).
The GeneralDeviceTest tests try to test StopDeviceCmd without running Initialize() on devices. We now use Initialize() on Lovense devices to figure out what kind of device it is, meaning we...
In #280, our workaround for the "Not GET Request" exception in v0.1.1 was to set a timer that will only trigger if we don't immediately connect after getting a WebSocketListener...
See https://github.com/buttplugio/buttplug-js/blob/master/src/server/bluetooth/devices/Maxpro.ts
See buttplugio/stpihkal#35. Ideally, this should happen after the cleanup of the serial core, and should share the core with the ET-312. Also need to figure out how we can bind...