Philips Hue's AI Automations Are Here. You Can't Edit What They Build

The pitch for AI in the smart home that I actually find convincing isn't a chatbot. It's this: describe what you want in a sentence, and the app builds the automation you'd otherwise spend twenty minutes clicking together.

Philips Hue just shipped that. It's called Custom AI Behaviors, and the first hands-on report shows both why it's appealing and where it falls down.

What it is

Signify announced it in September. "Exclusive to the Hue Bridge Pro, Custom AI Behaviors will allow users to create sophisticated and highly personalized lighting automations simply by describing what they want in everyday language." The assistant turns your request into a behavior by combining triggers, conditions and actions.

Signify's examples are the kind of thing the regular Hue app makes awkward: switches and sensors that behave "differently on weekends," or a scene that comes on "when it gets dark – regardless of the time."

It was supposed to arrive in early October. According to Hueblog, it landed about four weeks late, in Hue app 6.4.0.

What you need

• A Hue Bridge Pro on the latest firmware. "The older, white Hue Bridge is not supported."
• Hue app 6.4.0. It reached the Apple App Store first. On October 29, Hueblog said the Google Play version "should be coming soon."

You'll find it from the AI Assistant icon on the home screen, in rooms and zones, in the Automations tab, and in the settings for switches and sensors.

What happened in the first test

Hueblog's Fabian, who says he runs more than 50 Hue lamps himself, ran a simple test: two selected lights in a room should turn on at sunset, each day with a different one of ten gentle scenes.

The assistant understood the request and built the automation. But the scenes it created "turned on not only the two specified lamps but also all the other lights in the room." When he told it again to use only those two lamps, "it gave up and simply displayed an error message." His guess at a workaround was to first make a zone with only those two lamps.

Then the part that matters most: "There's no way in the Philips Hue app to manually edit an automation created by the AI after the fact."

Why that's the real problem

Every automation builder gets things wrong sometimes. That's fine when you can open the result and fix the one wrong setting. If the AI picks the wrong lights and you can't touch its work, your only options are to rephrase and hope, or delete it and build the thing by hand the old way.

That's the trade-off I'd want every mainstream AI feature measured on. Google's Gemini and Alexa+ are both moving toward "describe it and we'll build it." The question to ask of each is simple: when it gets it wrong, can you see and fix what it made? In Home Assistant, an automation an AI writes is still a normal automation you can open and edit. In Hue, for now, it isn't.

The switch reports are worth a look before you try it

Hueblog's comments section has a few early reports. They're anecdotes, not confirmed bugs, but they're specific:

• One reader said that setting up one Tap Dial button with a Custom AI Behavior "seems to reset all the other buttons," and that each button and the dial lose their normal settings menu and have to be set up through AI from then on.
• The same reader said a smart button's regular behavior menu disappeared once an AI behavior was assigned to it.
• A reader in Sweden with the latest app and Bridge Pro firmware couldn't find the feature at all.

Neither Signify's announcement nor Hueblog lists the supported languages or regions, and neither says whether the AI part runs in the cloud.

What I'd do

If you have a Bridge Pro, try it on something low-stakes first. A lamp that comes on at dusk, not the switch by the front door everyone uses in the dark. Look at exactly which lights it touches before you leave it running.

I'd stay away from assigning AI behaviors to a Tap Dial or any switch the household depends on until those reports are confirmed or ruled out. Losing the normal button menu is a bad trade for a clever weekend rule.

And if the AI gets it wrong twice, try the zone trick: make a zone with only the lights you want, then ask again. The idea is right. The missing piece is an edit button.