help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Peer reconnect

‎09-25-2022 12:40

‎09-25-2022 12:40

Is there a way to reconnect the peer socket 

 

I have seen lots of threads that say the companion app gets killed.

 

However, what I have observed is more an issue with watch side.

I have my watch and companion ping each other regularly (every 5-15 mins) and can see that messages stop.

However, to restart them, I can open an app which restarts the clock face and messages start working again (no touching the companion side)

 

So it seems that the watch loses the socket connection, but is then unable to re-open it.

 

I can't see any documentation to handle what to do with the socket state is not OPEN. Other than waiting for it to open...

Best Answer
0 Votes
1 REPLY 1

‎09-26-2022 07:09

‎09-26-2022 07:09

Further to this.

 

I can now see that i get socket errors with: "Peer socket error. - Code: 1. Message: Cannot establish icomm session for this app. Try restarting."

Best Answer
0 Votes