My Pebble Time 2 is on the way and I reconnected my fist Pebble with the app after the Bluetooth switch. Sadly I need Bluetooth on the Sailfish OS side for the Audio. Also the Android App isn’t syncing calendar entries and I can’t add a location to get the weather.
In the meantime, I hacked together
a way to get Sailfish OS notifications to my Pebble paired via AppSupport.
I don’t have a release-ready version yet, as I’d like to do some testing first - once I get my test device back. ![]()
If any developers want to give it a try:
https://github.com/dscheinah/harbour-rockbridge
Unfortunately, it currently only works with Gadgetbridge, as I couldn’t find a corresponding Intent API for the official new Pebble app.
yeah there are no intents for the official pebble app
awesome project though!
Unfortunately, yes. It would be great to have something like that available for automation. Do you think it would be worth opening a feature request in coredevices/mobileapp?
Anyway, I just got the first release-ready version done: https://openrepos.net/content/coanteen/rockbridge
if its just a feature request i dont think it’ll get taken (a lot of overhead on the 2 devs) but if you do a pr i think there is a good chance it’d get merged
@CoanTeen can you outline this solution?
Did I get it right, that this is a workaround to supply Sailfish OS notifications into Gadgetbridge, which is an unofficial method to connect the pebble to the phone.
How does this compare to the Pebble app? What is gained or lost by pairing with Gadgetbridge? Why communicate with Gadgetbridge and not the Pebble app?
Currently it is not yet possible to pair the new Pebble watches directly with a native Sailfish app such as Rockpool.
Thanks to the new Bluetooth Bridge, however, the watches can be paired through Android apps running inside Sailfish’s Android AppSupport. This works with apps such as Gadgetbridge or the official Pebble app. Since these apps run in an isolated environment, some features are limited. One of those limitations is access to native Sailfish notifications.
To work around this, I created RockBridge. It acts as a bridge by forwarding native Sailfish notifications to the watch. It does this using a special Gadgetbridge API.
At the moment, this API is only available in Gadgetbridge. The official Pebble app does not support it, and I currently don’t know of another way to achieve the same result.
To use a new Pebble watch with Sailfish OS, enable Bluetooth for Android AppSupport and pair the watch using Gadgetbridge. If you also want to receive native Sailfish notifications on your watch, install RockBridge as well.
What would I trade for the Sailfish OS notifications I would gain with Gadgetbridge and RockBridge compared to the official Pebble App without Sailfish OS notifications?
PS: I messed up and I will go and replace AppSupport in my post above with Gadgetbridge.
I’m not 100% sure since I only recently started using Gadgetbridge myself. So far, this has been my experience:
-
The initial pairing can be a bit unreliable, so you need to be somewhat lucky.
-
Installing apps is a bit unintuitive.
-
Some device-specific settings aren’t available (e.g. multi-button shortcuts).
Overall, though, it seems to work well as a replacement. Depending on your needs, it may even be the better option in some cases.
Work in progress. Lots of thanks to @JPlexer for adapting the official Pebble app backend to Rockpool!
Thanks for the work, I’m looking forward to getting my Pebble Time 2 to test it on my Sony or my future J2 on the way.
Are there plans to put the app in Chum?
Not currently possible to get it in Chum, as the daemon is going to very difficult to build on OBS. Maybe one day…
And in Storeman? Or is there a rpm to install manually…?
I’ll let you know when it’s finished
Thank you! No rush, I am just a bit curious ![]()
Hi, just wanted to check how is the progress?
I think i’ve got most of it implemented now, but there’s a lot of testing to do before I could say it was ready for release.


