Skip to main content

Set up standalone operation

This guide shows you how to set up a Kentix device in standalone mode. You will learn when standalone is useful, how to select the operating mode in the setup wizard, and which limitations apply compared to a SiteManager cluster.

Prerequisites​

  • A Kentix device with integrated KentixONE web interface (HTTPS)
  • Access to the device IP via web browser (factory defaults or already assigned IP)
  • Basic network knowledge: IP address/mask/gateway/DNS known or DHCP enabled
  • Latest firmware recommended – ideally identical to other devices if you plan a cluster later
info

The web interface is accessible via HTTPS. You can upload your own certificates under “Configuration → Network → SSL certificate”.

Step-by-step instructions​

1. Understand the operation modes​

  • SiteManager/Main: Central management unit for a device cluster (M network). Only the SiteManager can take the role of “Main device” and manage satellites.
  • Satellite: Device that is subordinate to a Main (SiteManager) and centrally configured/managed there.
  • Standalone: Single-device operation without a cluster. Configuration and operation are done exclusively on the device itself.
note

Example AccessManager: It can be used as a main device (“Operating mode: Main Device”) or as a satellite (“Operating mode: Satellite Device”) in a cluster with other AccessManagers. In standalone mode, it is used as a single system and managed locally.

2. Access the device​

  1. Connect the device to power and network (PoE if applicable).
  2. Open a web browser and navigate to the device IP.
  3. On first start, go through the setup wizard.
warning

Ensure your PC is on the same network segment as the device, or that appropriate routing/firewall permissions are in place.

3. Choose operating mode “Standalone”​

  1. In the setup wizard, you will be asked for language, time zone, and network settings.
  2. In “Operating mode”, select Standalone.
  3. Create an admin user for the device and complete the wizard.
tip

If you want to switch to a device cluster later, you can change the operating mode in the “Satellite settings” and assign the device to a SiteManager (Main). Check the firmware versions of all devices involved beforehand.

4. Define network and security​

  • Set fixed IP parameters or use DHCP. We also recommend a different static fallback address so the device remains reachable without DHCP.
  • If possible, upload your own certificate (Configuration → Network → SSL certificate) and use strong passwords for admin accounts.

5. Perform local configuration​

  • All settings are made directly on this device: users, profiles, alarm groups, signaling, etc.
  • For SmartAccess (e.g., AccessManager): Configure door locks, readers, and access profiles locally on the device.
  • For SmartMonitoring (e.g., Multisensor): Define alarm groups, thresholds, and signaling locally.

6. Scope and limitations in standalone mode​

  • No M network cluster: You cannot enroll, configure, or centrally manage additional devices/sensors as satellites.
  • No central user/role management via SiteManager or AlarmManager — everything is handled locally on the device.
  • No central history/reports across multiple devices — only local logs/reports.
  • Integrations (e.g., email, SNMP, webhooks) must be configured separately for each device.
danger

The SiteManager is intended exclusively as a main device. It cannot be operated as a satellite. Use it if you want to centrally manage multiple devices.

7. Optional: Switch to clustered operation​

If single-device operation is no longer sufficient:

  1. Align firmware versions (device ↔ SiteManager).
  2. In the device’s “Satellite settings”, change the operating mode to “Satellite”.
  3. Enter the SiteManager’s IP as the main address and add the device there. For details, see “Main device & satellites”.

Tips & further links​

  • Overview of operating modes and supported devices: see the knowledge article “SiteManager mode or Stand‑alone mode”.
  • Build central management: see Main device & satellites.
  • SSL certificate and network settings: see “Configuration → Network” in the docs.

Troubleshooting​

  • Device not reachable: Check your IP concept, use the fallback address if necessary, and test network/VLAN/firewall.
  • Login fails: Is the admin user correct? Observe the password policy.
  • Missing functionality: Check whether it is available in standalone mode or requires a SiteManager cluster.