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: 

messaging.peerSocket.onopen not always solicited

‎09-12-2019 11:42 - edited ‎09-12-2019 11:44

‎09-12-2019 11:42 - edited ‎09-12-2019 11:44

Since last fitbit android app update I've noticed that messaging.peerSocket.onopen is not sollecited until the smartphone receive a notification.

 

I used this steps to reproduce it:

  • turn off smartphone bt -> messaging.peerSocket.onclose is called
  • turn on bt and wait 1 or 2 minutes -> nothing happens
  • I push a notification to my smartphone (using push bullet or a chat) -> messaging.peerSocket.onopen is called

I also waited several minutes but only a notification has stimulate messaging.peerSocket.onopen

 

What can influence behavior of messaging.peerSocket.onopen call?

Best Answer
Labels:
3 REPLIES 3

‎09-14-2019 18:21 - edited ‎09-14-2019 19:06

‎09-14-2019 18:21 - edited ‎09-14-2019 19:06

Update: Whoa, notifications really do cause the messaging peersocket to open. That’s cool.

 

Very interesting. I need to see if a notification triggers a messaging.peersocket.onopen in my clockface projects. Using android and a Versalite I’ve tested putting my phone in a spot and walking away from it until the messaging.peersocket.onclose activates. Then I return to the phone to see if it ever opens again, and it never does (this is while repeatedly trying to send messages to wake the companion and using the 5min companion wake function to get the clockface running again). 

 

I’ve also noticed what I think is the peersocket closing when the phone switches WiFi sources...like when you come home and the phone switches to the house WiFi. Just a feeling. 

 

Beyond that, we really need the watches to automatically resume messaging capabilities if there is an interruption. Not to rub it in, but I believe Apple Watches do this. Fitbit, if you solves this you’ll sell more watches.

Best Answer

‎09-19-2019 01:31

‎09-19-2019 01:31

@alessandroame wrote:
  • I push a notification to my smartphone (using push bullet or a chat) -> messaging.peerSocket.onopen is called

What do you mean by "using push bullet or a chat"?

The guide says "Connections are established automatically, and the onopen event will be emitted upon connection". Isn't that true?

Best Answer
0 Votes

‎09-19-2019 02:36 - edited ‎09-19-2019 03:02

In response to Scorseze

‎09-19-2019 02:36 - edited ‎09-19-2019 03:02

To me is not true, and I've followed the documentation.

 

I mean that to create an android notification (the only thing that trigger the onopen in my reality not in the doc) I've used:

  1. push bullet: a software that enable me to push notification to android devices 
  2. hangout or whatever chat: that when you receive a messagge push an android notification

Due to I recevied the notification on the smartwatch I think the connection is open to device, but onopen was never called and when the notification appears on the watch immediately onopen is called.

 

 

 

 

Best Answer
0 Votes