I recently updated an NK-1 controller at a customer site to firmware v.2, and after updating, we're unable to manage the access points that the controller was previously setup to manage. The WK-1 APs were not upgraded to firmware v.2 before the controller was (they're still running firmware v.1.40), which has left them unmanageable.
Unfortunately, since the WK-1 units were managed by the NK-1 previously, they will not allow us to login to the device via the web interface. When the web interface for the WK-1 is visited, it shows "This device is managed by the NK-1", and doesn't allow display the login (username/password) fields.
I have a feeling that we're going to be required to perform a factory reset on the WK-1 units, then perform the v.2 firmware update, and finally re-join them to the controller so that they pickup the configuration again and become manageable.
Does anyone on this forum have experience with some type of backdoor access to the WK-1, or some other way to force a previously-managed WK-1 unit to allow us to login to update the firmware so that it can be managed again?
The release notes for both the WK-1 and NK-1 firmware update indicate that Ovrc is being used instead of BakPak, but the notes don't seem to provide an upgrade path (e.g., upgrade order for the devices being managed by the NK-1) for the devices, nor do they note that the WK-1 units might be left in an unmanageable state in the event that the NK-1 is updated to firmware v.2 before the APs.