Hi guys.
I’ve been using Zwift on the same setup now for well over a year with very few issues - the odd internet disconnect.
Dedicated PC setup.
In the last 2 days I’ve had 3 BT dropouts - well this is why I’m here, it looks like BT on my end, resistance in trainer drops and no power going to game. Reconnect screen comes up and within seconds its reconnected.
But when I load the Log File to Zwiftalizer afterwards it shows no BT dropouts.
I was streaming at the time - I stream almost every ride and never have a problem so thats not a new addition messing things up - and the disconnects are time stamped if anyone wants to see what happens in game.
Any help appreciated.
I did start using a new BT Heart Rate Chest Strap in the last few days that is connected via BT also - could that be causing a conflict?
I saw your post over on Facebook where there are a few comments about it but I’ll respond over here based on that info.
I have no idea why the log doesn’t show the dropout, which is puzzling given that you clearly had a disconnection.
I think it does make sense to try pairing the HRM via ANT+ or swap out the HRM but it’s hard to guess if that’s the issue. Bluetooth doesn’t have a fixed connection limit but how it performs does depend on which Bluetooth protocol is in use and how much data is being transmitted (so things like Bluetooth audio devices can eat up a lot of the bandwidth). I have the same number of devices paired as you do, using a TP-Link UB400 dongle (Bluetooth 4.0 protocol) on an extension lead that puts the dongle on the floor behind the front wheel. When I want to use ANT+ I swap out the Bluetooth dongle on that cable.
One thing I was curious about is whether the bike supports bridging the HRM to Zwift. The manual says it supports connecting a HRM to the bike but I wonder if it will also broadcast that data to other paired apps like Zwift. Some trainers support that and it provides an alternate way to pair the HRM that would eliminate one Bluetooth connection to the PC. Maybe someone here will know the answer to that question.
1 Like
Thanks. I’ll look into connecting through the bike - but I’ll try it on Ant+ tonight and see how that goes. Its the only change recently and it does line up with the problems started. I think my orignal HR strap failed just before Stage 1 - theiTT - and luckily my watch broadcast HR so I used it for that stage as last minute option. Then I used the new one for Stage 2 and I’m pretty sure thats when I had the first BT disconnect. And then 2 more on Stage 3 with same new HR Chest Strap.
Just really weird that Logfile shows none of them, which had me wondering if it was an issue Zwift side.
OK - Quick follow up.
Nothing conclusive - I’ll test more in bot rides next week to confirm - but it may have been the new HR Chest Strap. I switched back to my old one tonight (was just flat battery) and I had no issues. I’ll switch to new one again next week on a bot ride and see if happens again.
Still strange that it didn’t show in log file - and hard to know why it would interfere with the bike, but it looks like it might have.
1 Like
Zwiftalizer developer here. A change in the log file format in game version 1.72 and above was the reason Zwiftalizer did not report the BLE disconnects. I fixed it today. You will notice 4 dropouts if you upload your log again, 2 for each activity. There were two disconnects on the HR strap and two on the Wattbike. They have nothing in common.
3 Likes
Thats great - thanks for the reply. All I can do is carry on and see if it happens again. My setup is very fixed, nothing gets moved around etc as its set up in my gym/shed outside. Never a problem with the bike before. The HR is brand new so I have no history with it. As mentioned already I’ll revert back to my old HR for now and see how it goes - ZRL tonight and FRR for rest of week so plenty of opportunity for a problem if Im gonna have one 