I’ve been having similar issues as the original poster. Although a Garmin V2 cadence sensor in this particular instance connected via bluetooth to TR running on an iPad. Using a Saris H3.
For the last month or so, at least 1x per workout, I’ll get a random spike that maxes exactly at 255 for cadence. The rest of the cadence data for the workout seems pretty expected beyond these occasional spikes.
Have already contacted TR support to work through the issue, but curious if anyone has experienced this?
