I am disappointed that Meraki Sensors feature is leaving Meraki Dashboard because we use Meraki Sensors heavily across our Australian retail branches for a number of different use cases, and Meraki has discontinued the MT sensor product range, which will be getting sunset at some point. We are disappointed about that. I do not know yet if they are replacing it with something else, but I believe it may be going out to third-party manufacturers to offer that as a service that integrates. If I could improve the product in any way, I want to add that there are a number of functions in Meraki Dashboard that you can only do from the dashboard that are not available to us in the API. My role focuses heavily on automation, and that is a real pain point for us as new features come out. We really want to push Meraki to have API parity with every aspect of Meraki Dashboard. Configuration templates influence policy consistency across my distributed branches and are a big pain point for us with local site exceptions. If something needs to change for a local site requirement, then we end up having to break that site out of the template and manage it separately. The number of sites that we have had to do that for in the last couple of years has increased, which dramatically increases the management overhead for those broken-out networks, and it is slowly eroding the value that we get from templates. That is why we are looking to transition to more Terraform automation-driven configuration management and get rid of templates. I rate Meraki Dashboard a seven and not higher because templates cause us a lot of grief, and the lack of API parity is a real challenge for us. We would really appreciate seeing the API rate limit increased as well.
