Wired alarm device compatibility is a pre-sales assessment question, not a product-category shortcut. For installers deciding whether to connect wired alarm devices to a wireless system, a wired detector, panic button or keypad input may be worth evaluating, but the device name alone does not establish compatibility.
The useful decision is made at the actual alarm point: what contact changes, what powers the device, what event should be reported, where the wiring can be accessed, and whether the proposed Transmitter position has an acceptable wireless signal. This guide provides a repeatable assessment method for one selected third-party wired point at a time. For the wider keep, replace or add decision, see the wired alarm retrofit planning guide; this page focuses on compatibility evidence at the selected point.
How to assess wired alarm device compatibility
Roombanker documentation describes the Transmitter as a module for integrating third-party wired devices with NC/NO contact types into the Roombanker system. It identifies separate `ALARM` inputs for a wired device and `TAMP` inputs for a wired-device tamper connection. The specification also describes a 3.3 V / 30 mA power output and a programmable open-collector output that requires an external pull-up resistor.
That gives an installer a useful first screen, but it does not turn NC/NO into a universal compatibility promise. Two devices may both use normally closed contacts while differing in power, supervision, tamper wiring, event timing, cable condition or required output behavior.
Use this sequence:
1. Identify the device role and the event the customer needs.
2. Record the alarm and tamper contact states separately.
3. Check the device power requirement against the proposed connection.
4. Inspect the cable route, joints and accessible termination point.
5. Test the wired event at the Transmitter.
6. Test wireless signal at the proposed Transmitter position.
7. Record a final PASS, NEEDS TEST or NOT SUITABLE decision.
The Transmitter specification should be read with the Transmitter Quick Start Guide. The two documents answer different questions: the specification defines terminals and boundaries, while the guide describes enrollment and signal-strength testing.
Device roles that can enter the assessment
The following are assessment categories, not a list of guaranteed compatible brands or models.
Wired detector
A wired detector can enter the assessment when its protected area remains useful, the alarm contact is accessible, and the installer can reproduce the event at the connection point. Record whether the intended event is intrusion, fire or another configured event. Do not infer the event from the word “detector” alone.
If the customer needs a new movement zone rather than retention of the existing device, consider a separate Roombanker PIR Motion Sensor. That is a different design decision from evaluating the existing wired point.
Door or opening contact
A wired opening contact may be worth assessing when the door is correctly protected and disturbing the finished frame would be undesirable. Record the normal contact state, the alarm transition, the tamper arrangement and the exact door or opening represented by the point.
A new wireless opening point can be planned separately with the Roombanker Door/Window Magnetic Sensor. The presence of that product does not prove that an existing third-party contact will pass the Transmitter assessment.
Wired panic button
A panic point is closely tied to staff behavior and response procedures. Record who operates it, what event the customer expects, and how the alarm state will be acknowledged during testing. A panic input should not be treated as an ordinary detector simply because both use contacts.
The Roombanker Panic Button is a separate wireless product role. It is not a compatibility reference for every third-party panic device.
Keypad input or contact point
Some projects expose a keypad input or another contact point from an existing alarm installation. Before assessment, isolate the exact signal being bridged and confirm that it is an NC/NO contact event within the intended design. A keypad’s user interface, power, data bus and contact output are not interchangeable assumptions.
Where a new control point is required, the Roombanker Alarm Keypad should be evaluated as a separate system device.
Tamper loop and other contact-type points
The tamper connection needs its own record. A device can show a correct alarm transition while its tamper loop remains open, reversed or untested. Record `ALARM` and `TAMP` as separate lines in the handover sheet.
The specification lists event categories such as intrusion, fire, auxiliary alarm, panic, gas, leakage, glass break, temperature, masking, duress, vibration and custom events. These categories help define the intended system event; they do not replace checking the physical interface and the configured behavior. Mapping an event category does not represent fire or life-safety certification, regulatory approval, or acceptance by a monitoring center. Confirm those requirements with the relevant local authority, insurer and monitoring provider. For projects governed by an intrusion or hold-up alarm standard, the IEC TS 62642-7 application-guideline reference is a useful reminder that design, installation, commissioning and maintenance requirements remain project-specific.
Compatibility assessment matrix
Use the table below for the selected point. Every row must end with a decision, not only a measurement.
| Check | What to record on site | PASS | NEEDS TEST | NOT SUITABLE |
|---|---|---|---|---|
| Device role | Protected asset/area and intended event | Role and event are clear | Customer must confirm event meaning | No defined security role |
| Alarm contact | NC or NO at normal state and alarm state | State is identified and repeatable | State changes but wiring is unclear | No supported contact event |
| Tamper contact | NC/NO, loop behavior and enclosure condition | TAMP can be tested separately | Tamper route or state needs tracing | Tamper requirement cannot be represented |
| Power | Voltage/current requirement and source | Within the documented connection plan | Datasheet or measurement still needed | Power demand or source is unsuitable |
| ALARM terminals | Conductors, polarity where relevant and termination | Correct conductors identified | Existing panel logic needs isolation | No safe accessible connection |
| PO boundary | Whether an output is actually required | No output, or external pull-up design is documented | Output behavior needs technical review | Required output cannot be implemented safely |
| Cable | Route, joints, condition and approximate length | Cable is accessible and serviceable | Hidden route or joints need tracing | Damaged or inaccessible route prevents testing |
| Event type | Intrusion, fire, panic or other intended type | Event maps to the documented event mapping | Customer or monitoring path needs confirmation | Required event is unsupported or misleading |
| Transmitter position | Access for installation and maintenance | Wired connection is practical | Position needs a second survey | No safe or serviceable position |
| Wireless signal | Result from the signal-strength test at the proposed position | Test result is acceptable | Move and retest before decision | Signal result is unacceptable at viable positions |
| Field event test | Trigger, restore and repeat the selected wired event | Event is received and restored as expected | Repeat after wiring/configuration review | Event is missing, unstable or misleading |
| Handover | Final state, test result and maintenance note | Installer and customer records agree | Documentation is incomplete | Customer cannot be told what is monitored |
The matrix deliberately separates the wired interface from the wireless route. A point can pass the contact and power checks but still need a different Transmitter position. Conversely, a strong wireless signal cannot compensate for an unidentified alarm or tamper circuit.
Installer worksheet
Copy this worksheet into the site record for each selected point.
Point identity
• Site/room:
• Device label and role:
• Protected opening, area or staff action:
• Existing panel/termination location:
Wired interface test
• Alarm normal state: `NC / NO / unclear`
• Alarm triggered state: `NC / NO / unclear`
• Tamper normal state: `NC / NO / disabled / unclear`
• Power source and measured requirement:
• Proposed `ALARM` terminals:
• Proposed `TAMP` terminals:
• `PO` required: `yes / no / needs review`
• Bistable or pulse behavior required:
• Wired test result: `PASS / NEEDS TEST / NOT SUITABLE`
• Test evidence or technician initials:
Wireless position test
• Proposed Transmitter position:
• Access and serviceability:
• Signal-strength test result:
• Alternate position tested:
• Wireless test result: `PASS / NEEDS TEST / NOT SUITABLE`
Decision and handover
• Final decision: `PASS / NEEDS TEST / NOT SUITABLE`
• Event shown in the system:
• Field event test: trigger / restore / repeat result:
• Customer explanation:
• Follow-up owner and date:
This record prevents a common sales mistake: turning “the terminals look similar” into “the device is compatible.” The final decision should be based on the installed point and the two separate tests.
Power, cable and output boundaries
The Transmitter specification lists a 3.3 V / 30 mA power output. Treat that as a product boundary to compare with the selected device, not as a universal power supply for every wired alarm device. If the device needs another supply arrangement, stop and record the condition rather than improvising a connection.
The specification also lists cable length up to 130 m. This is a reference limit, not a guarantee for every building or route. Cable condition, joints, interference, access and serviceability still need to be checked on site.
If the project requires a programmable output, the specification describes `PO+` and `PO-` as open-collector output terminals requiring an external pull-up resistor. This is a design boundary for a qualified installer, not a reason to assume that any existing panel output can be copied without review.
What should happen after the assessment?
If the selected point is `PASS`, document the tested contact state, power arrangement, event type, field event result and wireless position before quoting the project. Use the Roombanker Transmitter product page for product evaluation and sample discussion.
If the point is `NEEDS TEST`, keep the opportunity open but identify the missing evidence: a wiring trace, a power measurement, a customer event decision or a second wireless position test. Do not present it as compatible until the missing test is complete.
If the point is `NOT SUITABLE`, choose a different design for that role. A separate wireless product may be appropriate where its role matches the site requirement, such as a Roombanker Alarm Siren for an audible-warning role or another device in the Home Alarm System range. That is a new role decision, not proof that the legacy point can be bridged.
For the wider system context, see the Wireless Security Alarm System Solution and RBF wireless alarm technology. For project discussion, use Partner, Where to Buy or Support according to the inquiry route.
Final rule for installers
Do not answer compatibility from the device label, contact type or a product photo alone. Assess the role, alarm contact, tamper, power, `ALARM`, `TAMP`, `PO`, cable, event type, Transmitter position and wireless signal as separate decisions. Only then should the selected point be marked `PASS`.
This approach gives distributors a clearer pre-sales conversation and gives installers a worksheet that can survive handover. It also keeps the Roombanker promise precise: evaluate a selected third-party wired alarm point against the documented interface and the real site conditions.