Jump to content
C4 Forums | Control4

Eddie Kelley

c4Forums Member
  • Posts

    6
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Eddie Kelley's Achievements

  1. To @Brunob00's credit, Pakedge/Control4 did not provide any documentation that outlines the steps required to connect the NK-1 or WK-1 into the OvrC portal after upgrading to firmware v.2 to be able to resume management of the access points. Although the firmware release notes state that the OvrC platform must be used, it (and other documentation within the Control4 portal) omitted the steps that have been provided above. That's the difference between comprehensive and non-comprehensive documentation (e.g., you can actually read about the steps required to correct management issues instead of having to use trial and error to resolve the problem). For example, the What you need to know about the new 1.30 Wireless Access Point firmware - WK-1 / WK-2 / WX-1 document was posted to provide users information "some important things to know about the latest firmware version"... There doesn't appear to be any comparable document (that I can find) regarding the major 2.0 firmware update (i.e., like the instructions provided for the minor 1.3 update).
  2. Enabling Wi-Fi management may require your OvrC portal to have at least one access point or controller (e.g., NK-1) added to it, but I believe that Wi-Fi Management can be enabled within the Customers section (top-left icon that resembles a silhouette of a person) > Customer Site Name > Site Settings > Wi-Fi Management (where 'Customer Site Name' is the name that you've assigned to the customer site).
  3. @DeevdT I ran into the same predicament, but was able to setup an OvrC account, then add the NK-1 into it, and enable Wireless Management. After enabling the wireless management feature in OvrC, the NK-1 was able to perform Upgrades to all of the access points (WK-1) that I was previously managing with the device via BakPak (by going into each wireless device that showed up, and then clicking the Update/Upgrade button). If you're open to using the (more mature?) OvrC platform, I'd recommend simply enabling wireless management there and upgrading the APs to firmware v.2 through the OvrC interface. Unless there's some compelling reason to use BakPak (which will probably be discontinued eventually), moving to OvrC seems to be the most future-proof solution. It would be nice to have some documentation on this - either in the firmware upgrade notes or elsewhere, but I was unable to find any articles that Pakedge provided to detail this upgrade process. Maybe I didn't look hard enough.
  4. After enabling Wi-Fi management within the Ovrc portal, and then selecting a device, the portal is allowing the older devices to be updated to firmware v.2 remotely.
  5. Thanks for the response Muj, You're right - it might be a headache to factory reset 27 WK-1 devices, update their firmware, and then re-join them to the Ovrc cloud so that they can obtain their configuration settings. However, I'm hoping that this isn't the simplest option. I have reached out to Control4 support, and am hoping to hear back.
  6. 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.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.