Hi @GroupeBleu I see you mentioned you got to the local status page but didn't mention what the error was listed there. I think at this point you should start getting concrete data about the state of the switch when it is facing problems without power cycling it. (For reference) All Meraki Go switches have a permanent local interface of 1.1.1.100, on a /24 subnet. If you connect a laptop and assign a static IP to the laptop of 1.1.1.99 and a subnet mask of 255.255.255.0, you should be able to go to 1.1.1.100 in your browser to see the real-time status of the switch. This includes the current error the switch is facing, causing the LED state to be what it is. Knowing what that error message, and knowing that the device has a sane configuration will go a long ways in pinning down the cause of your problems. The same tactic can be applied to the access points. If you connect to an access point wirelessly and navigate to ap.meraki.com you should hit the local status page, similar to the switch, showing the current status of the device.
... View more