A Software Update Bricked People's Smart Homes. There Was No Backup.

In late June, Philips Hue pushed a routine firmware update to its Bridge Pro hub, update 2071353020, described by the company as a handful of small operational improvements. For fewer than 100 owners worldwide, it did something else instead. The Bridge Pro went dark, a red LED lit up, and the whole house lost connection to the Hue app. Lights, sensors, scenes, automations. Gone in one push.

Philips has since confirmed the cause: the bug hit devices where the owner had turned off automatic updates, sat on an older firmware version for a while, then manually installed the update more than ten days after it had already downloaded. A narrow edge case. But narrow doesn't help you much when your Bridge Pro is the one thing sitting between you and every light in the house, and it's the one that hit the bug.

To their credit, Philips didn't drag this out. Every confirmed affected unit gets replaced free of charge, warranty or not. That's the right call, and it's worth saying so plainly. A lot of companies would have pointed at the small print and called it a day.

But read the fine detail in The Register's coverage and there's a line that matters more than the replacement policy: there's no way to back up a Bridge Pro's configuration. None. So even with a brand new unit on the way at no cost, every affected owner is starting from zero. Every light re-added, every scene rebuilt, every automation re-written by hand. The hardware failure is Philips' problem to fix. The hours it takes you to rebuild your house are entirely yours.

That's the part I want to sit with, because it isn't really a Philips story. It's a smart home architecture story, and it applies to more hubs than just this one.

Most consumer smart home systems work the same way underneath. One hub holds the brain: the pairings, the scenes, the automation logic, all of it living inside that single box's own storage. The hub gets its instructions pushed to it over the internet, on the manufacturer's schedule, whether you're paying attention that week or not. If the push goes wrong, or the hub itself just dies, you don't lose one device. You lose the whole house's memory at once, and there's nothing sitting outside that box to restore it from.

That's the actual design flaw here, not the bug. A single point of failure holding the only copy of everything, with updates arriving from outside your control.

A properly designed KNX installation doesn't work that way, and it's worth being specific about why rather than just claiming it's better. The intelligence in a KNX system isn't locked inside one hub's onboard storage. It lives in the ETS project file, the commissioning record of every device, group address, scene and logic function on that installation, which your integrator holds and can hand to you as a backup independent of any single piece of hardware. If one actuator or panel fails, you replace that one device and reload its part of the project. You are not rebuilding the house.

And nothing gets pushed to a KNX device from the internet while you're not looking. Commissioning is a deliberate act your integrator carries out with ETS, not a background download that decides for itself when to install. That doesn't mean KNX hardware is immune to firmware bugs. It means the blast radius is different, and so is the recovery, because the configuration was never something only one box remembered.

I'd rather be straight about this than sell it as a miracle cure. No hardware is bulletproof, KNX included. The difference is what happens on the bad day. Does one device failing cost you an afternoon, or does it cost you your whole house's memory with no backup to reach for?

If you're briefing a project right now, it's a fair question to put to whoever's speccing your automation: where does the configuration actually live, and what happens to the rest of the house if one box fails? If the honest answer is "it's all inside this one hub and there's no backup," that's worth knowing before you commit, not after a firmware update finds out for you.

Just a conversation about what the project needs.

Wayne

wayne@knxlogic.co.za | 082 564 3982 | www.knxlogic.co.za