Official Fitbit Weather App vs Messaging API clock face

[the_way]

Hello Community and here especially hello Fitbit folks,

Me as well as some folks here in the community experienced lacking communication between device and companion. 

I do apply the official guideline from Fitbit:

https://dev.fitbit.com/build/guides/communications/messaging/

, but the peerSocket.Open seems not to be reliable. This part here:

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

    // Send the data to peer as a message

    messaging.peerSocket.send(data);

  }

On the other hand the official Fitbit wetter app seems to work pretty well (haven't seen any delay more than 60 minutes).

Can you give some insights WHY and maybe advices to improve the weather data exchange!

Thank you and have a nice weekend!

[philvms]

I have also had reliability issues with the Messaging API where if it was a new build it would not send a message api at all. It would often require a restart to get it working. I stopped using the Messaging API entirely for this reason. The file transfer api never seemed to have this problem. This of course means you would have to create a small file with the message just to send it but this is just a trivial matter that gives more reliability to your app.