How can I integrate my system?
The Integration Assistant allows you to combine multiple Main‑Devices into a single SiteManager or AlarmManager. The integrated devices are automatically switched to Satellite‑Device mode. The assistant guides you through the process in five clear steps – including verification, conflict resolution and final report.
Requirements
- Access to both systems (the integrating target device – SiteManager/AlarmManager – and the Main‑Device to be integrated)
- Same KentixONE version on all devices
- IP address of the Main‑Device to be integrated
- API Bearer Token of an administrator user of the Main‑Device to be integrated
- Matching communication key on all involved devices
- Time settings of the devices are synchronized or within the allowed tolerance
- PIN length and RFID settings of the devices must be identical.
- Complete system backup has been created
SiteManager and devices that are already configured as Satellite‑Device prior to integration cannot be integrated as Main‑Device.
Overview
This is how the integration works in short:
- Each Main‑Device to be integrated is integrated individually.
- The Satellite‑Devices associated with the Main‑Device are taken over by the new Main (SiteManager/AlarmManager).
- Before starting, the assistant automatically checks version status, communication key, operating mode and time.
- Conflicts (e.g. duplicate names/configurations) are displayed and must be resolved.
- After completion, an integration report is available for download as CSV.
Step‑by‑step Guide
1. Starting the Integration Assistant
- Open the Integration Assistant on the target device (SiteManager or AlarmManager).
- Have the IP address of the Main‑Device to be integrated ready.
- Note: Multiple Main‑Devices are integrated consecutively.
2. Preparation and Checks
After entering the IP address of the Main‑Device, the assistant automatically checks:
- Communication key: Must be identical on all devices. Configuration: Configuration → Security.
- Version: KentixONE software version must be identical. Check under System → Device Information; perform update if necessary.
- Operating mode: A Main‑Device with its associated satellites is integrated. Devices already configured as Satellite cannot be integrated as Main.
- Time: Log entries contain timestamps; ensure clocks are synchronized.
- Backup: Make sure a current backup exists.
Set timezone, time and NTP identically on all devices to avoid conflicting log timestamps.
3. Authentication
- The integration is triggered via the KentixONE ReST‑API.
- Enter the API Bearer Token of an administrator account of the Main‑Device to be integrated.
- The token is stored in the admin's user profile.
4. Listing and Conflict Resolution
- The assistant lists all settings to be transferred and marks conflicts.
- Resolve conflicts by:
- Renaming the colliding entries of the device to be integrated, or
- Comparison: Choose between the settings of the target system and those of the system to be integrated. The chosen settings will apply system-wide afterwards.
Typical conflicts: Names of alarm groups, users/user groups, profiles, network or signaling settings.
5. Integration and Report
- Start the integration. All parameters and log entries are transferred.
- After completion, the system creates an integration report with all transferred parameters and any errors.
- Download the report as CSV if needed and document the change.
After successful integration, the integrated device and its previous Satellite‑Devices are listed in the Detail View of the target system. The integrated device is automatically switched from "Main‑Device" to "Satellite‑Device".
Tips & Tricks
- Plan integrations during maintenance windows – especially for large log transfers.
- Check duplicate identifiers beforehand and establish a naming scheme to minimize conflicts.
- Note the original IP addresses; after integration, management can be done centrally.
- Keep the integration report – it serves as proof and source for error analysis.
Troubleshooting
- Check fails:
- Align communication keys (Configuration → Security) and restart.
- Different software versions: Perform firmware update to same KentixONE version.
- Correct time differences (System → Date/Time/NTP).
- Authentication not possible: Check validity and permissions of admin token or generate new token from user profile.
- Conflicts not resolvable: Perform renaming in source or target system beforehand and restart integration.
- Satellites missing after integration: Check synchronization status; verify network accessibility and communication key.
Glossary
- Main‑Device: Primary device of a system to which satellites are connected.
- Satellite‑Device: Subordinate device that receives configuration from the Main.
- SiteManager / AlarmManager: Target systems into which Main‑Devices are integrated.
- API Bearer Token: Authentication token of a user account for the KentixONE ReST‑API.