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: 

Socket remains closed even when the device and phone are connected and synced

‎08-18-2022 03:32

‎08-18-2022 03:32

I have a fitbit application that is composed from a device app and companion. Every 30 seconds I ping the companion app asking for new data (and also for keeping it alive).

 

This works well for a few hours, but after some time the condition below is never true, and I can not send anything. 

if (messaging.peerSocket.readyState === messaging.peerSocket.OPEN) {

}

 

Is there anything that I can do that might make this happen?

Anything that I can do in order to close the socket and open it again?

 

The phone and device are connected through bluetooth, and are able to sync.

Best Answer
0 Votes
1 REPLY 1

‎08-18-2022 03:33

‎08-18-2022 03:33

One thing that I forgot to mention is that the code can be found here:
https://github.com/sulkaharo/nsfitbit

Best Answer
0 Votes