Improve developer connection support about cloudpebble HOT 4 CLOSED

I'd wager that in most cases, it's a configuration issue. Pebble app not in foreground, wrong wifi network selected, ... Perhaps we can improve those numbers simply by changing the instructions.

from cloudpebble.

I've seen three seemingly distinct failure modes:

1. Configuration failure (people particularly tend to over-think it and give their public IP from behind a NAT)
2. Large apps, for some definition of "large", seem to cause the iOS app to drop the WebSocket connection. The pebble tool doesn't have this issue; I think it's probably related to how the browser breaks the message up into frames.
3. Sometimes it just doesn't work, but will work in another browser. This may be related to number 2 above, or 1 + user confusion. I can't reproduce this case.

Unfortunately, I can't distinguish these cases with the data I have on hand. It might be worth improving the granularity of that. Improved wording would almost certainly help, though.

from cloudpebble.

at least some of these are me having killed the pebble app on my phone and forgetting to restart it :)

from cloudpebble.

2.1's 64k fix and websocket-autoconfig should do the job here; calling this done.

from cloudpebble.