Is the connection via bluetooth or IP? #3512
-
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
Hi @ciarancoffey! I'm Dosu and I’m helping the qdomyos-zwift team. The connection between QZCompanionNordictrackTreadmill.apk and qdomyos-zwift is indeed via TCP/IP, configured by IP address. The ethernet symbol next to the Wahoo KICKR 0000 33 in Zwift almost certainly means Zwift has discovered the device over the network, not Bluetooth—this matches both UI conventions and how the virtual device is set up in QZ Companion for network-based connections (source). Running qdomyos-zwift in a Docker container on another server is supported and should work fine as long as the devices/apps can reach each other over the network. The system is designed for flexible deployment, including containerized setups, and does not require the software to run on the same host as the physical connection device (source). Let me know if you need details on Docker setup or network configuration! To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other |
Beta Was this translation helpful? Give feedback.
Hi @ciarancoffey! I'm Dosu and I’m helping the qdomyos-zwift team.
The connection between QZCompanionNordictrackTreadmill.apk and qdomyos-zwift is indeed via TCP/IP, configured by IP address. The ethernet symbol next to the Wahoo KICKR 0000 33 in Zwift almost certainly means Zwift has discovered the device over the network, not Bluetooth—this matches both UI conventions and how the virtual device is set up in QZ Companion for network-based connections (source).
Running qdomyos-zwift in a Docker container on another server is supported and should work fine as long as the devices/apps can reach each other over the network. The system is designed for flexible deployment, including container…