Pretty sure this is due to the recent bifurcation of the switch firmware into the MS & CS lines. It now shows up on orgs with 0 switches. Probably some validation process no longer catches it as the underlying code trains have changed.
I'd open a Support case so they can log it as a UI bug.
Ryan / Meraki SE
If you found this post helpful, please give it Kudos. If my answer solved your problem click Accept as Solution so others can benefit from it.