integrate openbikecontrol logic into maximumtrainer - placeholder

[MaximumTrainer]

https://github.com/OpenBikeControl/bikecontrol

[maximus321]

Looked into what this integration would actually mean, writing it up so we can decide.

What "integrating" means

Not using any BikeControl code. The implementable piece is the open OpenBikeControl protocol: MaximumTrainer advertises _openbikecontrol._tcp via mDNS, accepts a TCP connection from the BikeControl phone app, and parses a small binary button-event format (standard action IDs for shift up/down, ERG intensity, pause/resume, skip interval, etc.). The BikeControl app handles all controller pairing on its side, including the Zwift server handshake needed to unlock/use both Click controllers.

Pro

• Left controller / full paddle sets (Zwift Play, Ride) without us touching Zwift's encrypted unlock flow.
• The rest of their device matrix comes free: Di2, SRAM AXS, Sterzo steering, gamepads, and phone-as-remote (pause/skip/intensity from the handlebars with no extra hardware).
• Small, clean surface on our side: one TCP parser + mDNS advertising, open spec, no license or patent exposure, and their Zwift protocol churn never breaks our build.

Con

• User complexity: a second app that must be running on a phone, on the same WiFi, with mDNS discovery working across firewalls/VLANs. BikeControl's repo has a dedicated Windows IPv6 troubleshooting doc, which hints at the support burden. Today the right Click is: enable the toggle, ride.
• Third-party dependency for the headline feature: BikeControl's Zwift controller support is beta, closed source (private prop submodule), non-commercial licensed, and routed through Zwift's auth servers with the rider's Zwift credentials. Zwift can break or block it at any time, and we would field the complaints.
• Debugging spans their app + network + our parser instead of one BLE link we own end to end.
• Qt has no mDNS responder, so we would need to embed/vendor one across four platforms.
• Unproven demand: the right Click already covers gear up/down, which is most of the value. Unknown how many users own a left Click or Play set and would install a companion app for it.

Recommendation

Not worth implementing right now. The left controller alone does not justify the added user complexity and the dependency on a beta, closed, server-dependent component. The current direct right-Click support (no unlock, no companion app) is the sweet spot for what users actually have.

Revisit if any of these change:

1. Zwift opens up their controller protocol officially, in which case we integrate directly and skip the workaround entirely (the preferred outcome).
2. Real user demand shows up for left Click / Play / Ride or the phone-remote use case.
3. BikeControl's Zwift support exits beta and proves stable.

Leaving the issue open as a parked decision record unless we would rather close it.

[maximus321]

Maybe I misread, I thought you wanted to integrate BikeControl protocol, but it is integrate "bikecontrol logic", and part of this was already done, we only suport the zwift click v2 right handle, only device I could validate since I don't have the others. Maybe a testing phase with other zwift controller can be done. But I think we are aligned to not add complexity in the UX by adding BikeControl protocol, but instead support the controller directly in the app? Cheers

[MaximumTrainer]

Thanks, tbh I wasn't thinking we would literally use the openbikecontrol app, more so use the code as an example of how to replicate in this codebase. You are spot on @maximus321 we need to keep the UX simple & straightforward for the user. ie they can pair zwift controllers along with any other equipment directly in the maximumtrainer application itself utlizing the functionality directly in maximumtrainer. So Zero need to use the openbikecontrol application or have that running alongside.
Sorry I should have been clearer (hence the placeholder notation in the title)

[maximus321]

Sounds good! we can validate with more devices then as more user test them. I can say the zwift click v2 works perfectly (right side controller only, because of zwift is locking the left) but it is enough to control the workout difficulty or virtual shifting.