Disconnect in Zwift : Debug Logging
Hi .. I am having the same problem I've seen reported in other articles.
Midway through a run in Zwift, I am getting interrupts/disconnects which causes an annoying 'stutter' (stop then start). It seems to come when things get faster (around 11.5 kmph), but oddly disappears when things get faster; or I change the speed a little bit.
Now I've seen the articles from people talking of reseating the unit, moving the unit or messing with the stickers. But all that seems to be an approach based upon no real data.
Is there a way I can put the Runn into some sort of debug mode, where I can read a log somewhere that tells me it is the Runn causing the problem. I totally know it could be something on the Zwift side or on the laptop side, so I want to find a way to debug what the issue actually is with some real actual reasoning and not guess work.
Hi Ivan, I use the Runn connected to my Garmin via ANT+ and never have any drop outs, however having a current issue with the Zwift game on ANT+ connecting to my Zwift Hub trainer, but works fine on BLE. are you using BLE or ANT+ with your Runn ? I'm also using that high reflectivity tape instead of the stickers that come with the unit. You could connect your Runn to nRFConnect on BLE and swipe right ( I think ) to view the log ( you may have to subscribe to the right characteristic to stream the speed from the unit. You probably could start a session in the Gym trackr app as you have up to 3 connections availble & just leave it running.
Hope that helps :)
Please sign in to leave a comment.