And I'm reporting back again

This afternoon I've took some time to properly look into how libpebble2 sends the pins to the timeline and how this app could do it. I've now got some big pile of hackish code which might actually work. So if someone really, really, really wants to be able to receive notifications, he (or she) can send me a private message and I can send the RPM then. But please do note that it is absolutely untested, so it might burn down your phone, Pebble, or house (I justed dumped all the binary data generated by libpebble2 and tried to "rebuild" it in this app, which I think I succeeded in).


Seems like this might be relatively easy to achieve. I think they start a WebSocket server on the phone which the SDK connects to. The messages send over this connection are the normal messages as send between the phone and watch, just wrapped with some extra information (like if the message is meant for the phone or the watch).

Update:
Thanks to HtheB and wormdrummer for being able to test it so quickly. Notifications are still broken. So there's no need anymore to ask for a test version. In the upcoming days I'll try to add some extra debugging code/logging to try to narrow down the issue, to see if I can narrow down the issue without actually having received my Pebble.