The response for updating a field can sometimes take up to 12 seconds . Too slow
28 vues (au cours des 30 derniers jours)
Afficher commentaires plus anciens
salaheddine alshawwa
le 10 Juin 2021
Commenté : salaheddine alshawwa
le 13 Juin 2021
I am working on a home control system .i am using the thingSpeak server to control Nodemcu . The problem is that once i send the GET request to update a specific field it can take up to 12 seconds. And this is so slow. My question is , does this happen with other people before or am i doing something wrong.
0 commentaires
Réponse acceptée
Vinod
le 10 Juin 2021
ThingSpeak has an operational metric to respond to requests to update a channel within a few hundred milleseconds of receiving the request. We monitor this metric daily. However, the connectivity to ThingSpeak servers is outside of our control. So, if you have a slow internet connection, or a general lack of network bandwidth on account of use by other processes, it is possible it takes a while for your request to make its way from you device to the ThingSpeak server.
One suggestion I can make is to try the MQTT API to update your ThingSpeak channel. MQTT is a more efficient protocol for machine-to-machine data. Take a look at the API and examples if you need a starting point.
5 commentaires
Vinod
le 12 Juin 2021
Modifié(e) : Vinod
le 12 Juin 2021
Unless you've purchased a license, 2 out of 3 of your requests will get a 200 status code with a 0 return value indicating the data was rejected. You're just wasting resources on your device and on ThingSpeak with these requests.
Only one point every 15 seconds will be stored, and you will get a positive number corresponding to the entry id back.
Plus de réponses (0)
Communautés
Plus de réponses dans ThingSpeak Community
Voir également
Catégories
En savoir plus sur ThingSpeak dans Help Center et File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!