@cmr time to connect is the time delay between re-association/association sent by the client and the final acknowledgment sent by the AP. Can we have a support case opened for this issue? We would like to investigate this further and get some more information that we can track internally and fix, if we identify this as a bug. ... View more

Hey @RaphaelL,   Thank you for bringing this to our attention. I had a quick question. Can you navigate to Dashboard > Wireless > Specific AP <Q3AJ-XXXX-XXXX> > Timeline and filter for "Authentication" in the connection step for the selected time period and compare the values from the indicated API and this page?  Currently, we are in the process of upgrading the backend algorithm for the data that is surfaced in the Connection Log tab to make it more consistent with the API. We have already updated the data in the AP timeline view and it should match more closely with your API output if the timestamps selected are exactly the same across Dashboard and the API call.     ... View more

@ChesterX Can we have a support case opened for this? This should not be the case since we fixed this issue. We would like to investigate this further to see why you are seeing this firmware version without an MT device in your network. ... View more

Is this behavior fixed with the new location heatmap? We made a few changes on how the heatmap calculates location, so you should have a much accurate view of the heatmap provided you have 3 or more APs for triangulation. ... View more