HUE Controller

KNX-Ultimate video tutorials (YouTube playlist)

Everything available from one node

A consistent Controller experience

• One device-first Hue resource picker with autocomplete and refresh; the matching function is derived automatically.
• Clicking or focusing the device field always opens the complete Hue resource list, even after a device has been selected; typing filters it.
• Capability-aware light mappings: Dim, Tunable White, RGB/HSV and native effects follow the live dimming, color_temperature, color and effects properties of the selected Hue API v2 light resource.
• Bounded Light-editor readiness wait: a spinning hourglass is shown while the Hue Bridge loads its resources, polling every 500 ms and releasing the editor with a localized error after about 10 seconds. Save, close and function changes cancel the timer.
• Compact KNX mapping rows keep GA, DPT and Name on one line; DPT and Name controls use reduced widths, with Name allowed to contract on narrow editor trays without altering its stored value. Saved DPT values are retained while selector options load asynchronously.
• Optional KNX gateway: use Group Addresses or imported ETS names; compatible datapoints come from the selected gateway.
• Profile-driven Node-RED pins for validated Hue API v2 input and Hue event output where supported.
• Startup state reads, Hue-to-KNX status synchronisation and loop protection inherited by each private profile.
• Fully local migration for all fifteen deprecated node types, followed by an editable usage email draft, an optional support button in the final message, local review and manual Deploy.

Start in four steps

1. Configure the Hue Bridge once.
2. Add HUE Controller, then choose or refresh a Hue device; its Device type is filled automatically.
3. Select a KNX Gateway and map the available commands/statuses, or leave it at none for flow-only use.
4. Set the function-specific behaviour and Node-RED pins, deploy, and verify the live node status.

No KNX gateway? The Controller remains useful as a Hue-to-Node-RED integration. KNX fields are hidden and the flow options supported by the selected function remain available.

The sections below are the complete per-function reference consolidated from the former dedicated nodes.

Convert legacy HUE nodes

The migration button appears only when the Node-RED editor detects at least one legacy HUE node in the current flows. A link to the explanatory migration video on YouTube appears immediately before the same high-contrast orange button with white text in HUE Controller and every legacy HUE editor. The disclaimer confirms that no flow or node data leaves the browser.

Press Convert legacy HUE nodes and confirm. The browser performs the entire conversion locally and sends no flow, node, hue-config, knxUltimate-config, group-address, wiring, credential, name, position or node-ID data anywhere. After a successful conversion, it opens only an editable email draft addressed to the author without navigating away from Node-RED. The draft contains only the number of converted nodes and space for optional notes; you decide whether to send it, and it is never sent automatically. The final Node-RED message offers an optional support button, and the donation page opens only when that button is clicked.

Before starting, export a backup of your flows. The browser closes the current node editor and changes only the matched legacy HUE nodes into HUE Controller instances. All saved node properties, configuration references, positions, group membership and wiring remain unchanged. The workspace is marked dirty, but the tool never deploys it: review the result and click Deploy yourself. A changed node, locked flow or local conversion error leaves the workspace unchanged. Safety check: before Deploy, inspect every modified HUE node and verify its function, configuration references, input/output pins and wiring. When the process finishes, a fixed Node-RED message remains visible until you click OK.

Hue events remain status updates and do not become new Hue commands. HUE Controller contains private runtime, editor, template and translation profiles, so it does not depend on loading the deprecated node types. The original Hue Light node remains unchanged. Dedicated Hue nodes remain registered for existing flows, but are frozen and receive no new features or maintenance updates. Node-RED hides their special deprecated category from the palette; existing instances remain editable and deployable, use a lighter color than HUE Controller, are marked (deprecated) on the canvas, and show a migration notice at the top of their editor.

Device function

• Light / grouped light (light)
• Plug / outlet (plug)
• Button (button)
• Tap dial (relative_rotary)
• Motion (motion)
• Area motion (area_motion)
• Camera motion (camera_motion)
• Contact (contact)
• Light level (light_level)
• Temperature (temperature)
• Humidity (humidity)
• Scene (scene)
• Battery (device_power)
• Zigbee connectivity (zigbee_connectivity)
• Device software update (device_software_update)

Light / grouped light (light)

This node controls Philips Hue lights (single or grouped) and maps their commands/states to KNX.

General

Locate device

Use the Locate button (play icon) to start a Hue identify session for the selected resource. While the session is active the button switches to a stop icon and the bridge makes the light — or every light in the grouped resource — blink once per second. Press the button again to stop immediately; otherwise the session ends automatically after 10 minutes.

OPTIONS

Here you can link KNX Group Addresses to the available Hue commands/states.

Start typing in the GA field (name or Group Address); suggestions appear while you type.

Switch

Dim

Tunable White

RGB/HSV

For controlling the HSV “V” (brightness), use the standard controls under the Dim tab.

Effects

Non-Hue basic effects

Hue native effects

Use the Hue native effects table to map your KNX values to the effects supported by the selected light (for example candle, fireplace, prism). Each row links a KNX value (boolean, numeric or textual, depending on the datapoint you pick) with a Hue effect. On the KNX side you can:

• send the mapped value to activate that effect;
• optionally provide a status Group Address: the node emits the mapped value whenever the Hue bridge reports an effect change; if no mapping exists the raw effect name is sent (requires a textual DPT such as 16.xxx).

Behaviour

| Property | Description | | —————————————– | —————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————- | | Read status at startup | Read the Hue light status at node-red’s startup or node-red’s full deploy, and send that status to the KNX BUS | | KNX Brightness Status | Updates the KNX brightness group address status, whenever the Hue lamp is switched ON/OFF. The options are When Hue light is Off send 0%. When Hue On, restore previous value (Default KNX behaviour) ** andLeave as is (default Hue behaviour) ** . If you have KNX dimmer with brightness status, like MDT, the suggested option is When Hue light is Off send 0%. When Hue On, restore previous value (Default KNX behaviour) _ | | Update local cached Hue state from KNX bus writes | Advanced option, enabled by default. When enabled, writes arriving from the KNX bus also update the node’s local cached Hue state immediately, without waiting for feedback/events from the Hue bridge. This gives faster local reactions and more consistent immediate KNX read responses, especially while the light or grouped light is OFF. Disable it if you prefer the cache to follow only real feedback/events from the Hue bridge. | | Switch on behaviour | It sets the behaviour of your lights when switched on. You can choose from differents behaviours. Select color: ** the light will be switched on with the color of your choice. To change color, just CLICK on the color selector (under the _Select color_ control). **Select temperature and brightness: ** the light will be switched on with the temperature (Kelvin) and brightness (0-100) of your choice. **None: the light will retain its last status. In case you’ve enable the night lighting, after the night time ends, the lamp will resume the color/temperature/brightness state set at day time. | | Night Lighting | It allows to set a particular light color/brightness at nighttime. The options are the same as the daytime. You could select either a temperature/brightness or color. A cozy temperature of 2700 Kelvin, with a brightness of 10% or 20%, is a good choice for bathroom’s night light.| | Day/Night | Select the group address used to set the day/night behaviour. The group address value is _true if daytime, false if nighttime. | | Invert day/night value | Invert the values of Day/Night group address. Default value is unchecked . | | Read status at startup | Read the status at startup and emit the event to the KNX bus at startup/reconnection. (Default “no”)| | Force day mode | You can force the day mode by manually switching the light as described here: Switch to DAY mode by rapid switching the ligth off then on (This light only) ** does what described and acts only on this light.Switch to DAY mode by rapid switching the ligth off then on (apply yo ALL light nodes)** acts to ALL Light nodes, by setting the Day/Night group address to Day mode. | | Node Input/Output PINs | Hide or show the input/output PINs. Input/output PINS allow the node to accept msg input from the flow and send msg output to the flow. Input msg must follow the Hue API v.2 Standards. This is an example msg, that turns on the light: msg.on = {"on":true}. Please refer to the official Hue Api page |

Note

The Dimming function works in KNX mode start andstop ** . To start dimming, send only one “start” KNX telegram. To stop dimming, send a “stop” KNX telegram. Pleaseremember that** , when you set your wall swiches properties.

Plug / outlet (plug)

Hue Plug / Outlet

Overview

The Hue Plug node links a Philips Hue smart plug (service plug) with KNX group addresses so you can control power and track the state directly from the BUS.

• Supports on/off control and status feedback.
• Optional mapping of the Hue power_state (on / standby).
• Can expose Node-RED input/output pins to forward Hue events to flows or send advanced API payloads.

Configuration

KNX Mapping Tips

• Use a boolean datapoint (e.g. DPT 1.001) for both command and status.
• If you expose power_state, map it to a boolean GA (true = on, false = standby).
• For read requests (GroupValue_Read) the node returns the last cached Hue value.

Flow Integration

When Node I/O pins are enabled:

• Input: send Hue v2 payloads to perform advanced actions (e.g. msg.on = { on: true }).
• Output: receive an event object { payload: boolean, on, power_state, rawEvent } whenever Hue reports a change.

Hue API Reference

The node uses /resource/plug/{id} over HTTPS. Status changes are delivered via the Hue event stream and cached for KNX read responses.

Button (button)

The Hue Button node maps Hue button events to KNX group addresses and exposes the same events on its flow output via button.button_report.event.

Start typing in the GA field (name or Group Address) to link the KNX GA; devices appear while you type.

General

Switch

Dim

Behaviour

Outputs

1. Standard output

   msg.payload carries the boolean (or dim object) sent to KNX; msg.event is the Hue event string (e.g. short_release, repeat).

Details

msg.event mirrors button.button_report.event. The original Hue event is exposed in msg.rawEvent. Use the optional Status GA to keep the toggle state in sync with wall switches or other controllers.

Tap dial (relative_rotary)

The Hue Tap Dial node maps the rotary service of the Hue Tap Dial to KNX and forwards the raw Hue events to your flow. Use the refresh icon beside the device field after pairing a new dial on the bridge.

Tabs

• Mapping - select the KNX GA and DPT used for the rotation events. Supported datapoints: DPT 3.007 (relative dim), DPT 5.001 (absolute level 0-100 %) and DPT 232.600 (vendor colour control).
• Behaviour - show or hide the Node-RED output pin. When no KNX gateway is configured the output is kept enabled so Hue events still reach the flow.

General settings

Mapping tab

Outputs

ℹ️ KNX-specific widgets appear only after selecting a KNX gateway; the Mapping tab stays hidden until both the bridge and the gateway are configured.

Motion (motion)

This node listens to a Hue motion sensor and mirrors the events to KNX and/or your Node-RED flow.

Start typing the KNX device name or Group Address in the GA field; suggestions appear while you type. Hit the refresh button next to “Hue sensor” to reload the device list from the bridge if you add new sensors.

General

Mapping

Behaviour

ℹ️ KNX widgets remain hidden until you select a KNX gateway, making it easy to use the node purely as a Hue → Node-RED listener.

Output

1. Standard output — msg.payload (boolean)

   true on motion, false when motion ends.

Area motion (area_motion)

The Hue Motion Area node listens to MotionAware area motion events (Hue Bridge Pro) and mirrors the aggregated detected/not detected state to KNX or your Node-RED flow.

Start typing in the GA field (name or Group Address) to link the KNX GA; suggestions appear while you type.

General

Mapping

Behaviour

Outputs

1. Standard output

   msg.payload (boolean): true when motion is detected in the area, otherwise false.

Details

msg.payload carries the latest MotionAware area motion status (aggregated from the underlying sensors).

Camera motion (camera_motion)

The Hue Camera Motion node listens to Philips Hue camera motion services and mirrors the detected/not detected state to KNX.

Start typing in the GA field (name or Group Address) to link the KNX GA; devices appear while you type.

General

Mapping

Outputs

1. Standard output

   msg.payload (boolean): true when motion is detected; otherwise false

Details

msg.payload carries the latest motion status reported by the Hue camera service.

Contact (contact)

This node forwards events from a Hue contact sensor and maps them to KNX group addresses.

Start typing in the GA field, the name or group address of your KNX device, the avaiable devices start showing up while you’re typing.

General

Outputs

1. Standard output

   payload (boolean) : the standard output of the command.

Details

msg.payload carries the raw Hue event (boolean/object). Use it for custom logic if needed.

Light level (light_level)

This node reads lux events from a Hue Light Sensor and maps them to KNX.

It emits the ambient illuminance (lux) each time it changes. Start typing in the GA field (name or Group Address) to link the KNX GA; devices appear while you type.

General

Mapping

Outputs

1. Standard output

   payload (number): current lux value.

Details

msg.payload carries the numeric lux value. Use it for custom logic if needed.

Temperature (temperature)

This node reads temperature (°C) from a Hue temperature sensor and maps it to KNX.

Start typing in the GA field (name or Group Address) to link the KNX GA; devices appear while you type.

General

Mapping

Outputs

1. Standard output

   msg.payload (number): current temperature in °C

Details

msg.payload carries the numeric temperature value.

Humidity (humidity)

This node reads relative humidity (%) from a Hue humidity sensor and maps it to KNX.

Start typing in the GA field (name or Group Address) to link the KNX GA; devices appear while you type.

General

Mapping

Outputs

1. Standard output

   msg.payload (number): current relative humidity in %

Details

msg.payload carries the numeric humidity value (percentage).

Scene (scene)

The Hue Scene node exposes Hue scenes to KNX and can forward the raw Hue events to a Node-RED flow. The scene field supports autocomplete; use the refresh icon after adding scenes on the bridge so the list stays up to date.

Tabs at a glance

• Mapping - link KNX group addresses to the selected Hue scene. DPT 1.xxx performs boolean recall, while DPT 18.xxx sends a KNX scene number.
• Multi scene - build a rule list that associates KNX scene numbers with different Hue scenes and chooses whether each scene is recalled as active, dynamic_palette or static.
• Behaviour - toggle the Node-RED output pin. When no KNX gateway is configured the pin remains enabled so bridge events still reach the flow.

General settings

Mapping tab

Multi scene tab

ℹ️ KNX-specific widgets only appear after a KNX gateway is selected. The Mapping tabs remain hidden until both the bridge and the gateway are configured.

Battery (device_power)

This node exposes the battery level of a Hue device to KNX and raises an event whenever the value changes.

Start typing the KNX device name or Group Address in the GA field; matching entries appear while you type. Use the refresh icon next to Hue sensor to reload the list from the Hue bridge after adding new devices.

General

Mapping

Behaviour

ℹ️ KNX mapping widgets remain hidden until a KNX gateway is selected. This keeps the editor tidy when the node is used only to forward Hue events into Node-RED.

Zigbee connectivity (zigbee_connectivity)

This node retrieves the Zigbee connectivity status from a Hue device and exposes it to KNX.

Start typing the KNX device name or Group Address in the GA field; suggestions appear while you type.

General

Mapping

Outputs

1. Standard output

   payload (boolean): connectivity state.

Details

msg.payload carries the boolean state (true/false).
msg.status contains a textual status: one of connected, disconnected, connectivity_issue, unidirectional_incoming .

Device software update (device_software_update)

This node monitors whether a selected Hue device has a software update available and publishes the status to KNX.

Start typing the name or group address of your KNX device in the GA field, the avaiable devices start showing up while you’re typing.

General

Mapping

Outputs

1. Standard output

   payload (boolean): update flag.

   status (string): one of no_update, update_pending, ready_to_install, installing .