Do you have specific errors? We did something very close to this just recently. We pull our configuration items. Store them into a sql db, config entry query ends up as its own table and each row is the site_id and updated_id so we can track the latest pull so we only compare the latest to our source of truth.   Currently we don't take any action but using the SQL we then built a PowerBI report compare the retrieved results compared to defined standards. We wrote the whole config pull via Python using the Meraki SDK and then have it scheduled to run nightly via a Github self-hosted runner. ... View more

No, is not working for me. ... View more

Using curl gives the exact same error. Strange, because other requests pass without any problem. ... View more

Please do report this to support. ... View more

You are right but if writing a tool, not only for my configurations, the tool does not have history of the secret, it should retrieve from API and restore if necessary. ... View more

I haven't used it but I assume because it returns data from the entire organization then you need org wide privilege. ... View more

Hi, both Early Access and VLAN Profiles are enabled for the organization but still Error 500 from Meraki if trying to submit a batch with a VLAN Profile action. ... View more

Congratulation - well done! ... View more

Nice!  Are there any others out there or just these two?  Not everything will be in the Meraki Marketplace...   Larger Organizations should have something in place, as there's nothing built-in to Meraki Dashboard. ... View more

Hi, the communication between MT and IoT Builder is through MQTT for the data and API for the configuration.    You can ask for a trial at the website https://v-app.io ... View more

Wow, that is a very specific usecase.  I'm interested to see how that goes 😉 At this time I only added manual AP positions. ... View more

I just asked for an update on my case.  The latest note in it from January 2022 from Meraki Support was they are still waiting to hear from the developers. What's sad is when I first raised awareness about this issue in the forum, a Meraki engineer on the forum said it is not an API bug, but how they are reading the data.  He said he added a note to my case, but I never saw it.  Perhaps, it was in an internally visible only field.  I've checked it using the interactive documentation and get the same result.  Maybe now with multiple people raising the issue, we can get some actual traction on it.  If the can't provide reliable data to with that API endpoint, they should disable that endpoint until they fix it.   ... View more

Awesome! Thank you @AmyReyes  ... View more

Hi, I have the cameras deployed on two different networks with the same DNS and one site is working correctly while the other not. ... View more

Hi, if you have a clientId like merakimv_SERIAL you are using an old firmware with lot of issues on MQTT. Newest firmware has a random clientId like mosqxxxxxxxxxx. Multiple reconnection is an issue also with latest firmware and depends on camera not sending always required keep alive packets and broker closing connection if keep alive packets are not received. ... View more

Thanks everybody, I found just few minutes later it was necessary not to specify null fields.   I think this should not be an API behavior as this logic should be inside API and not on caller. ... View more