Dear Support,
As described in the main guide of this not, in order to check the upload status of my datapoints, i have an switch node to check if the attribute "msg._mindsphereStatus" is getting an "OK" or not "OK" value, in order to feed the offline buffer flow we designed if it doesn't uploaded right. (Mention to issue #20 )
This used to work fine for buffering the packages that either didn't upload consequence of instable internet connection, but also for making more stable the upload rate (for some reason, some packages didn't upload right, maybe because of saturation) catching the one that didn't uplaod right.
This is the logic: (If you have any suggestions to make it better, we are open to improve it and share it with the community)
The problem is, now that we downloaded the (almost?) lastest version of this node, we are not able to check the mentioned "msg._mindsphereStatus" attribute to either finish the execution of the succesful uploads, or feed the buffering flow when we are offline.
Mindconnect Node configuration:
Description of error:
If we disconnect the device from internet (disconnect cable) in which this Flow is running, we are accumulating a lot of request in the MindConnect Node, instead of "failing the upload", setting an "Not OK" state for every failed json and feeding the offline buffer flow.
Is the node already buffering on its own? If so, i tried it out and its not able to handle hours of buffering (in my test case, i can try again if you say so)
If not, why isn't the node outputting every package with the attribute "msg._mindsphereStatus = Error" as it used to do?
Thank you