BMW M5 Remote Services Not Working: Causes, Fixes, and What to Check First
What BMW M5 Remote Services Do
BMW Remote Services let you control selected vehicle functions from the My BMW app or BMW Connected app, depending on model year and market.
Common features include locking and unlocking the doors, flashing the lights, honking the horn, checking vehicle status, and sometimes preconditioning the cabin or locating the car.
When BMW M5 remote services not working becomes an issue, the cause is often not a single failure.
It can involve the vehicle’s telematics unit, app permissions, account binding, cellular coverage, subscription status, or a temporary BMW backend outage.
Check the Most Common Causes First
Before troubleshooting deeper systems, rule out the issues that affect many BMW owners.
In most cases, the problem is caused by one of the following:
- Expired or inactive ConnectedDrive services
- Weak cellular signal where the car is parked
- Vehicle not fully awake or in sleep mode
- Outdated My BMW app version
- Incorrect BMW ID login or vehicle not properly linked
- Temporary server maintenance at BMW
- Missing privacy or consent settings in the iDrive system
These are especially relevant on performance models like the BMW M5, because the car may sit in secure garages, underground parking, or areas with poor mobile reception.
Remote commands depend on a stable data connection between the vehicle and BMW servers.
Confirm the Subscription and Vehicle Eligibility
Remote services only work when the vehicle is eligible and the service is active.
BMW ConnectedDrive service packages vary by model year, region, and production date, so a feature available on one M5 may not be enabled on another without the proper package.
Check the following in the My BMW app or ConnectedDrive portal:
- Remote Services or Remote Control is active
- The vehicle is assigned to the correct BMW ID
- Payment information is current if the service requires renewal
- The subscription has not expired
- Your market supports the feature for that VIN
If the vehicle recently changed ownership, the previous owner may not have removed the car from their BMW account.
In that case, the car may need to be re-registered or reset through BMW support.
Make Sure the My BMW App Is Properly Set Up
The app is often the first point of failure.
If the app cannot authenticate correctly, remote commands will not reach the vehicle even if the car itself is online.
Try these steps:
- Sign out of the My BMW app and sign back in with the correct BMW ID.
- Verify that the vehicle appears in your garage.
- Update the app to the latest version from the App Store or Google Play.
- Turn off VPNs or network filtering apps that may block BMW services.
- Allow app permissions for notifications and background data.
If possible, test the account from another phone or web browser.
That can help determine whether the issue is device-specific or account-based.
Check the Vehicle’s Connectivity and Wake State
Remote services depend on the BMW’s onboard telematics and cellular connection.
If the car is in deep sleep, in an area with poor coverage, or has a communication fault, commands may fail or remain pending.
Useful checks include:
- Move the vehicle to an area with better mobile signal
- Unlock the car manually and wait a few minutes before retrying
- Start the ignition or wake the vehicle through normal use
- Inspect whether other connected features, such as vehicle status updates, are also failing
If the M5 is parked in a garage with reinforced concrete or a basement level, the cellular signal may be too weak for remote execution.
In many cases, command delays are caused by poor coverage rather than a permanent fault.
Review Privacy Settings in iDrive
BMW vehicles include data and privacy settings that can limit remote functionality.
If privacy mode is set too strictly, the car may block certain online services.
In the iDrive system, check for settings related to:
- Data privacy
- ConnectedDrive services
- Remote access permissions
- Vehicle data transmission
Some menu labels vary by iDrive version, including iDrive 7 and iDrive 8, but the core idea is the same: the vehicle must be allowed to communicate with BMW’s servers.
If these settings were changed during service work or by a previous owner, remote commands may stop working until they are restored.
Look for Telematics or Software Issues
The BMW M5 uses an embedded communications module to manage connected services.
If that module has a software glitch or a hardware fault, remote commands can fail even when the app and subscription are correct.
Signs of a telematics issue may include:
- Vehicle status does not refresh
- Remote lock or unlock never completes
- Location updates are missing or outdated
- ConnectedDrive services fail across multiple functions
A software update or system reset may resolve minor problems.
In other cases, the dealer may need to inspect the telematics control unit, antenna connection, or related communication components.
Try a Basic Reset Before Visiting the Dealer
Simple resets can clear temporary faults.
Before scheduling service, try the least invasive steps first.
- Lock the vehicle and leave it untouched for 10 to 15 minutes
- Restart your smartphone
- Force close and reopen the My BMW app
- Log out and back into your BMW ID
- Restart the iDrive system if your version supports a safe reboot procedure
Some BMW owners also find that waiting after a drive cycle helps.
The vehicle may not accept remote commands immediately if it is still processing network changes or has not completed a normal shutdown.
Check for BMW Service Outages
Sometimes the problem is outside your vehicle.
BMW cloud services can experience outages, maintenance windows, or regional disruptions that temporarily affect Remote Services, BMW Maps, or My BMW app commands.
To verify whether the issue is widespread:
- Check BMW status pages if available in your region
- Look for recent reports from other BMW drivers
- Test again after a few hours
- Try both mobile data and Wi-Fi on your phone
If the commands are failing everywhere, and the app cannot even refresh vehicle status, an external backend issue is more likely than a car-specific defect.
When to Contact BMW Support or a Dealer
If basic troubleshooting does not restore service, contact BMW ConnectedDrive support or a BMW dealership with access to diagnostic tools.
Provide the VIN, model year, exact symptoms, and the steps you already tried.
Dealer-level diagnostics may be needed if:
- The car cannot register with BMW servers
- The telematics module reports faults
- Remote services worked before but failed after a software update
- The vehicle was recently purchased, transferred, or coded
- The issue affects multiple connected features, not just remote lock and unlock
In some cases, a dealer must reinitialize services, update vehicle software, or replace a faulty communication component.
If the M5 has a history of battery issues or a recent low-voltage event, that can also contribute to connected service failures.
Practical Troubleshooting Checklist
If your BMW M5 remote services not working issue needs a quick diagnostic sequence, use this order:
- Verify the subscription is active.
- Confirm you are signed into the correct BMW ID.
- Update the My BMW app.
- Check mobile signal at the vehicle’s location.
- Review iDrive privacy and remote access settings.
- Wait for the vehicle to wake up, then retry.
- Test for a BMW service outage.
- Escalate to BMW support if the fault persists.
Following this process helps separate account, app, network, and vehicle-side problems without unnecessary guesswork.
For a connected performance sedan like the BMW M5, that distinction is the fastest way to restore remote control features and determine whether the issue is temporary or hardware-related.
