Location Scanning API v3 missing expected data

[JackReuter]

Hello,

We have the Location Scanning API v3 set up and are ingesting incoming events from it, but the data from it seems unexpectedly sparse. When I look at all clients seen in the last 2 hours, either via the online dashboard or the REST API, I see 5 clients. I would expect to see location events for all them. Only 2 of the 5, however, have location events coming in regularly. The rest have at most one event an hour, some even less than that.

Does anyone know if there is a setup step I am missing, or misunderstanding about the behavior of the API? If a client is connected to the network I would expect it to have an observation in each incoming location payload, with locations if it was seen by 3+ APs, or the latestRecord key if not.

Thanks,

Jack

[sungod]

According to v3 documentation, you should be getting an update for each network far more often (it says both once a minute and every 2-3 minutes).

Tbh I would be wary of expecting the client counts from UI/API to match the location API, especially with small numbers of clients.

As a next step, I'd try to physically verify the presence of active clients within range, and check if the location API is seeing them (and the UI/API too).

Then if there's a definite discrepancy that can't be explained, open a support case.