Thanks for your feedback. We have a lot more troubleshooting capabilities planned in the near term releases. This will show some of the information and tools available to you today from ZD. So thats coming.
The crux of your question though, is why can't you login to AP UI/CLI. There are a couple of use cases after you login to the AP
- - Troubleshooting or monitoring on a per AP level
- - Making optimization of config on a per AP or even radio level
Moment you make config changes to the AP or radio from the AP UI/CLI, we end up in a state of two masters controlling that config. One might argue that AP changes should override cloud changes. However, when you consider scenarios at a wider scale this becomes increasingly problematic and runs counter to the philosophy of ease of management via Ruckus Cloud.
So the decision to not allow AP UI/CLI access was a design choice. Let us know what your use case is. We can try and accomodate that using APIs or direct features in the Ruckus Cloud.