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

Hello Sungod.   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,           Regards, ... View more

Well, you could get the same value, but to do that you would need to take your sample at the same time(s) that the Overview figures are calculated, I'd guess this is done daily.    But unless you happen to take a sample at the same time, the API will always get a result that is equal or greater than shown in Overview due to usage since the daily sample.   This assumes all my guesses about how it works are close enough 😊   ... View more

In Dashboard and the current API I believe the only power consumption data is for switch port PoE...   powerUsageInWh   ...in the https://developer.cisco.com/meraki/api-v1/#!get-device-switch-ports-statuses call.   We gather this for customer reporting to show daily switch PoE maximum vs. switch PoE budget (needs a manual lookup table of budget for each model), used/free ports are also tracked plus warnings and errors.   In our case this is for capacity planning rather than tracking consumption over time, for that you'd need to sample shorter periods.   ... View more

You seem to be running once per minute with an 800 second lookback from 'now', the only Nones that I see in your sample occur in the last record.   I'd guess the most recent data have not yet reached the cloud.   If you instead use a t0-t1 window that starts, say, 20 minutes ago and ends 5 minutes ago, do you still get the Nones? ... View more

The PR is already merged. It is not yet in a released version, but you can use it on the  v1 api directly from github.   In the creation of the Async/DashboardAPI object you have to specify the parameter 'use_iterator_for_get_pages = True' examples: https://github.com/meraki/dashboard-api-python/blob/master/examples/get_pages_iterator.py & https://github.com/meraki/dashboard-api-python/blob/master/examples/aio_get_pages_iterator.py ... View more

It's an ISO 8601 timestamp. ... View more

Morning sungod, thanks for the pointer, I believe there is an APIv1 Node-Red module in Dev at the moment in Beta test, I'm curious if anyone knows a General Release date. ... View more

Thanks!  I am looking for a solution that will allow me to monitor and config both.   ... View more

Happy Sunday @CiscoUser  As per Cisco Meraki documentation, APIs are rate limited to 5 calls per second per organisation. https://documentation.meraki.com/General_Administration/Other_Topics/Cisco_Meraki_Dashboard_API   This limit is Cisco Meraki wide and there is no way to increase this limit, at least for the time being. Please make use to the Make-a-Wish button in your dashboard to give your feedback to the Cisco Meraki team.   Keep an eye out on the API documentation as it will be update whenever any changes are made, and on that note, also regularly check the Announcements button at the top of your dashboard and the new released features section under Help > New Features. Have a good weekend! ... View more

I have tried V0, but it seems the application usage request is new to V1, or at least I couldn't find it in V0. The only way I found to get the application usage in V0 is with the traffic usage request, but just like V1 it is daily and for one client at the time.   Thank you for help. If I don't get an answer here, then I'll open a case. ... View more

You should know which version of the API output is being generated - It's a while since I set mine up but, when you create a post URL (destination for the output) the API version is selectable, via a dropdown. If you see only v1 or v2, I suspect you don't meet the pre-requisites for the Beta.  Beyond just having MR Access Points, this is down to firmware: Firmware R26 for WiFi observations Firmware R27.5 for BLE observations One of the major advances with v3 is that it consolidates observations to a single POST (and location) per network, rather then getting different values, at slightly different times, from different APs. This info and more is available here: https://developer.cisco.com/meraki/scanning-api/#!overview/requirements   Note that for AP models which pre-date 11AC Wave 2, r27 and subsequent firmware verions are not supported.   Some more info in this area here:   https://documentation.meraki.com/General_Administration/Firmware_Upgrades/MR_Mixed_Firmware_Networks   ... View more

Thank you all. ... View more