Site device configuration¶
Site Device Configuration identifies an installed application or integration service, associates it with a site and optionally a post, and declares the capabilities that TEKControl should provide to it.
Open General Administration, select a site, and then select Device Configuration. This action requires Global Client Admin-level authority or higher.
Note
These records are different from Device Administration, which inventories registered mobile devices, and from AllBox administration, which controls AllBox and kiosk menus.
Create a configuration¶
- Leave Items on Add New.
- Select the operational Post when the service belongs to one post.
- Enter a required, recognizable Description.
- Enter the identifiers supplied by the installed application or integration.
- Select only the capabilities used by this deployment.
- If this is an LPR service, select its responsible cameras.
- Select Save.
After a successful save, the form refreshes and returns to Add New with blank values. This is expected; reopen Items to verify the saved record.
Edit a configuration¶
Select an existing description in Items. The form loads its details, capabilities, camera assignments, reported version, and health action when available. Save before selecting another item—the editor does not warn about unsaved changes.
Device details¶
| Field | Guidance |
|---|---|
| Post | Operational post served by the device. The UI marks it as required, but the placeholder can be saved as no post. Treat it as required unless the integration is intentionally site-wide. |
| Description | Required administrative label. Use a unique name that identifies the function and location. |
| Device identifier | Primary identifier used when an endpoint requests configuration or sends integration activity. Copy it exactly and do not reuse an active identifier. |
| Connected device identifier | Optional related-device or service identifier used for integration lookup and health matching. |
The editor does not validate identifier format or uniqueness. Duplicate or mistyped values can make an endpoint receive the wrong configuration, fail to authenticate to the expected workflow, or match the wrong health record.
Capabilities¶
| Capability | Intended configuration |
|---|---|
| Kiosk | Kiosk-capable application or endpoint. |
| Intercom | Intercom integration or workflow. |
| LPR | LPR service that retrieves site and assigned-camera configuration. |
| Desktop | TEKControl Windows/Desktop application record. |
| Petro | Petro integration; Petro configuration requests require this flag. |
| Keri | Keri access-control integration; enables the external configuration action for an existing record. |
Flags are not mutually exclusive and the editor does not verify that the installed software supports the selected combination. Match them to the deployment record. API workflows can reject a device whose required capability is not enabled.
Assign LPR cameras¶
Enable LPR to use Responsible LPR Cameras. The list contains assignable cameras for the selected site and labels each with its name, external camera ID when available, and TEKControl camera ID.
Assign only cameras monitored and synchronized by this installed service. A camera already owned by a different LPR device configuration may not be offered. Saving with LPR disabled submits an empty assignment list and removes this configuration's current camera responsibility.
The LPR service receives only assigned cameras that are themselves LPR-enabled. Camera connection details, credentials, post relationship, and relay source come from the camera and related access-control configuration; maintain those records separately.
Warning
Incorrect camera ownership can cause duplicate processing or leave a camera unmonitored. Review every camera assignment before replacing, splitting, or consolidating an LPR service.
Version and health¶
Version appears for an existing configuration after the connected client has reported one. A blank version means no value is currently stored; it does not prove that the endpoint is offline.
Health Details appears only when TEKControl can match a health target by the configuration record or its device identifiers. Use it to inspect the current health data, but verify identity before assuming a similarly named target is this endpoint.
Save and lifecycle boundaries¶
Create, update, site association, post association on creation, and camera assignments are persisted during Save. The main record is saved before its LPR camera assignments; a server error during assignment can therefore leave the record saved but cameras incomplete.
There is no delete, deactivate, or retire action in this dialog. Do not repurpose an old record merely to remove it from the list. Coordinate cleanup through the approved support or deployment process so identifiers, camera ownership, audit history, and dependent integrations are preserved correctly.
For Keri records, see External Keri configuration. For common failures, see Troubleshooting.