The Python library supports timespan...   def getDeviceSwitchPortsStatuses(self, serial: str, **kwargs): """ **Return the status for all the ports of a switch** https://developer.cisco.com/meraki/api-v1/#!get-device-switch-ports-statuses - serial (string): (required) - t0 (string): The beginning of the timespan for the data. The maximum lookback period is 31 days from today. - timespan (number): The timespan for which the information will be fetched. If specifying timespan, do not specify parameter t0. The value must be in seconds and be less than or equal to 31 days. The default is 1 day. """   Usage would be like...   serial="1234-1234-1234" t=31*24*60*60 getDeviceSwitchPortsStatuses(serial, timespan=t)   ... View more

This call  https://developer.cisco.com/meraki/api-v1/#!get-device-switch-ports-statuses   allows timespan up to 31 days (timespan=2678400).   The way you add the parameters depends how you are coding, i.e. Meraki Python library, crafting you own URLs, something else etc.   I suggest look at the linked page (see the 'template' tab on the right for a few examples) and associated usage info. ... View more

I'd think you need to add extra things to the existing PYTHONPATH or other variables, rather than add it standalone.   I.e. if the one you're adding is overriding the existing one set up by the install, it'd explain why other things stopped working.   If the original settings are lost, just repeat the Python install.   Then check the value of PYTHONPATH, whatever it is, append the location of the Meraki package, each path in the list is separated with a semicolon ;   If you type    pip show meraki    it'll tell you the install path. ... View more

Sounds like an issue with your install/set-up, I'd guess the search path in the environment is not set correctly.   I'm not familiar with Python on VS/Windows, but try checking the PYTHONPATH setting, see here in the Windows section...   https://bic-berkeley.github.io/psych-214-fall-2016/using_pythonpath.html   ...this page also includes a simple script to tell you the value of the variable, if you run it in VS and then as executable, see if the answers differ.   ... View more

If it were possible for an admin to define multiple org-specific keys that were either full admin or read-only, it'd address many of my wishes.   As it stands I (or another admin) need to create multiple logins, each needing a different email alias, each needing TFA set-up. If the admin changes, it all needs ripping up and redoing. It's not a good solution with multiple orgs.   The API authentication process starts with the key, clearly the logic to look-up a key is there.   That's the point at which the access privileges for that key are established it doesn't seem a huge complication to make those privileges those of the key rather than of the owning admin.   If it really must be based on a user ID, then let admins create multiple aliases that each have only one editable thing in their user profile: the API key (everything else just inherits from the parent ID.)   The login email address could use a syntax like n!real.email@real.com  where the n is a Dashboard generated 'alias ID' followed by a '!', so we don't need to create and manage real email aliases, there's still only the single admin email - this alias isn't ever used as an email address, the ! is never going to get routed as a bang path 😀   Then we just add the alias ID as the admin and it can have it's own org access settings.   It's a bit of a 'bag on the side', but again it's something that feels it should be possible as a simple extension.   ... View more

You need to specify the destination IP, it's mandatory.   For instance, if I get the details for a few minutes for WAN 1 on an MX that is set to use 8.8.8.8 for it's latency reporting, with query parameters...   timespan 1200, resolution 60, interface wan1, ip 8.8.8.8   I get...   [ { "startTs": "2022-05-31T12:48:00Z", "endTs": "2022-05-31T12:49:00Z", "lossPercent": null, "latencyMs": null, "goodput": null, "jitter": null }, { "startTs": "2022-05-31T12:49:00Z", "endTs": "2022-05-31T12:50:00Z", "lossPercent": 0, "latencyMs": 13.96, "goodput": 100000, "jitter": 0.35 }, { "startTs": "2022-05-31T12:50:00Z", "endTs": "2022-05-31T12:51:00Z", "lossPercent": 0, "latencyMs": 13.92, "goodput": 100000, "jitter": 0.38 }, { "startTs": "2022-05-31T12:51:00Z", "endTs": "2022-05-31T12:52:00Z", "lossPercent": 0, "latencyMs": 13.95, "goodput": 100000, "jitter": 0.34 }, { "startTs": "2022-05-31T12:52:00Z", "endTs": "2022-05-31T12:53:00Z", "lossPercent": 0, "latencyMs": 14.04, "goodput": 100000, "jitter": 0.53 }, { "startTs": "2022-05-31T12:53:00Z", "endTs": "2022-05-31T12:54:00Z", "lossPercent": 0, "latencyMs": 13.9, "goodput": 100000, "jitter": 0.28 }, { "startTs": "2022-05-31T12:54:00Z", "endTs": "2022-05-31T12:55:00Z", "lossPercent": 0, "latencyMs": 13.87, "goodput": 100000, "jitter": 0.35 }, { "startTs": "2022-05-31T12:55:00Z", "endTs": "2022-05-31T12:56:00Z", "lossPercent": 0, "latencyMs": 13.91, "goodput": 100000, "jitter": 0.21 }, { "startTs": "2022-05-31T12:56:00Z", "endTs": "2022-05-31T12:57:00Z", "lossPercent": 0, "latencyMs": 13.85, "goodput": 100000, "jitter": 0.29 }, { "startTs": "2022-05-31T12:57:00Z", "endTs": "2022-05-31T12:58:00Z", "lossPercent": 0, "latencyMs": 13.94, "goodput": 100000, "jitter": 0.3 } ]   ... View more

As above, sounds like an issue with your install/set-up, I'd guess the search path in the environment is not set correctly.   I'm not familiar with Python on VS/Windows, but try checking the PYTHONPATH setting, see here in the Windows section...   https://bic-berkeley.github.io/psych-214-fall-2016/using_pythonpath.html   ...this page also includes a simple script to tell you the value of the variable, if you run it in VS and then as executable, see if the answers differ.   ... View more

It's just how the API calls behave.   When creating a network, dashboard says...   You can create a network with multiple types of Meraki hardware (Combined hardware) or a network for one type of hardware. Additionally you can create a Systems Manager network.   Afaik by default networks are 'combined', there's no documentation saying that the API return value includes only productTypes where one (or more) of a type is present.   I'd guess the latter return value is a legacy of internal structure from earlier times, as it doesn't include cameras or sensors.   ... View more

If you can't do it with action batch, and assuming you are using Python, another way to speed things up is use the asyncio option in the library.   This allows you to run the requests concurrently, much faster than iterating through hundreds/thousands of networks/devices waiting for each to complete   You may need to wrap some back-off and retry logic around the API calls as the rate limit will kick in and the built-in recovery in the library is not always enough.   See https://github.com/meraki/dashboard-api-python there are some examples.   ... View more

Bear in mind that you are using v0 API endpoints, v0 has been deprecated for some time and is now in sunset period where operation is not guaranteed, see: https://community.meraki.com/t5/Developers-APIs/Dashboard-API-v0-End-of-Support-Sunset-amp-Grace-Period/m-p/138696#M5473   You really should use v1, it is the current version and is where new features are added. ... 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

Have all the devices generating location data been correctly placed on the map?   I think any 'stray' ones may default to the SF area. ... 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

You need to persuade them to open an internal case with the Dashboard-API support team. ... View more

For us the issue was resolved on 21st around midday UTC.   If you still see a problem then I suggest post a comment on the case you opened asking for an update.   ... View more

Normal operation still for me, no server disconnects/non-connects, using the gateway. ... View more

I fed this back to support on the case I opened and gave a link to your post.   They said they're investigating a wider issue than just my case, so good to know they are aware and working on resolution. ... View more

I've seen similar on n383 over the last couple of weeks, seems to be degrading over time.   From my end (using Meraki Python package), the problem is showing as server disconnects and server not accepting connections, rather than HTTP errors.   I opened a case yesterday, low priority but fast contact back from support, and then provided a lot of detail info to them.   As above, open a case is the best approach.   ... View more

Empty array typically means there are no matching events/other data, empty/null elements can  occur in many API responses.   You need to precisely define what you mean by "connected" and "disconnected", in the terms exposed by the available APIs and how wifi association/authentication work.   I.e. if a client moves out of range, there's no "disconnect me' event, it simply is no longer seen, but disconnection can still be inferred from the absence of information based upon some rules about things like when it was last seen.   The scanning API is used by commercial applications to determine client connect/other metrics (and at massive scale.)   In very simple outline, how the scanning API can be used...   detect a client not currently in list of connected clients, add it, set the 'first seen' timestamp   detect one that is already in the list, update the 'last seen' timestamp   periodically, go through the list, if the 'last seen' is too long ago, call it disconnected    There needs to be additional book-keeping to record/consolidate multiple sessions, but you see the basic idea.   This a very simplistic approach, in practice you'd also fuse with other data to refine results, such as RSSI, location, any authentication service info, data usage etc..   ... View more

For wireless clients, another approach is to use the scanning API... https://developer.cisco.com/meraki/scanning-api/#!introduction   Client data is delivered in real time to then analyse for 'presence' purposes. You can either write your own server, or there are open source and commercial options.   Another approach would be some kind of screen scraper to get what you need from the Location Analytics page on dashboard (which is driven by the same data as scanning API I think).   ... View more

Options depend on what type of client "connection" you are trying to measure.   Unless it is a connection type with explicit connected and disconnect events, you have to see what else you can use.   You could use https://developer.cisco.com/meraki/api-v1/#!get-network-clients   ...then call the difference between firstSeen and lastSeen the connection time for each client (within the sample period), you could then average the result.   But it is probably not going to be that accurate.   For wireless clients you could use...    https://developer.cisco.com/meraki/api-v1/#!get-network-clients   ...to get the list of clients (do it on each network), then iterate through the wireless ones with...     https://developer.cisco.com/meraki/api-v1/#!get-network-wireless-client-connectivity-events   ...using the assoc and disassoc events and timestamps to calculate the total time 'associated' over the sample period, call that the 'connected' time, then divide by clients to get the average.   ... 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