Skip to content

External Keri device configuration

External Device Config is available only after an existing site device configuration is marked Keri. It requests and displays the raw JSON configuration reported through the application gateway.

This window is read-only. It does not edit, validate, save, or push JSON back to the controller.

Pull configuration data

  1. Confirm the selected device description and device identifier in the parent editor.
  2. Select External Device Config.
  3. Select Pull Config Data.
  4. Allow the request to reach the gateway and the Keri integration to report its configuration.
  5. Review the formatted payload.

The portal waits approximately two seconds after sending the pull request and then displays the payload currently loaded for the record. The external device reports updated data asynchronously, so a slow response may not appear during that first refresh.

Refresh configuration data

Refresh Config Data redraws the payload currently held by the open dialog. If the device reported after the record was loaded, close both configuration windows, reopen the site device record, and open External Device Config again to load the latest stored value.

If no payload is stored, the dialog displays Configuration not found. If the value is not valid JSON, it reports a parsing error instead of formatting the content.

Warning

Raw controller configuration can contain security-sensitive identifiers, topology, addresses, and integration values. Do not paste the payload into an unrestricted ticket or chat. Redact secrets and personal or site-security information before sharing it with support.

Troubleshoot a pull

  • Confirm the configuration is saved, marked Keri, and has the exact device identifier expected by the integration.
  • Confirm the application gateway address and port are available to the portal.
  • Confirm the Keri service is online and able to return its payload to TEKControl.
  • Wait for the asynchronous response, then close and reopen the record.
  • Use Health Details in the parent editor and relevant gateway/device logs to establish where the request stopped.

Pulling configuration is an operational request, not proof that the controller accepted any change. Compare the returned data with the approved Keri configuration before taking corrective action.