Direct answer
For the Hue Bridge v2, event capture, cloud processing, phone permission, Focus/background rules and alert zones are separate layers. First, trigger one repeatable event and compare event timestamp with alert time.
What this covers
- Hue Bridge v2 (BSB002)
- Hue Bridge v2; 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: notifications are late, missing or excessive
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 phone's operating system is holding or silencing the notification
What separates it The event exists in the app's history with the right timestamp, but nothing appeared on the lock screen — or it appeared much later, in a summary. Focus modes, scheduled summaries, per-app notification settings and battery optimisation all do this silently.
How to confirm Compare the event's timestamp in the history with when the phone showed it. A correct event and a late or absent alert puts the fault entirely on the phone, and nothing done to the device will change it.
- 2
Alert-type settings do not match what is being triggered
What separates it Some events notify and others do not, consistently by type — motion alerts arrive but person alerts do not, or vice versa. The app's own alert settings are layered per device, per zone and per event type.
How to confirm Compare the event types present in the history against the alert types enabled. This is the most common cause of 'missing' notifications and involves no fault anywhere.
- 3
Network delay between the device and the provider
What separates it Alerts arrive in bursts after a delay, several at once, rather than individually late. The device is queuing events it cannot deliver.
How to confirm Compare the reported signal strength and the event timestamps. Bunched delivery is a transport problem; evenly late delivery is a processing or phone problem.
- 4
Several people share the device and each has their own alert settings
What separates it One household member gets alerts and another does not, from the same device. Alert preferences are per user, not per device.
How to confirm Compare the settings on each phone rather than assuming the device is configured once for everyone.
- 5
The app has been force-stopped or restricted in the background
What separates it Alerts stop after the phone was cleaned up, updated, or put into a battery-saving mode. An app that cannot run in the background cannot present a push notification reliably.
How to confirm Check the phone's background activity and battery optimisation settings for the app specifically. Aggressive power management on some Android builds does this by default.
- 6
Duplicate alerts from more than one integration
What separates it Every event notifies twice, from the manufacturer's app and from a linked platform. Both are working correctly; nothing is broken.
How to confirm Disable notifications in one of the two rather than changing device settings.
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.
- One repeatable, deliberate event — walk the same path at the same time — because a comparison needs a known trigger, not a remembered one.
- The timestamp of that event in the app's history, and the timestamp the phone displayed the alert. The gap between them is the single most diagnostic number on this page.
- Whether the event exists in the history at all. A missing event is a detection problem; a present event with no alert is a notification problem.
- The alert types enabled in the app, per device, compared against the event types actually being recorded.
- Whether other household members received the same alert, since preferences are per user.
- The phone's Focus, scheduled summary, per-app notification and battery-optimisation state at the time.
Trigger one deliberate, repeatable event
ReversibleWalk a known path at a known time rather than waiting for something to happen. Every comparison below needs a trigger whose real time you know, and a remembered event will not do.
Check whether the event exists in the history at all
ReversibleThis splits the problem in half and costs one look. No event in the history means nothing was detected, and the detection record applies instead — no notification setting can deliver an alert for an event that was never recorded.
Compare the event timestamp with the alert timestamp
ReversibleA correct event time and a late or absent alert puts the fault on the phone or the push path. Both times late puts it on the device or the provider. This one comparison decides which half of the remaining steps is worth doing.
Audit the phone's own notification settings before the app's
ReversibleFocus modes, scheduled summaries, per-app permissions and battery optimisation each suppress alerts silently and are the most common single cause. Check them explicitly rather than assuming they are as you left them.
Compare enabled alert types against recorded event types
ReversibleAlert settings are layered per device, per zone and per event type. Motion recorded but person alerts enabled — or the reverse — produces exactly the reported symptom with nothing actually broken.
Compare settings across every account that uses the device
ReversiblePreferences are per user. One person receiving alerts and another not is a settings difference on the phone, not a device fault, and changing the device will not fix it.
Change one setting at a time and retest with the same event
ReversibleSensitivity, zones and alert types interact. Changing several at once produces a result that cannot be attributed, which is how a working configuration gets tuned into a broken one.
Verify with the phone locked and away from home
ReversibleNotification behaviour differs between an unlocked phone on the home network and a locked phone on cellular data. Only the second test reflects how the alert will actually reach you.
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
- BSB002. Hue Bridge v2; the hub every Zigbee accessory reports through, and the only component in a Hue system with its own network connection.
- Capacity
- Philips states the Bridge supports up to 50 lights and 12 accessories. Those are two separate limits, and the accessory limit is the lower and the one people reach first — a switch or sensor that will not pair on a large system is worth checking against the 12-accessory figure before anything else.
- Network
- Connects to the router by Ethernet cable, not Wi-Fi. That is the single most useful fact about this device for troubleshooting: Wi-Fi problems cannot affect the Bridge's own connection, and a Wi-Fi fix will never help it. What can affect it is the cable, the router port and the router's client list.
- Radio to accessories
- Zigbee to every light and accessory. Accessories have no independent path to anything — they reach the Bridge over Zigbee and nothing else — so a Bridge fault presents as every light and switch failing at once, and no accessory-level check means anything until the Bridge is confirmed working.
- Power
- A supplied mains adapter, 120 V in the US, with standby power consumption stated as 0.1 W. There is no battery, so the Bridge stops with the power and returns with it, and everything commissioned to it stops too.
- Mesh behaviour
- Mains-powered Zigbee devices — the lights — repeat the mesh. Battery accessories such as dimmer switches and motion sensors do not. That is why adding another battery accessory never improves range, and adding a mains-powered light often does.
- Philips Hue's own specification
- Philips publishes the Bridge's specification at philips-hue.com/en-us/p/hue-bridge/046677458478, and its support section for the system at philips-hue.com/en-us/support/product/philips-hue-system/100005.
- 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 v2 when it notifications are late, missing or excessive. 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.
- !Critical security or safety alerting is unreliable after the checks above. Consumer push notification is a best-effort service and should not be the only layer for anything that matters.
- !The device records events correctly and the provider consistently fails to deliver them, which is a service fault only the provider can see.
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 system support". Philips Hue's own support section for the Hue system and Bridge — the hub every Zigbee accessory reports through, and the only component with a network connection of its own. What that article does not carry is the model boundary — it is written for a product line, and BSB002 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 connect over Wi-Fi?+
No — it connects to your router by Ethernet cable. This is the most useful thing to know when troubleshooting it: a Wi-Fi problem cannot affect the Bridge's own connection, and no amount of Wi-Fi work will help. Check the cable, the router port and the router's client list instead.
How many devices can the Hue Bridge handle?+
Philips states up to 50 lights and 12 accessories. Those are separate limits, and the 12-accessory limit is the lower one — so a switch or sensor that refuses to pair on a large system is worth counting against that figure before assuming the accessory is faulty.
All my Hue lights stopped working at once.+
Check the Bridge first. Every light and accessory reaches it over Zigbee and has no independent path to anything else, so a Bridge fault takes the whole system out simultaneously. It also has no battery, so a power cut does the same thing.
Will adding another dimmer switch improve my Hue range?+
No. Mains-powered Zigbee devices — the lights — repeat the mesh; battery accessories such as switches and sensors do not. Adding a battery accessory adds a leaf to the network, not a relay. Adding a mains-powered light in the gap is what extends range.
How much power does the Bridge use?+
Philips states standby power consumption of 0.1 W, from a supplied mains adapter (120 V in the US). Its own consumption is negligible; what matters is that it has no battery, so anything depending on it stops during a power cut.
Alerts arrive minutes late. Where is the delay?+
Compare the event's timestamp in the history with when the phone showed it. If the event time is correct, the delay is entirely on the phone or the push service, and nothing you change on Hue Bridge v2 will help. If the event time itself is late, the delay is at the device or the provider.
I get no alerts but the recordings are all there.+
That is the cleanest possible split: detection and recording work, delivery does not. Check the phone's Focus modes, scheduled summaries and per-app notification permission first — they suppress alerts without any indication that they are doing so.
My partner gets the alert and I do not.+
Alert preferences are per user account, not per device. Two phones on the same device routinely have different settings, and the device is configured correctly for one of you. Compare the two phones rather than changing the device.
Alerts arrive several at once after a gap.+
Bunched delivery means the device queued events it could not deliver and then flushed them. That is a transport problem — signal or provider — rather than a notification setting. Evenly late delivery would point somewhere else entirely.
Does Do Not Disturb block these?+
Yes, along with Focus modes, scheduled notification summaries, per-app permission changes and battery optimisation. All of them suppress alerts silently, which is why the phone should be audited before the device.
I get every alert twice.+
You almost certainly have the manufacturer's app and a linked platform both notifying. Nothing is broken. Turn notifications off in one of them rather than changing anything on the device.
Alerts stopped after I updated my phone.+
Operating system updates reset per-app notification permissions and background activity limits more often than people expect. Check the app's notification permission and its background activity allowance specifically — a restricted app cannot deliver a push reliably.
How do I test this properly?+
Walk one deliberate, repeatable path at a known time, with the phone locked and on cellular data rather than Wi-Fi. Anything less realistic than that produces a result that does not match how the alert will actually reach you.
Should I reinstall the app?+
Rarely necessary and it loses your per-device settings. Work the timestamp comparison first — it identifies the layer in one step, and a reinstall that happens to fix things teaches you nothing about which layer was at fault.
Does this answer apply to every Philips Hue model?+
No. It is scoped to BSB002. Hue Bridge v2; 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 notifications or alerts?+
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 notifications, alerts. The ordered checks preserve that evidence.
When should I stop and use qualified service?+
Preserve critical security/safety alerts and privacy.
Answer for the exact device and software version shown above.