A wireless alarm system moves an event through a clear chain. A detector identifies the event and sends it over the RBF wireless link to its paired Hub. The Hub creates the local system state and carries out the configured local action. If the project also reports alarms to an alarm receiving centre (ARC), the event then enters a separate reporting path after the Hub.
For the installer, the practical sequence is to establish and validate the local Hub–device system, then document the external reporting path when the project uses one. This guide follows the event from detector to Hub and shows where to continue when the next question is installation, link diagnosis, or RF interference.
Follow the event from detector to Hub
The detector and Hub form the first communication layer. When the detector identifies an event, RBF carries that event across the local wireless link to the paired Hub. The Hub then turns it into the relevant local system state and configured action.
This local layer is the foundation for the rest of the alarm path. It tells the installer which device belongs to which Hub and where the event first enters the system. Pairing establishes that relationship; installation validation confirms that the completed link is ready for the project.
Following the event in order answers four practical questions: which detector created it, which Hub receives it, which local action is configured, and whether the event must continue to an external receiver. That sequence makes commissioning and later service conversations much clearer.
External reporting begins after this local step. The Hub event may continue through a separately configured reporting path when the project includes ARC monitoring. Continue to ARC integration planning for the external reporting handoff and receiving-centre layer.
See the communication chain in a small shop
Imagine a small retail shop after closing, with the alarm system armed. If the Door Window Sensor at the entrance detects an opening event, it sends that event over RBF to its paired Home Security Hub R2. In a separate example, the PIR Sensor in the sales area can detect a movement event and send its own event to the same paired Hub. These are two independent examples of the same communication path, not a required sequence between the sensors.
Triggered sensor → RBF → paired Hub → configured local action → optional separate reporting
When the Hub receives either event, it creates the corresponding local system state and carries out the configured local action. If the project is configured with an Indoor Siren, the Hub can command it to produce a local alarm. During installation, the installer uses the RB Link App to pair and configure the relevant devices; the event itself travels from the triggered sensor to the Hub over RBF. If the shop also uses ARC monitoring, the event enters that separate reporting path after the Hub.
Use the distance figure as a planning reference
Roombanker Hub–device communication in the 868/915 MHz bands can reach up to 3,500 metres in an open, unobstructed test environment. This describes the potential of the wireless link under defined conditions.
A real building adds materials, layout, device location, and the local radio environment, so the installed result still needs to be verified at the site. The wireless alarm site survey guide owns the detailed method for comparing Hub and device locations, testing before mounting, adjusting weak positions, and recording final-position results.
Pair the device to its intended Hub
Pairing creates the relationship between a device and the Hub that will receive its events. Hub-paired devices can complete the defined pairing flow within three seconds, and RB Link provides the relevant onboarding and configuration surface.
Pairing confirms system membership; it is followed by validation at the final installed location. Use the wireless alarm site survey guide for that installation and commissioning workflow.
Understand what RBF contributes to the system
RBF is Roombanker’s communication layer between the Hub and the devices paired through it. Its public radio description is FSK + FHSS. Within the system, it supports long-distance wireless communication, low-power device operation, and fast pairing.
Those capabilities support the local device-to-Hub stage of the alarm path. They help the installer build the Hub-paired system; after the Hub receives an event, any separately configured reporting path carries it onward.
RBF applies to devices paired through the Hub. Wi-Fi-direct devices use a different connection path. For the engineering background, continue to RBF wireless alarm technology. Sub-GHz versus 2.4 GHz covers the separate frequency-planning decision.
Wireless communication also connects to maintenance planning because event frequency and local link conditions can influence battery use over time. Continue to wireless alarm battery life and protocol design when battery planning becomes the next project decision.
Know which wireless problem you are dealing with
An installed link that appears weak or unstable is a communication-quality question. Use the signal stability versus signal range guide for that diagnosis.
An RF interference alert after the system is operating points to a different kind of problem. Use the RF jamming detection guide to understand that event.
Recognising the difference prevents site planning, an unstable installed link, and an RF interference alert from being treated as the same problem.
Complete the communication map before handover
Before handover, the communication system should be clear at a high level:
• each Hub-paired device is mapped to its intended Hub;
• final-position validation has been completed through the site survey and commissioning workflow;
• every unresolved exception has a defined next action;
• any reporting beyond the local system is recorded as a separate path.
With this record, the next installer or service technician can see how an event reaches the Hub, whether final validation was completed, which exception still needs attention, and where the reporting layer begins.
Reliable wireless alarm communication is therefore more than a distance figure or a protocol name. It is a system in which the detector, RBF link, paired Hub, local action, installation validation, and separate reporting path each have a clear role.