Setting up Olarm SIGNALS 2.0

Setting up Olarm SIGNALS 2.0



Step 1: Setup Preparation for SIGNALS 2.0

Before you begin, ensure you have the following ready:

  • Install and configure a test device

    • Install an Olarm MAX on an alarm panel for testing.

    • Verify the alarm panel is correctly programmed so the device can transmit signals.

  • Prepare Olarm COMMAND CENTRE

    • Log into Olarm COMMAND CENTRE.

    • Claim the Olarm MAX test device, complete the setup, and assign an account code.

  • Prepare Olarm APP

    • Install the Olarm APP on your mobile device.

    • Create a profile and add the Olarm MAX test device.

    • You will use the app to arm/disarm for testing signals.

  • Coordinate with monitoring software provider

    • Schedule a session with your monitoring software provider.

    • Confirm whether your monitoring system is configured as a TCP Client or TCP Server.

      • This information is required for Signals Proxy setup.

  • Download and install Olarm SIGNALS PROXY

    • In CC, go to: Settings > Connections & Ports > Enable SIGNALS 2.0 > Download here.

    • Install the application on the monitoring server PC.

System requirements (minimum):

  • Windows 10+

  • 4 GB RAM

  • 1 GHz CPU

  • 500MB storage




Step 2: Creating a Connection

  • Log into Olarm COMMAND CENTRE.

  • Navigate to: Settings > Connections & Ports > SIGNALS 2.0.

  • Click Add Connection.

  • Complete the fields:

    • Connection Name → e.g., “RCC Security Primary”.

    • Protocol Selection → choose either SIA DC-09 or Sur-Gard CID, depending on the signals you wish to receive.

    • Priority →

      • 1 = Primary (first connection used).

      • 2 = Secondary (backup connection).

        • Lower number = higher priority.

    • Connection Key Name → create a label for the key (e.g., “RCC Security CK1”).

  • Click Create.

  • Copy the Connection Key for use in the Olarm SIGNALS PROXY.



Step 3: Adding a Signal Path

  • Launch Olarm Signals Proxy on the monitoring server.

    • Click Add Signal Path.

    • Complete the fields:

      • Signal Path Name → e.g., “RCC Security Primary”.

      • Connection Key → paste the key copied from Olarm COMMAND CENTRE.

      • Connection Type → select based on your monitoring software:

        • If monitoring software is TCP Server → select TCP Client.

        • If monitoring software is TCP Client → select TCP Server.

      • Host / Port Details → enter the Domain name/IP address and port as provided by your monitoring provider.

    • Click Add Path.

    • Confirm successful setup:

      • In Olarm SIGNALS PROXY → status should show Connected.

      • In Olarm COMMAND CENTRE → the connection should display as Active.



Step 4: Testing the Connection

Once your Signal Path is added, verify that signals are being delivered correctly:

  • Heartbeat Verification

    • Olarm SIGNALS 2.0 sends an automatic heartbeat every 30 seconds from the Olarm Cloud.

    • This confirms that the connection is alive.

    • Example heartbeat formats:

      • SIA: 7B9F002C"NULL"9999L000000#0000[]_07:52:19,08-26-2025

      • CID: 31 30 31 31 40

  • Event Verification

    • Use the Olarm APP to send an Arm/Disarm command.

    • Confirm the monitoring software receives the corresponding signal event.

  • Logs and Transparency

    • View connection logs in either:

      • Olarm SIGNALS PROXY (local logs for troubleshooting).

      • Olarm COMMAND CENTRE (all configuration changes and SIGNALS 2.0 activity are logged for auditing).