Your reply so far is completely not to the point:
- The Wahoo Kickr does not estimate cadence, as you later acknowledge.
- I do have a Wahoo cadence sensor. But the Zwift app is very bad in connecting to the Wahoo TickrX and Wahoo cadence sensor. Whereas the Wahoo app always immediately connects to both sensors, I often have to retry connecting with Zwift on Apple TV. (And before you mention: I do not try to connect to both apps simultaneously. Only Zwift OR Wahoo app.) So, I only used the TickrX as cadence sensor, because the Wahoo cadence sensor would not connect to Zwift.
I used the TickrX as HRM and cadence sensor at the same time. It is perfectly capable of doing that.
There are no dropouts. I never have dropouts using BT. And suggesting that dropouts are related to the slopes in Zwift is just silly.
I have tested the TickrX as cadence sensor: I used the Wahoo cadence sensor with Zwift, and the TickrX as cadence sensor on the Wahoo app at the same time. The readings are pretty similar. Only when I change my cadence, the TickrX reacts more slowly than the Wahoo cadence sensor. So, this problem has nothing to do with the TickrX being inaccurate.
The problem is that when the gradient in Zwift changes, the display of the cadence drops form 90 to about 40, whereas I keep pedalling at the same frequency in ERG mode. And when the road becomes flat again, the cadence reading immediately goes up to 90 again. That has nothing to do with inaccurate readings of the TickrX, dropouts or whatever. The problem is obviously within Zwift…
- The controllable of my Kickr has nothing to to with the cadence readings of the TickrX. There is no relation between this, as you should know.
So, I know the Wahoo cadence sensor is more accurate as the TickrX. But Zwift offers the option to connect the TickrX as cadence sensor, it works pretty good, but Zwift fails in interpreting the data of the TickrX.