Closed genik88 closed 3 months ago
uhm there is a
Thu. Jun. 27 12:11:29 2024 1719504689838 Debug: ../src/virtualdevices/virtualbike.cpp void virtualbike::error(QLowEnergyController::Error) "virtualbike::controller:ERROR AdvertisingError"
Working on my side
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I can't get this to work. QZ is running on Android, TrainerDay is running on iOS. Power sensor is enabled under Experimental settings.
I've tried selecting Cycling Power (see below) and Smart Trainer KICKR CORE within TrainerDay. There is no reported T.Power on QZ and my Echelon EX-3 is not being controlled.
power sensor must not be selected, otherwise trainer day can't control the bike also rename your android device to bike (only 4 letters) and reboot it
power sensor must not be selected, otherwise trainer day can't control the bike also rename your android device to bike (only 4 letters) and reboot it
I renamed the device to bike, rebooted. For some reason now I only see Cycling Power (bike) as a sensor in TD, KICK Core is gone and doesn't come up anymore. I've restarted the TD app multiple times.
It's right that you don't see the kickr core because it's connected to QZ. Did you disable the power sensor in the experimental settings in QZ?
It's right that you don't see the kickr core because it's connected to QZ. Did you disable the power sensor in the experimental settings in QZ?
Previously I could pick a 'KICK Core' device in TD. Now I can only choose Cyling Power (bike, some id) as a device in TD. I have enabled the power sensor under Experimental settings. I have rebooted Android, restarted QZ, reinstalled TD on iOS. Nothing works.
I said you have to DISABLE the power sensor setting in the experimental settings to show QZ there as a power sensor and cadence and speed and controllable as shown in my shots above here. Also, as i said, it's normal that you can't see the KICK CORE because it's connected to QZ: once it connected it doesn't broadcast anymore: what you saw it was just a bluetooth cache ghost (or you wasn't connected correctly to the KICKR from QZ).
Anyway again:
If it doesn't, post a fresh debug log
I said you have to DISABLE the power sensor setting in the experimental settings to show QZ there as a power sensor and cadence and speed and controllable as shown in my shots above here. Also, as i said, it's normal that you can't see the KICK CORE because it's connected to QZ: once it connected it doesn't broadcast anymore: what you saw it was just a bluetooth cache ghost (or you wasn't connected correctly to the KICKR from QZ).
Anyway again:
- disable the power sensor setting in qz
- open TD and pair it up
If it doesn't, post a fresh debug log
Sorry for the confusion. It seems we are both communicating past each other. I'm not using a KICKR Core, Roberto haha. Anyway I disabled the power sensor (I thought you said previously I should enable it, but whatever) it works great (chefs kiss) now. Thanks!
if you can remember that maintain qz is a really hard job: if you didn't have already, remember to join patreon or buy me a coffee from the sponsors page above here. thanks
I just did a one hour ride. Unfortunately the connection with QZ from TrainerDay was dropped multiple (3) times during the ride. When this happens a new device is shown in the devices screen (Smart Trainer (some_new_id) and I have to unpair the old one and pair the new one.
Was qz always on foreground? Did you try the opposite? Td on android and qz on iPhone? It seems a classic android Bluetooth issue (by the way which android device is it)?
Roberto Viola Software engineer and open source enthusiast http://robertoviola.cloud
Il giorno ven 9 ago 2024 alle 21:49 Dennis de Vaal @.***> ha scritto:
I just did a one hour ride. Unfortunately the connection with QZ from TrainerDay was dropped multiple (3) times during the ride. When this happens a new device is shown in the devices screen (Smart Trainer (some_new_id) and I have to unpair the old one and pair the new one.
debug-Fri_Aug_9_20_03_52_2024.zip https://github.com/user-attachments/files/16566191/debug-Fri_Aug_9_20_03_52_2024.zip
— Reply to this email directly, view it on GitHub https://github.com/cagnulein/qdomyos-zwift/issues/2413#issuecomment-2278637657, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAALYWFVFEKNO3N3GHVJPN3ZQUMLVAVCNFSM6AAAAABKAIQVLWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZYGYZTONRVG4 . You are receiving this because you modified the open/close state.Message ID: @.***>
Was qz always on foreground? Did you try the opposite? Td on android and qz on iPhone? It seems a classic android Bluetooth issue (by the way which android device is it)? Roberto Viola Software engineer and open source enthusiast http://robertoviola.cloud Il giorno ven 9 ago 2024 alle 21:49 Dennis de Vaal @.> ha scritto: … I just did a one hour ride. Unfortunately the connection with QZ from TrainerDay was dropped multiple (3) times during the ride. When this happens a new device is shown in the devices screen (Smart Trainer (some_new_id) and I have to unpair the old one and pair the new one. debug-Fri_Aug_9_20_03_52_2024.zip https://github.com/user-attachments/files/16566191/debug-Fri_Aug_9_20_03_52_2024.zip — Reply to this email directly, view it on GitHub <#2413 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAALYWFVFEKNO3N3GHVJPN3ZQUMLVAVCNFSM6AAAAABKAIQVLWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZYGYZTONRVG4 . You are receiving this because you modified the open/close state.Message ID: @.>
Yeah it was always on the foreground. It's a Galaxy Note10+. (Android 12). Always worked fine with TrainerRoad and Peloton. I still need to try the opposite though. Will let you know.
If it works with other apps, it could be just a td bug, try also to contact them
Roberto Viola Software engineer and open source enthusiast http://robertoviola.cloud
Il giorno ven 9 ago 2024 alle 22:05 Dennis de Vaal @.***> ha scritto:
Was qz always on foreground? Did you try the opposite? Td on android and qz on iPhone? It seems a classic android Bluetooth issue (by the way which android device is it)? Roberto Viola Software engineer and open source enthusiast http://robertoviola.cloud Il giorno ven 9 ago 2024 alle 21:49 Dennis de Vaal @.
> ha scritto: … <#m-5168385712749192803> I just did a one hour ride. Unfortunately the connection with QZ from TrainerDay was dropped multiple (3) times during the ride. When this happens a new device is shown in the devices screen (Smart Trainer (some_new_id) and I have to unpair the old one and pair the new one. debug-Fri_Aug_9_20_03_52_2024.zip https://github.com/user-attachments/files/16566191/debug-Fri_Aug_9_20_03_52_2024.zip https://github.com/user-attachments/files/16566191/debug-Fri_Aug_9_20_03_52_2024.zip — Reply to this email directly, view it on GitHub <#2413 (comment) https://github.com/cagnulein/qdomyos-zwift/issues/2413#issuecomment-2278637657>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAALYWFVFEKNO3N3GHVJPN3ZQUMLVAVCNFSM6AAAAABKAIQVLWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZYGYZTONRVG4 https://github.com/notifications/unsubscribe-auth/AAALYWFVFEKNO3N3GHVJPN3ZQUMLVAVCNFSM6AAAAABKAIQVLWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZYGYZTONRVG4 . You are receiving this because you modified the open/close state.Message ID: @.>
Yeah it was always on the foreground. It's a Galaxy Note10+. (Android 12). Always worked fine with TrainerRoad and Peloton. I still need to try the opposite though. Will let you know.
— Reply to this email directly, view it on GitHub https://github.com/cagnulein/qdomyos-zwift/issues/2413#issuecomment-2278662301, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAALYWESYVOL3A4A75WN4LTZQUOKFAVCNFSM6AAAAABKAIQVLWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZYGY3DEMZQGE . You are receiving this because you modified the open/close state.Message ID: @.***>
debug-Thu_Jun_27_12_11_15_2024.log