Frequently Asked Questions

4G (LTE) is faster and more future-proof, since 2G networks are being phased out. For new installations, 4G is recommended; 2G is cheaper and can be an advantage where 4G coverage is weak. Many models (FLEXi SP3, G16, CG17, G17F) are available in both versions.

Traditionally via telephone line (TIP/RING) — a universal solution that lets devices communicate regardless of brand. Trikdis's own development means that panels on the supported list (and only those) can also be connected directly and digitally via serial port or data cable — as far as we know, no one else offers this, backed by 10-15 years of development.

Protegus 2 is the 2nd generation of Trikdis's cloud app: control your alarm system from your phone and get instant notifications. We recommend it for every current internet-connected Trikdis device. The user app is free; the paid, usage- (customer-) based tier is for monitoring stations, installers and companies.

Check the product page of any direct-connection communicator — e.g. E16, G16, GT, GT+, GET: if your panel's model is on the supported list, we strongly recommend that one. In every other case, choose the telephone-line (TIP/RING) version. Pick the communication type (4G / Ethernet) based on what's available on site.

Yes: the E16/E16T and FLEXi SP3 are purely Ethernet, but there are also SIM-combined, dual-path (redundant) versions — e.g. the GET and the matching FLEXi SP3 variant. Ethernet is a stable, unlimited-data channel for alarm signalling.

Two parallel communication channels (e.g. Ethernet + 4G): if one drops, the other automatically takes over signalling. This gives the highest reliability, which standards may even require (a higher Grade rating). The GET and FLEXi SP3 work this way. An add-on module also exists for existing communicators, in WiFi (W485) and Ethernet (E485) versions.

The radio communicator (T16U UHF / T16V VHF) signals on its own radio frequency to a dedicated receiver station — ideal where there's no reliable mobile network or internet. GSM/IP communicators signal over the mobile network or internet to a monitoring station or to Protegus.

Yes, using the TrikdisConfig programming software (via USB or remotely). The latest firmware is recommended for the best compatibility and security.

With the GV17 GATOR you can open and close a motorised gate, garage door, barrier, or magnetic-lock garden gate from the free Protegus 2 app — with up to 1000 users and revocable permissions — or with a traditional phone call.

Yes. With the GV17's call-based control, it identifies and opens based on the caller's number without answering the call — so the call is free. You can set it so only numbers on the list can open it, or anyone who knows the number; you can also block numbers with a blacklist.

Yes. GV17 events are logged, so it can also be used as a simple access control system; for wireless access control, the GATOR RF-LoRa accessory provides a flexible solution. Time tracking is a separate feature with different functionality — our knowledge base provides detailed guidance.

With the G17F fire communicator, any fire alarm unit or panel can be extended with mobile-network event transmission: when a fire alarm triggers, the event is forwarded to the configured destinations — for example, the fire brigade or a monitoring station — and the owner is also notified in the Protegus 2 app. It handles two parallel communication channels, each with its own backup channel.

Where the fire alarm system requires standard-compliant, certified signalling, an EN54-certified device is needed: such as the Trikdis FireCom, which communicates over Ethernet and/or two-SIM 4G mobile network, and meets the strictest European fire safety requirements.

You can choose from three keypads: SK-LED Button (LED display + physical buttons, entry level), SK-LCD Button (LCD display + physical buttons), and FLEXi LCD (touch, blue LCD, full menu, 8 partitions). The FLEXi LED touch-button keypad is being discontinued and is only available in limited (single-unit) stock.

The LED keypad provides basic functions (arming, fault indication, zone bypass, alarm memory) with light signals and physical buttons — simple, affordable, and typically able to display up to 2 partitions. The LCD keypad shows system status, zones, faults, even temperature and multiple partitions on a text display — more convenient for daily use and overview.

Yes: Protegus 2 can be tried on a live demo system, without installation or purchase — from a browser and from the mobile app too. This lets you see in advance what arming, notifications, and system status look like on a working alarm system.

There is no standalone Trikdis communicator that communicates exclusively over Wi-Fi, but the SIM-card communicators can be extended with the W485 Wi-Fi expansion module. There is also a purely Wi-Fi version, as well as a Wi-Fi + SIM 4G version, of the FLEXi SP3 alarm panel.

Currently the FLEXi SP3, the CG17, and the GV17 support SMS forwarding; this feature is not yet available on the other devices.

Protegus 2 typically retains the event list for up to two months; with a large volume of events, this period may shorten to as little as one month.

The AUX power output of the Paradox SP4000 alarm panel has limited load capacity. In certain cases — whether using a dedicated or a universal TRIKDIS communicator — the communicator's current draw can place too much load on the AUX output. As a result, the communicator may become unstable, restart, or fail to operate correctly.

Experience shows that the problem is usually solved by powering the TRIKDIS communicator directly from the alarm panel's battery terminals (+/-) instead of from the AUX output. This provides a stable power supply and eliminates the restart or operational issues.

Note: Before changing the wiring, always check that the system complies with the manufacturer's specifications and that the total load on the power supply does not exceed the permitted value.

The Trikdis communicator reads the codes from the panel at start-up, so it only knows the codes that existed at that moment. If codes are changed in the Paradox panel, the Trikdis device must be restarted — for example by disconnecting and reconnecting its terminal block.

After restarting, the device reads the current codes and the new code works in the app as well.

Not for Paradox devices: Paradox's own tools, e.g. Babyware, IP150, IP180, work with a locked serial port as well. Unlocking the serial port is only needed when connecting a third-party device — such as a Trikdis communicator.

Yes. On the DSC data bus the Trikdis device plays a mostly passive, listening role. If many other devices communicate on the bus — typically keypads and expander modules — the Trikdis device may not “get a word in”: it may fail to read system data and may be unable to send control commands (such as partition arming).

The issue does not occur in every installation, but above 3–4 keypads or expander modules the likelihood increases — worth considering during the site survey.

For such cases we recommend the universal version that connects to the phone-line (TIP/RING) input: the E16T or the G16T. On the GT, GT+ and GET the connection mode can be switched inside the device, so where possible we recommend these for such installations.

For decades, alarm panels reported events to the monitoring station over the fixed telephone network: the telephone dialler built into the panel “made calls” in a standard format — typically Contact ID (CID). It became such a universal standard that the TIP/RING connection is still present in almost every panel from every manufacturer, including the newest ones.

The fixed telephone line is disappearing, but the connector has found a new life: a modern communicator (such as the Trikdis E16T or G16T), wired to the TIP/RING terminals, “presents” a telephone line to the panel — providing line voltage and a dial tone. The panel believes it is calling the monitoring station; in reality the communicator answers the call, decodes the Contact ID message and forwards the event over the internet or the mobile network to the monitoring station and the Protegus 2 app.

The great advantage of this solution is brand independence: it works with practically any panel — even decades old — that has a telephone dialler, with no direct bus or serial integration. That is why we call this type of device a universal communicator.

A regularly recurring problem: during installation you want to create the system in Protegus 2, but you get the message that the device is offline. In that case it is best to rule out the SIM card and the data connection first — it takes a few minutes with a phone.

Checking the SIM card with a phone

1. Remove the SIM card from the device and insert it into a phone.
2. Turn off every other source of internet connection so that the SIM card in question can be tested undisturbed: Wi-Fi, on a dual-SIM phone the other SIM card as well, or anything else — this way the traffic certainly goes through the card being examined.
3. Turn on mobile data.
4. Open a website in the browser, for example a news site, and open an article inside it too. If the article loads as well, the data connection on the card works. (A home page you opened earlier may come from the phone's cache — that is why an article must also be opened.)
   If there is no internet connection, find out why: an incorrect or missing APN setting, no subscription on the card, an exhausted or expired data allowance, etc. Once that is sorted out and the connection really works, continue with step 5.
5. In the phone's settings check which APN belongs to this SIM card and write it down.
6. Recommendation: turn off the PIN code request on the SIM card. A PIN code can of course be used and it does add security, but in devices like these we generally do not recommend it, and it is not needed for operation.

Back into the device

7. Take the SIM card out of the phone and put it back into the Trikdis device.
8. Using TrikdisConfig, enter the device's programming and set the APN you wrote down in the APN setting.
9. Write the changes to the device, then check whether the data connection is restored — that is, whether the device is online in Protegus 2.

If it works in the phone but not in the device

The problem is almost certainly the PIN code or the APN. If the device sees the network but no connection to the server is established, check the APN first — an empty or mistyped APN is the typical symptom.

If the device picks up several networks and switches between them, it is worth setting a preferred operator. See: Setting a preferred operator – MCC and MNC codes (Europe).

The symptom: the Ethernet-connected device — E16, E16T, GET or FLEXi SP3 — is on the network and gets an IP address, yet no connection is established towards Protegus 2 or the monitoring station.

Why: in most such cases the device is not at fault; the local network simply will not let it out. On company and institutional networks this is caused by a firewall rule, a content filter, a proxy, MAC filtering or a strict VLAN policy. In our experience this happens almost exclusively on closed corporate networks — but there we have run into it several times already.

The recommended solution: put the communicator on a separate, isolated network or VLAN with no access to the internal LAN. This solves two things at once:

• the internal network's rules do not interfere with the communicator's outgoing traffic;
• it is also the right arrangement from a security point of view: the alarm device cannot see the internal machines, and a possible infection of the internal network cannot reach the communicator.

What the device needs:

• outgoing internet access, without filtering;
• DHCP, or with a fixed IP address the correct gateway and DNS;
• no inbound port forwarding is required — the communicator establishes the connection outwards itself.

If a separate VLAN is not possible: on the firewall, exclude the device's IP address from content filtering and from the proxy, and allow its outgoing traffic without restrictions.

And keep in mind: a communicator has two separate connections — one towards the alarm panel (bus or TIP/RING) and one outwards (Ethernet or SIM). This fault affects the outward side; communication with the panel may well be working.

The RF-LORA firmware can be updated in two ways, depending on which firmware is currently on the device.

With old firmware (USB drive method)

1. Download the latest firmware from the Downloads tab on the RF-LORA product page, then rename the file to rf-lora.fw.
2. Remove the device cover so that the USB connector is accessible.
3. Press and hold the button on top of the device and, while still holding it, connect the device to the computer with a USB cable.
4. A new drive appears on the computer. On that drive there is a file with the same name as the renamed firmware file: rf-lora.fw.
5. Delete the old rf-lora.fw file from the drive, then copy the new, latest firmware file onto the drive.

With newer firmware (TrikdisConfig)

1. Remove the device cover so that the USB connector is accessible, then connect the device to the computer with a USB cable.
2. Start the TrikdisConfig programming software and follow the firmware update steps.
3. Select the latest firmware file with the Browse button, then start the update with the Upload button.