Suunto 9 Peak Pro / SuuntoPlus Editor 1.42 — secure BLE bonding and GAP Peripheral capabilities? (Bosch eBike integration)
-
Hello SuuntoPlus developers,
I am building a SuuntoPlus sports app for a Suunto 9 Peak Pro and a Bosch Performance Line CX Smart System e-bike (eBike Flow). The goal is to display e-bike battery state of charge (%) and rider power (W) directly on the watch, without a smartphone bridge or any additional hardware.
The app already starts and renders its diagnostic screen in the SuuntoPlus simulator with the Suunto 9 Peak Pro / E-MTB profile. I inspected the local SuuntoPlus Editor v1.42.0 documentation (developer-doc/reference.html) and found appConn.connect(), appConn.regUuid(), appConn.readChar(), appConn.writeChar() and appConn.enaCharNotf(). These appear to describe a GAP Central / GATT Client workflow.
The official Bosch Live Data Interface has an unusual BLE role arrangement: Bosch acts as GAP Central, while the accessory must act as a connectable GAP Peripheral and advertise the Bosch service solicitation UUID 0000eb20-eaa2-11e9-81b4-2a2ae2dbcce4. The connection requires secure bonding and an appropriate ATT MTU. I could not find SuuntoPlus APIs for advertising/Peripheral mode, pairing/bonding or MTU control.
Could someone from the SuuntoPlus team clarify, specifically for the Suunto 9 Peak Pro firmware, whether:
A SuuntoPlus device app can advertise a custom connectable BLE peripheral / service solicitation UUID and accept an incoming central connection. If not, a SuuntoPlus app using appConn.connect() can connect to a previously unpaired, secured BLE device, invoke OS-managed LE Secure Connections pairing/bonding, then subscribe to custom GATT notifications (similar to the BLE central connection used by the Bosch eBike Flow app). Device apps can reuse a Bluetooth bond created from the watch's standard Pair sensor menu with a custom GATT service, not just the supported Power POD profile. There are platform limitations for appConn bonding, connection concurrency and/or GATT MTU on the 9 Peak Pro. If unsupported, is a documented workaround, alternative SDK API, or Suunto-supported integration available that does not require a hardware bridge?I would especially appreciate a yes/no answer for the 9 Peak Pro, and a link to working SDK examples or the applicable API/firmware constraints. I do not want to attempt risky pairing and affect the user’s existing Bosch eBike Flow bond without a supported procedure.
Thank you.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login