We are a school that just this past summer converted to all Meraki equipment.  We have a high density environment with 196 MR57s scattered across 11 buildings and are seeing all the same things everyone has been seeing ( massive unexpected disassociations, constant roaming of devices that are standing still, repeated disconnects and inability to reconnect making it impossible to have zoom calls, constant eapol timeouts, repeated connections to an AP "for a few seconds").     We have upgraded to 30.5 and it seems to have made dent into the connection problems we've been having.  It's not perfect by any means.  We still get some disconnections and looking at our connection log, there are constant authentication failures due to eapol timeouts.  Has anyone else tried 30.5? ... View more

I have written some thing similar recently, except I have use a HTML interface to display my results ... View more

The simple way to get round it is to count the unique mac in    dashboard.wireless.getNetworkWirelessClientsConnectionStats( network_id )     ... View more

This has the same issue there needs to be something to capture the hooks, store the data and then create a report at the end of the week / month. And this is what i am trying to avoid we have a number of tools that check AP status and so i could for example use a call to Solarwind to get the AP up / down time. But i was curious if there was a way to do native in meraki.   And it looks like you can do it using the network alerts history and network devices.    results = dashboard.networks.getNetworkAlertsHistory(net["id"], perPage = 1000, total_pages='all')     for net in networks: results = dashboard.networks.getNetworkAlertsHistory(net["id"], perPage = 1000, total_pages='all') print (results) deviceevent = (event for event in results if event["device"]["serial"] == "xxxxxxxxxx") for event in deviceevent: print (f' Time start {event["occurredAt"]} type {event["alertType"]}') print   gives the events for an AP and only needs 2 calls per network. Then it's not too hard to loop through this and for a specified time range count the down time per AP.    Time start 2023-02-13T10:05:24Z type An access point came up Time start 2023-02-10T23:25:20Z type An access point went down Time start 2023-02-05T17:07:55Z type An access point came up Time start 2023-02-01T00:21:30Z type An access point went down ... View more

Can you post the parameters given in the call to https://developer.cisco.com/meraki/api-v1/#!get-network-wireless-client-count-history   and also the complete return data.   Fwiw for a few years I've used https://developer.cisco.com/meraki/api-v1/#!get-device-wireless-connection-stats for analysis/reporting, it's proven good for understanding where/why there are problems across large organizations.     ... View more

Sorry I resolved it, needed to move the looping though networks out side the "try" as it was failing on one network and ending the loop, using "try" after the "for net in networks:" and it works as expected ... View more

Peering directly from MX-B is likely your best option.   What you are trying to do will not work for the already mentioned reason ... View more

Cheer I have got a responce back and Engineer so sorting it out.    I think it would be nice if we could "tag" these Default routes and have them exempt from unique checking our selves. or chose to validate agsint either or both  "assigned subnets" and / or "routes".   Becasue the validation is useful but this method in networking of using supernet routes for summarising is common. We use it in all out hub sites to route all private IP's back to the core.    ... View more