Keep in mind that it is the client that makes the join/roam decision and not the AP. Also keep in mind that Windows Update does not typically update the Wireless NIC drivers, you need to pull it from the manufacturers site and package that yourself, or teach your users how to do the upgrade themselves. This might improve the clients that are roaming to less optimal AP. And yes I also agree that you should disable the client load balancing feature.     If all of the above still doesn't resolve most of the roaming issues, having a site survey performed to evaluate the way the network currently looks, after adding AP that were not in the original plans, should be a big help in seeing what is going on in the RF.   ... View more

  This is from my dashboard:   Epson Printer   iPhone   If it is just a matter of the client reporting their capabilities to the dashboard, that could 100% be due to the Cisco Meraki/Apple partnership, which includes things like Fastlane(+), allows us to get more information from the device drivers than we do with other devices, as seen above. ... View more

so two dumb question:   1) when you are putting the username and password in are hitting tab to move to the next field, or are you clicking in the box?   2) is there a trailing white space on either the username or password? ... View more

just did it and it worked for me. ... View more

1.0.2 was posted back in July.   Looking at the Meraki Github 0.4.0 was committed 2 days ago, and I see that function there.   From the Changelog - August that looks like that function was added in 0.3.0.   it looks like both Developer and postman are both referencing functions in 0.3.0, though it is not available from pypi yet   ... View more

I think @MarcP was just pointing you to the Content filtering configuration area. Under URL Blocking, you wouldn't put " * ", you would put "cineblog01.*" as you had wanted in your OP ... View more

Honestly, sounds like a bug in the forwarding table of the MR33, since a reboot resolves it. I'd open a case, when you are having the issue so that they can look at the backend and see what's going on. it may also be useful to get a pcap of the AP's port, in the bad condition, and see what is being sent to the wire. ... View more

so to make sure I have this right. If you start out on the top floor (MR33) and roam to the bottom floor ( 3 AP) there is no issue. If you start on the bottom floor and roam to the upper floor, you get the "error getting IP address". Then, if you reboot the MR33 it will work again. is the above correct? Looking at the image you shared, it looks like the client gets authenticated just fine, and is on VLAN 100. Is this the correct VLAN for the client? ... View more

@chengineer Can you add that to the documentation? while they don't show up under Help > API, they do show up on (Postman Documentation) ... View more

@chengineer so the new "client" calls pertain GDPR? thank you for weighing in Shiyue ... View more

I've reached out to the SE that posted the meraki.py on Github to see if he can weigh in on this as well. ... View more

@Steinbep it shouldn't matter what your tracking is set to, as long as you are calling the correct element. If you are tracking by Mac, you call the client Mac. if you are tracking by IP, you call the client IP. but you should *always* be able to call the client ID. I just tested this both with track Mac and track IP and I get a 404 error either way I try to test it. ... View more

I read that: "Return the client associated with the given identifier. This endpoint will lookup by client ID or either the MAC or IP depending on whether the network uses Track-by-IP." the way I read this: 1) We should always be able to poll for the client ID 2) poll via mac or IP, is based on Client Tracking. I'm tracking by Mac and not IP as well, so I should be able to do a call with the client Mac address and have that return. It does not. I should be always able to make the call and use the client ID and have that return, it does not. ... View more

I'm seeing the same issue. I see that the PIP module is updated (0.34) and it has the Client function defined. when I attempt to make the call, however, it fails. it doesn't matter if I use the mac, IP or client-ID. for anyone that can make this work, what is your dashboard address? I'm hitting n49, and I'm wondering if there is just a slowness in the calls being opened to other shards ... View more

so digging into the that call, it looks like you can. the help(meraki) shows ``` updatedevice(apikey, networkid, serial, name=None, tags=None, lat=None, lng=None, address=None, move=None, suppressprint=False) # Update the attributes of a device # https://api.meraki.com/api_docs#update-the-attributes-of-a-device ``` if you click on the link to the API documentation, you can see what the call looks like to update the tags. keep in mind that you are updating per device, per network ``` updatedevice(apikey, networkid, serial, name=None, tags=None, lat=None, lng=None, address=None, move=None, suppressprint=False) ``` ... View more