-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is the Zwift Steerer code still working? #4
Comments
I found the same issue, exactly as @Berg0162 described (testing with nRF). I suppose, they did a update on ZWIFT togheter with a firmware update on STERZO to block "parallel-versions" of it: Search on the web, I found very interesting input from Keith Wakeham - see https://www.youtube.com/watch?v=BPVFjz5zD4g to get our Home Made Version "activated" on ZWIFT - if it is still to update... I can say it... Below is the piece of example code it should be included into the code.. but nothing for me, I'm just a beginner - maybe experts could help us. // uint16_t calculate_response_code( uint16_t challenge ) |
Does anyone have some information, or better: a solution for this? |
I'm also interested in knowing this. Anyone made it work? |
@vincent290587 Thx for the contribution. Could it be that the STEERING_RX_CHAR_UUID is also changed? Or the initial notify values? Because zwift doesn't respond anything on the write characteristic. |
I added the complete code to the repo, they indeed added more characteristics |
I know that people have been reverse engineering the zwift play controllers encryption and i think it would be a better way to go than steerzo, as you also would have the option to use the extra button functionality you don't get with a keyboard, like rideon bombs and breaking and potentially gear changes at some point. |
I have been testing the Zwift-Steerer code with little success. The code connects (successful) via the Power Pairing screen but the steering activation is hanging with "Activating" forever... No transfer of steering angles is ever reached...
I would not be surprised if the protocol has been changed with the latest Sterzo/Zwift update....? It seems that Zwift never issues the 0310 starting value on Char 31... By hand that works : I did some testing with NRF-Connect and the code reacts correctly on the offered protocol data...?
Do you have a working version at this moment?
Kind regards,
Jörgen van den Berg.
The text was updated successfully, but these errors were encountered: