I’ll add my 2 cents for what it’s worth:
An hour of my time is worth more than the cost of the dreaded Apple TV from the evil empire, so I have one now. And it’s working 99% of the time. I have over 30 years in the IT industry & teaching tech. I feel my knowledge is pretty good when it comes to sorting out technical issues.
I have ran Zwift unsuccessfully on 2 – Windows desktops, 5 – laptops, including a MacBook. I say unsuccessfully because I was able to sort out the issue(s), and it worked for a while. Then it would start crashing. I noticed this more after an upgrade of either windows or Zwift. I felt that even on the MacBook there were too many other “things” (.dll’s, video driver versions, BTLE revisions and driver conflicts etc.) to waste my life on.
After speaking with a large number of my friends that use Zwift, and reading the forums, talking to people while Zwifting, I finally – after more than 2 years of pain & time – bought the latest and greatest ATV. I’ve had no issues for about 6 months.
I do agree with the troubleshooting steps above. Eliminate everything possible so you can isolate the issue. It’s all been said above.
My current setup is a little complex. Sorry there is no diagram. (Dan)
I do some testing of devices so I know for a fact that the Tacx Neo 2T, Neo 2, and Neo all connect to BTLE and ANT+ simultaneously. The biggest flaw in the Neo series is the cadence and it has been for each of the devices. That story is above. (note that some people say they don’t have this issue).
I have an ATV connected to the Neo2T and a Garmin HRM using BTLE. At the same time, the Neo 2T is broadcasting ANT+ to 2 – Garmin Edge 830’s and a Fenix F6. The Garmin HRM is connected to the ATV, 2, Edge 830’s and the F6. I also have Gamin Vector 3 and Rally pedals connected to one or more of the heads depending on the testing. So, concurrent connections is not the issue.
MacBook likely shares the same connection limit that the ATV does. (but I don’t know if that’s true). Max 2 Bluetooth devices. After that, companion comes to the rescue.
From the diagnostic logging that is turned on for data collection on the Edge devices, it is visible that the Neo does drop connection, but not long enough for the Zwift gamming app to notice.
It’s important that the Neo is on the latest firmware which is 0.0.38 as of last week when I checked. It resolves a number of issues depending on the firmware that your Neo is on. But this does not fix the cadence issue. You can update the firmware via the Tacx App, if you haven’t already.
This probably doesn’t help, but, that’s my 2 cents.