You open the alarm app to check the house or lock up the shop, but it won’t connect. Before changing anything, note the exact message and whether another authorised user can still get in. Those two details can narrow the checks considerably.
If your Bosch Solution 6000 uses iFob Control and MyAlarm, start with the phone’s internet connection, then match the symptom below. A registration problem, a user restriction and a fault in the alarm’s communications hardware need different attention. Resetting the panel won’t tell you which one you have.
What is the “Bosch 6000 app”?
iFob Control is the mobile app used with compatible Bosch Solution 6000 systems through the MyAlarm cloud service. Solution 6000 is the alarm panel, not the app. Solution 6000-IP is a distinct panel variant with its own hardware and firmware requirements.
Bosch’s MyAlarm and iFob Control support information explains that MyAlarm is a subscription service which Bosch does not administer. Your MyAlarm registered installer sets up the service. Mobile-user access can be managed by the installer or an authorised site owner. Downloading an app alone does not complete the alarm’s remote-access setup.
Check your installation paperwork for the panel name and look at the app name on your phone. If either is different, ask your installer which instructions apply. Keep guidance for other Solution models separate, even when the keypad carries the same Bosch logo.
What can you check first without changing the alarm?
- Record the failure. Is there an error message, a registration button, missing controls or simply no notification? Take a screenshot with private details hidden.
- Check the phone’s internet. Try opening a fresh webpage. Then compare iFob on Wi-Fi and mobile data, where both are available. Tell the installer which connection works and which fails.
- Ask another authorised user. Have them check their own access, without sharing PINs or accounts. If they connect, report that difference to the installer.
- Note what changed. A replacement phone, router change, new internet service or altered user access is useful context. Also note when the app last worked.
You only need to establish whether the app connects and displays current status. There is no need to trigger an alarm, operate a door or change the property’s armed state as a test.
Match the message or symptom
“No Network Connection”
MyAlarm associates this warning with poor connectivity on the phone. Move somewhere with a better signal and try again. If other internet services work but iFob still fails, record the result; general browsing does not test every part of the alarm connection.
A new phone will not connect
App Codes register mobile devices and are separate from your alarm PIN. They are single-use, so a replacement device may need a new code from the installer or authorised site owner. Don’t assume transferring the old phone’s apps has completed registration.
The button says “Register” instead of “Connect”
Check the panel serial number and App Code against the details issued for that site. MyAlarm identifies incorrect entries as a cause of this symptom. If the details are uncertain, ask the installer before changing the site record.
These checks come from MyAlarm’s iFob Control FAQ. Keep App Codes, PINs and unredacted setup screenshots private.
It works at home but not away
A Wi-Fi-only user restriction can produce this behaviour. Ask the site owner or installer whether one applies. Check that restriction alongside the phone’s mobile-data connection.
The connection limit is exceeded
MyAlarm documents a limit of two users connected to control the system at the same time. Wait a few minutes for other users to finish, then retry. That limit is separate from how many people have accounts.
It connects, but a door or other control is missing
Ask which functions your user is authorised to operate. Doors and outputs also need installer configuration before they are available in the app.
MyAlarm’s Getting Started Guide covers these access options. The guide dates from July 2015; its access explanations are also supported by MyAlarm’s online FAQ. Use current installer guidance for setup screens and programming.
The MyAlarm user page shows “Quarantined”
Repeated incorrect PIN attempts can quarantine a mobile-user profile. Stop guessing and contact the installer to check your user PIN and the blocked profile.
Notifications are missing, but the app connects
If current status loads but alerts are missing, check whether your phone allows notifications from iFob. Ask the installer which events your service is configured to report. Explain that connection works and notifications are the missing part; that helps them investigate the right issue.
Does the alarm itself have a working connection?
Your phone can have internet while the alarm’s communications equipment does not. The next question is how this particular installation reaches the service.
For the original Solution 6000, MyAlarm’s prerequisites list supported Ethernet (network cable), Wi-Fi keypad and cellular (mobile network) options, together with firmware and service requirements. For Solution 6000-IP, Bosch’s brochure documents iFob access through MyAlarm and an IP module or Wi-Fi keypad for IP connectivity. Your installation paperwork or installer can confirm which equipment is fitted.
If the problem started after a router or Wi-Fi change, tell the installer before buying replacement equipment. They can establish whether the alarm uses that network and check its configuration. If it uses cellular communications, the module, signal and service need their own checks.
Also ask whether the MyAlarm interactive service is active and the site registration is complete. A working keypad does not confirm either. Our Solution 6000 installation and app setup service covers the configuration of remote access as part of the wider system.
What if the keypad is beeping or shows “Comms Fail”?
Record the exact message as well as the app symptom. A communications warning can concern the alarm’s reporting path and needs to be interpreted for the installed panel. It should not simply be labelled an app fault.
Our guide to “Comms Fail” and “Line Fault” messages explains that distinction. If the keypad is also beeping, the Bosch alarm beeping guide explains why identifying the model and fault comes before a reset.
If the system is professionally monitored, ask the monitoring provider or installer to verify reporting separately. Being able to use the keypad or app does not establish that an alarm report is reaching the monitoring centre.
When does the problem need installer-level checks?
Contact the installer if access remains unavailable after the phone checks, registration details cannot be confirmed, several users are affected, or the keypad reports trouble. Provide the observations you have collected so they can check the relevant part of the system.
The assessment may include the communicator model, network configuration, service registration, user permissions and panel event history. Firmware is another possibility, but it must be assessed against the exact panel and installed version.
Bosch has documented iFob connection fixes in a Solution 6000 firmware notice from April 2022. It records a past fix for some sites, not a recommendation to install that version today. Bosch also warns that an upgrade can default programming and specifies hardware restrictions, so this is an installer decision.
Why resetting the alarm should not be the first step
A factory reset can remove programming that the installation relies on. It does not identify whether the original problem was the phone, access setup or communications equipment. Leave the panel, battery and installer programming alone while the cause is being established. Port forwarding and disabling network security are not general-purpose iFob fixes either.
A practical checklist before contacting SIPKO
Have these details ready:
- The panel model from your paperwork, plus the app name and version.
- The exact error and whether the problem affects connection, particular controls or notifications.
- Whether it behaves differently on Wi-Fi and mobile data.
- Whether another authorised user can connect.
- When it last worked and any recent phone, network or account changes.
- Any keypad trouble message and the communicator model, if already recorded in your installation documents.
You do not need to open the alarm cabinet or send your PIN to gather that information.
FAQ
Why has iFob Control stopped connecting?
The cause may be the phone’s internet connection, device registration, user access or the alarm’s communication path and MyAlarm service. Record the exact message and compare another authorised user’s access before changing settings.
Why does iFob work on Wi-Fi but not mobile data?
Check that the phone has a working mobile-data connection. Also ask the site owner or installer whether your user is restricted to the home Wi-Fi zone; MyAlarm documents this access option.
Do I need a new App Code after changing phones?
You may. App Codes are single-use, and transferring apps to a replacement phone does not confirm that its alarm access is registered. Ask your installer or authorised site owner for help; an App Code is separate from your alarm PIN.
Does a working keypad mean remote access and monitoring are working?
No. Local keypad operation does not confirm the MyAlarm service or remote connection. If the system is professionally monitored, ask the monitoring provider or installer to verify alarm reporting separately.
Should I reset the alarm or contact the installer?
Do not factory-reset the panel to troubleshoot app access; a reset can remove its programming. Contact the installer if phone checks do not restore access, registration details are uncertain, several users are affected or the keypad reports trouble.
SIPKO provides Bosch alarm repairs and support in Melbourne. If the checks above do not explain the failure, contact us with the symptom and what you have already checked. We can check how your system is set up before recommending a repair or change.
