Can an NBN change break Bosch alarm reporting?

Yes. If the old reporting path relied on a traditional phone line or a communicator that was never recommissioned after the change, the site may lose reporting without realising it straight away.

Should I change communicator settings myself?

Not unless you are the competent technician responsible for that system. Customer-safe checks should stay at the infrastructure and fault-message level.

What should I tell support first?

Tell them what changed on site, what the keypad says, and what communication path the customer believes the system should still be using.

What should I record before changing any settings?

For Bosch Alarm Notification and Communication Path Checklist, record the exact model, firmware if known, current status, precise error wording, screenshots and the last known working condition. Change one item at a time.

Should I factory-reset the equipment while troubleshooting?

Not as an early step. A reset can erase network, recording, user, account or integration settings. Use it only with a configuration backup, known credentials and a model-specific recovery plan.

How do I confirm the problem is genuinely fixed?

Repeat the original test, then check the relevant local and remote paths separately. For an intermittent fault, monitor through the conditions that previously caused it.

What details should I send technical support?

Send the order number if available, exact product models, firmware if known, screenshots or photos, precise error wording, failure times and a short list of completed checks.

Should I change several settings at once?

No. Change one item, repeat the same test and record the result. Multiple simultaneous changes make it difficult to identify the fault or safely reverse the change.

Support

Bosch Alarm Notification and Communication Path Checklist

On Bosch alarms, "notifications not working" is often really a communication-path problem. The fault may sit in the old phone-line path, the NBN change, the modem, the communicator, or the assumption that the system still reports the same way it used to.

Bosch Communication Support

Summary

Use this page when a Bosch alarm site is unsure whether the system still communicates correctly after NBN, router, phone-line or monitoring changes.

Applies to

Older Bosch alarm systems
Sites with changed phone, internet or monitoring paths
Communication and reporting trouble conditions

Difficulty and time

Difficulty: Moderate

Estimated time: 15 to 35 minutes for safe checks

What you will need

Keypad access
History of modem, NBN or phone changes
Monitoring or technician contact details
Photos of the communicator or panel area if safe

This guide is not about bypassing or disabling an alarm. It is about working out whether the communication path the customer thinks they still have is actually the one the panel is using today.

Before you start

Ask whether the site used an old phone-line dialler path.
Ask whether the premises moved to NBN, new modem hardware or mobile backup recently.
Write down any keypad messages before power-cycling anything.
If the site is monitored, treat communication certainty as important, not optional.

Step 1: Work out what the system is meant to report through

Ask whether the panel used a traditional phone line, IP module, GSM path or another communicator.
Do not assume the current internet modem automatically replaced the old alarm reporting path.
If the customer cannot answer this, involve the technician or monitoring provider sooner rather than later.

Step 2: Check the obvious infrastructure changes first

Ask whether the old PSTN service was removed.
Check whether the modem, NBN box or communications cabinet has power.
Ask whether a router was replaced and the alarm path never rechecked afterwards.
Look for a keypad communication or line-fault indication.

Step 3: Separate customer-safe checks from technician checks

It is fine for the customer to confirm power, recent changes and fault wording. It is not fine to improvise panel rewiring or deeper communicator programming.

Customer-safe: note the trouble message, confirm power, confirm recent NBN or router changes.
Technician-level: communicator programming, panel wiring, monitoring-path recommissioning and reporting tests.

Step 4: Decide whether the system still meets the site expectation

Sometimes the real answer is that the alarm is still arming locally, but the reporting path the customer thought they had no longer exists.

Confirm whether the customer expects professional monitoring, app alerts or both.
Confirm whether the present hardware can still deliver that path.
If not, treat the job as an upgrade or recommissioning job rather than a quick fix.

Troubleshooting table

Symptom	What to check	What to do next
The local device also fails	Power, cable, storage or local configuration	Keep the test local and resolve the first failed layer before changing app or cloud settings.
Local operation works but the app fails	Ownership, sharing permission, cloud status or remote network	Keep the proven local setup and compare owner versus shared-user access on mobile data.
Only one channel, zone, door or user fails	Item-specific schedule, permission, wiring or assignment	Compare it side by side with one working item and change only the meaningful difference.
The fault started after another change	Router, password, firmware, account, power or configuration change	Document the last known working state and reverse only the relevant change where safe.
The fault is intermittent	Exact time, logs, signal, load, power and environmental pattern	Capture failure times and screenshots so support can correlate the event instead of guessing.

When to contact support

Contact SecurityWholesalers support when the local result, exact model, firmware or app version and one controlled test are documented but the fault remains. Send the order number if available, screenshots, exact failure time and the checks already completed.

Common mistakes

Changing several unrelated settings before repeating the original test.
Skipping the local device check and relying only on an app symptom.
Resetting, formatting or unbinding equipment without a backup and ownership record.
Escalating without the exact model, version, error text and test time.

Worked example

Compare one failing path with one working path

Situation: One device, channel or user failed while another comparable item still worked.

Solution used: The two paths were compared at the local device first, one meaningful difference was corrected, and the original test was repeated.

Why this was chosen: The comparison isolated the affected layer without disturbing the rest of the system.

Installation notes: The final status, screenshot and test time were added to the handover record.

Related support guides

Relevant product categories

Still stuck?

Need help choosing or setting up a system? Contact SecurityWholesalers support with your order number, product model and a clear description of the issue.

Related buying guides

SecurityWholesalers Buying Guides - Check compatibility and system-design guidance.
Full Store Directory - Find the relevant product family.

Frequently asked questions

Can an NBN change break Bosch alarm reporting?
Yes. If the old reporting path relied on a traditional phone line or a communicator that was never recommissioned after the change, the site may lose reporting without realising it straight away.
Should I change communicator settings myself?
Not unless you are the competent technician responsible for that system. Customer-safe checks should stay at the infrastructure and fault-message level.
What should I tell support first?
Tell them what changed on site, what the keypad says, and what communication path the customer believes the system should still be using.
What should I record before changing any settings?
For Bosch Alarm Notification and Communication Path Checklist, record the exact model, firmware if known, current status, precise error wording, screenshots and the last known working condition. Change one item at a time.
Should I factory-reset the equipment while troubleshooting?
Not as an early step. A reset can erase network, recording, user, account or integration settings. Use it only with a configuration backup, known credentials and a model-specific recovery plan.
How do I confirm the problem is genuinely fixed?
Repeat the original test, then check the relevant local and remote paths separately. For an intermittent fault, monitor through the conditions that previously caused it.
What details should I send technical support?
Send the order number if available, exact product models, firmware if known, screenshots or photos, precise error wording, failure times and a short list of completed checks.
Should I change several settings at once?
No. Change one item, repeat the same test and record the result. Multiple simultaneous changes make it difficult to identify the fault or safely reverse the change.