Data loss and latency issues from Node Red to ThingSpeak channel.
4 views (last 30 days)
Show older comments
I'm currently busy with a project in which I use a wearble device that uses an accelerometer to track a worker's motions. I'm using Node Red to develop the system and from there I send the data to a ThingSpeak channel. There is however latency issues between these two platforms. It takes a few seconds for measurements to pop up on the ThingSpeak channel after the captured data has been displayed on Node Red. Additionally, only a quater of the data displayed on Node Red can be accounted for on ThingSpeak.
Any adivce would be greatly appreciated.
0 Comments
Answers (1)
Christopher Stapels
on 11 Jul 2023
The most likely cause of lost data is sending too fast. If you are using a free account or using the bulk write endpoint, the minimum time between updates is 15 seconds. For the paid account you can post updates at most once per second. Data sent faster than those rates can be lost.
Although ThingSpeak will keep an accurate record of ingested data, the infrastructure does not guarantee 'real time' updates. I would definitely expect a delay of several seconds, and occasionally slightly more depending on the system load at the time.
0 Comments
Communities
More Answers in the ThingSpeak Community
See Also
Categories
Find more on Read Data from Channel in Help Center and File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!