It gives that connect reset message every time I try this ping... but carry on anyway.

# rfcomm bind 0 00:18:2f:cc:ec:a9

next:

./p.py --pebble_id ECA9 ping

will make the pebble buzz and show a ping message on screen.

Now run as many p.py commands as you like.

At some point when I did this previously, it got a persistent pairing with the pebble - I have no idea where in my hacking around the persistent pairing happened as at one stage I had to do it for every interaction...