I really wouldn't suggest changing the code to anyone. Requests Retry-After will give you the identical results. I've built all my python codes using Meraki library and when I tried converting it to Requests with the IF statement I still get the same error 429 with a Retry-After in 59 or 60 seconds. Nothing greater or less and I had a max retry of 10. I thought  the Retry-After would give off random seconds, but it was consistently 59 or 60.   Because of this result, I'm adding time.sleep() with a random integer in between API calls and use this setting for my dashboard. dashboard = meraki.DashboardAPI(API_KEY, suppress_logging=True,wait_on_rate_limit=True,maximum_retries=10)     Supposedly Meraki is looking into increasing the API calls to 50, but this was in early Alpha stages when I asked my rep. ... View more

Just an update to this the firmware is under stable release candidate: Cellular gateway firmware versions MG 3.101 changelog New feature highlights Enabled support for Verizon C-Band (N77) for the MG51/E Introduced automated discovery for AIF Telecom ... View more

This is such an apple support forums response for a basic feature. It's just uptime of last reboot. Meraki support has this uptime information of the last 3 boots. You can't say this information is not reliable itself, but supports can gather this information for themselves. And the only way for us to see it is to open a ticket. Meraki had some concepts on having uptime on the dashboard for customers, but it's been almost a year and they probably dropped the idea.  It's in my orgs wish list and still remains.  Of course if I had the last 3 reboot uptimes I can use that to help troubleshoot my issues. ... View more

I’ve had it on MG41 brand new out of box. Rebooting lime 4-5 times fixes it. I reboot and wait for it to appear online on the dashboard. Factory reset does fix it, but it sometimes doesn’t.  ... View more

We submitted this request to our SE and still nothing. We’re changing from Cradlepoint to MX and it’s a big step down. Cradlepoint offers a remote connect feature. (https://customer.cradlepoint.com/s/article/NCM-Remote-Connect-LAN-Manager)   We use this feature to connect to the local status page of the MG that is being installed and also the MX whenever that has issues.  it’s a feature we will miss entirely whenever we move on from Cradlepoint. We never needed a PC, raspberry PI or another computer to maintain. Not all field techs have a laptop so we’re SOL.  ... View more

This is only true for devices on the network. I'm only getting a handful of MGs with the API call below.  We have 250 that are unclaimed.  I can probably come up with a python script to create a dummy network and add the devices to get the information.    response = dashboard.organizations.getOrganizationDevices(     ORGID, total_pages='all',models='MG41' ) ... View more

sungod has it nailed in python the code below will do what OP is looking   import meraki API_KEY = "API-KEY-HERE" dashboard = meraki.DashboardAPI(API_KEY,suppress_logging=True)   response = dashboard.networks.getNetwork(     network_id ) #This looks for existing tags and stores it into local variable updated_tags = response['tags'] #Below adds two tags. updated_tags.append('WIFI') updated_tags.append('NEW YORK') #Finally update the network with the tag. Keeps the existing tags and adds the two I mentioned. response = dashboard.networks.updateNetwork(     network_id,     tags=updated_tags ) print(response) ... View more

How are you all running your speed test ? iperf to public servers ? ... View more

I think I’m experiencing this issue and I can reproduce it with only a MG41. I read a post on the MG section and tried to connect a MG41 to a MS120-48LP. My MG41 would get power, and on the port status the lightning symbol appears. Eventually the lightning disappeared and the MG41 was off. I flipped the connection with a Cisco 8811 IP phone. The phone powers on and I see the boot logo. The MG41 is now on the port the phone and powers on, but then turns off after a few seconds. The port turns off and also the 8811. I also have a MR access point on the switch and that loses power. Now no other port works with POE and the power tab on the switch on then dashboard does not show the POE  consumption. Just a blank screen.  Rebooting the switch fixes it and I try to reproduce the issue again. I plug in MG41 to port 48, 8811 on port 45 and MR back on port 37. I do the phone and MR first and they boot and connect. I now do the MG41 and the device powers on. On the port status I see it drawing 1.3 w to .9w or 0. This cycles for a few seconds then eventually 0 and the device stays off. I flip the 8811 and  MG41. Phone is powering on and MG. Eventually everything POE turns off phone MR and MG. Reboot fixes the issue.  This MG41 works on a MX85 it did prior to connecting to the switch. I’ve read other posts of users connecting to the switch on their network to get the MG41 POE power. So this is supposed to work, but it looks like the switch is having issues.    MS 14.33.1 ... View more

Also experiencing this issue with our APs 28.6.1 did not fix the issue for us.   ... View more