Notices

Just released 1.0 (feature complete) to OpenRepos.

Main new features:

• Firmware Upgrade support
• Music volume controls alter the system volume (thanks to Andrew Branson)

Hi,
I'm new here, and want to say thanks a lot for your great work on this! I bought a used Pebble Steel last week, and was happy to see how nicely it plays with my Jolla through the pebble daemon and app - especially after the last update, which solved the app uploading problem. Thank you!

I now want to try writing a Pebble+Sailfish companion app. For this I've started playing around with the org.pebbled interface through dbus-python, but I must admit that I'm very much of a DBus novice. I manage to ping my pebble and to upload, unload and remove apps, as well as to read the various properties. But I can not figure out how to call SendAppMessage. Does it need any more argument in addition to uuid and message? I get 'TypeError: More items found in D-Bus signature than in Python arguments'. (And 'a{sv]' means that the message argument should be a dictionary with strings as keys, right?) Please excuse me for what might be stupid questions!

Also, is there any way to send a notification text to the Pebble from a script on the phone (through org.pebbled or otherwise)?

You should note that Firmware upgrade support is a paid option .

Only the UI screen. ;-)

All the mechanic is present and you are free to upgrade the firmware using any other tool (i.e. qdbus command line).

Good work!

By the way - what with installation of custom fw? f.ex. one from pebblebits?

No idea. I didn't try it.

Well, custom sw is a .pbz file - so when I'm d'loading it on the phone and clicked on it - app is opened but no action is taken.
So far custom fw is a good option (at least to read messages in still not supported languages) - so it will be a good option to add such a feature.

You may try uploading it manually using DBus interface.
But I do not support it, so do it on your own risk.

It's basically the same file as the original though.
Just not picked from the Pebble servers.

Writing platform specific companion apps is not that good idea. They are not portable and restrict your companion app to one platform only.

Pebble SDKv2 introduced JavaScript based companion apps you should use. We support them very well. Also pebbled will make sure your JS companion app gets started whenever user opens the app on the watch and it does not have to be run manually or always in background. Just read Pebble SDKv2 documentation and follow.