Can't find Controller on my Mac while Power source is there but no signals


(Sizheng Chen) #1

Recently, after upgrading my mac to High Sierra, I started to having trouble connect to my Wahoo Kickr trainer. 

I can’t see my Kickr the controller anymore, but can see it in Power source, although there is no signal on that power source.

I can connect Kickr to my app fine, so the bluetooth connection IN/OUT on trainer seems fine to me…

 

From the log, I saw:

[21:16:32] NETWORK:error (4) sending player state

[21:16:33] FPS  20, -372284, 48932, 190112

[21:16:33] NETWORK:error (4) sending player state

[21:16:33] Starting Native BLE search

[21:16:34] NETWORK:error (4) sending player state

[21:16:35] NETWORK:error (4) sending player state

[21:16:36] Starting Native BLE search

[21:16:36] NETWORK:error (4) sending player state

[21:16:37] NETWORK:error (4) sending player state

[21:16:37] FPS  20, -372284, 48932, 190112

[21:16:38] NETWORK:error (4) sending player state

[21:16:38] Starting Native BLE search

[21:16:39] NETWORK:error (4) sending player state

[21:16:40] NETWORK:error (4) sending player state

[21:16:41] Starting Native BLE search

[21:16:41] NETWORK:error (4) sending player state

[21:16:41] Starting critical power curve search job (20156444)  mTimeStamp = 70.49500  m_lastSearchTime = 70.49500   calculating=false

[21:16:42] NETWORK:error (4) sending player state

[21:16:42] FPS  20, -372284, 48932, 190112

[21:16:43] NETWORK:error (4) sending player state

[21:16:44] Starting Native BLE search

[21:16:44] NETWORK:error (4) sending player state

[21:16:45] NETWORK:error (4) sending player state

[21:16:46] Starting Native BLE search

[21:16:46] NETWORK:error (4) sending player state

[21:16:47] NETWORK:error (4) sending player state

[21:16:47] FPS  20, -372284, 48932, 190112

[21:16:48] NETWORK:error (4) sending player state

[21:16:49] Starting Native BLE search

[21:16:49] Loading Accessory Normal Texture:  Humans/Jerseys/Layout_normWithPocket.tga

[21:16:49] Loading Accessory Instanced Mesh data/Humans/Accessories/Shoes/ZwiftL.gde

[21:16:49] Loading Accessory Mesh data/Humans/Accessories/Shoes/ZwiftR.gde

[21:16:49] Loading Accessory Instanced Mesh data/Humans/Accessories/Shoes/ZwiftR.gde

[21:16:49] NETWORK:error (4) sending player state

[21:16:50] NETWORK:error (4) sending player state

[21:16:51] Starting Native BLE search

[21:16:51] NETWORK:error (4) sending player state

[21:16:52] Starting critical power curve search job (20166518)  mTimeStamp = 80.57231  m_lastSearchTime = 80.57231   calculating=false

[21:16:52] NETWORK:error (4) sending player state

[21:16:53] FPS  20, 59972, 10708, -50969

[21:16:53] NETWORK:error (4) sending player state

[21:16:54] Starting Native BLE search

[21:16:54] NETWORK:error (4) sending player state

[21:16:55] NETWORK:error (4) sending player state

[21:16:56] Starting Native BLE search

[21:16:56] NETWORK:error (4) sending player state

[21:16:57] NETWORK:error (4) sending player state

[21:16:58] FPS  20, 59972, 10708, -50969

[21:16:58] Profile: shutdown

[21:16:58] Profile bike distance: 322354

[21:16:59] Analytics logged


(Forrest B.) #2

It sounds like you are running into an issue with the newest version of OSX (10.13.4) that can keep sensors/peripherals from connecting via native Bluetooth.

Since this is an issue with the OS, and not Zwift itself, we are unable to fix the problem from our end, but we do have a couple of workarounds for this in our known issues article.