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: 

Successfully using peer.messaging - then it just stops, rarely recovers.

‎11-22-2019 12:44

‎11-22-2019 12:44

Hi All,

 

I am developing a watchface that has to reliability and regularly connect to our servers to pull data to be shown on the watchface.

 

As others have noted the messaging appears flaky.  So I check the socket is open with the code below, and often  disappears and nevers comes back.

 

messaging.peerSocket.readyState === messaging.peerSocket.OPEN

 

I do communicate with the companion every couple of minutes to maintain a connection,  does not seem to work.

 

I made sure the Fitbit app is in the front, and has the background app refresh enabled and that bluetooth is working; in fact the Fitbit app showed the watch had just synched moments earlier , but still the connection was closed.

 

Is there anything people have found to resurrect the connection? 

I had to go as far as removing the app from the watch to re-enable the connection.

 

Has anyone tries the suggestion on using file transfers instead of peer messages?

 

Does anyone have any suggestions?  There needs to be no documentation on this.

 

Stumped

 

Geoff

Best Answer
2 REPLIES 2

‎11-27-2019 21:41

‎11-27-2019 21:41

Hello,


I am also experiencing difficulties regarding the reliability of the messaging API... I would really appreciate some feedback from the devs at Fitbit.

 

Thanks,

 

David

Best Answer
0 Votes

‎11-28-2019 05:23

In response to mm22dl

‎11-28-2019 05:23

Also have problems with all clockfaces after updating on Fitbit OS v.4 and SDK 4.0.

The problem is in Companion - it just unloading and doesn't wake up anymore.

Best Answer