Just got my PT2, pretty cool device! I set up everything the way I want and my old watchfaces were immediately there, so far so good.
Then trying to pair it with my work phone: The BT settings screen says “forget this device to pair a new device”. Seriously? You want me to unpair my private phone each time I want to use the watch with my work phone?
So I did this, and the procedure is super cumbersome. It’s not sufficient to just unpair on the watch, it seems like you also have to manually remove the watch on the phone app to later add it again when you switch from work to private phone again. And that doesn’t even work, on the most recent Android version I selected REMOVE on the device page, but the watch stays there, in disconnected state, not offering remove anymore on the three-dot menu, and not connecting either (when you press connect, it won’t pair, as the watch is expecting a new pairing).
After trying back and forth, killing the Pebble app etc., it eventually worked. But there is no way I will be doing this twice a day when going to/returning from work.
To be honest, this drawback was never communicated, everywhere it said “like the old watches, but better”. Not being able to switch back and forth with my work phone is a showstopper for me, I want my money back if this won’t be possible. Is there a refund process?
I’m faced with this problem too, and it’s a major annoyance. So much, that I still use my old Pebble Time Steel as daily driver.
I don’t think it would require so much work to fix this in software, at least not if you don’t enable simultanious pairing with multiple phones. Being able to manually switch the phone in the BT settings of the watch would already help a lot. Everything would be easier than complete unpairing and repairing.
You wouldn’t. You would just switch between the pairings manually, basically suspending one pairing while the other one is active. From a technical point of view, this is easily possible. To demonstrate it in a simple example:
You have two config files: pairing1.cfg.inactive and pairing2.cfg.inactive. The one that is currently active gets renamed to bt_pairing.cfg (which is loaded on start of the BT stack). Switching between the phones does nothing else than renaming the files accordingly and restarting the BT stack.
Of course not as good as the watch automatically connecting to the phone that is closest, or even both at the same time. But it would do for now. And shouldn’t be that hard to implement.
So in other words, this feature was removed in the new watches without it being communicated. Great way to treat your fans, Pebble! I’m seriously disappointed.
Any news on this one? At least a manual switch on the watch would be great. Currently it forced you to unpair previous phone and re-do the whole pairing each time you want to switch.