Direct answer
For the Hue Bridge Pro, trigger, conditions, controller/hub, permissions and action chain should be tested separately. First, review activity history and trigger the action manually.
What this covers
- Hue Bridge Pro (the model number is on the underside of the bridge; the app also reports it under Settings)
- Hue Bridge Pro; the hub every Zigbee accessory reports through, and the only component in a Hue system with its own network connection.
- The specific fault this record addresses: routine, schedule or automation is not running
What it does not cover
- ×The same symptom on a different Philips Hue product line, which has its own record and its own cited source
- ×An on-screen error code whose meaning has not been checked against this exact model's manual
- ×Live electrical, gas, sealed-system, internal battery-cell or structural repair — a technician boundary, not a self-service step
Differential
What actually causes this, and how to tell them apart
These are ordered by how often each one is the answer, not by how easy it is to try. The point of the middle column is that two causes producing the same headline symptom rarely produce the same detail — that detail is what tells you which one you have before you change anything.
- 1
The trigger never fired
What separates it Nothing appears in the activity history at the expected time. Running the action manually works perfectly, which is what convinces people the automation is broken when the action is the one part that is fine.
How to confirm Check the history first. No entry means the trigger, not the action — and every minute spent on the action is wasted.
- 2
A condition was false at the moment it fired
What separates it The history shows the automation evaluated and did nothing. Conditions on presence, time of day, sunset, another device's state or a household member's location fail silently by design.
How to confirm Remove conditions one at a time and re-run. A routine that works with no conditions and fails with one identifies that condition exactly.
- 3
Time zone or location is wrong on the home, not the phone
What separates it Everything runs, at the wrong time — often by a whole number of hours, or with sunrise and sunset offset. The home's location is a separate setting from the phone's, and it defaults to wherever it was created.
How to confirm Check the home or hub's own time zone and address rather than the phone's. Sunset-based automations firing at a consistently wrong hour is this and almost nothing else.
- 4
Presence detection is the trigger and it is unreliable
What separates it Arriving and leaving automations fire late, early, twice, or not at all — and worse for one household member than another. Geofencing depends on the phone's location permission, its background activity allowance and its power state.
How to confirm Compare each member's phone permissions. A geofence needs 'always' location rather than 'while using', and battery optimisation defeats it silently.
- 5
The controller was asleep or offline when the trigger fired
What separates it Automations run when you are at home and using the app, and fail overnight. Something has to be awake to evaluate the rule, and on some platforms that is a specific hub rather than the cloud.
How to confirm Check which device is the active controller and whether it was online at the trigger time. This is the failure that looks most like randomness.
- 6
One action failed and stopped the chain
What separates it The first part of a routine happens and the rest does not, consistently at the same point. Actions run in order and a failure partway leaves a half-executed result.
How to confirm Run each action individually. The one that fails alone is the one that is stopping the chain, and it usually has its own separate fault.
- 7
The automation belongs to an account that lost access
What separates it It stopped on a date that matches someone leaving the home, a password change or a device being re-added. Automations are owned, and ownership is not always transferred when a device changes hands within the household.
How to confirm Check which account created the routine and whether that account still has permission to the devices it touches.
- 8
Two automations are fighting
What separates it The result flickers, or the last state does not persist. A schedule and a sensor rule that disagree will each keep applying their own outcome.
How to confirm Look for another routine touching the same device at an overlapping time. This is invisible from either routine's own screen.
- 9
The device was renamed or moved to another room
What separates it The automation exists and references something that no longer resolves. Renaming a device or moving it between rooms breaks rules that referenced it by name or by room.
How to confirm Open the routine and confirm each referenced device still resolves rather than showing a placeholder.
Before you touch a setting
Record this first — changing settings destroys the evidence
Every item below stops existing the moment a reset, re-pair or settings change is made. Written down first, they are what separates the causes above; recovered afterwards, they are guesswork.
- Whether the automation appears in the activity history at all at the expected time — this single check splits trigger problems from action problems.
- The exact time it should have run and the exact time anything happened, because an offset of whole hours is a time-zone answer.
- The full list of conditions attached to it, before any are removed.
- Which account created the routine, and whether that account still has access to every device it touches.
- Whether it fails always, or only overnight, or only when nobody is home — each points somewhere different.
- For presence triggers, each household member's location permission and background activity allowance.
- Which device is acting as the controller, and whether it was online at the trigger moment.
Read the activity history before changing anything
ReversibleAn entry at the expected time means the trigger fired and the problem is downstream. No entry means the trigger never fired and nothing about the actions is worth investigating. This one look decides which half of the work is real.
Run every action manually, one at a time
ReversibleActions execute in order and a failure partway leaves a half-run routine. Running each alone identifies which one stops the chain, and that action almost always has its own separate fault worth fixing on its own terms.
Check the home's time zone and location, not the phone's
ReversibleThe home has its own location setting and it defaults to wherever it was created. Everything running at a consistently wrong hour, or sunrise and sunset landing wrong, is this and very little else.
Remove conditions one at a time and re-run
ReversibleConditions fail silently by design — presence, time window, sunset offset, another device's state. A routine that works with none and fails with one has told you exactly which condition is false at the moment it matters.
Verify presence permissions on every phone involved
ReversibleA geofence needs 'always' location rather than 'while using', and background activity has to be allowed. Battery optimisation defeats both silently, and the symptom differs per household member because the settings do.
Confirm the controller was awake at the trigger moment
ReversibleSomething has to evaluate the rule, and on hub-based platforms that is a specific device rather than the provider's cloud. Automations that work while you are home and fail overnight are describing a controller that was not available.
Look for a second routine touching the same device
ReversibleTwo rules that disagree each keep applying their own result, which shows as flicker or as a state that will not persist. This is invisible from either routine's own screen and has to be looked for deliberately.
Confirm every referenced device still resolves
ReversibleRenaming a device or moving it between rooms breaks rules that referenced it by name or room. The routine still exists and still appears valid; it simply points at nothing.
Run it twice at the intended time and state
ReversibleOnce proves it can work. Twice, at the real trigger time and in the real household state, proves it does. Automations that pass a manual test and fail in life are failing on a condition that manual testing never reproduces.
Model-specific
What is true of this model and not of its siblings
Generic advice for the product line fails here. Each item below is a property of this specific model family that changes which of the steps above apply to you.
- Model scope
- the model number is on the underside of the bridge; the app also reports it under Settings. Hue Bridge Pro; the hub every Zigbee accessory reports through, and the only component in a Hue system with its own network connection.
- Can run over Wi-Fi — unlike the standard Bridge
- Philips states it connects "over WiFi or use the Ethernet cable provided." This overturns the single most useful fact about the standard Bridge v2, which is Ethernet-only: on a Bridge Pro, a Wi-Fi problem CAN be the cause of a Bridge outage, so checking the Wi-Fi connection is a real troubleshooting step here that it isn't on the older Bridge.
- Capacity
- Supports 150+ lights and 50+ accessories — three times the standard Bridge's 50 lights and 12 accessories. A system that outgrew the original Bridge's accessory limit is a legitimate reason to upgrade, not a sign of a faulty Bridge.
- MotionAware
- A Pro-exclusive feature that lets compatible Hue light bulbs themselves participate in motion detection, turning the lighting system into a motion-aware network rather than relying only on dedicated sensors. This has no equivalent on the standard Bridge.
- Processor and scenes
- Runs on a dedicated higher-performance chip described as capable of complex algorithms and AI-powered features, and supports up to 500 personalized scenes versus fewer on the standard Bridge.
- Radios and security
- Uses Bluetooth and Zigbee like the standard Bridge, but adds an upgraded Zigbee Trust Center for stronger encryption. Matter support is provided via the Bridge on both models.
- Power
- 100-240V AC input through an included adapter, 5V DC output at up to 1A, with 0.1W max standby draw — same power profile as the standard Bridge.
- Power path
- Mains adapter into a standard outlet. Switched outlets and outlets on a circuit that trips are the two failure modes that present as device faults. Use the supplied adapter — third-party adapters that supply the right voltage at the wrong current are a common cause of intermittent restarts.
- Radio
- Zigbee mesh through a bridge. The accessory has no independent internet path, so a bridge fault presents as every accessory failing at once. Mains-powered Zigbee devices repeat the mesh; battery ones do not, which is why adding a battery accessory never improves range.
- Radio
- Wired Ethernet available. A wired path removes signal strength, band steering and Wi-Fi credentials from the investigation entirely, and is worth using during diagnosis even if the device will end up wireless.
- Symptom boundary
- This record covers Philips Hue Hue Bridge Pro when it routine, schedule or automation is not running. A different symptom on the same hardware, or this symptom on a different Philips Hue product line, has its own record with its own causes and its own cited source.
Stop boundary
When this stops being a self-service repair
Continuing past any one of these costs more than the repair saves — in safety, in warranty, or in evidence a technician needs.
- !The automation is relied on for anything safety-critical — heating for a vulnerable person, medication reminders, access for someone who cannot let themselves in. Consumer routines are best-effort and are not specified for that.
- !The controlling account is inaccessible and the routines cannot be edited or reassigned.
- !A hub has failed and the automations it evaluated cannot be moved to another controller.
Evidence ledger
Sources behind this answer
Visible sources support the visible claims. Home Product Support records the publisher, the fact used and the review date; community reports can suggest an issue but do not become a published fact on their own.
Where the manufacturer's article stops. Philips Hue Support publishes this as "Philips Hue app support". Philips Hue's own support topic for the app, where routines, schedules and automations are configured. What that article does not carry is the model boundary — it is written for a product line, and the model number is on the underside of the bridge; the app also reports it under Settings is the scope applied here. Where a control label, terminal, indicator pattern or reset sequence differs on your unit, the manual for that exact model is the authority, not this page and not the article.
Exact questions
Common follow-ups
Does the Hue Bridge Pro need an Ethernet cable like the regular Bridge?+
No — this is the one thing that's different from the standard Bridge. The Pro can connect over Wi-Fi or Ethernet, so on this model a Wi-Fi problem really can take the Bridge offline, unlike the Ethernet-only original Bridge.
Why upgrade to a Bridge Pro?+
Capacity and features: 150+ lights and 50+ accessories versus the standard Bridge's 50/12, MotionAware (lights that participate in motion detection), up to 500 scenes, and a faster processor for more complex automations.
What is MotionAware and do I need a separate sensor?+
It's a Bridge Pro-exclusive feature that lets your existing compatible Hue bulbs detect motion themselves, without needing a dedicated Hue Motion Sensor for that function. It doesn't exist on the standard Bridge.
I have more than 50 lights and things are getting unreliable.+
The standard Bridge's practical limit is 50 lights and 12 accessories. The Bridge Pro raises that to 150+ lights and 50+ accessories — if you're near or over the old ceiling, that's the likely cause, not a fault to troubleshoot away.
Is the Bridge Pro's Zigbee any different from the standard Bridge?+
Same Zigbee radio to lights and accessories, but with an upgraded Zigbee Trust Center for stronger encryption. Accessory range and mesh behavior work the same way as on the standard Bridge.
The action works when I run it by hand but the routine never fires.+
That is the clearest possible evidence the action is fine and the trigger is not. Check the activity history — no entry at the expected time means nothing downstream is worth investigating, and running the action manually only confirms the part that already worked.
Everything runs an hour off.+
Check the home's own time zone and address rather than the phone's. The home has a separate location setting that defaults to wherever it was created, and an offset of a whole number of hours — or sunrise and sunset landing wrong — is almost always this.
My arrival routine fires late, or twice, or not at all.+
Geofencing depends on the phone, not the home. It needs 'always' location permission rather than 'while using', and background activity has to be allowed — battery optimisation defeats it silently. That is also why it behaves differently for different household members: their phone settings differ.
Half the routine runs and the rest does not.+
Actions execute in order, and one failing stops the chain. Run each action on its own to find which one fails alone — it will usually have a fault of its own worth fixing independently, and the routine will then complete.
It works during the day and fails overnight.+
Something has to be awake to evaluate the rule. On hub-based platforms that is a specific controller rather than the provider's cloud, and a controller that sleeps or drops off overnight produces exactly this pattern.
It stopped working and nothing changed.+
Something usually did. Check for a device renamed or moved to a different room, a household member who left, a password change, or a device removed and re-added. Routines reference devices by name and room, and reference the account that owns them.
The light flickers between two states.+
Two automations are fighting over the same device — commonly a schedule and a sensor rule that disagree. Neither routine's own screen shows the other, so it has to be looked for deliberately by checking everything that touches that device in the same window.
Should I delete and rebuild the automation?+
Not before reading the history. A rebuild that happens to work teaches you nothing about which of the four parts failed, and the same cause will take out the next routine you build. Diagnose first, rebuild only if the routine is genuinely corrupt.
Can I rely on this for something important?+
No consumer automation platform is specified for safety-critical use. Trigger, condition, controller and action each fail independently and silently, and none of them alerts you when they do. Anything that matters needs a layer that is designed to fail loudly.
Why did it work when I tested it and not in real life?+
Because a manual test skips the conditions. Presence, time window, sunset offset and another device's state are all true when you are standing there testing and frequently false at the real trigger moment. Test at the intended time, in the intended household state, twice.
Does this answer apply to every Philips Hue model?+
No. It is scoped to the model number is on the underside of the bridge; the app also reports it under Settings. Hue Bridge Pro; the hub every Zigbee accessory reports through, and the only component in a Hue system with its own network connection.
What should I record before troubleshooting routine or automation?+
Record the complete model identifier, exact message or indicator, software/firmware where visible, the operating stage and what still works.
Why is a factory reset not the first step?+
A reset can erase accounts, networks, maps, schedules or preferences without distinguishing routine, automation. The ordered checks preserve that evidence.
When should I stop and use qualified service?+
Do not use consumer routines as the sole safety-critical control.
Answer for the exact device and software version shown above.