When a combo doesn't trigger: finding the problem step by step

You've added a code, but nothing happens in the car – or something other than expected. Usually one of a few causes is behind it: a different profile, an XOS version that's too old, conditions that are never true at the same time, or a second combo working against it. This guide goes through them one by one.

Updated: 29 October 2026

A quick check in five steps

Is the combo saved and enabled?
Are you signed in with the profile that added the combo?
Does your XOS version know every condition in the combo?
Can the trigger and conditions be true at the same time at all?
Is another active combo controlling the same thing?

The following sections explain each point.

The combo belongs to another account

A combo only runs while the XPENG account that added it is signed in to the car. If someone drives with their own profile, the combo doesn't trigger. If you share the car, each person adds the combos they want to their own account.

XOS version and updates

XPENG introduced XCOMBO with the global XOS 5.4 update (XPENG's announcement of XOS 5.4); in Europe, the feature arrived with XOS 5.4.5. Since then, major updates have added new options, and some combos depend on them:

Searching by code requires XOS 5.6 or later.
Location conditions require XOS 5.9.5 (XPENG's XOS 5.9.5 page).
8940 0031 even requires XOS 5.9.5.8906.

If your software doesn't know a condition, it doesn't apply – the combo then never triggers, or triggers in the wrong place. So check which XOS version is installed in the car before you spend a long time looking for other causes.

Trigger and conditions don't fit together

A combo only takes effect if all conditions are met at the moment it is triggered. A typical mistake: “gear D and speed 15–180 km/h” never takes effect when you select D, because the car is still stationary at that moment. 4479 0023 gets it right and only starts the massage once the car reaches 90 km/h.

Also pay attention to the type of trigger: vehicle combos react while the car is on, for example to the gear or a door. Remote combos run while the car is off, for example to pre-heat in the morning. So a vehicle combo can't pre-heat a parked car.

Some combos are started by you

Not every combo triggers on its own. Some are meant to be started by hand – marked “Start manually” in the collection. These include the car-wash combos, such as 2485 0004, and 4237 0000, which demists the windscreen, rear window and mirrors at the push of a button. If such a combo “doesn't trigger”, that's not a fault.

Location conditions

A combo you add doesn't know your location – you enter it yourself in the app. Locations are detected within a radius of about 200 m, which can include the next street. For pairs such as 7205 0054 and 2136 0055, the same location must be set in both. More in the guide “Location conditions: combos for home, garage and on the road”.

Another combo is working against it

Two combos that control the same thing overwrite each other. It can then look as if one of them doesn't trigger. Every code in the collection shows its conflict group; keep only as many per group as make sense at the same time. Two examples:

A Sentry combo without an exception cancels the “except at home” exception of another Sentry combo such as 9313 0040.
4302 0029 prevents locking while someone is in the car and therefore contradicts the combos that lock automatically.

“My combos” on the codes page shows you such conflicts. The guide “Combining combos: how to avoid conflicts” explains how to avoid them. If you'd rather not combine them yourself, start with one of the sets, such as “Commuting & everyday” or “Winter” – they are put together without conflicts.

Combos from other models

Codes can be shared between XPENG models, but a combo built on a G6 or P7+ may use functions or names your G9 doesn't have. The collection marks such cases, for example 1783 0050 from the G6 or 7970 0050 from the P7+. 3598 0041 and 8960 0051 only work if the massage programmes have the same names on the G9 and G6. Test such combos especially carefully.

It triggers but doesn't do everything

Some actions simply don't exist: in a car wash, no combo can shift to N or switch off Auto Hold (“Going through a car wash with XCOMBO”).
Some combos have known limits: 4532 0013 doesn't work at fast chargers, 2229 0033 can't include the tailgate, and 2174 0034 only locks the car but doesn't switch it off.
With some warning-sound combos, a message still appears that you have to confirm on the display.
A combo can overwrite settings you made by hand – with 3997 0009, for example, lighting settings may be lost.

Code not found

Enter the 8 digits without spaces. If the app still can't find the code, the combo may have been deleted or changed, or it needs a newer XOS version than yours. Because a combo can be changed after it's published, what the app shows always counts – read every condition and action before you save.

How to test sensibly

Test while parked in a safe place, not while driving.
Enable new combos one at a time so you know which one does what.
Trigger it on purpose: open a door, buckle up, select a gear.
Adjust values such as temperatures, times and locations, then test again.