When sending tags data to Wiliot Cloud, how is exactly the cloud filtering the messages? We do not know if the behaviour we are experiencing is right: Having 4 tags, we collect 4 payloads and send them to the cloud. The result is that we can see only data from 2 tags in our cloud endpoint. We assume this is because from the 4 payloads sent to Wiliot Cloud, there were payloads corresponding to same tags, so Wiliot is filtering them just to show once each tag. However, all the payload timestamps sent in the message are different, so it shouldn’t filter it…
These 4 tags are proven to work, being the only issue the one I just described. So, we can confirm that our MQTT connection and publications are correct.
Now, when we try to go further in our experiment, we add several tags from the Starter Kit, and we associate them to our application in the Wiliot Cloud. The thing is that when we collect, let’s say, 20 payloads and send them to the cloud, the result is that in our cloud endpoint we can visualize data for 0 or 1 tag always! When we can see 1 tag, it is usually corresponding to one of the 4 tags that initially were working (not the ones in the Starter Kit). From the Starter Kit we can only see 1 single tag from time to time (and its always the same). This outcome is confusing because when we sent 20 tags to Wiliot Cloud we would expect to see 20 data messages in our cloud. We can understand that the repeated tags are being filtered, but if we sent 20 payloads and we have nearly 15 tags, it is impossible to receive 0/1 data in our cloud.
As there are occasions when we receive no data with this latter configuration, our thinking is that we are maybe collecting data from the “new” tags (Starter Kit), that seems not to be associated to our application (although there are), and when we have 20 collections, we sent them to the cloud before any collections of the “old tags” has taken place, and that is why the output is no data at all.
Please sign in to leave a comment.