For the past 2 to 3 weeks I’ve been having issues with the Companion app. After trying to understand what the problem was I have now found that when checking through the app it tells me “No Zwift Hardware Found” when the Companion app is scanning for devices. I’ve tried doing the various suggestions and checks but bluetooth on my iPhone doesn’t find any Zwift hardware. Zwift on my MacBook Air works fine but I get nothing on the Companion app.
I’ve spent hours trying to figure this out but am at a loss as to what to do next.
Before the last couple of weeks everything worked fine, all linked together and I could see what I was doing on the Companion app. Don’t think I’ve done anything to alter it but don’t know what to do next.
Has anyone had this happen and what can I do?
I assume your macbook is not on when you are trying to pair to the iphone.
The problem with bluetooth is that can only connect to one device so if your macbook grabs the connection first it could be interfering. Worth switching off/disabling bluetooth if that could be an issue.
Hi @Teresa_J ! The “Zwift Hardware” section in Zwift Companion is mainly for performing firmware updates on Zwift first party hardware (e.g. Zwift Ride, Zwift Click, Zwift Play, or Zwift Hub). If you’re not using any of these devices to Zwift, then “No Zwift Hardware Found” would be an expected result of visiting that tab.
With that said, could you elaborate more on the experience you were having before and what changed? Are you having problems pairing your devices to Zwift via Zwift Companion bridge?
Thanks Rowdy, there wasn’t any indication that the “Zwift Hardware” section referred to firmware updates so I thought it was odd that nothing could be found.
The issues I was having were related to the Mac and the iPhone seemingly not “speaki;g” to each other. The Companion app wasn’t showing/receiving anything from the game (no riding, no workouts etc).
It has now been solved with help from the Zwift Support Team.
I have carried out a “Fresh Instal” of the game to remove any corrupted data and done a tweak to the Mac firewall (which wasn’t on) to make sure incoming Zwift data was allowed…
All this seems to have solved the problems.