dvmarinoff
commented
2 years ago Thanks for the report, it’s incredibly valuable. And I am sorry to hear your workout didn't went through.
-
The protocol Looking at the log, I see the trainer is using the wahoo cycling power service (wcps). That’s an old Wahoo specific proprietary protocol from the days before the now standard bluetooth FTMS, and the bad news about it is that it’s also undocumented. Officially it is not supported by this project, but unofficially I have tried to do my best in hunting down and stitching together various bits and pieces from partial implementations around the internet. I couldn’t find anyone with a trainer that uses this protocol and is willing to help test it, so you won’t see it listed as officially supported. My implementation remained untested on real device and I am amazed it’s even working. So your log here is the first and only feedback I have.
-
The disconnect I am not sure what triggered the drop out. It might be a coincidence or something protocol related, but auto-reconnects over web-bluetooth are a special case and are not supported at this point (they require a specific option in the browser settings to be checked out). If the connection drops, you would have to manually connect back to the device. Did you try reconnecting to the trainer?
In my case, my Tacx Flux S trainer has a well known firmware bug, which makes it drop the connection when you stop pedalling after a prolong steady effort at intensity. But in any case I get drop outs rarely, like 1 a week, and it’s quick and easy to reconnect the controllable from the top menu.
The rest is more or less expected behaviour. The workout kept running, and the power value remained at the last data point it received. What I can do is reset values to 0 when the connection is dropped, but trying to distinguish between real signal and signal that’s stuck is hard in this case (some trainers seriously over smooth data when in ERG, etc., and such a feature is likely to cause more problems than solve any).
GCuser99
TClin76
Hi @dvmarinoff,
Here are the results of a short test I ran today on your development version (flux-devel.vercel.app) ...
I created the following workout file for the test:
Next I succesfully paired my Wahoo Kickr and cadence sensors ...
I started the 23 minute workout, and after about 10 minutes the activities power profile in the display stopped updating and (I perceived) my output power remained constant at 180 watts throughout the remainder of the workout. Here is a snapshot that I took at the end of the workout:
What I noticed during the workout:
I took a screen shot of the settings tab at the end of the ride and the Kickr no longer appears to be paired:
However, after uploading the fit file to Strava, it appears the entire 23 minute activity was captured and appears to verify that my power output was indeed 180 watts after the +-10 minute mark:
Here is the Developer Console output. Near the backing up of 600 records, the Ble for the controllable disconnected, but the cadence sensor remained connected until the end: