Re: [Announce] Pebble Watch Connector daemon
 

DIN Time gave up doing weather too. I haven't bothered finding out why, though I believe it uses Yahoo as well.

But you can set it to use a specific location code rather than polling GPS. Might be an option (and might work with other faces too).

Re: [Announce] Pebble Watch Connector daemon
 

Could be that we're using old versions of these apps, and newer versions have an updated geo call. Pebbled doesn't support the app locker, so there's no support for detecting new versions of apps and upgrading them.

Re: [Announce] Pebble Watch Connector daemon
 

Looks like pebbled can't get GPS location - when I put it manually everything works. But for me it started right after latest OS update.

Re: [Announce] Pebble Watch Connector daemon
 

It does - the request to the yahoo geo lookup contains latitude and longitude. The result of that call comes back with an empty location code.

Re: [Announce] Pebble Watch Connector daemon
 

can not confirm!
i have not updated to latest sailfish as of yet but also do not get yahoo weather related info on pebble apps in my classic steel with latest non time classic firmware.

Re: [Announce] Pebble Watch Connector daemon
 

For example, this is what MyStyle is sending to Yahoo:

http://query.yahooapis.com/v1/public...22&format=json

"results":null is the problem. I believe it used to return a location code that could be used to look up the weather info.

Can anyone find any information as to the state of these services? I've turned up nothing yet.

Re: [Announce] Pebble Watch Connector daemon
 

It seems it was the Yahoo service shutting down, and face makers are now finding other solutions.

https://www.reddit.com/r/pebble/comm...yahoo_weather/

Re: [Announce] Pebble Watch Connector daemon
 

Warning!

If you haven't updated to firmware 3.9.x, I would hold off doing so for now. Two nights in a row since the update my watch has spontaneously deleted all applications and watchfaces from itself. Obviously that wouldn't matter too much if you were using Android / IOS, because they'd be reloaded as they're used, but on Sailfish it's a problem...

I'll try a factory reset and see if that gets me any further.

[edit - incidentally there also seem to be a few reports of terrible battery life on this version.]

Re: [Announce] Pebble Watch Connector daemon
 

False alarm, sorry about that.

Removing all watch applications / faces from the application, then doing a factory reset and adding a few back, seems to have fixed it, so it could have been a screwy upgrade, or maybe a misbehaving app, but it doesn't look like it's a fundamental problem with the firmware. (too early to say much about battery life though).

Re: [Announce] Pebble Watch Connector daemon
 

Pebble Time users can't upgrade past v3.6 with pebbled, I'm not sure how it detects the latest available FW - does the app require an update each time there's a new FW version?

Re: [Announce] Pebble Watch Connector daemon
 

I'm not sure it does for every minor version, but for major versions they seem to release in sync, and the firmwares are only available once you've upgraded the app.

At a complete guess though this might be because they're implementing new protocols (e.g. the speech thing, and now health), and once it's settled down maybe it'll be different.

Re: [Announce] Pebble Watch Connector daemon
 

When in doubt Use the source, Luke... ;-)
https://github.com/smokku/pebble/blo...irmware.cpp#L8

Pebble App gets the latest available firmware from http://pebblefw.s3.amazonaws.com/pebble/.../latest.json so it is always up to the latest version published by Pebble company. No magic in use there. When Pebble company pushes new firmware to AWS, pebbled will have it available. No sooner, no later.

(pebbled upgrade may be required only, when a new Pebble model hits the market - pebbled needs to know how is it codenamed and where to fetch its latest.json from.)

Re: [Announce] Pebble Watch Connector daemon
 

Mine is also stuck on 3.6. Pebble app is not though :)

Re: [Announce] Pebble Watch Connector daemon
 

v2.8 seems to be out for the Pebble Time Steel, are you saying they have released it via their Android and iOS apps but not made it available on that server?

Re: [Announce] Pebble Watch Connector daemon
 

Looks like that only checks for v3 firmware if the hardware id starts with 'snowy_'. Are those the Pebble Times?

Re: [Announce] Pebble Watch Connector daemon
 

Hi guys,

I am not sue if you are aware of a project called RockWork that is a Pebble app for Ubuntu Touch. It's open source and almost hitting v1.0. Pebble is involved in that project so should work properly on all watches from original OG to the PTR.

I think that is the best source for documentation, etc.

Re: [Announce] Pebble Watch Connector daemon
 

Yup. It is a rewrite of pebbled. You can see that if you follow the codebase from revision 1. ;-)
As with a long tradition of Ubuntu apps it does not credit the authors of code being rewritten. ;-)

Nope.
The best source for Pebble documentation are official libpebble and libpebble2.

Re: [Announce] Pebble Watch Connector daemon
 

I've been told by Pebble representative that some components in libpebble and libpebble2 are deprecated.

Anyway, I'll try your app on my Jolla Phone... :)

Re: [Announce] Pebble Watch Connector daemon
 

Looks like the string to the URL has to be 'release-v3.8' to pick up the latest releases, for all Pebble models. There's a migration firmware to install first though if you're below v3.0.0.

Re: [Announce] Pebble Watch Connector daemon
 

That is actually a tradition of most "app-store-first" platforms. I have plenty of experience here with the Nokia/Ovi store.... and "rewrite" is being too generous here.

That said, we cannot really compete with a full-time employee working on it. "Rewriting" it back from their version should be considered an option. For me at least it looks easier than writing a store UI.

They also removed support for the pre-3.0 firmware on the original models, btw.

Sadly no, their "documentation"/implementation is far from complete. Like every other smartwatch, I had to sniff their protocol out, otherwise I still wouldn't know how to upload a binary. Almost nothing of BlobDB is documented there.

The best source for documentation at this point is pebbled, and the fact that Ubuntu guys decided to rip it off entirely and even Pebble employees themselves are using parts of it now should be kind of proof...

Re: [Announce] Pebble Watch Connector daemon
 

I've been watching Rockwork a fair bit lately, and spoken to the author Michael on the Jolla Fan Club Telegram group. He is a Canonical employee, but this isn't his day job - he writes rockwork in his spare time.

Yes it started off with the pebbled code, but he's done a really nice job expanding and refactoring it. He's added a large amount of new support, and kept all of the Ubuntu specific stuff separate leaving a core libpebble that's really comprehensive. I believe we could add Sailfish support around it and even share a common codebase in the future, and Michael was keen on collaborating on that. Pebbled has stalled a bit lately since Smokku gave up on his Jolla, so Sailfish rockwork (Rockpool?) would be able to keep the flow of code coming and keep up to date.

Re: [Announce] Pebble Watch Connector daemon
 

Dude, we don't even have a release yet, and by the time you wrote this, I didn't even have my own name and no about dialog or something. I don't think that's the most important part. What went wrong in FOSS that everyone starts off with hating every other project? If you don't want other people to look at your code, don't publish it, it's as simple at that.

Actually in some areas Rockwork supports more stuff than libpebble2 by now.. I'd say the best documentation available is a combination of the two.

EDIT: fixed typo

Re: [Announce] Pebble Watch Connector daemon
 

If you look at the commit times of RockWork you'll notice that all of them are late night, mostly weekends. RockWork is really a spare time project. That said, how did this become about competition? I've intentionally made the platform integration very sparated from the rest of the code.

Actually in the beginning I started off trying to port the sailfish pebble directly, but then, all the SFOS specific parts were deeply integrated all over the place. After the 100th #ifdef I gave up and started from scratch, trying to avoid this mistake.

EDIT: Also, writing the store UI is super simple, that's a matter of an afternoon or so. Maintaining a WebView with all the hacks that integrates with the pebble store website is IMO *much* more hard work.

Yes, pebbled has been a pleasure to "rip off". At this point there is nothing useful for me in it any more, especially since support for watch firmware >= 3.0 is quite poor. Anyhow, the offer still stands, I'd be happy to accept a SFOS backend in RockWork.

Re: [Announce] Pebble Watch Connector daemon
 

A more appropriate question would be: what went wrong in FOSS that everyone starts with forking, renaming the project, wrapping behind their doors, refactoring, rewriting, and only then offering to maybe, you know, actually share code and avoid a fork?

Specially when upstream is still quite alive with plenty of contributors, if only slow?

The sad part is that we had the same discussion like, less than a few months ago..

But oh well, that opportunity is lost already, so let's center on the future. I personally agree on the store UI changes and dropping pre3.0 support. Slots are too annoying either way.

EDIT:
In the sense of evaluating what will be the best option ahead for users (and developers) of Pebble and Sailfish, and at this point, I believe it's 'embracing your fork'.

But no need to "act surprised" when meeting resistance after taking over the reins of still-alive project.

Re: [Announce] Pebble Watch Connector daemon
 

I didn't completely give up on SailfishOS though.
I'm still hoping that SFOS port for OnePlus One reaches the state that it could replace Android as my daily driver.
I bought OnePlus One exactly because it looked like it would be any day now... and after a year - still big NOPE... :(

Re: [Announce] Pebble Watch Connector daemon
 

I really wanted to reuse pebbled as it was, I think I even still have a directory on my disk where all the SFOS stuff is #ifdef'ed out and replaced with ubuntu specific things. It just wasn't feasible any more at some point. Reusing software is a hard thing if it hasn't been created with platform abstraction in mind. I really hope I did a decent job with that in RockWork (as I've only ran it on Ubuntu so far, this part yet has to be proven).

Re: [Announce] Pebble Watch Connector daemon
 

I've been having a lot of fun trying to port Rockwork back over to Sailfish. The daemon's running, and connecting to the pebble (v3 firmware). Music/volume control works, and notifications, which have lots more flavours than the old v2: telegram, whatsapp, hangouts, which i've mapped over to the android and native apps where present. I also managed to find a bit of code to decode the notification actions, so you can now open the email on the phone from the watch.

Re: [Announce] Pebble Watch Connector daemon
 

This is awesome :) despite some initial misunderstandings, it looks like things are progressing to the point where the fork will contribute some useful enhancements back to the original project.

There's so much overlap between people interested in Sailfish and Ubuntu Touch, that it makes a lot of sense to collaborate on this!

Re: [Announce] Pebble Watch Connector daemon
 

Awesome news! With the authorization of mzanetti or smoku (if necessary, I don't know), is that something you can publish at some point ?

Thanks!

Re: [Announce] Pebble Watch Connector daemon
 

Oh certainly. I've got it installing as an rpm now, but diving into the QML has been tricky so far, especially seeing as I don't really know much about that. The Rockwork QML looks much more complex than anything I've seen in Sailfish so far, and my usual technique of cobbling it together using other projects as example isn't really working - there are just too many elements and attributes :).

What I might do is get the platform integration for the daemon mostly together, then pop it up on Github and see if anyone else fancies looking after the UI. If not, then I'll just have to get a book or something and learn it properly.

Mzanetti has been giving me tips, and I'm pretty sure smoku is aware and ok with it.

Re: [Announce] Pebble Watch Connector daemon
 

That would be awesome, I know some QML so will definitely give it a look once it's up on GitHub and I expect I'm not the only one.

Thanks Smoku, Abranson & Mzanetti

Re: [Announce] Pebble Watch Connector daemon
 

Cool. I'm away next week so I'll get it up before the weekend. Looking forward to some collaboration!

Re: [Announce] Pebble Watch Connector daemon
 

https://github.com/abranson/rockpool is up, but it's very preliminary and not ready for day-to-day use, so please don't upgrade your pebble classics to v3 just to try it or you'll be sorely disappointed. I wanted to fix the crash on callEnded, but ran out of time and thought it best to get it up asap anyway. Contributions welcome.

Re: [Announce] Pebble Watch Connector daemon
 

"Rockpool, a Sailfish port of Rockwork on Ubuntu, which is a port of Pebbled for Sailfish"

<inserting "Yo Dawg" meme>
http://i.imgur.com/KL0uxZn.jpg

Re: [Announce] Pebble Watch Connector daemon
 

Most of the code has been written from scratch...

Re: [Announce] Pebble Watch Connector daemon
 

Still funny!

Re: [Announce] Pebble Watch Connector daemon
 

I'd say the figure was somewhere between 'most' and 'a lot of'. Much of the new stuff has been inspired by the old, and it's interesting to see the echoes all the way back to skipping stones. Still, if we cared about scoresheets and timecards we wouldn't be doing this. It was intended to be humorous...

Re: [Announce] Pebble Watch Connector daemon
 

To be completely honest, pebbled started as waterwatch. ;-)

https://github.com/smokku/pebble/blo...d4fb/README.md

Re: [Announce] Pebble Watch Connector daemon
 

I'm just wondering how you're going keep up with RockWork and the other way around. As I've contributed a lot of code (including the Sailfish port) to Kodimote (previously Xbmcremote) which is developed by mzanetti, but we had everything in one repo so a lot of features were already available in both apps without changing any platform specific code. But as you're hosting on GitHub, and thus are using Git, and RockWork is hosted on Launchpad and using Bazaar you can't just pull in changes from one another.

I might be able to help in this area. As I've got my own small daemon for the Pebble (but didn't do any development on it the last months), and filling the timeline based on the calendar is one of the things I do have working. And the same goes for call handling, which I've got operational too (so I might be able to fix the crasher there).

Which is about everything I have working actually :p. Timeline for notifications, email (not using notifications, so I can show a full message preview, which differs from at least Pebbled, haven't check RockWork yet), calendar, phone call handling and the app fetching (but I don't have a UI either, so that also only works by putting the app file in the correct directory).

Re: [Announce] Pebble Watch Connector daemon
 

Well, and with respect to the protocol implementation, SkippingStones is mostly merely a Qt/QML port of the libpebble Python implementation.

You live, ehm code, you learn.

Not to forget, for this small niche (free mobile OS independent from Android and ios), people working in their spare time are an important factor.

Edit: And to add, I think that poking fun is, well, sometimes fun, but on the other hand I think that a more welcoming tune sometimes would be also, lets say, helpful.