Yes support is helping with the case. Also had to pull some strings with our Cisco rep for escalation. ... View more

Yes I can confirm its v1 issue. Here is an update from meraki team "After further investigation, we have determined that this is a known issue that our development team is aware of. After a device is claimed, it takes a period of time for that change to be replicated across the Meraki infrastructure globally. This issue arises because the server handling your API call has not received an updated copy of the device claim change made in the previous call." Looks like they are working on it. I will update once they have a fix. ... View more

Yes it looks like it is v1. Did you get a chance to work with meraki support on this at all? ... View more

I am using the SDK version 1.4.3. I believe this uses v1 of the API. ... View more

Thats the frustrating part. The stability of the API/SDK is the concern because sometimes the same call works and sometimes it does not. ... View more

Yes invalid serials does give that error but I have a function specifically to remove invalid serial/mac that are not part of my orgs inventory. I cannot share the code but the following is the function thats giving the error.   respData = m.devices.updateDevice( apSerial, name = apname, tags=apTags )   apSerial parsing cannot be wrong because, I use the same variable to assign licenses and thats working. Weirdly enough the same function works after few hours.   ... View more