Connection on connect button not on start button.
The device will begin passing data as soon as connected, so this needs to be cut off as well.
The mock ble connection needs to be updated to start passing data as soon as connected (this can AND SHOULD be not real run data, as this is just data to be cut off anyway).
Device uuid should be stored in frontend (?) maybe backend too for easy reconnect. Backend storage would require new attribute. Consider multiple runners wearing same shoe / multiple shoes for same runner (?) - would we need a pair button that would allow connecting to new device?
Does mock ble currently actually disconnect and reconnect? Is the data actually truncated?
Connection on connect button not on start button.
The device will begin passing data as soon as connected, so this needs to be cut off as well.
The mock ble connection needs to be updated to start passing data as soon as connected (this can AND SHOULD be not real run data, as this is just data to be cut off anyway).
Device uuid should be stored in frontend (?) maybe backend too for easy reconnect. Backend storage would require new attribute. Consider multiple runners wearing same shoe / multiple shoes for same runner (?) - would we need a pair button that would allow connecting to new device?
Does mock ble currently actually disconnect and reconnect? Is the data actually truncated?