Thank you. I understand what you are saying but the elements needed to track a bug we are hitting in the MR code is only easily seen/noted in the Connection Log data -> Failure Reason text.  We can correlate it to some event logs but when doing that we get a ton of false positives.   The actual data/text from Connection Log data -> Failure Reason so far is the only place where the data is available.   Same with the "Failure stage" = Association.  Basing on just this information doesn't fulfill the need and we get a ton of false positives again. Example date: Failure stage: Association Failure Reason: auth_mode='wpa2-psk' 11k='0' 11v='0' ft='1' reason='invalid_pmkid' radio='0' vap='5' channel='11' rssi='51' ... View more

None of the API calls I have attempted so far provide the data/text within Connection Log data -> Failure Reason. ... View more

Yes, just tried that one, it doesn't provide the same data elements, like Failure stage and Failure Reason. ... View more

Yea, so far none of these provide the data the dashboard does. ... View more

Sadly unavailable seems to be the results. Looking for it on the MX WAN ports, but LAN ports would be nice as well. ... View more

Is this what you are looking for?   https://developer.cisco.com/meraki/api-v1/update-network-alerts-settings/ ... View more

I believe you are looking for health alerts:   (Deprecated: This operation has been marked as deprecated, which means it could be removed at some point in the future.) https://developer.cisco.com/meraki/api-v1/get-network-health-alerts/    Replaced with: https://developer.cisco.com/meraki/api-v1/get-organization-assurance-alerts/     ... View more

No, this is not related to the ServiceNow plugin.  This question is specific to what abilities Meraki Support has to troubleshoot 401 errors. Any help would be appreciated  Thanks. ... View more

Does Meraki have an logging on 401 errors or ability to troubleshoot them?  They do not show in the Get Organization API requests call.   Where would I need to instruct Meraki Support to look? Thanks. ... View more

In the meantime you could get the device models from call "getOrganizationDevices"   https://developer.cisco.com/meraki/api-v1/get-organization-devices/     ... View more

The ask is not exactly clear here.  As you noted the Uplink statuses includes both WAN1, WAN2, and Cellular if needed.  You would filter out what you don't need.   https://developer.cisco.com/meraki/api-v1/get-organization-appliance-uplink-statuses/   If your WAN2 interfaces are Meraki MGs then you can get more information around those devices statuses from API Call:  "Get Organization Cellular Gateway Uplink Statuses"   https://developer.cisco.com/meraki/api-v1/get-organization-cellular-gateway-uplink-statuses/     ... View more

Check out Lambda filter options for the list.  I believe it will do want you need.  I can share an example later if still needed.  ... View more

Is there any documentation around this "Improvements to functionality of Day-0 Zero-touch connectivity"?  Thanks. ... View more

I take that back. Think I’m wrong there.  ... View more

I’m pretty sure the profile you are looking at there is the security profile for the port, not the switch.   ... View more

Be aware sometimes the notes within the email contain more/different information than dashboard changelog.   Do not expect all bugs or issues to be properly documented or disclosed - in either.   ... View more

Posting update as I was looking for this API call.   https://developer.cisco.com/meraki/api/cycle-device-switch-ports/ ... View more

Posting update as I was looking for this API call.   https://developer.cisco.com/meraki/api/cycle-device-switch-ports/ ... View more

I have heard whispers that Device uptime and reboot reasons are in the works on the MS product line, with MX and MRs to follow...   As in soon to come.. Not waiting two years on the wish list.   The basic information within standard Cisco (non-meraki) devices. ... View more

Not sure if this exactly fits what you need, but this was just announced recently.   https://community.meraki.com/t5/Developers-APIs/Now-GA-Device-Availability-Change-History/m-p/201052?utm_source=communitymembers&utm_medium=email&utm_campaign=immediate_general%27#M8583   /organizations/:organizationId/devices/availabilities/changeHistory ... View more

It use to be, but I believe it still is coded for V0 API calls last I looked.  It was a great place to start to learn the API and get data back in a simple format.   The evolution was this:  https://developer.cisco.com/docs/meraki-tools-google-sheets-add-on/#!introduction/meraki-tools-for-google-sheets   They are quick and dirty, simple but limited in function, but no code/low code to get some basic data back in a usable format.  I started with them early on, but once you get into python you won't likely go back.   My opinion. ... View more

I have had luck with using a Throttler, but you have to play with the timers sometimes. It will also depend if you have other scripts running against the API on your ORG, which will impact your rate limit.   from asyncio_throttle import Throttler # Used to control flow of API calls to the API interface throttler = Throttler(rate_limit=16, period=1) # snip of code async def gather_ports(aiomeraki, serial): # had to use throttler or it would overun the API. async with throttler: try: switch_ports = await aiomeraki.switch.getDeviceSwitchPorts(serial) except meraki.AsyncAPIError as e: print(f"Meraki API error: {e}") except Exception as e: print(f"some other error: {e}")     ... View more