Olarm SIGNALS PROXY Guide (Step by step)
The Olarm SIGNALS PROXY securely forwards alarm signals from the Olarm Cloud to your monitoring software using industry protocols likeSIA DCS and Ademco CID.
It forms the final link in Olarm’s signal delivery chain, ensuring reliable communication between Olarm-connected alarm systems and your ARC.
Step 1: Creating a Connection in Command Centre
To securely link the SIGNALS PROXY to the Olarm Cloud:
Log into Command Centre
In Command Centre, go to Settings > Connections
Click ‘Add Connection’
Enter the following:
Click ‘Create'
Copy the Connection Key from the connection details page
Step 2: Installing Olarm SIGNALS PROXY
Download and Install
Open the Application
Step 3: Add a Signal Path
Click ‘Add Signal Path’
Name the Signal Path
Use a clear, recognisable name (e.g. Main Office TCP Link
)
Select the Connection Type
If your monitoring software is a TCP Server, choose TCP Client
If your monitoring software is a TCP Client, choose TCP Server
If you select TCP Client please provide the Host and Port that the Monitoring Software is listening on.
If you select TCP Server please provide the Port that you would like the Proxy to listen on.
The Proxy can use any available port, but ensure that the selected port is not already in use by another service. Using a port that is already occupied may result in connection conflicts.
Step 4: TCP Configuration
If using TCP Client:
- The monitoring software must be set up as a TCP Server
- You must enter the IP address or domain hostname and port where the monitoring software is listening
- The SIGNALS PROXY will initiate the TCP connection
If using TCP Server:
- The monitoring software must be configured as a TCP Client
- You must choose a local port for the SIGNALS PROXY to listen on
- The monitoring software will initiate the TCP connection to the proxy
In both cases, the SIGNALS PROXY will forward signals from the Olarm Cloud to the monitoring software over this TCP link.
Step 5: Finalising the Signal Path
Paste the Connection Key from Command Center
Confirm the connection type, protocol, and port
Save the Signal Path
Once saved, the SIGNALS PROXY will establish a secure WebSocket connection and begin routing signals.
Email Alerts
Olarm sends automatic alert emails to help monitor connection health:
Incompatible Connection Type
Sent daily or every 12 hours if a signal path cannot receive data due to a mismatch
Failed to Process Signals
Sent daily or every 12 hours if a connection is failing due to configuration or network issues
All alert emails include a direct link to Command Centre for resolving issues quickly.
Related Articles
Exporting Signals data
All signals data is downloadable via CSV format (which can be used with tools like Microsoft Excel, or similar tools). To export signals data, first ensure that the correct Day or timestamp has been applied. When you’ve select the amount of data rows ...
How to download an event log from an Olarm communicator in Command Centre
Event logs provide a detailed history of the Olarm device's signals combined with the events recorded by the alarm system. You can download these logs in CSV format directly from Command Centre for analysis, auditing, or recordkeeping. This feature ...
How to lock/unlock Olarm APP access in Command Centre
You can control whether a users have app access to a specific Olarm device. Locking out users prevents them from viewing or controlling the device in the Olarm APP - but it does not stop the device from sending signals to the monitoring platform. Go ...
How to migrate settings from one Olarm device to another in Command Centre
If you're replacing or upgrading your Olarm device, you can easily transfer its configuration to the new unit using the Settings Migration feature. This ensures your new device inherits all key settings from the old one, saving time and reducing ...
How to set Account Codes & References in Command Centre
If you're using third-party monitoring software, it's important to ensure the account code in Command Centre has been set in order to receive signals from the device. These codes help uniquely identify each device - and its partitions - for accurate ...