Skip to content

Bug: Echo Mode + Just Lift prevents the user from doing a second set #17

@kelltom

Description

@kelltom

To recreate, I first do a normal set with Echo Mode, with Just Lift enabled.

I can do this set just fine.

However, I notice the auto-stop feature "spins". The console shows multiple Stop commands being sent. While the weight does stop, it appears that I can't begin another set beyond this point. I can pick the handles back up and do some reps, but it's weightless and nothing happens. I can click "Start Echo", which seems to restart the set, but warmup reps won't count -- weightless.

The only fix I've found is to refresh and reconnect.

Here's the steps of me doing a normal Echo Set, waiting, then trying to do another set:

After the set, the webpage shows this for a number of seconds:
Image

Then, it shows this. So far, so good:

Image

During this wait, I see this in the console -- constant repeating what seems like an endless loop, but after a while, it stops:

Workout stopped!
Workout stopped by user
Workout completed and saved to history
[notify c7b73007-b245-4503-a1ed-9e4e97eb9802] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[notify 67d0dae0-5bfc-4ea2-acc9-ac784dee7f29] 00 00 00 00
-> Stop command (4 bytes): 0a 00 00 00
<- Stop command acknowledged
Workout stopped!
Workout stopped by user
-> Stop command (4 bytes): 0a 00 00 00
<- Stop command acknowledged
Workout stopped!
Workout stopped by user
-> Stop command (4 bytes): 0a 00 00 00
<- Stop command acknowledged
Workout stopped!
Workout stopped by user
-> Stop command (4 bytes): 0a 00 00 00
<- Stop command acknowledged
Workout stopped!
Workout stopped by user
-> Stop command (4 bytes): 0a 00 00 00
<- Stop command acknowledged
Workout stopped!
Workout stopped by user
-> Stop command (4 bytes): 0a 00 00 00
<- Stop command acknowledged
Workout stopped!
Workout stopped by user
-> Stop command (4 bytes): 0a 00 00 00
<- Stop command acknowledged
Workout stopped!
Workout stopped by user
-> Stop command (4 bytes): 0a 00 00 00
<- Stop command acknowledged
Workout stopped!

Since we are in Just Lift mode, I'd expect to just pick up the weights to start a new set. If I do so, the Warmup Reps do not increment, and nothing is appended to the console. Warmup Reps are at -/3. So, it seems we are totally idle.

If I hit "Start Echo" again, the UI changes to indicate I'm starting a set. However, as I pick up the weights, the Warmup Reps do not increment, instead they stay at 0/3. The console shows this:

Starting Echo mode: Hard level, 100% eccentric
Sending Echo control frame (32 bytes): 4e 00 00 00 03 ff 00 00 64 00 32 00 cd cc cc 3d 00 00 80 3f 00 00 48 42 00 00 00 00 00 00 c8 c2

And at this point, I'm inclined to refresh the browser. However, as I sit here typing this issue, I noticed that the "Start" command issued successfully to the device, and I was able to continue a set. I couldn't catch the console output for that, but as I stopped the set, I saw this, frantically repeating again:

ending STOP command...
Auto-stop triggered! Finishing workout...
Sending STOP command...
Auto-stop triggered! Finishing workout...
Sending STOP command...
Auto-stop triggered! Finishing workout...
Sending STOP command...
Auto-stop triggered! Finishing workout...
Sending STOP command...
Auto-stop triggered! Finishing workout...
Sending STOP command...
Auto-stop triggered! Finishing workout..

So there might be some bugs in the communication. And endless loop somewhere in the code. Sorry for the sprawling notes -- it's hard to diagnose the behaviour.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions