Issue with endTime parameter in /ec2/analyticsLookupObjectTracks endpoint

Answered

Follow

Gaspar Gómez

• May 22, 2024 08:08

Hi everyone,

I'm experiencing an issue with the '/ec2/analyticsLookupObjectTracks' endpoint. When I use a past timestamp for the 'endTime' parameter, even if it's just a minute before the current time, I don't get any results. However, when I set 'endTime' to a future date that hasn't occurred yet, the endpoint returns data.

Here's a summary of the problem:

• Endpoint: /ec2/analyticsLookupObjectTracks
• Issue: No results when endTime is a past date
• Expected behavior: Should return data for past dates
• Actual behavior: Returns data only when endTime is a future date

Has anyone encountered a similar issue or have any insights on why this might be happening? Any suggestions or workarounds would be greatly appreciated.

Thanks in advance!

0

• 

  Ichiro

  • May 23, 2024 08:45

  Hi Gaspar Gómez
  
  Thanks for your question. Can you please confirm if you are using epoch time in millieseconds?
  (an integer total in 13 digits)
  
  As you can see, I am trying to use the current epoch time in milliseconds, even though the server is in different timezone than mine), I am still able to get the proper response.
  Just FYI, the response of the best shot, the timestamp is in "microseconds, likely you need to divide it by 10^3" if required. 
  

  You might see the test video here : https://we.tl/t-j4i7gDHHWV

   

  0

  Comment actions Permalink
• 

  Gaspar Gómez

  • May 24, 2024 08:46

  Hi Ichiro

  thanks for answering!

  Alright, it seems that the issue might be related to the duration for which these data are being stored. When I make a call without parameters in ascending order, the first result is from just a minute ago. Could this be due to a large volume of objects detected by the device? It looks like the format I'm using is correct, in milliseconds.

   

  0

  Comment actions Permalink
• 

  Ichiro

  • May 24, 2024 10:55

  Hi Gaspar Gómez,
  
  Thanks for your reply. I am afraid that I may not quite sure about your question.
  Do you mean you have lots of objects but their order is incorrect? 

  What are the issues you may face now?

  0

  Comment actions Permalink
• 

  Ichiro

  • May 29, 2024 02:26
  • Edited

  Hi Gaspar Gómez,

  I am not sure if you still need any assistance, but I may suggest you could update the system to the latest 5.1.4 at the moment. We have solved a few API issues. Thanks.

  0

  Comment actions Permalink
• 

  Gaspar Gómez

  • May 29, 2024 10:25

  Hi Ichiro,

  I'm sorry for the confusion in my last post.

  What I meant to say is that when I make a call without specifying the parameters, only with ascending order, the results only include data from the last few seconds. Given this, I have two questions:

  1. Is there a default value for endTime or startTime when none is specified?
  2. Could it be that our device is storing too many objects and potentially deleting older ones, which is why we are not retrieving them? (just an idea of why this may be happening)

  Thank you for your help.

  0

  Comment actions Permalink
• 

  Ichiro

  • May 31, 2024 04:06
  • Edited

  Hi Gaspar Gómez,

  We don't remove the old objects. This is a possible known issue for early 5.1.x, and we have fixed for some period of time ( specifically fixed in 5.1.2 already)
  
  I may suggest you could update the system to the latest 5.1.4 at the moment. We have solved a few API issues, including the srotOrder issues.

  Please let us know if you still see the same issue on the last v5.1.4. Thanks.

  0

  Comment actions Permalink
• 

  Gaspar Gómez

  • August 01, 2024 08:42
  • Edited

  Hi Ichiro,
  
  Thank you for your assistance, this was indeed solved on the last v5.1.4!
  
  Anyways, the image is not showing when endTime is a past date, why might this be happening?

  0

  Comment actions Permalink

Please sign in to leave a comment.