Cycplus device: Missing characteristic: 00002a27...

[rusak47]

Hello!
Nice to see that someone is working on an alternative for a PC, thank you for your efforts!
I've tried to sync data from Cycplus device, but it fails.

✔ Select a XOSS device to connect to · M2_FAE4 (E4:FA:E7:***)
2024-06-10T05:37:14.353098Z  INFO f_xoss_util::cli::setup: Connecting to M2_FAE4 (E4:FA:E7:***)...
2024-06-10T05:37:14.355326Z  INFO bluez_async: Services already resolved.    
2024-06-10T05:37:14.355530Z  INFO new{id=hci0/dev_E4_FA_E7_***}: f_xoss::transport::device: Discovering XOSS services...
2024-06-10T05:37:14.382762Z ERROR f_xoss_util::cli::setup: Failed to connect to XOSS device:
 Failed to connect to XOSS device

Caused by:
    Missing characteristic: 00002a27-0000-1000-8000-00805f9b34fb

Is there a way to enable debug mode to dump more data?

[DCNick3]

I have my doubts that a cycplus device would have anything in common with a xoss nav (the only device that I have really tested with and written this piece of software for).

re: debug mode: you can set debug filters in RUST_LOG environment variables, syntax is documented here. Some simple ones can be RUST_LOG=trace or RUST_LOG=debug.

But it probably won't reveal anything new, f-xoss can't find the BLE services that are expected to be there for the protocol, so it cannot continue.

UPD: I see now that it uses the same Xoss companion app.. Curious, but still seems to have a different protocol. If any support is to be implemented ever, the protocol would need to be reverse-engineered.

[rusak47]

I have my doubts that a cycplus device would have anything in common with a xoss nav (the only device that I have really tested with and written this piece of software for).

re: debug mode: you can set debug filters in RUST_LOG environment variables, syntax is documented here. Some simple ones can be RUST_LOG=trace or RUST_LOG=debug.

But it probably won't reveal anything new, f-xoss can't find the BLE services that are expected to be there for the protocol, so it cannot continue.

UPD: I see now that it uses the same Xoss companion app.. Curious, but still seems to have a different protocol. If any support is to be implemented ever, the protocol would need to be reverse-engineered.

Thank you for the prompt reply. I had assumed that XOSS might use the same or a similar protocol for all of its devices, since both communicate via bluetooth. Anyway, i discovered that the XOSS app stores .fit data in the Android /data directory, which makes it much faster to access records there than hacking their protocol.

p.s. It would be nice from their side just to share it, as i can't image what could be so secret in communication protocol. Have you tried asking them for it?

[ekspla]

p.s. It would be nice from their side just to share it, as i can't image what could be so secret in communication protocol.

Most part (but not all) of the protocol is described in this Xingzhe's web site
Though it is described in Chinese, we can use web based translator.

Very recently, I've also implemented the protocol to Python to bring data from my XOSS G+.