Is it possible to change the UUID of the BLE server/service?

[aehs]

Hello and thank you for the great work, I love it!

I have a data field from https://apps.garmin.com/apps/0e10bae1-9753-4915-b856-040d0cbdd82a?tid=1 on my Venu Sq 2 Music.
And on an ESp32, I have https://github.com/zpukr/ArduRower/tree/main
running. That works quite well, and the values are transferred via FTMS.

Now I have tried to connect the data field to openrowingmonitor, but as expected, this does not work. My assumption is that the data field only connects to a specific BLE name. So my question is: is it possible to change the BLE name in openrowingmonitor?

EDIT:
I have now discovered that the search for a specific UUID is taking place. Where and how can I change it?
The search is performed by FTMS UUID 00001826-0000-1000-8000-00805f9b34fb

Thanks and best regards,
André

[Abasz]

Not sure I understand the question. If you switch the broadcast to FTMS on ORM GUI it will broadcast on that UUID. This is the FTMS UIID as per the spec.

A side note, if you have esp32 you cant try: https://github.com/Abasz/ESPRowingMonitor

It is ESP32 based and runs a very close version of the algorithm of ORM (with some simplification).

[JaapvanEkris]

Hello and thank you for the great work, I love it!

I have a data field from https://apps.garmin.com/apps/0e10bae1-9753-4915-b856-040d0cbdd82a?tid=1 on my Venu Sq 2 Music. And on an ESp32, I have https://github.com/zpukr/ArduRower/tree/main running. That works quite well, and the values are transferred via FTMS.

My understanding us that Garmin never understood FTMS, that is why we provide the CPP and CSC profiles. Has that changed?

EDIT: I have now discovered that the search for a specific UUID is taking place. Where and how can I change it? The search is performed by FTMS UUID 00001826-0000-1000-8000-00805f9b34fb

Alternative is to upload directly to Garmin Connect. There are some uploaders for that.

[Abasz]

The correct statment is that Garmin does not support FTMS natively (i.e. in their own stock profiles). They prefer (rather force) their own ANT+ profile (which is now conveniently deprecated...). But this does not mean that a custom app on the watch cannot connect to FTMS. Actually it can connect to any BLE device but you need to write the app from scratch.

[JaapvanEkris]

The correct statment is that Garmin does not support FTMS natively (i.e. in their own stock profiles). They prefer (rather force) their own ANT+ profile (which is now conveniently deprecated...). But this does not mean that a custom app on the watch cannot connect to FTMS. Actually it can connect to any BLE device but you need to write the app from scratch.

Ah, that explains it. So in essence the app-maker on the Garmin side has been too restrictive, potentially just creating a tandem of apps where only a specific watch app connects to a very specific FTMS implementation. Sounds like a minefueld where we would be walking into any implementation issues with regards to the official FTMS spec.