RBF Tegnologie

Wireless alarm technology built for the people who install it.

RBF is Roombanker's proprietary Sub-1G wireless technology for selected alarm and automation devices. It is designed to support long-range, low-power wireless communication across walls and floors under suitable installation conditions. For distributors, installers, and OEM/ODM partners who need a differentiated wireless alarm product line, RBF turns radio technology into a clearer portfolio story, simpler site planning, and a stronger reason to contact Roombanker. Outcomes depend on device model, usage, configuration, and site environment.

One Hub
Designed for Broad Coverage
Fewer Repeaters
Under Suitable Conditions
Lang lewe
Model & Usage Dependent
RBF-protokol RBF-skyfie RBF-module
Roombanker RBF technology products for wireless alarm communication
Sub-1GLess crowded than many 2.4 GHz contexts
TDMA + FHSSHelps manage channels
AES-CCMUsed where specified
Wat dit vir jou beteken

If you install wireless alarm systems, here is what RBF changes.

You know the pain points: extra repeaters that add cost and complexity, batteries that require maintenance, and crowded 2.4 GHz environments that can complicate wireless planning. RBF is designed to reduce these problems in suitable installations and connect technical evaluation to the right Roombanker pad: Vennoot Hub, Wireless Alarm System Solutions, and RBF product-system planning.

RBF wireless signal coverage planning for a residential installation

Designed for broad coverage from a central hub.

RBF uses Sub-1G wireless communication rather than the crowded 2.4 GHz band used by WiFi and Bluetooth. Lower frequencies can support better wall and floor penetration in many residential and light-commercial environments. In suitable layouts, installers may reduce or avoid repeater placement, but final coverage always depends on building materials, device placement, and local signal conditions.

RBF sensor battery planning depends on model, usage, and installation conditions

Fewer battery-change visits. More predictable margins.

Selected RBF sensors are designed for long battery life by waking at scheduled moments rather than communicating continuously. Actual battery duration depends on device model, battery type, usage frequency, signal quality, temperature, and installation conditions. For your business, that makes battery planning more predictable when the right device is matched to the right site.

RBF closed system — single manufacturer, clear responsibility

Closed system. Clear responsibility.

RBF works exclusively with Roombanker devices. This is not a limitation — it is a design choice. When every component in the system comes from one manufacturer, there is one support number, one warranty policy, and one team to call when something goes wrong. You never argue with three vendors about whose device is causing the problem.

Hoe werk dit?

Three design decisions that make RBF different.

Every wireless protocol makes trade-offs. RBF chose three things to be excellent at — and they happen to be the three things installers care about most.

Sub-1G frequency comparison for wireless alarm planning

It uses a frequency that travels further.

RBF operates in Sub-1G frequency bands used for selected regional product variants, rather than the 2.4 GHz band shared by WiFi routers, Bluetooth speakers, and many consumer devices. In suitable contexts, Sub-1G bands can be less crowded than many 2.4 GHz environments and can support stronger penetration characteristics in many building layouts.

Designed to support more reliable wall and floor penetration than many 2.4 GHz approaches under suitable site conditions. Actual performance depends on construction materials, placement, and local regulations.
TDMA scheduling concept for supported RBF device communication

Devices talk on a schedule, not all at once.

RBF uses TDMA (Time Division Multiple Access) in supported configurations so devices can communicate according to scheduled timing. Think of it like a meeting where everyone speaks one at a time, rather than a room where everyone shouts at once. This is designed to reduce collisions and support lower power operation.

The scheduling approach helps multiple devices share the system more predictably. Alarm handling, priority behavior, and supported device count should follow the specific product and system configuration.
AES-CCM encryption — every transmission encrypted end-to-end with FHSS across 50 channels

Security is built into the signal, not bolted on.

RBF product documentation references AES-CCM encryption and FHSS channel hopping for supported devices and configurations. These mechanisms are designed to improve communication security and resilience compared with fixed-channel or unencrypted approaches, but no wireless system can claim absolute immunity from interference or attack.

Use EN 18031-1 / CE / RED language only for products and configurations with supporting evidence. For commercial projects, confirm the exact model, region, firmware, and certificate scope before making a compliance claim.
Onder die enjinkap

RBF is three layers working together. Here is what each one does for your business.

You do not need to be an engineer to understand why these matter. Think of them as: the rules of the road, the engine, and the assembly kit.

laag
Dink daaraan as
Wat dit vir jou besigheid doen
Key capability
RBF-protokol
The rules of the road
Defines how supported devices communicate, including timing, channel behavior, and security-related mechanisms. For installers, it is designed to help prioritize alarm communication, reduce device contention, and support more predictable multi-device behavior in supported configurations. Explore the RBF Protocol target page.
TDMA scheduling · FHSS channel hopping where specified · AES-CCM where specified · Listen-Before-Talk where supported · selected direct hub communication models where supported by the system configuration
RBF-skyfie
Die enjin
Roombanker-controlled chip options can combine processing, memory, radio, and power-management functions for compatible RBF devices. OEM and distributor discussions should confirm the exact chip variant, package, operating range, and documentation scope before using detailed specifications. Explore the RBF Chip target page.
Example specification fields may include processor class, memory, package, operating range, and regional variants; confirm exact values from the current product documentation before publication.
RBF-module
The assembly kit
A documented integration path for compatible RBF modules. It can reduce RF design, compliance, and antenna-matching workload when the module scope, reference design, and regional documentation apply. Explore compatible product systems.
Designed to support CE/RED-oriented integration paths where documentation and module scope apply · OEM/ODM integration support · reduced RF design workload for compatible products
How RBF Compares

You already know Z-Wave and Zigbee. Here is how RBF is different.

We are not saying RBF is "better." We are saying it made different design choices — and those choices happen to align with what security installers need most.

Waaroor jy omgee
Typical Z-Wave / Zigbee
RBF
Repeaters in a standard home
Often used to extend coverage
Lower repeater dependency where model, site, and configuration support it*
Signal through walls & floors
Often planned around shorter hops
Central-hub planning where site layout and device placement support it*
Sensor battery vervanging
Depends on device and usage
Long-life design, model and usage dependent*
Frekwensie band
2.4 GHz — shared with WiFi
Sub-1G bands, less crowded than many 2.4 GHz environments in suitable contexts
Toestelversoenbaarheid
Multiple brands can mix
Roombanker devices only
Who you call for support
Multiple manufacturers
Een maatskappy
EU cybersecurity standard
Wissel volgens handelsmerk
Certificate-scope dependent

* Depends on product model, firmware, site layout, installation conditions, and documented certificate scope.

Wat dit beteken op die terrein

You are not comparing data sheets — you are comparing what happens when you arrive at a customer's property with a van full of equipment.

Less hardware to buy and install
Reducing repeater dependency can mean fewer components to purchase, unpack, mount, pair, and test. In suitable installations, this can reduce both hardware cost and the labor needed to plan signal extension.
Fewer service calls for dead batteries
When selected sensors are matched to the right site and usage pattern, longer battery intervals can reduce battery-related service visits. Actual maintenance timing should be planned by model, battery type, usage, signal quality, and environment.
Simpler troubleshooting
Selected RBF system configurations are designed around direct hub communication with supported devices, which can make the signal path easier to understand than multi-hop routing. Site layout, device placement, supported device family, and configuration still determine the final planning model.
Enkele aanspreeklikheid
When a system uses devices from one manufacturer, there is one warranty process, one support queue, and one technical team that knows how the whole system works together. No finger-pointing between suppliers.
How RBF Helps You Win

Different roles. Different conversations. One technology story.

RBF is not a spec sheet to hand to customers. It is a technology story, an installation-planning advantage, and a differentiator when claims are tied to the right site conditions and product evidence. Here is how each role uses it.

Security distributor evaluating product portfolio in warehouse

Sekuriteitsverspreiders

RBF gives your installer customers a reason to choose your portfolio. In suitable residential and light-commercial layouts, central-hub planning can reduce repeater dependency, shifting the margin story from device price alone to total installation cost.

Installer measuring and placing a sensor in a residential hallway

Installasie maatskappye

Less hardware where the site allows it, fewer labor hours where repeater planning can be reduced, and longer battery intervals for selected devices under suitable conditions. These are practical details installers can explain when a customer compares quotes.

Project integrator planning multi-site system deployment with floor plans

Project integrators

In multi-story buildings, retrofits, and concrete-heavy sites, Sub-1G planning can be a useful differentiator. The right claim is not guaranteed coverage; it is a site-aware design approach that may reduce complexity when building conditions support it.

OEM engineer evaluating RBF module on test bench

OEM / ODM vennote

RBF SiP chip and module options can support a deeper technology story for OEM/ODM discussions. Use module, certification, and integration claims only within documented model and region scope, especially when discussing CE/RED or cybersecurity requirements.

Taalgids

Claim boundaries for public use.

The page should sound technical and confident, but must avoid absolute guarantees.

Use this language

RBF technology is designed to support long-range, low-power wireless communication for Roombanker alarm and automation devices under suitable installation conditions.

Avoid this language

Guaranteed coverage, zero interference, works in every building, absolute anti-jamming, best, No. 1, market leader.

Always explain dependencies

Wireless performance can depend on site layout, walls, floors, device placement, signal environment, model, and configuration.

Algemene vrae

What installers and partners ask about RBF.

Not always. RBF is designed to reduce repeater dependency in suitable residential and light-commercial layouts by using Sub-1G communication that can support stronger wall and floor penetration than many 2.4 GHz approaches. That does not mean every building can be covered from one hub. Large properties, multi-building sites, unusual floor plans, dense concrete, metal structures, and local interference may still require a site survey and adjusted device placement.

The main differences that affect your daily work: (1) RBF is designed around central-hub planning and may reduce repeater dependency in suitable layouts; (2) selected RBF sensors are designed for long battery life, with actual duration depending on model, usage, and conditions; (3) RBF uses Sub-1G communication, which can avoid some congestion associated with 2.4 GHz environments; (4) RBF is a closed ecosystem, so devices work with Roombanker hubs and support accountability stays with one vendor. Z-Wave's strength is multi-brand compatibility; RBF's strength is controlled system design and single-vendor support.

Supported RBF devices and configurations may use Frequency-Hopping Spread Spectrum (FHSS) and AES-CCM encryption as part of the communication design. These mechanisms are intended to improve resilience and data protection compared with fixed-frequency or unencrypted approaches. No wireless system can claim absolute immunity to jamming, interception, or interference, and specific security or compliance claims should be confirmed against the exact product, firmware, region, and certificate scope.

No — RBF is a proprietary Roombanker protocol. RBF devices work exclusively with Roombanker hubs. This is an intentional design choice: when every component comes from one manufacturer, the system is tested as a whole, support accountability is clear, and firmware updates are coordinated across the entire device fleet. If you need multi-brand flexibility, this is a trade-off to evaluate. If you value predictable performance and single-vendor support, it is an advantage.

EN 18031-1 is a European cybersecurity standard for radio equipment. If a specific Roombanker model, firmware version, and regional configuration is documented as compliant, that evidence can support project, tender, or distributor discussions. Do not generalize EN 18031-1, CE, or RED claims across all RBF devices unless the certificate scope supports it.

The installation workflow is designed to be familiar. Because RBF uses central-hub planning rather than multi-hop mesh routing, suitable installations may involve fewer repeater-placement decisions and less route troubleshooting. The pairing process should be evaluated by product family and firmware version. The main adjustment is conceptual: you plan coverage from a central point, then verify coverage based on the actual site.

Yes. RBF is most useful when distributors can explain both the technology and the installation value in simple terms. Roombanker can support partner discussions around product positioning, installer training, portfolio planning, and sales materials. The recommended next step is to start from the Vennoot Hub or submit a partner inquiry with your target market, product categories, and channel model.

OEM/ODM discussions should start with the target product family, region, certification requirements, firmware scope, and whether the project needs finished devices, module-level integration, or a broader wireless alarm product system. RBF module, chip, and protocol claims should be confirmed against the exact documentation and certificate scope before publication or tender use.

Start with the building type, wall and floor materials, expected hub location, sensor count, and local signal environment. RBF is designed to support broad coverage and lower repeater dependency in suitable residential and light-commercial layouts, but dense concrete, metal structures, unusual floor plans, and multi-building sites should be checked with site planning and signal verification.

Use RBF as a technology authority page, not a datasheet.

Connect this page to Vennootprogram, RBF-skyfie, RBF-protokol, Wireless Alarm System Solutions, and installation-focused support content.

Scroll na bo
Kontak Ons

    Hierdie webwerf is beskerm deur reCAPTCHA en die Google Privaatheidsbeleid en Algemene Diens toe te pas.