| Device connection | Cable routes connect field devices | Radio links connect paired devices to the hub |
|---|---|---|
| Building work | May require new or existing alarm cabling | Can reduce new cable work at device locations |
| Expansion | Usually depends on available circuits and routes | Additional compatible devices can be planned around coverage and system capacity |
| Commissioning focus | Circuit integrity and device operation | Device operation plus final-position radio validation |
Neither architecture is automatically right for every property. Existing cabling, building materials, occupancy, modification limits and service requirements should determine the choice.
Separate the device link from the reporting path
A protected door contact sends its event to the hub over the local radio link. The hub then applies the configured alarm actions. Remote notification adds another path from the system to its recipient. A successful device-to-hub test therefore answers a different question from a successful remote-reporting test.
For example, if the hub receives the door event but the intended recipient does not, changing the door contact’s location does not address the demonstrated gap. The next check belongs to the configured reporting path and recipient. If the hub never receives the event, the local device connection needs attention first.
The intrusion alarm system guide explains the complete detection, control and response chain. For the local radio link and its validation, use the wireless alarm communication guide.
Where wireless architecture fits well
Wireless can be a strong project fit when:
• the building is already finished or occupied;
• drilling and new cable routes are restricted;
• protection must be expanded or changed over time;
• a retrofit needs new devices beyond the reach of usable existing wiring;
• the installation team can validate the final radio path and maintain the system.
Consider an apartment where the entrance, hallway and balcony door need protection but permanent cabling is not practical. Wireless devices may reduce disruption. The installer still has to consider dense walls, metal, the candidate hub position and each final device location.
Let the building change the architecture choice
Three representative situations show how the choice changes. They are planning examples, not claims about a particular Roombanker model’s wired or hybrid support.
| Site condition | What changes the decision | Practical next step |
|---|---|---|
| A finished apartment where new cable routes are restricted | Wireless can reduce building work, but the required detector positions still need usable radio links | Plan the entrance and interior protection points first, then validate the candidate hub position against those points |
| An office retrofit with existing alarm circuits and a new storage room | Usable existing wiring may be worth retaining; hybrid is an option only when the proposed equipment supports those circuits and the new devices | Have the existing circuits checked and compatibility confirmed before choosing between reuse and replacement |
| A workshop where required device locations cannot establish acceptable links in the proposed layout | Avoiding cable work no longer settles the choice: the system must communicate from the locations needed for protection | Reconsider the hub position or architecture; do not move a detector away from its required protection area solely to obtain a better link |
A new build with accessible cable routes may also favour wired architecture. Compare the actual building work and available connections before assuming wireless is the simpler installation. An open-space range number cannot settle any of these site decisions.
What to validate at the required device positions
Confirm the intrusion-system design first, then validate whether wireless architecture fits the required device positions, reporting model and commissioning process.
Keep the site checks focused on what the wireless connection changes:
| Check | How the result changes the next step |
|---|---|
| Can each required device communicate from its intended position? | A successful test supports that layout. An unacceptable link calls for a revised hub position or architecture while preserving the required detection coverage. |
| Has the proposed layout been checked in its final positions? | If only temporary positions were tested, validate the final arrangement before accepting the design. |
| Does the hub receive the event, and does the intended remote recipient receive it? | Test the two paths separately. If the hub receives the event, investigate the onward path rather than treating the result as a detector radio failure. |
| Can planned additions use compatible devices within the selected system’s capacity and coverage? | Confirm those conditions before promising expansion; the presence of a radio link alone does not establish compatibility or capacity. |
If the project has a compliance requirement, verify the exact system and component evidence rather than relying on the word “professional.” The EN 50131 Grade 2 system guide provides the next decision point.
If professional monitoring is required, define the receiver and service path with the ARC integration planning guide. When the design is ready for physical execution, move to the installation guide.
Choose wireless when it fits the required protection points and building conditions, then prove the radio links at the final installed positions and test remote reporting separately.