qDot
**Feature Description** Add task names to async manager, so we can use them when debugging in tokio-console. They'll be ignored for any non-tokio manager, and will be compiled out when...
If a sensor supports both SensorRead and SensorSubscribe, it can appear at different indexes within the SensorRead and SensorSubscribe capabilities in DeviceInfo structures, even though its the same sensor. Matching...
Like SensorRead, SensorSubscribe should contain SensorRange values, otherwise users won't know what to expect for min/max ranges.
With the way the current manufacturer data matching works, we don't know what data is from the device and what data is from our config file. We use the shortest...
**Feature Description** See if we can reconnect to disconnected bluetooth devices without waiting for an advertisement. This could speed up device reconnection due to line of sight loss, but may...
**Feature Description** The serial port manager is the only DCM that requires user configurations. Users have to know which com port they're connecting their device to in order for us...
**Feature Description** While we don't need to get it through the protocol, we should be able to access the list of registered device comm manager names via the server. This...
**Feature Description** Would be handy to be able to get a list of protocol names so we can match them to config files to show which devices we can connect...
This is an optimization bug more than anything, and it's only for the Edge at the moment. Lovense "Vibrate:X" causes all motors to vibrate, while "Vibrate1X:", "Vibrate2:X", etc cause single...
We don't currently have any rules about how we handle repeated subindexes in Generic Commands. For instance, with VibrateCmd, say someone creates the following packet: ```json { "VibrateCmd": { "Speeds":...