Hello Everyone
I purchased my Trek Fuel Ex-e 9.5 back in November. I've had an ongoing issue with connecting the Trek Central App since my purchase.
I initially took it to my dealer in November to check for Firmware Issues/Errors but it came back clean. They did submit a request to Trek for comment on the issue, however Trek's last response was that there would be an app update out at the start of February that would resolve the issue. I've since re-downloaded the app and the issue continues.
The issue is as follows - I've installed the app, logged into my account, I then find the bike through the app, the pairing code then appears on the bike and then I enter the code and the error occurs - "Something went wrong".
What the dealer and I have tried
I thought this was a good place to post to see if anyone else has experienced the issue and/or resolved it?
I saw a TQ representative was active on this forum so was wondering if they could provide some input on the issue @Roman
Thank you
I purchased my Trek Fuel Ex-e 9.5 back in November. I've had an ongoing issue with connecting the Trek Central App since my purchase.
I initially took it to my dealer in November to check for Firmware Issues/Errors but it came back clean. They did submit a request to Trek for comment on the issue, however Trek's last response was that there would be an app update out at the start of February that would resolve the issue. I've since re-downloaded the app and the issue continues.
The issue is as follows - I've installed the app, logged into my account, I then find the bike through the app, the pairing code then appears on the bike and then I enter the code and the error occurs - "Something went wrong".
What the dealer and I have tried
- Tried multiple different phones, both IOS and Android, none of them work
- Resetting the bike (Holding down power + down on remote)
- Checking for firmware update back in November
- Removing the Bluetooth connection to the bike from the phone
- Removing/Reconnecting Battery
I thought this was a good place to post to see if anyone else has experienced the issue and/or resolved it?
I saw a TQ representative was active on this forum so was wondering if they could provide some input on the issue @Roman
Thank you