Yesterday I encountered issues with the (Neo2T) trainer connecting via Bluetooth. This is the second time within a one month span. Using a combination of Apple iPad and Windows 10 PC, I was able to deduce that the problem lies within the trainer itself and not the connecting "computers". The trainer itself indicates all systems are nominal and no evidence of overheating (one solid red and blue light each). Both times, the disconnects begin relatively early in a ride (4-5 miles) and progressively get worse. I was able to make it through 15 miles when I switched to the iPad from the PC, but it still ultimately lost the connection (and the warning signs were already there after 7-8 miles - i.e. unusual and substantial cadence/power changes with steady pedaling effort).
While attempting to troubleshoot, I thought I'd disconnect power to the trainer as part of the process. At the time, I was still Bluetooth connected within Zwift and was surprised to find that disconnecting the power (at the trainer) did not break the connection. Furthermore, I could still detect the trainer using the Tacx Utility app. So it seems that there must be residual remaining voltage (within the trainer) after disconnecting that is sufficient to power the Bluetooth emitter.
I mention the above because the last time I had intermittent connection issues, I was able to fix the problem for several weeks by upgrading the firmware. That leads me to wonder if the Bluetooth emitter hardware accumulates errors with time, much like a router/modem will do. If so, then attempting to reset by unplugging the DC charger briefly for 1-2 minutes (at the trainer end) may not be sufficient to "clear" the Bluetooth memory. To test this theory, I unplugged overnight and will try another ride today without changing anything else. I'll report back the outcome.
Just curious if anyone else has encountered similar issues or if Garmin tech - should they actually be monitoring this forum - might care to comment?
