Setting Up Event Broadcasting
The article describes how to set up broadcasting of events from the Ri-HUB control center installed at a monitored object to the central monitoring station (CMS) and make sure that events are correctly transmitted from Ri-HUB to the CMS. The instructions are step-by-step, with explanations of the key parameters and setup recommendations.
To set up broadcasting of events from Ri-HUB to the CMS of the security company, you need to:
- Open the RiCoder admin web panel.
- Add the CMS server to which events from Ri-HUB will be broadcast.
- Create an event broadcast template.
- Connect the monitored object to the broadcast template.
1. Adding a broadcast server (CMS)
You can learn about the specifics of RiCoder interaction with the "Tsentr Okhrany" software server in the article Integration of RiCoder software with "Tsentr Okhrany" software (C-Nord) (in Russian).
1. Select Organization profile in the left side menu.
2. In the Outgoing connection to CMS block, select Add server.
3. Enter the Host and Port of the server that will receive events from RiCoder. Click Add Server.
Use the public IP address or DNS name of the CMS server if the server receiving messages from RiCoder is available by DNS name.
4. The CMS server is added to the Outgoing connection to CMS list, and the CMS connection status column shows the Connection error status. Go to the next section to create a broadcast.
RiCoder initiates a check of the connection to the CMS only when the specified CMS server address is linked to a broadcast. If there is no broadcast linked to the CMS server, the status will always be Connection error.
2. Creating an event broadcast template
1. Select Broadcasts in the left side menu.
2. Click Create broadcast. The button is located in the upper right corner of the screen.
3. Enter the broadcast name in the Broadcast template name field.
The broadcast template name and the additional information about the template must be short: up to 15 characters.
4. Fill in the Additional information field if necessary.
5. In the CMS server field, select the required server from the list.
A mandatory condition for creating a broadcast is selecting the CMS server to which events will be broadcast.
The CMS server list shows the servers that you previously added in the Organization profile section. Learn more in the section Adding a broadcast server.
6. Set the ping period from RiCoder to your CMS server in the Connection check period field.
- The period is set in seconds.
- Values from 1 to 500 seconds are allowed.
- Recommended value: 100 seconds.
- To reduce the network load (traffic), set a higher value for this parameter.
The connection check ping is required to keep the connection between the CMS and RiCoder up to date. The ping cannot be disabled. In the absence of frequent events from Ri-HUB, RiCoder sends test events to the CMS over the open connection to check the connection. You can view the results of the connection check ping in the CMS server logs, if this option is available.
7. Set the timeouts for monitoring the Ri-HUB connection to RiCoder.
The timeouts monitor the Ri-HUB connection to RiCoder and are a common setting of the broadcast template. The setting will apply to all objects (Ri-HUB) connected to this broadcast template.
- Timeout for sending the connection loss event (7.0.1)
- Timeout for sending the connection restoration event (7.0.0)
Recommended value for Timeout for sending the connection restoration event (7.0.0): at least 30.
With values above 30 seconds, events are guaranteed to be sent and processed.
The value of Timeout for sending the connection loss event (7.0.1) can be any.
1. To avoid frequent events from Ri-HUB, do not set minimum values.
2. With a poor connection, frequent reconnections of Ri-HUB to RiCoder are possible.
8. Configure the mapping of RiDom and Ademco codes.
If you do not want to transmit some RiDom code from the object to the CMS, select Do not use in broadcast in the Ademco code field opposite the corresponding RiDom code.
New RiDom codes are added when the functionality of Ri-HUB control centers is extended. When the RiCoder software is updated, the list of broadcast codes will be supplemented with new combinations. Make sure the code mapping in the broadcast template remains up to date after the update.
9. If necessary, add an Ademco code if you did not find the required one in the list. Learn more in the section How to add an Ademco code?
10. Click Save broadcast.
11. Make sure that the connection between RiCoder and the CMS server is established some time after the broadcast template is created. Go to the next section to check the connection.
For additional monitoring of the Ri-HUB connection to RiCoder and to keep the broadcast active, configure the periodic communication testing event by schedule or by interval in the Ri-HUB settings in the RiDom mobile application.
2.1. Checking the connection between RiCoder and the CMS server
After the broadcast template is created, its initial status is No connection to CMS.
1. Wait until the date and time appear in the Last connection column.
You need to wait until the end of the connection check period that you set when creating the broadcast. As soon as RiCoder receives a response from the CMS server (ping), the Last connection column will show the time and date of the last message received from the CMS. You can see the ping result only in the CMS server logs.
If there was no ping for longer than the time set when the broadcast template was created, there is a problem with the RiCoder connection to the CMS. Learn more about possible faults ...
2. The broadcast template is configured. Go to the next section to work with requests from Ri-HUB owners for the security company to take objects under monitoring.
If necessary, you can edit the broadcast template: set other ping intervals, timeouts, Ademco codes. To do this:
1. Double-click the row with the required broadcast.
2. On the page with the broadcast information, click the Edit button in the upper right corner.
3. Change the data and click Save changes.
The broadcast does not stop during editing. The changes are applied immediately after saving.
3. Connecting a monitored object to a broadcast
3.1. Processing monitoring connection requests from Ri-HUB owners
Requests from RiDom users to connect an object (Ri-HUB control center) to monitoring are located in the Requests section.
Requests are synchronized every 30 minutes or on demand.
To force synchronization outside the schedule:
1. Click Synchronize requests with the RiDom cloud, the button in the upper right corner of the request list page.
2. After the synchronization is completed, you will see a pop-up notification in the upper right corner.
2. Double-click the request row to view its details.
3. Make sure that the owner's Ri-HUB is currently connected to the RiCloud cloud service (a RiDom component).
If Ri-HUB is offline, the request will not be accepted. Learn more about fault diagnostics ...
4. Click Start monitoring if the Ri-HUB owner filled in the data correctly and the object will be taken under monitoring in accordance with the internal rules of your security company.
5. Select the broadcast to which Ri-HUB will be connected from the list of available ones.
6. Enter the object identifier in the CMS in accordance with the internal rules of your security company.
You will see the specified identifier on your CMS when receiving messages.
7. Click Connect. The object is now monitored by your organization. You can find information about the connected object in the Objects section.
If Ri-HUB is offline, an error message will appear. The connection will not be made. The Ri-HUB owner's request will remain in the Requests list unchanged.
8. Make sure that the broadcasting of events from Ri-HUB to the CMS works. Go to the next section.
3.2. Checking the broadcasting of events from Ri-HUB to the CMS
2. Find the recently created object in the list, visually or using search.
3. Check the statuses. The broadcast works correctly if the corresponding columns of the table show the statuses:
- Hub connection: Active, RiCoder is connected to Ri-HUB.
- CMS connection: green check mark (
), which means that events can be transmitted in the broadcast.
Broadcasting of events from the Ri-HUB control center located at the monitored object to the CMS of the security company is configured and works correctly.
4. Check whether events from RiCoder reach the CMS. If they do not, diagnose and fix the fault. Learn more ...
5. If the following statuses are displayed:
- Hub connection: Inactive, there is no connection to Ri-HUB. Learn more about fixing the fault ...
- CMS connection: red cross (
), there is no connection to the CMS. Learn more about fixing the fault ...
Last updated: 04/16/2026











No comments to display
No comments to display