Machine state status interface

[MonsieurRz]

Make use of the status byte received from the last response.
This feature would help keep track of the state of the CSAFE device (Ready/Offline/Idle/...)

[MoralCode]

Do you have a link to the spec document for this?

Ultimately I think this library was built primarily to support the c2bluetooth library so i think i just included the minimum necessary for that, but would be down to add more support!

[MonsieurRz]

https://web.archive.org/web/20071207110624/http://www.fitlinxx.com/CSAFE/Framework.htm

• 2.5 => bits 3-0 returns the state of the device
• 2.5.3 => all possible states

(I'll do it)

[MoralCode]

I think its already decoding the status
https://github.com/OpenRowingCommunity/csafe-fitness/blob/1e2ddc4cf5b66b5c94ca6a80489abf31e31f5ea6/lib/src/types/command_types.dart#L72C3-L72C22

it just likely isnt doing much with that status information other than extracting the framecount:

csafe-fitness/lib/src/csafe.dart

Lines 57 to 71 in 1e2ddc4

	if (_previousFrameCount == null) {
	_previousFrameCount = resp.status.frameCount;
	// resolve that future successfully
	matchingCommand.completer.complete(resp);
	} else if (_previousFrameCount == resp.status.frameCount) {
	//last packet received was not ok
	// resolve the future with an error
	// TODO: turn these status types into more proper error types that are easier for users to handle
	matchingCommand.completer
	.completeError("previous command state was ${resp.status.prevState}");
	} else {
	_previousFrameCount = resp.status.frameCount;
	// resolve that future successfully
	matchingCommand.completer.complete(resp);
	}