We have a few dozen Electrons operating on a 3rd party (Zantel) network off the coast of Tanzania.
They are all running version 0.6.1 of firmware
The Zantel network (and all other networks for that matter) are heavily overburdened in these areas. This results in moderate to severe network latency issues.
It would seem that when the latency is on the more severe end of the spectrum, the Particle Cloud API stops working properly with our fleet.
I have posted about this issue in another thread, but thought that this phenomenon should exist in its own dedicated thread.
One example of how latency breaks the Particle to Electron communication system is when calling a
Particle.function() that has been exposed to the cloud. In my app, I have a cloud function which when called sets a flag that queues a
Particle.publish(). This means that I know if a cloud function call is successful because I will see a subsequent
Particle.publish() that gets triggered and sent to the Particle servers.
Often (~10% of the time), when I call that function, the Particle console responds (after about 10 seconds or so) saying that the device could not be reached. Then (5-10 seconds later), my device will publish the triggered publish, which means that in reality the function call did go through.
Since my app needs to be able to tell if a function call was successfully executed, and since the Particle API will report that the function did not successfully execute (even though it did), this means that I cannot rely on the Particle API to report whether a function call went through successfully. This means that I have had to program an
ACK publish protocol that acknowledges
Particle.function() calls. This means a bigger program size (which is a big deal since my program size has already reached its maximum size) and also means more cellular data to support my app using
I think the solution here is to make the Particle Cloud API wait for longer before giving up on a function call. I would recommend 20-30 seconds minimum based on the latency I have been observing.
Particle.function() timeout deficiency something that can be changed for my product at the product level? If not, is this something the the Particle development team is going to address at a system-wide level?
Similar to the problem with calling
Particle.function() timing out, many times (~50% of the time) when I try to query the value of a
Particle.variable() on one of my devices, the result is an error message saying the device can’t be reached. I believe that this is the same problem of the
Particle.variable() GET request timing out. I have not been able to gather some Serial debug logs proving that the variable get request made it to the device since I am not in Tanzania at the moment. I will try to do so.
Particle.variable() timeout deficiency something that can be changed for my product at the product level? If not, is this something the the Particle development team is going to address at a system-wide level?
(See link to other thread, above)