Hue Bridge Pro is offline or unavailable

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.

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.

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.

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.

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.

At the router or the hub, not at any device. Simultaneous failure across unrelated hardware is the signature of a shared dependency, and re-adding devices one by one before that dependency is fixed is work you will have to repeat.

It rules out the router, the internet connection and the provider — all of which would take the others with them. What remains is that device's own power, its own radio path, and its own account state.

That interval is the clue. A drop that recurs on a roughly fixed schedule usually tracks the router's DHCP lease. A reservation for the device's MAC address at the router removes it permanently, where rebooting only resets the clock.

Both, in sequence. Marginal signal degrades first — slower live view, late notifications, missed events — and only then drops out. A device that went straight from perfect to absent is more likely a power or credential problem than a signal one.

Because they still hold the old network's name and password, and nothing can tell them otherwise. Setting the new router to the old network name and password is often faster than re-adding every device, and is worth doing before the first re-add.

Then the local link is probably fine and the break is further along — between the router and the provider, or at the provider itself. Check the provider's status page and the router's internet connection before doing anything to the device.

Not as a first step, and not during a provider outage. A reset discards local settings and, on a shared device, can discard other people's access. Establish what is actually broken first — reset is a recovery action, not a diagnostic one.

No, and it is rarely necessary. Deleting a home or hub destroys every automation, permission and share attached to it. Remove and re-add the single failed accessory instead.

The app talks to the provider's cloud; the accessories talk to the hub. Both being true at once means the hub is the break. Nothing about an individual accessory is worth checking until the hub is confirmed online.

Router firmware updates can turn on band steering, IoT client isolation or DNS filtering that was previously off. Compare the current settings against the defaults for those three specifically — a device that worked for a year and stopped on an update date is describing a router change, not a device failure.

Router first, fully up, then the hub, fully up, then accessories. Restarting everything simultaneously produces address conflicts and rejoin storms that look exactly like the original fault, which is how a five-minute check turns into an afternoon.

Give the router several minutes to finish handing out addresses, and battery devices longer still — several report on a duty cycle and will not check in immediately. Judging at thirty seconds produces false failures and unnecessary resets.

It can. Consumer routers have finite client tables, and a household with dozens of connected devices can exceed one. The symptom is that a device drops whenever a new one joins, which reads as random until the pattern is spotted.

That is a useful, specific result: the device joined the local network successfully, so credentials, band and signal are all fine. The break is between the router and the provider — DNS filtering, a firewall rule, or the provider's own service.

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.

Record the complete model identifier, exact message or indicator, software/firmware where visible, the operating stage and what still works.

A reset can erase accounts, networks, maps, schedules or preferences without distinguishing offline, unavailable. The ordered checks preserve that evidence.

Protect security devices and avoid deleting the entire home for one offline accessory.