Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Register or Sign in
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About SENSEi-James
SENSEi-James
Comes here often
Member since Mar 25, 2022
Nov 16 2023
Community Record
7
Posts
0
Kudos
0
Solutions
Badges
Nov 15 2023
8:57 AM
Hi, Is it still the case that the processed location analytics data is not available via an API endpoint? The only way I can get this data is to view it in the dashboard, or to calculate it myself using the data from the scanning API? Many thanks 🙂 James
... View more
Mar 30 2022
2:08 AM
Thanks @PhilipDAth It's the interval between posts from the scanning APIs that I'm trying to find if there's a maximum length of, irrespective of how any particular device behaves. It's back up to about 7 to 11 minutes this morning. Overnight I noticed it was occasionally down to just over a minute. Can anyone from Cisco comment if there's a maximum possible duration for the post interval? Will something timeout if the interval gets too long? This is to help me make some design decisions for an analytics service.
... View more
Mar 29 2022
7:51 AM
According to the docs for both V2 and V3 scanning APIs 'One JSON POST per access point, per minute per, type (WiFi/BLE)' but with these disclaimers: V2: 'Note: Meraki cannot provide a guaranteed interval, as it can depend on a number of factors, including quantity of access points in the network, and the response time (latency) of the customer receiver. Typical POST intervals range from 1-2 minute intervals, but are not guaranteed.' V3: 'Note: Meraki cannot provide a guaranteed interval, as it can depend on a number of factors, including quantity of access points in the network, and the response time (latency) of the customer receiver. Typical POST intervals range from 2-3 minute intervals, but are not guaranteed.' This morning on V2, I was seeing intervals up to 11 minutes. At the moment the intervals are back down to around 4 minutes. V3 is still not sending anything at all at the moment. Is there a maximum interval that I can safely rely upon? I see there's a variety of reasons for these increased intervals. Is it because those reasons are causing increased load on the APs, or increased load on the Meraki cloud services, or something else? Thanks 🙂 James
... View more
Mar 25 2022
8:46 AM
Sorry, didn't answer your question about how many APs. There are 8. I have opened a support case. I have DM'd a serial number
... View more
Mar 25 2022
8:21 AM
One month ago, I was running with ONE AP and collecting lots of information (but no trilaterated locations) with ONE AP According to your own documentation, I should still be receiving some data: - START QUOTE- What will happen if I enable V3, but some physical locations don’t have at least three compatible APs? In scenarios where the Scanning API V3 does not have at least 3 data points, no location information will be generated in the API output for a given wireless client. The API will provide the nearest AP MAC address based on the RSSI in the output. This can be used to get a rough estimate of the location of the wireless client device on the floor plan, but it is recommended to deploy at least three APs at any physical location that is upgrading to Scanning API V3 -END QUOTE-
... View more
Mar 25 2022
5:16 AM
Hi, One month ago I developed a service to receive data pushed from the scanning API v3. This was working fine and plenty of data was coming in. The APs were boxed up and shipped to a customer. They were installed and turned on yesterday. Nothing is being pushed from the scanning API v3. If I change it to v2, loads of 'DevicesSeen' data gets pushed to me, but that's not what I've developed my service to work with. Is there a problem with the scanning API v3 at the moment, or am I missing something obvious? Many thanks 🙂 James
... View more
© 2024 Cisco Systems, Inc.
