My post about controllable not paring through iOS Companion was moved to:
But I’ve been trying some things out and this pertains to both topics.
I’ve used Windows 10 on new gaming laptop since 31 July 2021. I used to use ATV 4K (2017) since December '18. When the gradient / resistance bug appeared and was not sending correctly to my KICKRv5, I rolled back the KICKR f/w to 4.1.2 which solved the issue.
- Tried ANT+ a couple of days ago, and as expected it was a dropout-fest. Zwiftalizer said “Yikes! Your ANT+ device signal was up and down like a fiddler’s elbow”
2.Yesterday tried pairing through direct PC bluetooth, and everything paired including Controllable. Initially got a Connected - No Signal from the TICKR HRM, but then it connected, and I started an hour’s ride with Anquetil. HR dropped out a few times and then completely dropped out after 46minutes. Similar always happened when I first got the gaming laptop, end of July, so HR dropping out was happening before 1.17.x. Always said Connected - No Signal (even though it was not connected to anything else except the PC), and is why I went to Companion pairing, which was always solid until 1.17.x
@shooj
3. Today, I tried updating my KICKRv5 to the latest Wahoo firmware (4.2.3). The iOS Companion app paired to everything, including Controllable. I started my Out and Back Again freeride, expecting to encounter the random gradient / resistance issues due to being on the latest KICKR fw, so I monitored what gradient was being sent to my CLIMB via the Wahoo app (KICKR supports multiple simulations BLE connections). It was perfect. The KICKR was receiving exactly the same as was on-screen (e.g. 2% on screen, 1% sent to KICKR, as I have trainer difficulty at the default 50%)
So updating the KICKRv5 to the latest firmware [v4.2.3 - 1 June 2021 Added: Bluetooth FTMS support] seemed to fix the issue completely regarding pairing Controllable through iOS Companion, with no random crazy hard resistance when descending and super easy when climbing.