Command-line tool for COOSPO CS500/CS600 bike computers over Bluetooth LE. It shows device
information, battery level and memory usage, and downloads your activities (.fit files) without the
CoospoRide app.
$ coospo info
Searching for Coospo compatible device...
Connected to CS500-1234567
Model: CS500
Serial: 1234567
Hardware: V1.41
Firmware: V1.5.0
Battery: 87%
Memory: 25.3M/26.9M used (93%)
| Device | Status |
|---|---|
| COOSPO CS500 | tested (hardware V1.41, firmware V1.5.0) |
| COOSPO CS600 | expected to work (same protocol family), not tested yet |
Older COOSPO models (BC102/107, BC200) use a different protocol (YMODEM over Nordic UART). Use xoss_sync for those.
If you own a CS600 or another model, please report whether it works in an issue.
Requires Python 3.13+ and a Bluetooth LE adapter. It uses bleak, so it should run on Linux (BlueZ), Windows and macOS; so far it's been tested on Linux.
pipx install coospo-cli
pip install coospo-cli works too. For the latest development version:
pipx install git+https://github.com/blshkv/coospo-cli
coospo info show model, serial number, firmware, battery and memory usage
coospo sync download new activities into fit_files/
coospo sync -o ~/rides ... into another directory
coospo get filelist.txt Setting.json download specific files
coospo -n CS500-1234567 info pick one of several devices by name
coospo -a AA:BB:CC:DD:EE:FF info ... or by Bluetooth address
Run coospo --help or coospo COMMAND --help for all options.
syncfirst downloadsfilelist.txt(the list of activities on the device), then every.fitfile not already in the output directory. It's safe to interrupt and run again: files are only saved after the transfer has been verified, and existing ones are skipped.- Nothing is ever deleted from the device.
- The exit status is 0 on success and 1 if the device wasn't found or any file failed.
- Device not found: the bike computer stops advertising while it is connected to the phone. Close CoospoRide or turn off Bluetooth on the phone, and make sure the device is switched on.
- Several devices nearby: use
-nwith the full name shown on the device (e.g.CS500-1234567) or-awith its Bluetooth address.
The CS500 doesn't use the Nordic UART/YMODEM protocol of older models. It uses vendor service
0xFDA0 with HDLC-like frames carrying protobuf payloads, plus a separate raw data channel for file
contents. PROTOCOL.md documents everything known so far.
tools/gatt_dump.py (in the repository, not installed with the package) lists a device's GATT
services and characteristics, which is a quick way to check whether another model uses the same
service:
python3 tools/gatt_dump.py CS600
Support for new devices or features (setting the clock, uploading settings) comes from capturing what the official app does:
- On Android, enable Developer options → Enable Bluetooth HCI snoop log, then toggle Bluetooth off and on.
- Use the feature in CoospoRide.
- Run
adb bugreport bugreport.zip; the log isFS/data/misc/bluetooth/logs/btsnoop_hci.log.
Don't attach the log or the bug report to a public issue. They contain personal data such as your location, device addresses and ride history. Describe what you did and share the relevant frames instead.
coospo sync downloads the activities the index (~/.local/state/coospo/index.db) does not know
yet. coospo watch does the same whenever the device comes into range, at most once per --interval
(default 10 minutes). Both can pass each new activity to a command, e.g. an uploader:
coospo init # once: ignore the rides already on the device
coospo watch --post-sync ~/bin/strava-upload
contrib/strava-upload is such an uploader for Strava (standard library only). Create an API
application at strava.com/settings/api with the callback domain localhost, copy the script to
~/bin, and run strava-upload auth once.
- The command is run as
CMD FILE, withCOOSPO_FILE,COOSPO_SERIALandCOOSPO_ACTIVITY_TIMEin the environment. If it exits non-zero it is retried with growing delays (1 min up to 6 h). - Downloaded files are deleted once the command succeeds. With
--output DIRthey are kept there. Without--post-sync, files are always kept (default~/.local/share/coospo/fit_files). - A file that is still being recorded is not a complete FIT file; it is skipped and fetched again later.
- Settings can go in
~/.config/coospo/config.toml(or$XDG_CONFIG_HOME/coospo/config.toml, or the file given with-c):name,address,scan_timeout,output,post_sync,interval. Seecontrib/config.tomlfor a commented sample. contrib/has a systemd user unit and an OpenRC init script that runcoospo watch.
pip install -e .
python3 -m unittest discover -s tests
GNU General Public License v3.0 or later, see LICENSE.
Inspired by xoss_sync, which supports XOSS, Cycplus and older COOSPO devices.