I use a Runn Treadmill Sensor which is not now detected by Zwift Run.
If connecting my Runn TM Sensor to my Garmin 245 as an external speed & cadence sensor, then connecting the watch to Zwift using Virtual Run, the speed on Zwift is overstated by around 1 to 1.5kph.
Does anyone know why this is? I assumed the Runn data would be unaffected, even working through such a bridge.
The Garmin watch has its own inbuilt motion system to calculate speed and cadence but I found it notoriously hard to calibrate to the TM (which itself is not an accurate indicator of actual speed) and when finally calibrated, very inaccurate and fluctuating data - the reason I bought the Runn.
I have contacted Zwift directly via e-mail on two occasions now but they are completely unable to provide a timeline for rectification of this defect.
Suggests they have no idea what got altered in the last update to cause the defect.
Is the answer not to revert to the previous version which was working fine and then push out the latest update once properly tested before going live. Why would this not be possible?
The treadmill shows up under a cycling power source. Seems like the cycling connectivity code is capturing the treadmill and preventing the run side from seeing it.
Same issue here, for now I am using a calibrated Zwift running pod as my speed sensor. However, the incline that I have always set to 4% (to simulate real world running experience for me) was not recognised by the running pod.
That is worse than unstable pacing I have had from the sensor
@Ride_Cyclery when is this going to be fixed it’s been almost a week now. Surely you can push out the previous software version so we can at least use our training equipment and our £12 a month Zwift subscription which I’ve paid a month for but only had 3 weeks of use.
It’s been almost a week! Zwift made the service unusable for a very large group of users and is not even acknowledging this major l incident on the status page! How is this even remotely acceptable?!
Unacceptable silence from Zwift on this. Presumably this is a P1 on Zwift’s internal defect tracking?
Running may be relative niche for you, but for many, it’s important to us. And with ZA Run coming up, this is not a good look.
Bluetooth appears to have been a high-risk area of code change in recent times, and indeed, back to the Innsbruck launch where it broke re-pairing (leading to no trainer resistance changes, I remember it well - it took ~5 months to fix). What do you plan to do differently to avoid this happening next time, and the time after that?
I’d have hoped that Zwift would’ve learned that pushing out a major software release on a Thursday, and having customers discover and debug issues on the Thurs/Fri, and then have the dev teams unavailable because of the weekend is poor planning, especially it results in significant proportion of the customer base (runners) being unable to use the product.
UPDATE: The v 1.16.1 patch addresses this bug, and it’s being released this morning. Once you’ve updated to 1.16.1, please let us know that this is solved / not for you, and let us know what tread / NPE / other run speed hardware you’re using.
Win10 + Sole f65 2019. App connect to treadmille. But when I start activity - speed is 0. So app show that connection is succsesfull, but really dont take the speed from treadmille
