Update the attributes of a device This endpoint is totally batchable! That would increase your throughput 100x.   https://developer.cisco.com/meraki/api-v1/#!action-batches-overview https://developer.cisco.com/meraki/api-v1/#!supported-resources Also, take a look at the action batch helper I made, here: https://github.com/TKIPisalegacycipher/Action-Batch-Helper/blob/main/main.py   ... View more

Thanks for reaching out! Glad you asked this publicly because there's a good chance you're not the only person to google this issue.   The shortest solution is to use API v1 endpoints, which have the base URL api.meraki.com, thus avoiding the v0 deprecation issue (as @sungod mentioned), and reaping the benefits of both api.meraki.com and API v1 endpoints.   Of course, if you can reproduce this issue using api.meraki.com and the v1 endpoint, let us know! ... View more

We saw API failures between 0100-0200 UTC on both USA and EU hosted organizations.   Seemed to be transient, only a couple of API calls failed hard enough for our system to give up on back-off/retry.   ... View more

Examples are in https://github.com/meraki/dashboard-api-python/tree/master/examples     ... View more

You can use https://developer.cisco.com/meraki/api-v1/#!get-device to get a device's coordinates.   ... View more

In general, the API call support for grabbing data for a specific time period is inconsistent, in some cases absent..   For events, I just grab the lot and iterate through with...   if event['occurredAt'] >= starttime and event['occurredAt'] <= endtime:     do something   ...to get events for the time period I want.   Forty years ago I was tweaking every line of assembler and using tricks to save CPU cycles, this just makes me feel dirty.   ... View more

It's already done! But they can't say anything...... ... View more

There are a generic methods (including some ready to use libraries) to 'flatten' JSON to key:value pairs, which you could then convert to row/column form.   But I don't really think that helps you as you'd just end up with umpteen columns named by the composite keys which you'd still need to interpret to make sense of the info.   When I extract data for reporting/analysis, I just write Python to pull out the bits I want from the nested structures, iterating through if necessary, and then output them as one row at a time in a standard column format of my choosing, that then feeds into downstream analysis routines.   Due to differences in the JSON structures returned depending on context (and sometimes null data), the code needs to be specific to the API call (and in some cases, the way the API call is being used and its target.)   From a quick look at the google sheet source, this is what it is really doing. It has specific output code for each API call it supports, i.e. it is not figuring it out dynamically, it is hard-coded.   See the code section titled "Reports"  https://gist.github.com/dexterlabora/9884aa4399715df8f453ea9de63255a0  that's the code from around line 688 onwards (at least with current numbering.)   ... View more

You need to handle multiple pages of client details if you are using the 'raw' API.   If you use the Python SDK, it will do the page handling for you, for instance...   clients = await aiomeraki.networks.getNetworkClients(net['id'], timespan=t, perPage=1000, total_pages="all")   ...can return many thousands of clients.   ... View more

Hi, Meraki closed the ticket. At this time we are not experiencing issues. Are you? ... View more

When looking at a single day, the summary numbers on the Dashboard location analytics page are hourly averages (over the 24 hour day), otherwise they are daily averages.   The discrepancy you see may simply be due to that.   For a single day, if you had 24 devices connecting, each for an hour, I'd assume the hourly average would be one.   Though I'd guess time connected is also part of the calculation, so if the 24 devices each connected for a total of two hours, the hourly average would be two.   Comparing what is seen in Dashboard to what is calculated using API data is not always straightforward. To get the same answer you would need to replicate how the Dashboard calculation is being made (which is not something that is documented).       ... View more

I've found it still breaks down under load, such as when nested to get per device/other element data for hundreds of networks in 'one' aio call, then calls will intermittently fail with the error "429 Too Many Requests".   To handle that, inside the sub-functions there's a capped exponential backoff and retry if a failure occurs.   This issue certainly was in v0 and beta/early v1, perhaps the library code improved since then? But I've not tried running without the extra error recovery as it also helps gracefully recover from other transient errors that can occur.   This is used in scripts that daily pull various performance data for analysis for large organizations that we manage, it's important that it operates without human intervention to recover/re-run. Any time there's a 'new' error found, I try to add code to avoid/recover.   ... View more

Thank you are feedback, I am trying to learn more about using API/Python to provide reports.    Your suggestion looks like it will work but want to get more comfortable with the above skills. Have a great day! ... View more

This looks like the only call that returns app data, you'd need to try it against a test device to see if the return data gives what you are looking for... https://developer.cisco.com/meraki/api-v1/#!get-network-sm-device-softwares   You will need to find your organization ID, you can find it with... https://developer.cisco.com/meraki/api-v1/#!get-organizations   Also you need the network ID of a system manager network, use this to find all networks and choose an SM one... https://developer.cisco.com/meraki/api-v1/#!get-organization-networks   To create a script to automate things, the loop would be...   get all networks in the org with... https://developer.cisco.com/meraki/api-v1/#!get-organization-networks   iterate through that list, testing the productTypes element for each network that is a system manager network, run the get-network-sm-device-softwares call to get the device data   I recommend using the Python API library as it does a lot of the low level stuff for you... https://pypi.org/project/meraki/   ... View more

You can use this call on each network, it includes IP address...   https://developer.cisco.com/meraki/api-v1/#!get-network-devices ... View more

Thank you for the information. That leads me down a closer path to what I need. Luckily I work in a school with controlled devices, so we shut off the Mac randomization 🙂 ... View more

Thanks for the information, I don't have a privilage to modify these settings but I will keep this as an alternative option. ... View more

Fyi the problem with the getNetworkWirelessDevicesConnectionStats call has been fixed.   It's possible the latency stats call will also work now, I suggest try a test.       ... View more

Yes, just tried running on an affected org and also looks ok now.   Thanks for the update.   ... View more

Yes, it is good in some situation and I actually use it for collecting hourly data statistics. But from the GetNetworkClients I get VLAN/SSID and more that I need to be able to work on.   If there was no limit in the number of api-calls, you could use a combination of calls to figure it all out 🙂   But I really would like to have a T1 on get network clients, I guess there is a reason for why that is missing....   ... View more

Switch port PoE use is one of the things we report for our customers.   Use this call  https://developer.cisco.com/meraki/api-v1/#!get-device-switch-ports-statuses   Port PoE usage is reported as Watt-hours consumed over the timespan specified when making the call.   So if you want average power usage over period T, set the timespan to T and normalise to Watts by Wh/T (with T in hours).   Note that this call doesn't use a t1 parameter, so whether you use t0 or timespan it will always return data looking back from the time of the call. I just run it daily at the same time to build up long term stats.   Afaik switch PoE budgets still aren't visible, but it's simple enough to use a look-up table, just need to remember to add new switches to the table when they are released.   ... View more

Hello Kvkewn   Many thanks for posting your issue and thoughts. I am in a similar situation using PRTG too. I am struggling to understand how to combine the "timespan" parameter and the right "polling" frequency to collect data from Meraki API. I am collecting the number of clients associated per Meraki Access Point or Network using the following URL:   https://api.meraki.com/api/v0/networks/MY_NETWORK/clients?perPage=1000&timespan=3600   In order to avoid the API Rate Limit I am collecting the result every hour using PRTG. The timespan used inside the URL is also 3600 seconds (1 hour). The problem is that the data is coming in a very inconsistent way.        Please, could you help me to understand how can I use the Meraki API timespan correctly ? What is the recommended time interval to collect the connected clients ?   Regards, ... View more