Latest data available lags real-time

[JGeko]

It looks like when I query for intraday heart rate data the latest data point is about 5 minutes behind the current time. Is this expected?

Are there any plans to improve data lag? Having something closer to "real-time" ( < 5 seconds) for heart rate would allow a lot of interesting applications.

[Gondwana · Accepted solution]

The Web API only provides data that has been synced from the watch, and that doesn't happen continuously. If you want real-time data, you'll need to write your own clockface or app using the device API.

[JGeko]

This is what I assumed, but wanted to double check. I have a Charge 4 and because it doesn't run FitBit OS I can't develop anything for it. I was trying to find a work around. Bummer!