An alarm that false-alarms three times in the first week erodes trust faster than any technical fault. By the fourth event, the customer has stopped arming the system, and the installer is making a return visit—unpaid. Most post-installation service calls share the same root causes: signal planning missed during the site survey, sensors placed where they should not be, or configuration defaults that do not match site conditions.
This guide covers the seven most common wireless alarm installation problems we see across residential and small commercial sites in EMEA. Each problem includes root cause diagnosis, a step-by-step solution, and a prevention measure so the issue does not recur on the next job. The guidance is built around Roombanker’s RBF Protocol ecosystem, but the diagnostic method applies to any wireless alarm system.
Before You Start: Diagnostic Tools in the RB Link App
All Roombanker RBF devices report diagnostic data through the RB Link mobile app. Before making any hardware changes, collect these readings from every affected device:
- RSSI value — Device Settings > Signal Test. Take three readings over 30 seconds with the building in its normal occupied state. Record the lowest value.
- Battery voltage — Device Settings > Device Info. Reported as percentage and millivolt reading.
- Firmware version — Device Settings > Device Info. Compare against the latest version listed in RB Link.
- LED status pattern — Visual inspection of the device LED. Each pattern maps to a specific condition (see LED reference table below).
Document these four values for every problematic device before proceeding. In internal testing across 200+ RBF device installations (Roombanker field engineering lab, 2024 Q3–Q4), 78% of reported issues were resolved without hardware replacement when the installer had collected these four diagnostics first.
Problem 1: Weak or Marginal RSSI Signal
Symptom
Intermittent “Sensor Lost” notifications in RB Link, missed alarm events, or delayed sensor response. The device shows RSSI below −85 dBm in the Signal Test screen.
Root Cause
The RF path between the sensor and the hub is attenuated by building materials (reinforced concrete, metal framing, insulated glass), the device is too far from the hub, or the hub antenna is obstructed by a metal enclosure.
Step-by-Step Solution
- Open RB Link, navigate to Device Settings > Signal Test for the reporting device. Take three readings over 30 seconds. Record the lowest.
- If RSSI is between −76 and −85 dBm (Fair): move the device 1–2 metres in any direction and retest. A shift of even 50 cm can improve RSSI by 3–6 dB when moving away from a reinforcing bar or duct.
- If RSSI is −86 dBm or lower (Poor/Dead): reposition the hub at a more central location, at least 30 cm above floor level, antenna oriented vertically and not inside a metal cabinet. Re-run the signal test.
- If repositioning the hub is not possible, install an RBF Repeater between the hub and the affected device. Place the repeater roughly halfway, within line of sight to both the hub and the device.
- Re-test after every change. A single improvement of 10 dB or more confirms the root cause.
Prevention
Conduct a full site survey before mounting any equipment. The Roombanker Site Survey Guide documents a repeatable walkthrough methodology that covers hub placement rules, building material attenuation data, and coverage mapping. Installers who followed that methodology across 45 trial sites in Germany and Poland (2025 Q2) logged zero signal-related return visits within the first six months.
Problem 2: False Alarms from PIR Sensors
Symptom
Motion alarm events logged in RB Link with no corresponding intrusion. Often time-correlated with HVAC cycles or sunrise/sunset.
Root Cause
In Roombanker internal analysis of 217 field service tickets from Q3 2024 through Q2 2025, 43% of false alarm calls traced to PIR placement within 1.5 metres of an HVAC outlet, a sun-exposed window, or a heat radiator. The remaining common cause was pet movement at sensor heights below the recommended 2.1 metres.
Step-by-Step Solution
- In RB Link, review the Event Log for the false alarm timestamps. Correlate with known HVAC schedules or sun position.
- Verify the sensor is mounted at the correct height: 2.1 metres for the Roombanker PIR Motion Sensor (Indoor), 0.8–1.2 metres for pet-immune coverage.
- Check the sensor’s field of view. If it faces an HVAC vent, window, or radiator, relocate the sensor or install a directional mask.
- Adjust PIR sensitivity in RB Link: Device Settings > Sensor Configuration > Sensitivity. Reduce by one step, then monitor for 48 hours.
- Test with the environment normalised — close windows, turn off HVAC, wait 10 minutes for the air temperature to stabilise — then trigger a walk test.
Prevention
Include HVAC, window, and heat-source mapping in the site survey. Mark PIR placement no closer than 2 metres from any forced-air outlet or direct sunlight path. For sites with pets, select pet-immune PIR models and verify coverage height during commissioning.
Problem 3: Unexpected Battery Drain
Symptom
“Low Battery” notifications appearing within months of installation. Battery reported below 20% in RB Link when the device should have 3–5 years of service life.
Root Cause
The three most common causes are: (1) supervision polling interval set shorter than the default 15 minutes, (2) the device installed in a location where ambient temperature regularly falls below −10 °C or exceeds 50 °C, or (3) outdated firmware causing excessive radio wake-ups. A less common cause is a device placed in a high-traffic zone (e.g., a door/window sensor on a frequently used door) where the transmission count far exceeds the design average.
Step-by-Step Solution
- Check the reported battery level in RB Link: Device Settings > Device Info > Battery. If below 15%, replace batteries first, then monitor.
- Verify the supervision interval in RB Link (Device Settings > Communication > Supervision Interval). The RBF default is 15 minutes (900 seconds). If set lower, return to default.
- Check the ambient temperature at the device location using RB Link’s temperature reading (supported on Roombanker Temperature/Humidity Monitor and Outdoor PIR). If below −10 °C or above 50 °C, consider relocating the device or adding insulation.
- Compare the device firmware version (Device Info) against the latest available in RB Link. If outdated, initiate a firmware update.
- If all the above are normal and the device is in a high-traffic zone, note the actual transmission count in RB Link and compare against the battery life projection. Some high-traffic door positions legitimately consume more power.
Prevention
Roombanker field data from 450 installed RBF sensors across 60 sites in Germany, Poland, and Romania (January–December 2024) shows average battery life of 4.8 years for PIR motion sensors, 6.2 years for door/window contacts, and 3.1 years for outdoor PIRs. These figures assume 15-minute supervision intervals and temperate indoor conditions. For a deeper discussion of protocol-level power management, see Wireless Alarm Battery Life: Protocol Design vs Battery Size.
Problem 4: Device Pairing Failure
Symptom
RB Link does not discover the device during the pairing process, or the device appears but fails to confirm pairing.
Root Cause
Four factors account for over 90% of pairing failures in RBF devices (Roombanker support ticket analysis, 2024): the device is too far from the hub during pairing (beyond 3 metres), the tamper switch is not fully closed because the backplate is loose, the device was previously paired to another system and not factory-reset, or RF interference is present at the pairing location.
Step-by-Step Solution
- Bring the device within 3 metres of the hub and within line of sight. Pairing requires a stronger signal than ongoing communication because the device transmits at a higher data rate during initial handshake.
- Verify the tamper switch is fully compressed. The device backplate must be flush against the mounting surface with all screws tightened. A gap of even 1 mm can keep the tamper open.
- Factory-reset the device before pairing: consult the device-specific quick-start guide for the reset sequence (typically holding the tamper button for 10 seconds or inserting a pin into the reset hole).
- Check the hub’s device list in RB Link to confirm the device is not already paired to this hub or another nearby hub.
- If pairing still fails, move to a different location within 3 metres of the hub — away from other electronic devices, metal objects, and concrete pillars — and try again.
Prevention
Always factory-reset new devices before first pairing, even if they appear unused. Pair devices at the hub location, not at their final mounting positions, then verify RSSI after mounting. The Wireless Alarm Installation Workflow documents this sequence with timing targets for each step.
Problem 5: Firmware Update Failure
Symptom
RB Link reports “Update Failed” after reaching a percentage, or the device becomes unresponsive during the update process.
Root Cause
Three conditions cause the majority of update failures: the RB Link app itself is outdated, the hub lost internet connectivity during the update, or the device battery level dropped below 30% mid-update, causing the device to power off before the new firmware was fully written.
Step-by-Step Solution
- Update RB Link to the latest version from the iOS App Store or Google Play Store. The app and the device firmware update are separate — a current app is required to push firmware to devices.
- Verify hub internet connectivity: check the RB Link dashboard for “Hub Online” status. If the hub is offline, resolve the network connection before retrying the update.
- Check the device battery level in RB Link. Do not attempt a firmware update below 30% battery. Replace batteries if needed and wait 5 minutes for the device to stabilise before retrying.
- Retry the update. If it fails again, power-cycle the device (remove battery, wait 10 seconds, reinsert) and attempt the update once more.
- If the device remains unresponsive after a power cycle, remove it from the hub device list in RB Link, factory-reset the device, re-pair, and retry the update.
Prevention
Check battery levels on all devices before initiating a firmware update across a multi-device site. Update devices with the highest battery levels first to confirm the process works, then proceed to devices at lower charge. Keep RB Link updated as a standing practice.
Problem 6: Interference from Other Wireless Devices
Symptom
RSSI values fluctuate by more than 10 dB between readings taken minutes apart. Intermittent communication failures that correlate with specific times of day or specific nearby equipment operating (Wi-Fi routers, wireless doorbells, baby monitors, other alarm systems).
Root Cause
Roombanker’s RBF Protocol operates in the 868 MHz band (EU) or 915 MHz band (other regions). While this sub-GHz band is less congested than 2.4 GHz, it can still experience interference from other devices operating in the same spectrum — particularly wireless doorbells, older-generation alarm systems, and some industrial automation equipment.
Step-by-Step Solution
- Use the RB Link site survey tool: Settings > Site Survey > Spectrum Scan. Run the scan for a full 5-minute cycle to capture periodic interference sources.
- Review the scan results for frequency channels with elevated noise floor (above −95 dBm baseline). RBF auto-selects the clearest channel during hub setup, but a new interference source may have been introduced since installation.
- If a specific interference source is identified, physically relocate the hub or affected device away from the source. A separation of 2–3 metres from a wireless doorbell or Wi-Fi access point is usually sufficient.
- If relocation is not possible, change the RBF communication channel in RB Link: Settings > Hub Configuration > RF Channel. Select a channel that the spectrum scan shows as clean. Re-pair devices after the channel change.
Prevention
During the initial site survey, identify all existing wireless equipment on site and their frequency bands. Document locations of wireless doorbells, Wi-Fi access points, baby monitors, and neighbouring alarm systems. Include a spectrum scan as part of every site survey — not just at the hub location but at the far corners of the coverage area.
Problem 7: ARC Communication Failure
Symptom
The monitoring centre reports no supervision heartbeat from the alarm system, or a test call (Contact ID test report) fails to reach the ARC receiver.
Root Cause
The hub’s primary communication path (Ethernet) or backup path (4G) has lost connectivity, or the SIA DC-09 configuration (receiver number, account ID, reporting format) does not match the ARC’s receiver settings.
Step-by-Step Solution
- Check hub connectivity status in RB Link: Settings > Hub Info > Connection Status. Verify both Ethernet and 4G backup paths separately.
- If IP connectivity is down: check the customer’s router and Ethernet cable. If 4G is down: check the SIM card status, data plan balance, and cellular signal strength (reported in RB Link as “Cellular RSSI”).
- Verify SIA DC-09 configuration: navigate to Hub Settings > ARC Configuration. Confirm the receiver number, account ID, and reporting format (Contact ID or SIA) match the ARC’s specifications exactly. A single digit mismatch in the account ID will cause the ARC to reject the report.
- Initiate a test call from RB Link: Settings > ARC Configuration > Send Test Report. Wait 60 seconds for the ARC to confirm receipt.
- If the test fails and the configuration matches, check the hub firmware version. ARC protocol handling was improved in RBF hub firmware v4.2 and above.
Prevention
Before handover, run a full communication test from the final hub location with both primary and backup paths. The ARC Integration Guide covers per-country ARC protocols, dual-path failover timing, and supervision heartbeat intervals required for EN 50131 Grade 2 compliance.
LED Blink Code Reference
All Roombanker RBF devices report their operating state through LED indicators. The table below covers the most common patterns across RBF sensors, detectors, and the hub. Patterns are consistent across firmware v4.2 and above.
| LED Pattern | Meaning | Action Required |
|---|---|---|
| Solid green (continuous) | Normal operation, hub connected, no faults | None — system is operational |
| Slow flash red (1 blink every 3 seconds) | Tamper alarm triggered or device fault | Check tamper switch closure; verify backplate is flush against mounting surface with all screws tightened |
| Fast flash red (3 blinks per second) | Alarm event in progress | Check RB Link event log; determine if intrusion or environmental trigger |
| Alternating red/green (rapid) | Pairing mode active | Complete pairing process within 60 seconds or device exits pairing mode automatically |
| 3 rapid red flashes, repeat every 5 seconds | Low battery (below 15%) | Replace batteries within 7 days to avoid communication loss |
| 2 red flashes, pause, repeat | Supervision heartbeat timeout — device lost contact with hub | Check RSSI in RB Link; reposition device or add repeater |
| 4 red flashes, pause, repeat every 3 seconds | Firmware update in progress | Wait — do not power-cycle the device during update |
Battery Troubleshooting Decision Tree
Use this sequence when a device reports battery drain faster than expected. Follow the order — each step eliminates the most likely cause before moving to the next.
- Step 1: Check reported battery level in RB Link → Device Info → Battery. Below 15%? Replace batteries and monitor for 7 days. If drain recurs within 6 months, proceed to Step 2.
- Step 2: Verify supervision interval is set to 900 seconds (15 minutes). If shorter, return to default. Wait 24 hours and recheck battery level.
- Step 3: Check ambient temperature at device location. Below −10 °C or above 50 °C? Relocate the device or add environmental protection. Battery chemistry efficiency drops sharply outside 0 °C to 40 °C.
- Step 4: Compare device firmware version against latest in RB Link. Outdated firmware may use inefficient radio wake cycles. Update and recheck.
- Step 5: Review device trigger frequency in RB Link → Device Statistics. If the device transmits more than 200 events per day (typical for a high-traffic door), document the usage pattern — the battery drain is explained by actual use, not a fault.
- Step 6: If Steps 1 through 5 are normal and the device continues to drain, contact Roombanker support with the device serial number, firmware version, and battery voltage log from RB Link.
RSSI Interpretation Guide
RSSI (Received Signal Strength Indicator) values reported in RB Link represent the signal level between an RBF device and the hub. Values are measured in dBm (decibels relative to 1 milliwatt); less negative values indicate a stronger signal. Thresholds below are validated against RBF device testing across 200+ installation sites (Roombanker field engineering, 2024–2025).
| RSSI Range (dBm) | Rating | Expected Reliability | Installer Action |
|---|---|---|---|
| −30 to −60 | Excellent | 100% reliable. No missed events. | No action needed. |
| −61 to −75 | Good | Reliable under normal conditions. Minimal risk during peak household RF activity. | Log as acceptable. No action required. |
| −76 to −85 | Fair | Minor risk of intermittent communication during RF busy periods. | Consider optimising placement if routing allows. Shift device position 1–2 m and retest. |
| −86 to −95 | Poor | Intermittent communication failures likely. “Sensor Lost” events possible. | Reposition device, relocate hub, or install RBF Repeater between hub and device. |
| Below −95 | Dead | Unreliable. Frequent communication loss. Alarm events may not reach the hub. | Must relocate hub, add RBF Repeater, or move device to a different zone. |
When to Call Support vs Self-Resolve
Knowing the boundary between field-serviceable issues and those requiring factory support saves time for both the installer and the support team. The following guidelines come from Roombanker support ticket analysis covering 1,200+ cases handled in 2024.
Self-Resolve on Site
- Device not pairing: factory-reset, verify tamper switch, pair within 3 metres of hub
- Low RSSI from one or two devices: reposition device, relocate hub, add repeater
- False alarms from PIR: check placement for HVAC/sun exposure, adjust sensitivity
- LED indicates low battery: replace batteries, verify supervision interval
- Single device offline: power-cycle device, re-check RSSI
Contact Roombanker Support
- Hub will not connect to network (Ethernet or 4G) after verified configuration
- Multiple devices (three or more) failing simultaneously — may indicate hub or firmware issue
- Persistent firmware update failure after power cycle and battery replacement
- ARC test call consistently fails with correct receiver configuration
- System-wide communication failure — no device reports to the hub
- RBF Repeater does not pair or relay signal after factory reset
Frequently Asked Questions
How do I check the RSSI value for a sensor in RB Link?
Open RB Link, navigate to Device Settings > Signal Test for the specific device. Take three readings over 30 seconds with the building in its normal occupied state (doors closed, people moving through). Record the lowest value. If multiple readings show more than 10 dB of variation, interference may be present — run a spectrum scan from Settings > Site Survey.
What is the minimum RSSI needed for reliable alarm communication?
−85 dBm is the practical threshold for reliable RBF communication. Devices at −86 dBm or below (Poor/Dead range) have a measurable risk of intermittent communication. If an installed device reports RSSI below −85 dBm, reposition the device or add an RBF Repeater. This threshold is validated against RBF device field data from 200+ installation sites across Europe during 2024–2025.
Why does my PIR sensor false-alarm at the same time every morning?
Time-correlated false alarms are almost always caused by environmental triggers — either HVAC system startup (forced air hitting the sensor at 7:30 AM) or direct sunlight entering through an east-facing window and heating the sensor’s lens. Check the event log in RB Link for the false alarm timestamps, then examine the sensor’s field of view for an HVAC vent or window at that position. Relocating the sensor by 1–2 metres or adding a directional mask usually resolves the issue.
How often should I test ARC communication from the hub?
EN 50131 requires that alarm transmission equipment (ATE) be tested at intervals not exceeding 7 days. Roombanker hubs send automatic supervision heartbeats at configurable intervals (default 15 minutes) that satisfy this requirement. Manual test calls should be run at installation handover and after any firmware update that affects the hub. Use RB Link’s “Send Test Report” function under Settings > ARC Configuration to generate a Contact ID test report to the ARC.
Can an RBF Repeater work with any Roombanker sensor?
Yes. All Roombanker RBF devices — PIR sensors, door/window contacts, smoke detectors, keyfobs, and outdoor sirens — are compatible with the RBF Repeater. The repeater operates at the protocol level, not the device type level. After pairing, the repeater relays signals from any RBF device within its range (up to 3500 metres / 2.17 miles in open air) back to the hub.
What does it mean when the hub LED is flashing red but no device is alarming?
A red flashing hub LED with no active alarm event typically indicates one of three conditions: the hub has lost its WAN connection (Ethernet or 4G), a tamper event is open on one of the paired devices, or the hub is in the process of a firmware update. Check RB Link for the hub connection status and the event log for tamper alerts.
Download the Wireless Alarm Troubleshooting Field Guide
This guide in PDF format includes the LED blink code reference, RSSI interpretation table, and battery decision tree on two pages that fit in a tool bag. Download the Wireless Alarm Troubleshooting Field Guide for offline reference on site. For installation planning, see the complete installation workflow and site survey methodology.
Explore more: RBF Protocol Technical Deep-Dive | SSG Romania Case Study | Roombanker Smart Hub | Become a Distributor