A self-monitoring burglar alarm system relies on named people, rather than an Alarm Receiving Centre (ARC), to judge events and take the next agreed action. When the Hub has an available network, RB Link lets the designated users see system event information. The local alarm and this remote visibility are two different paths.
Self-monitoring is therefore not “no one is monitoring.” It works when named people can see the event, understand the site and respond when needed. If nobody is available, an App notification alone does not solve the problem.
Follow one alarm from the rear door to the person responsible
Consider a small shop after closing. A door contact on the rear entrance is triggered while the system is armed.
The detector sends the event to the Hub. The Hub applies the configured alarm logic, and the local siren operates as configured. When the Hub has an available network, the event is also visible through RB Link to the designated user.
The path is easy to understand when each part has one job:
| Part | What it does | What the person responsible still needs to do |
|---|---|---|
| Door contact | Detects the door opening and sends the event to the Hub. | — |
| Hub and local siren | Apply the configured local alarm behaviour. | Make sure the site has been armed and tested as intended. |
| RB Link | Gives the designated user access to system information when the Hub has a usable network connection. | Check the event and decide what action the situation requires. |
| Named person | Uses the site plan, contacts or other available information to judge the event. | Call the site, contact another person or follow the action agreed for that property. |
The App gives the user information. It does not replace the person who must notice the event and act.
This short example shows how the person responsible can use the available view to check a visitor before deciding what to do next:
Local alarm and remote visibility are two different paths
This difference matters most when the site network fails.
If a detector is triggered, the Hub and siren can still carry out the configured local alarm action. The local alarm does not depend on the phone seeing the event.
Remote visibility is different. If the Hub has no available network, RB Link shows the Hub and all of its devices as offline. That does not mean the detectors or local siren have stopped working. It means the App cannot see the system through a network at that time.
Some Roombanker Hub configurations have an available cellular connection. In that case, the Hub automatically switches to cellular and continues App communication and any configured ARC reporting. This applies only where the Hub and project have that usable cellular path.
| What you see | What it means | Check first |
|---|---|---|
| Local siren operates and RB Link shows the event | The local and remote paths are both available for this event. | Follow the action agreed for the site. |
| Local siren operates but the Hub and devices appear offline in RB Link | The local alarm is working, but the Hub has no available path to the App. | Check the site’s internet and any cellular path provided for that Hub. Do not replace the detector only because the App is offline. |
| The primary site internet fails, but RB Link remains connected | Another usable connection may still be carrying App communication. | Confirm which connection is active and whether the project expected that backup. |
| No intended event appears locally | The problem starts before remote monitoring. | Check the detector, Hub event and relevant arming or zone settings first. |
This split gives an installer a faster way to investigate a complaint. “The App is offline” is a network-visibility problem until site evidence shows that the detector or local alarm also failed.
Three conditions decide whether self-monitoring will work
1. Someone must be available
The main user may be driving, asleep, abroad or unable to check the phone. A site that depends on self-monitoring should therefore name a primary person and at least one backup who understands what to do.
If the project cannot provide a reliable backup, the weakness is not the detector or the App. It is that nobody is consistently available to handle the event. That is a reason to evaluate professional monitoring.
2. The Hub needs a usable network for remote visibility
Local alarm behaviour and remote App visibility should be tested separately. Trigger an agreed event and confirm the local result. Then confirm that the designated people can see the system information they need through RB Link.
If the project depends on cellular backup, test the available connection as part of the planned setup. Do not assume every Hub or every site has that option.
3. The person needs a clear next action
Seeing “rear door alarm” is useful only when the person knows which shop and door it refers to and what to do next.
For the small shop, the action might be to call the keyholder, check another available source of information or follow the site’s agreed escalation route. The right action depends on the property and the people responsible for it. Write it down before handover so the first alarm is not the first time they discuss it.
Self-monitoring or ARC monitoring?
The main difference is who is expected to receive and handle the event.
| Question | Self-monitoring | ARC monitoring |
|---|---|---|
| Who watches for events? | The users or named people responsible for the site. | A professional receiving team under the agreed service. |
| Who decides what to do? | The named person follows the site’s own plan. | The ARC follows the action agreed for that account. |
| What if the first person is unavailable? | The site needs its own backup person and escalation method. | The next action depends on the monitoring contract and account instructions. |
| What must the installer confirm? | App access, available network, named people and a usable response plan. | Reporting configuration, ARC receipt and the service agreed for the account. |
Self-monitoring can suit a residence, shop or small business when the people responsible are available and willing to act. An ARC is worth evaluating when selected events must reach an external professional team and be handled under an agreed service.
For the ARC role and receiving process, read What Is an Alarm Receiving Centre?.
Agree these four things before handover
Keep the handover short and usable:
- Name the main person who will use RB Link to check events.
- Name a backup person for times when the first person is unavailable.
- State which events need attention and what the first action should be.
- State what to do if RB Link shows the Hub and all devices offline.
If those four answers are realistic, the project has the basic operating conditions for self-monitoring. If they cannot be agreed, do not describe the job as complete simply because the App has been installed.
Self-monitoring also does not automatically mean “no contract.” Equipment, software, installation, maintenance and monitoring are separate commercial questions. Use the no-contract alarm guide to compare those terms before choosing an offer.