HueMagic provides several input and output nodes for Node-RED and is the most in-depth and easy to use solution to control Philips Hue bridges, lights, groups, scenes, rules, automations, buttons/switches, dials, doorbells, speakers, motion sensors, cameras, contact sensors, temperature sensors, light level sensors and the Hue Play HDMI Sync Box.
- Simple and comprehensive control of the Hue Bridge and connected devices
- Automatic discovery of Philips Hue bridges as well as devices, scenes & groups…
- Output and input of multiple color code definitions (HEX, RGB & human readable color names)
- Automatic color temperature & brightness setting based on the current time
- Event-based status messages for all devices connected to the Hue Bridge
- Pairing of new devices without app enforcement (TouchLink)
- Automatic firmware updates to the Hue Bridge and connected devices
- Activating / deactivating of sensors, rules & automations on the Hue Bridge
- Extended alarm and colorloop effects on light bulbs and whole groups
- A large selection of animations and the option to create custom animations
- Additive state settings on all nodes with multiple commands
- Change states even if the corresponding devices are offline or turned off
- Real-time status messages for each node & in the Node-RED UI (SSE)
- Nodes can stay passive and only answer the commands you send them
- Uses the latest CLIP/v2 API version of the Philips Hue Bridge
- Supports the Hue Bridge Pro as well as the square-shaped Hue Bridge
- Supports Hue Secure cameras, video doorbells, contact sensors and speakers
- Controls the Hue Play HDMI Sync Box over its own local API
- Turns your lights into motion sensors with MotionAware (Hue Bridge Pro)
- Plays the built-in light effects and the sunrise / sunset simulation
- Sets the behaviour of a light after a power cut
- Switches a Hue wall switch module between rocker and pushbutton mode
- Recalls scenes with their own transition time and brightness
- Calibrates temperature sensors and the darkness threshold of light level sensors
- Available in ten languages, including the complete node documentation
HueMagic was written for Node.js 18+ and Node-RED v3+. It supports the square-shaped Hue Bridge with the firmware 1948086000+ or higher as well as the Hue Bridge Pro. You can install HueMagic directly via the Node-RED Palette Manager or manually using npm / yarn.
npm install node-red-contrib-huemagic
Please make sure that you deactivate other Hue-related nodes in Node-RED and meet the minimum requirements of Node.js and the Philips Hue Bridge firmware!
- Hue Bridge
- Hue Magic
- Hue Light
- Hue Group
- Hue Scenes
- Hue Buttons
- Hue Motion
- Hue Contact
- Hue Temperature
- Hue Brightness
- Hue Speaker
- Hue Automation
- Hue Rule
- Hue Sync Box
HueMagic provides a large selection of full featured sample flows for all nodes. You can find these examples in the examples folder on GitHub or directly in Node-RED. To import a full featured example into your Node-RED interface, click on the Node-RED menu icon, then select "Import" and navigate to "Examples" in the sidebar of the popup. Then select the HueMagic folder, the language you are most comfortable with and your desired node to import a sample flow. The examples are translated into all ten languages, with one folder per language.
The "Hue Bridge" node is a universal node that can output all settings of the bridge and status messages from other nodes.
First select the desired Hue Bridge. You can optionally deactivate all automatic status messages for this node by clicking the setting “Skip global device updates / messages on this node”. The node will then no longer issue device updates.
Alternatively, you can also choose whether the initialization messages of all nodes should not be suppressed when Node-RED is started. If you activate this setting, you will receive a status message from all resources connected to the bridge after each deployment.
Outputs the current status / settings of the bridge as soon as the following message has been sent to the node. Alternatively, you can also press the button in the Node-RED interface without having to pass a message to the node beforehand.
| Property | Description |
|---|---|
| payload (boolean) | Returns the current status of the bridge |
You can couple new or old devices to the bridge using a "TouchLink scan" (e.g. after a reset). To do this, transfer the object msg.payload with the following content:
| Property | Description |
|---|---|
| touchLink (boolean) | Couples old or new devices with the bridge |
With the "fetch" command you can output a list of specific devices that are currently connected to the bridge. To do this, transfer the object msg.payload with the following content:
| Property | Description |
|---|---|
| fetch (string / array [string, ...]) | Can accept light, group, button, motion, contact, temperature, light_level or rule as value(s) |
You can use the following command to change specific settings on the bridge. Please note that changing the network settings requires reconfiguring the bridge on HueMagic. Transfer the object msg.payload.settings with the following setting options to the node:
| Property | Description |
|---|---|
| name (string) | Changes the name of the bridge and must contain at least 4 to a maximum of 16 characters |
| zigbeeChannel (int) | Changes the current ZigBee channel (either 11, 15, 20, 25 or 0) |
| ipAddress (string) | Changes the IP address in the network settings |
| dhcpEnabled (boolean) | true, activates DHCP in the network settings, false, deactivates the setting |
| netmask (string) | Changes the network mask in the network settings |
| gateway (string) | Specifies the gateway in the network settings |
| proxyAddress (string) | Sets a proxy address in the network settings |
| proxyPort (string / int) | Specifies the port of the proxy in the network settings |
| timeZone (string) | Changes the currently set time zone on the bridge |
The status reports of the "Hue Bridge" node are dynamic. Although they follow a certain pattern, their output can vary depending on what action has just been carried out on the node.
| Property | Description |
|---|---|
| id (string) | Unique ID of the Hue Bridge |
| name (string) | Currently set name |
| factoryNew (boolean) | Indicator whether the bridge is brand new |
| replacesBridgeId (string / boolean) | Outputs the old bridge ID (if a migration was carried out) or outputs false |
| dataStoreVersion (string) | Version of the data store |
| starterKitId (string / boolean) | Name of the starter kit created in the factory or false |
| softwareVersion (string) | Software version of the bridge |
| apiVersion (string) | API version of the bridge |
| zigbeeChannel (int) | Currently used ZigBee channel |
| macAddress (string) | MAC address of the bridge |
| ipAddress (string) | IP address of the bridge |
| dhcpEnabled (boolean) | Indicates whether DHCP is enabled |
| netmask (string) | Netmask of the bridge |
| gateway (string) | Gateway of the bridge |
| proxyAddress (string / boolean) | Currently used proxy address or false |
| proxyPort (string) | Currently used proxy port |
| utcTime (string) | UTC time on the bridge |
| timeZone (string) | Currently set time zone on the bridge |
| localTime (string) | Local time zone |
| portalServicesEnabled (boolean) | Indicates whether portal services are enabled |
| portalConnected (boolean) | Indicates whether the bridge is connected to the portal |
| linkButtonEnabled (boolean) | Indicates whether the link button is enabled |
| touchlinkEnabled (boolean) | Indicates whether TouchLink is enabled |
| autoUpdatesEnabled (boolean) | Indicates whether the HueMagic will automatically check for updates |
| users (array [object, ...]) | List of all users on the bridge (array with objects) |
| updated (string) | Time of the last update of the resource by HueMagic (ISO 8601) |
| model (object) | Contains the model information of the bridge under id, manufacturer and name |
If the "fetch" command has been used on the node, the bridge outputs the corresponding results under the msg.results object. The object contains the queried resource groups, which in turn contain all the corresponding resources in the form of an array.
Unless deactivated, the node outputs an updated status message for each resource on the bridge. The status message under msg.updated follows the pattern of the respective resource and varies depending on the type of device that was last updated.
If the status of the node has changed via a certain command, the entire command that was executed is also output. Otherwise this object will not be output by the node.
The "Hue Magic" node can apply complex and custom animations to lights and groups.
First give the node a name in order to clearly classify your animation in the Node-RED interface. You then have the choice between the options "Loop" and "Restore". Select the loop option if you want your animation to run endlessly on a light or group until you manually stop it. If you want to restore the previous state of the target resource (light / group) after the animation has ended, check the "Restore" option. Otherwise the last frame of the animation remains on the respective resource.
Below you can choose from pre-made animations from HueMagic. Click on your desired animation to set it.
Choose one of the included animations to apply to a Hue Light or Hue Group node.
To play or stop an animation, pass an object with the following content to the node:
| Property | Description |
|---|---|
| payload (boolean) | true, starts the animation, false, stops the animation |
If you pass your own animation to the node, the preselected, pre-defined animation (if set) will be temporarily replaced by yours. Own HueMagic animations are a sequence of commands that have been combined in an array. Each array element forms a step - whereby a step can also consist of several frames (transition effects).
Create an array with the respective animation steps in the form of an object and transfer it to the HueMagic node under msg.payload.steps.
| Property | Description |
|---|---|
| delay (int) | Number of milliseconds to wait until this step is carried out |
| animation (object) | The object contains the action(s) to be carried out in this step. Identical parameters as for the "Hue Light" & "Hue Group" nodes |
If you have created your own animation that you would like to share with others, add it at /huemagic/animations/XXX-youranimationname.json and create a pull request. Take a look at this directory for structure help.
This example shows what a simple animation could look like. In the first step, the delay of 500 milliseconds is waited for. The color of the light is then slowly changed to red over a period of one second. As soon as the light has completely changed to red, the second step is carried out, which also has a delay of 500 milliseconds. Finally the color changes to blue.
If you have set the animation to loop, this process is repeated indefinitely until you manually stop the animation or redeploy the node.
Pass the following object in msg.payload to play the example animation.
{
"animate": true,
"steps": [
{
"delay": 500,
"animation": {
"hex": "#FF0000",
"transitionTime": 1
}
},
{
"delay": 500,
"animation": {
"hex": "#0000FF",
"transitionTime": 1
}
}
]
}
Sometimes it makes sense to play an animation in a disorderly manner - e.g. if fire should be imitated more realistically. To play the individual steps randomly, you can pass the following command to msg.payload.specials:
| Property | Description |
|---|---|
| randomOrder (boolean / any) | true, activates the random playback of the individual animation steps |
This node does not output any status messages. Please connect the output of the node with a group instead of individual lights if you want to animate several lights at the same time with the same animation. The previews of the pre-made animations are simulations and may differ slightly (timing, colors) from the actual animation on a resource.
The "Hue Light" node can control lights connected to the bridge and receive their status messages.
Select the pre-configured Hue Bridge and hit the search button to find all the available lights. If you already know the ID of a light, you can also enter it here manually. You can either assign a new name for the light internally or choose the predefined name. Optionally, you can also deactivate all automatic status messages for this node by clicking the setting "Skip events from node". The node will then no longer issue device updates. Alternatively, you can also choose whether the node's initialization message should not be suppressed when Node-RED is started. If you activate this setting, you will receive a status message for the currently selected light after each deployment. If you would rather have the node stay silent until you send it something, activate "Only report after a command". It then ignores changes from the app or a switch and only answers your own commands.
If you activate the setting "Activate color naming", the node will try to describe the currently set light color for each status message. You will then receive an additional parameter with the English description of the currently set color in the output.
If you do not select a light and use the node configuration in this way, the node works in the so-called "universal mode". In this mode, the node receives and outputs all status messages of the same type. You can also apply settings in universal mode to a specific light by transferring the corresponding light ID as a string in msg.topic together with your settings.
Outputs the current status of the light as soon as a msg.payload object with the following content has been passed to the node. Alternatively, you can also press the button in the Node-RED interface without having to pass a message to the node beforehand.
| Property | Description |
|---|---|
| status (boolean) | Returns the current status of the light |
To quickly switch a light on or off in simple mode, pass an object with the following content to the node:
| Property | Description |
|---|---|
| payload (boolean) | true switches the light on, false switches it off |
In addition to simply switching it on and off, there are also many other options available for controlling the light. All nodes in HueMagic can be controlled with additive commands. This means that you can first pass one setting and then another setting in a later command without discarding the previous setting. Transfer the following parameters to a msg.payload object to make more extensive settings on the light:
| Property | Description |
|---|---|
| on (boolean) | true switches the light on, false switches it off |
| toggle (boolean / any) | Toggles between switching on and off, depending on the previous status of the light |
| brightness (int / string) | Percentage value of the light brightness (0-100) or a string with the value auto to automatically set the brightness based on the current time |
| brightnessLevel (int) | Numerical value of the light brightness (0-254) |
| incrementBrightness (int / boolean) | Specifies by how many percent the light should be made brighter or true to make the light brighter in 10% steps |
| decrementBrightness (int / boolean) | Specifies the percentage by which the light should be made darker or true to make the light darker in 10% steps |
| color (string) | random to set a random color or an English color name (e.g. red) |
| hex (string) | Color value in hexadecimal in the form of a string |
| rgb (array [0,0,0]) | Color value in RGB format in the form of an array |
| xyColor (object {x [float], y [float]}) | Color value in the XY color format in the form of an object |
| gradient (object {hex […]}) | An object with a supported color object (e.g. hex, rgb, ...) and several colors to set a gradient to supported lights. An optional mode spreads the colors as interpolated_palette, interpolated_palette_mirrored, random_pixelated or segmented_palette |
| mixColor (object) | A color to be mixed with the current light color. Can accept color, hex, rgb or xyColor objects and optionally amount (int) to indicate the mixing ratio in percent |
| image (string) | Path of an image (local or on the web) to set the current color of the light to the average color of the image |
| saturation (int) | Percentage of the saturation of the current color (beta) |
| colorTemp (int / string) | Value between 153 and 500 to set the color temperature of the light or the values cold, normal, warm, hot and auto - where auto is the color temperature based on the current time |
| incrementColorTemp (int / boolean) | Value by how much the color temperature should be warmer or true to make the color temperature warmer in steps of 50 |
| decrementColorTemp (int / boolean) | Value by how much the color temperature should be colder or true to make the color temperature colder in steps of 50 |
| transitionTime (float) | Transition time of the current setting in seconds. If 0 is entered, the light changes to the desired setting immediately. If 3 is entered, the light changes to the desired setting with a slight transition in the next 3 seconds |
| effect (string / boolean) | Plays one of the built-in effects of the light, e.g. candle, fire, sparkle or prism. false stops it again. Which effects a light knows is listed under msg.info.model.effects |
| effectSpeed (float) | Speed of the effect between 0 and 1 (only on lights that support the newer effects_v2) |
| timedEffect (string / boolean) | Plays a sunrise or sunset simulation, false stops it again. Which of them a light knows is listed under msg.info.model.timedEffects |
| duration (float) | Duration of the timed effect in seconds (maximum 6 hours) |
| powerUp (string / object) | Behaviour of the light after a power cut. Either one of safety, powerfail, last_on_state or custom as a string, or an object with preset: "custom" and on, brightness, colorTemp or xyColor |
| colorloop (float) | Plays a "colorloop" animation for the selected duration in seconds and then switches back to the original state of the light |
| alert (float) | Plays an "alert" animation for the selected duration in seconds and then switches back to the original state of the light |
As soon as a change in the light settings has been detected (regardless of whether via Node-RED or externally), the following status message is returned by the node:
| Property | Description |
|---|---|
| on (boolean) | State of the light, where true stands for on and false for off |
| brightness (int / boolean) | Current brightness in percent or false, if the light does not support a brightness setting |
| brightnessLevel (int / boolean) | Current brightness from 0-254 or false, if the light does not support a brightness setting |
| reachable (boolean / string) | true if the light is connected to the bridge, unknown if the connection status deviates |
| connectionStatus (string) | The current connection status with the bridge in the form of a string. Can contain connected, disconnected, connectivity_issue or unidirectional_incoming as a value |
| rgb (array [int, int, int] / optional) | Current light color in the form of an RGB value, if the light can display colors |
| hex (string / optional) | Current light color in the form of a hexadecimal value if the light can display colors |
| xyColor (object {x [float], y [float]} / optional) | Current light color in the form of an XY value, if the light can display colors |
| color (string / optional) | Current light name in English, if the light can display colors and the corresponding setting of the node has been activated |
| gradient (object / optional) | Current gradient setting with all available color units in the form of an array, if the light supports gradient settings, where colors outputs the colors, numColors the number of set colors in the gradient and totalColors the maximum possible Number of colors the resource can support in the gradient |
| colorTemp (int / boolean / optional) | Current color temperature of the light, if the light can display color temperatures and a color temperature has been set |
| colorTempName (string / optional) | Current color temperature of the light in the form of a descriptive string with the values cold,normal, warm or hot, if the light can display color temperatures and a color temperature has been set. Otherwise unknown is output |
| effect (string / optional) | The effect that is currently playing on the light or no_effect, if the light supports effects |
| timedEffect (string / optional) | The timed effect that is currently playing or no_effect, if the light supports a sunrise / sunset simulation |
| powerUp (string / optional) | The currently set behaviour of the light after a power cut, if the light supports it |
| updated (string) | Time of the last update of the resource by HueMagic (ISO 8601) |
| Property | Description |
|---|---|
| id (string) | Indicates the new ID of the light |
| idV1 (string / boolean) | Indicates the old ID of the light |
| uniqueId (string) | The unique ID of the light |
| deviceId (string) | The unique ID of the device |
| name (string) | The currently set name of the light |
| type (string) | The type of light (always light) |
| softwareVersion (string) | The current firmware of the light |
| model (object) | Contains the model information of the light under id, manufacturer, name, type, certified, friendsOfHue, colorGamut and colorGamutType |
Lists individual parameters in the form of an object that have changed compared to the last state of the light. If no changes have been registered, this object is empty.
Contains the complete status object (see output values above) of the last status before the last change. If the last state of HueMagic has not yet been registered, it will output false.
If the status of the node has changed via a certain command, the entire command that was executed is also output. Otherwise this object will not be output by the node.
The "Hue Group" node can control several lights behind a group on the bridge at the same time.
Select the pre-configured Hue Bridge and hit the search button to find all available groups. If you already know the ID of a group, you can also enter it here manually. You can either assign a new name for the group internally or choose the predefined name. Optionally, you can also deactivate all automatic status messages for this node by clicking the setting "Skip events from node". The node will then no longer issue any updates. Alternatively, you can also choose whether the node's initialization message should not be suppressed when Node-RED is started. If you activate this setting, you will receive a status message for the currently selected group after each deployment. If you would rather have the node stay silent until you send it something, activate "Only report after a command". It then ignores changes from the app or a switch and only answers your own commands.
If you do not select a group and use the node configuration in this way, the node works in the so-called "universal mode". In this mode, the node receives and outputs all status messages of the same type. You can also apply settings in universal mode to a specific group by transferring the corresponding group ID as a string in msg.topic together with your settings.
Outputs the current status of the group as soon as a msg.payload object with the following content has been passed to the node. Alternatively, you can also press the button in the Node-RED interface without having to pass a message to the node beforehand.
| Property | Description |
|---|---|
| status (boolean) | Returns the current status of the group |
To quickly turn an entire group on or off in simple mode, pass an object with the following content to the node.
| Property | Description |
|---|---|
| payload (boolean) | true switches the whole group on, false switches them off |
In addition to simply switching it on and off, there are also many other options available for controlling the group. All nodes in HueMagic can be controlled with additive commands. This means that you can first pass one setting and then another setting in a later command without discarding the previous setting. Transfer the following parameters to an msg.payload object to make more extensive settings for the group:
| Property | Description |
|---|---|
| on (boolean) | true switches the entire group on, false switches it off |
| toggle (boolean / any) | Toggles between switching on and off, depending on the previous status of the group |
| brightness (int / string) | Percentage value of the light brightness (0-100) or a string with the value auto to automatically set the light brightness based on the current time |
| brightnessLevel (int) | Numerical value of the light brightness (0-254) |
| incrementBrightness (int / boolean) | Specifies by how many percent the group should be made brighter or true to make the group brighter in 10% steps |
| decrementBrightness (int / boolean) | Specifies the percentage by which the group should be made darker or true to make the group darker in 10% steps |
| color (string) | random to set a random color or an English color name (e.g. red) |
| hex (string) | Color value in hexadecimal in the form of a string |
| rgb (array [0,0,0]) | Color value in RGB format in the form of an array |
| xyColor (object {x [float], y [float]}) | Color value in the XY color format in the form of an object |
| image (string) | Path of an image (local or on the web) to set the current color of the group to the average color of the image |
| colorTemp (int / string) | Value between 153 and 500 to set the color temperature of the group or the values cold, normal, warm, hot and auto - where auto is the color temperature based on the current time |
| transitionTime (float) | Transition time of the current setting in seconds. If 0 is passed, the group changes to the desired setting immediately. If you pass it to 3, the group changes to the desired setting with a slight transition in the next 3 seconds |
| colorloop (float) | Plays a “colorloop” animation for the selected duration in seconds and then changes back to the group's original state |
| alert (float) | Plays an "alert" animation for the selected duration in seconds and then switches back to the original status of the group |
If a change in the group is detected, the following status message is returned from the node.
In contrast to the "Hue Light" node, you have less status information available here, as a group can contain many different device types with different values that cannot be combined. Color information is therefore only reported if all lights of the group agree on it.
| Property | Description |
|---|---|
| on (boolean) | State of the group, where true stands for on and false for off |
| brightness (float / boolean) | Brightness of the group in percent or false if the group cannot be dimmed |
| brightnessLevel (int / boolean) | Brightness of the group as a numerical value (0-254) or false if the group cannot be dimmed |
| rgb (array [0,0,0]) | Current color of the group in RGB format (only if available) |
| hex (string) | Current color of the group in hexadecimal format (only if available) |
| color (string) | Human readable name of the current color (only if "Colornamer" is activated) |
| xyColor (object {x [float], y [float]}) | Current color of the group in the XY color format (only if available) |
| colorTemp (int) | Currently set color temperature of the group (only if available) |
| updated (string) | Time of the last update of the resource by HueMagic (ISO 8601) |
| Property | Description |
|---|---|
| id (string) | Indicates the new ID of the group |
| idV1 (string / boolean) | Indicates the old ID of the group |
| name (string) | The currently set name of the group |
| resources (object) | Contains all devices/resources behind the group |
| type (string) | The type of the group (always group) |
Lists individual parameters in the form of an object that have changed compared to the last state of the group. If no changes have been registered, this object is empty.
Contains the complete status object (see output values above) of the last status before the last change. If the last state of HueMagic has not yet been registered, it will output false.
If the status of the node has changed via a certain command, the entire command that was executed is also output. Otherwise this object will not be output by the node.
The "Hue Scene" node can resume scenes saved in the bridge and apply them to certain groups.
Select the pre-configured Hue Bridge and hit the search button to find all the available scenes. The scenes are sorted by room or zone first and then by their name, so the scenes of one room always stay together in the list. If you already know the ID of the scene, you can also enter it here manually. Alternatively, you can also assign an internal name for the scene or choose the predefined name of the scene.
You can activate a predefined scene by transferring an object with the following content:
| Property | Description |
|---|---|
| payload (boolean) | Activates a preconfigured scene |
| transitionTime (float) | Transition time of the scene in seconds. If 0 is passed, the scene is applied immediately. If you pass it to 3, the lights fade into the scene within the next 3 seconds. The bridge accepts up to 6000 seconds |
| brightness (float) | Brightness of the whole scene in percent (0 – 100), so you can recall one and the same scene brighter or dimmer depending on the time of day |
Both settings are only available for normal scenes. A smart scene follows the times you have defined for it in the Philips Hue app.
If you operate this node in the so-called "universal mode" and have not set a scene in the node configuration, you can also transfer your desired scene to the node as a command. To do this, pass a msg.payload object with the following content:
| Property | Description |
|---|---|
| scene (string) | ID of the scene to be activated on the bridge |
Connect the output of this node to one or more groups to apply a scene to specific groups. Alternatively, you have the option of doing this "dynamically" by passing an msg.payload object with the following content to the node:
| Property | Description |
|---|---|
| group (string / array [string,…]) | ID of the group or an array with the IDs of several groups in order to limit the scene to these groups |
This node does not issue any status messages. Please also note that you can only apply scenes to groups if these are already linked to the respective scene on the bridge. Otherwise nothing will be applied.
The "Hue Buttons" node receives switching events from input devices connected to the bridge. Besides switches and dials it also covers the Hue Secure video doorbell.
Select the pre-configured Hue Bridge and hit the search button to find all the available switches/buttons. If you already know the ID of the switches/buttons, you can also enter it here manually. You can either assign a new name for the switches/buttons internally or keep the predefined name of the device. Optionally, you can also deactivate all automatic status messages for this node by clicking the setting "Skip events from node". The node will then no longer output any switching events. Alternatively, you can also choose whether the node's initialization message should not be suppressed when Node-RED is started. If you activate this setting, you will receive a status message for the currently selected switches/buttons after each deployment. If you would rather have the node stay silent until you send it something, activate "Only report after a command". It then ignores changes from the app or a switch and only answers your own commands.
If you do not select a switch/button and use the node configuration in this way, the node works in the so-called "universal mode". In this mode, the node receives and outputs all status messages of the same type.
Outputs the current status of the switch/button as soon as a msg.payload object with the following content has been passed to the node. Alternatively, you can also press the button in the Node-RED interface without having to pass a message to the node beforehand.
| Property | Description |
|---|---|
| status (boolean) | Returns the current status of the switch/button |
A Hue wall switch module can either work as a rocker or as a pushbutton. Which modes your device supports is reported under msg.info.switchModes. To change it, pass an object with the following content:
| Property | Description |
|---|---|
| switchMode (string) | One of the supported modes, e.g. switch_dual_rocker or switch_dual_pushbutton |
As soon as a key has been pressed or a dial has been turned, the following status message is returned by the node:
| Property | Description |
|---|---|
| reachable (boolean / string) | true if the switch/button is connected to the bridge, unknown if the connection status deviates |
| connectionStatus (string) | The current connection status with the bridge in the form of a string. Can contain connected, disconnected, connectivity_issue or unidirectional_incoming as a value |
| button (int / boolean) | Numeric ID of the key that was last pressed or false if no key was pressed |
| action (string / boolean) | false if no key was pressed or initial_press, repeat , short_release, long_press, long_release or double_short_release in the form of a string |
| rotation (object / boolean) | false if the device has no dial or was not turned, otherwise an object describing the last rotation (see below) |
| doorbell (boolean) | true if the press came from a Hue Secure video doorbell |
| updated (string) | Time of the last update of the resource by HueMagic (ISO 8601) |
Devices with a rotating bezel like the Hue Tap Dial Switch or the Lutron Aurora report their movement here.
| Property | Description |
|---|---|
| action (string) | start for the beginning of a movement or repeat while it continues |
| direction (string) | clock_wise or counter_clock_wise |
| clockwise (boolean) | true if the dial was turned clockwise |
| steps (int) | Number of steps that were turned, where 1000 steps correspond to a full rotation |
| degrees (int) | The turned steps converted into degrees |
| duration (int) | Duration of the movement in milliseconds |
| Property | Description |
|---|---|
| id (string) | Indicates the new ID of the switch/button |
| idV1 (string / boolean) | Indicates the old ID of the switch/button |
| uniqueId (string) | The unique ID of the switch/button |
| deviceId (string) | The unique ID of the device |
| name (string) | The currently set name of the switch/button |
| type (string) | The type of the switch/button (always button) |
| softwareVersion (string) | The current firmware of the switch/button |
| battery (float / boolean) | The current battery level of the switch/button, false, when there is no battery |
| batteryState (string / boolean) | The current status of the battery level. Can contain normal, low or critical as a value, false, when there is no battery |
| switchMode (string / boolean) | Currently set mode of a wall switch module or false. Can contain switch_single_rocker, switch_single_pushbutton, switch_dual_rocker or switch_dual_pushbutton as a value |
| switchModes (array / boolean) | All modes the device supports or false |
| model (object) | Contains the model information of the switch/button under id , manufacturer, name, type and certified |
Lists individual parameters in the form of an object that have changed compared to the last state of the switch/button. If no changes have been registered, this object is empty.
Contains the complete status object (see output values above) of the last status before the last registered change. If the last state of HueMagic has not yet been registered, it will output false.
If the status of the node has changed via a certain command, the entire command that was executed is also output. Otherwise this object will not be output by the node.
The "Hue motion" node can register and report movements from a suitable sensor on the bridge. Besides the classic motion sensor it also covers Hue Secure cameras and, on the Hue Bridge Pro, the MotionAware areas that turn your lights into motion sensors.
Select the pre-configured Hue Bridge and click the search button to find all the available sensors. If you already know the ID of the sensor, you can also enter it here manually. You can either assign a new name for the sensor internally or choose the predefined name of the sensor. Optionally, you can also deactivate all automatic status messages for this node by clicking the setting "Skip events from node". The node will then no longer issue device updates. Alternatively, you can also choose whether the node's initialization message should not be suppressed when Node-RED is started. If you activate this setting, you will receive a status message for the currently selected sensor after each deployment. If you would rather have the node stay silent until you send it something, activate "Only report after a command". It then ignores changes from the app or a switch and only answers your own commands.
If you do not select a sensor and use the node configuration in this way, the node works in the so-called "universal mode". In this mode, the node receives and outputs all status messages of the same type. You can also apply settings in universal mode to a specific sensor by transferring the corresponding sensor ID as a string in msg.topic together with your settings.
Outputs the current status of the sensor as soon as a msg.payload object with the following content has been transferred to the node. Alternatively, you can also press the button in the Node-RED interface without having to pass a message to the node beforehand.
| Property | Description |
|---|---|
| status (boolean) | Returns the current status of the sensor |
If necessary, the sensor can be turned on and off remotely. If the sensor has been turned off, it no longer registers any movements and accordingly no longer outputs them. To do this, pass an object with the following content:
| Property | Description |
|---|---|
| payload (boolean) | true turns the sensor on, false turns it off |
Cameras and MotionAware areas can be made more or less sensitive. The highest value your device accepts is reported under sensitivityMax. To do this, pass an object with the following content:
| Property | Description |
|---|---|
| sensitivity (int) | Sensitivity between 0 and the reported maximum |
As soon as the sensor has registered a movement, the following status message is returned by the node:
| Property | Description |
|---|---|
| active (boolean) | Indicates whether the sensor is switched on or off |
| reachable (boolean / string) | true if the sensor is connected to the bridge, unknown if the connection status deviates |
| connectionStatus (string) | The current connection status with the bridge in the form of a string. Can contain connected, disconnected, connectivity_issue or unidirectional_incoming as a value |
| motion (boolean) | Indicates whether a motion has been registered |
| sensitivity (int / optional) | Currently set sensitivity, if the source supports it |
| sensitivityMax (int / optional) | Highest sensitivity the source accepts, if it supports it |
| updated (string) | Time of the last update of the resource by HueMagic (ISO 8601) |
| Property | Description |
|---|---|
| id (string) | Indicates the new ID of the sensor |
| idV1 (string / boolean) | Indicates the old ID of the sensor |
| uniqueId (string) | The unique ID of the sensor |
| deviceId (string) | The unique ID of the device |
| name (string) | The currently set name of the sensor |
| type (string) | The type of the source. Can contain motion, camera_motion, grouped_motion, convenience_area_motion or security_area_motion as a value |
| softwareVersion (string) | The current firmware of the sensor |
| battery (float) | The current battery level of the sensor |
| batteryState (string) | The current status of the battery level. Can contain normal, low or critical as a value |
| model (object) | Contains the model information of the sensor under id, manufacturer, name, type and certified |
Lists individual parameters in the form of an object that have changed compared to the last state of the sensor. If no changes have been registered, this object is empty.
Contains the complete status object (see output values above) of the last status before the last registered change. If the last state of HueMagic has not yet been registered, it will output false.
If the status of the node has changed via a certain command, the entire command that was executed is also output. Otherwise this object will not be output by the node.
The "Hue Contact" node reports whether a contact sensor (e.g. Hue Secure) is currently open or closed.
Select the pre-configured Hue Bridge and click the search button to find all the available sensors. If you already know the ID of the sensor, you can also enter it here manually. You can either assign a new name for the sensor internally or choose the predefined name of the sensor. Optionally, you can also deactivate all automatic status messages for this node by clicking the setting "Skip events from node". The node will then no longer issue device updates. Alternatively, you can also choose whether the node's initialization message should not be suppressed when Node-RED is started. If you activate this setting, you will receive a status message for the currently selected sensor after each deployment. If you would rather have the node stay silent until you send it something, activate "Only report after a command". It then ignores changes from the app or a switch and only answers your own commands.
If you do not select a sensor and use the node configuration in this way, the node works in the so-called "universal mode". In this mode, the node receives and outputs all status messages of the same type. You can also apply settings in universal mode to a specific sensor by transferring the corresponding sensor ID as a string in msg.topic together with your settings.
Outputs the current status of the sensor as soon as a msg.payload object with the following content has been transferred to the node. Alternatively, you can also press the button in the Node-RED interface without having to pass a message to the node beforehand.
| Property | Description |
|---|---|
| status (boolean) | Returns the current status of the sensor |
If necessary, the sensor can be turned on and off remotely. If the sensor has been turned off, it no longer registers any contact changes and accordingly no longer outputs them. To do this, pass an object with the following content:
| Property | Description |
|---|---|
| payload (boolean) | true turns the sensor on, false turns it off |
As soon as the contact changes, the following status message is returned by the node:
| Property | Description |
|---|---|
| active (boolean) | Indicates whether the sensor is switched on or off |
| reachable (boolean / string) | true if the sensor is connected to the bridge, unknown if the connection status deviates |
| connectionStatus (string) | The current connection status with the bridge in the form of a string. Can contain connected, disconnected, connectivity_issue or unidirectional_incoming as a value |
| contact (string / boolean) | contact if the contact is closed, no_contact if it is open or false if the sensor has not reported yet |
| changed (string / boolean) | Time of the last contact change (ISO 8601) or false if the sensor has not reported yet |
| tampered (boolean) | Only available on sensors with tamper detection, true if the sensor has been tampered with |
| updated (string) | Time of the last update of the resource by HueMagic (ISO 8601) |
| Property | Description |
|---|---|
| id (string) | Indicates the new ID of the sensor |
| idV1 (string / boolean) | Indicates the old ID of the sensor |
| uniqueId (string) | The unique ID of the sensor |
| deviceId (string) | The unique ID of the device |
| name (string) | The currently set name of the sensor |
| type (string) | The type of the sensor (always contact) |
| softwareVersion (string) | The current firmware of the sensor |
| battery (float / boolean) | The current battery level of the sensor, false when there is no battery |
| batteryState (string / boolean) | The current status of the battery level. Can contain normal, low or critical as a value, false when there is no battery |
| model (object) | Contains the model information of the sensor under id, manufacturer, name, type and certified |
Lists individual parameters in the form of an object that have changed compared to the last state of the sensor. If no changes have been registered, this object is empty.
Contains the complete status object (see output values above) of the last status before the last registered change. If the last state of HueMagic has not yet been registered, it will output false.
If the status of the node has changed via a certain command, the entire command that was executed is also output. Otherwise this object will not be output by the node.
The "Hue Temperature" node can call up and report the current ambient temperature from a suitable sensor on the bridge.
Select the pre-configured Hue Bridge and click the search button to find all the available sensors. If you already know the ID of the sensor, you can also enter it here manually. You can either assign a new name for the sensor internally or choose the predefined name of the sensor. Optionally, you can also deactivate all automatic status messages for this node by clicking the setting "Skip events from node". The node will then no longer issue device updates. Alternatively, you can also choose whether the node's initialization message should not be suppressed when Node-RED is started. If you activate this setting, you will receive a status message for the currently selected sensor after each deployment. If you would rather have the node stay silent until you send it something, activate "Only report after a command". It then ignores changes from the app or a switch and only answers your own commands.
Motion sensors are usually mounted in a corner of the room and often measure a little too warm because of their own electronics. With the setting "Offset" you can calibrate the sensor without any detours: the value you enter here (e.g. -1.5) is added to every measured value before the node outputs it. The offset applies to all temperature units at the same time.
If you do not select a sensor and use the node configuration in this way, the node works in the so-called "universal mode". In this mode, the node receives and outputs all status messages of the same type. You can also apply settings in universal mode to a specific sensor by transferring the corresponding sensor ID as a string in msg.topic together with your settings.
Outputs the current status of the sensor as soon as a msg.payload object with the following content has been transferred to the node. Alternatively, you can also press the button in the Node-RED interface without having to pass a message to the node beforehand.
| Property | Description |
|---|---|
| status (boolean) | Returns the current status of the sensor |
If necessary, the sensor can be switched on and off remotely. If the sensor has been switched off, it no longer registers any temperature changes and accordingly no longer outputs them. To do this, pass an object with the following content:
| Property | Description |
|---|---|
| payload (boolean) | true switches the sensor on, false switches it off |
As soon as the sensor has registered a temperature change, the following status message is returned by the node:
| Property | Description |
|---|---|
| active (boolean) | Indicates whether the sensor is switched on or off |
| reachable (boolean / string) | true if the sensor is connected to the bridge, unknown if the connection status deviates |
| connectionStatus (string) | The current connection status with the bridge in the form of a string. Can contain connected, disconnected, connectivity_issue or unidirectional_incoming as a value |
| celsius (float) | Indicates the current ambient temperature in °C (degrees Celsius) |
| fahrenheit (float) | Indicates the current ambient temperature in °F (degrees Fahrenheit) |
| temperatureIs (string) | Describes the current temperature with the values very cold, cold, slightly cold, comfortable, slightly warm, warm, hot or very hot |
| deviceValue (float) | The original value of the temperature from the sensor |
| updated (string) | Time of the last update of the resource by HueMagic (ISO 8601) |
| Property | Description |
|---|---|
| id (string) | Indicates the new ID of the sensor |
| idV1 (string / boolean) | Indicates the old ID of the sensor |
| uniqueId (string) | The unique ID of the sensor |
| deviceId (string) | The unique ID of the device |
| name (string) | The currently set name of the sensor |
| type (string) | The type of the sensor (always temperature) |
| softwareVersion (string) | The current firmware of the sensor |
| battery (float) | The current battery level of the sensor |
| batteryState (string) | The current status of the battery level. Can contain normal, low or critical as a value |
| model (object) | Contains the model information of the sensor under id, manufacturer, name, type and certified |
Lists individual parameters in the form of an object that have changed compared to the last state of the sensor. If no changes have been registered, this object is empty.
Contains the complete status object (see output values above) of the last status before the last registered change. If the last state of HueMagic has not yet been registered, it will output false.
If the status of the node has changed via a certain command, the entire command that was executed is also output. Otherwise this object will not be output by the node.
The "Hue Brightness" node can read the current light level from a suitable sensor on the bridge.
Select the pre-configured Hue Bridge and click the search button to find all the available sensors. If you already know the ID of the sensor, you can also enter it here manually. You can either assign a new name for the sensor internally or choose the predefined name of the sensor. Optionally, you can also deactivate all automatic status messages for this node by clicking the setting "Skip events from node". The node will then no longer issue device updates. Alternatively, you can also choose whether the node's initialization message should not be suppressed when Node-RED is started. If you activate this setting, you will receive a status message for the currently selected sensor after each deployment. If you would rather have the node stay silent until you send it something, activate "Only report after a command". It then ignores changes from the app or a switch and only answers your own commands.
The setting "Dark below" determines from which light level the node considers a room to be dark. A room with a bright lamp needs a completely different value than a hallway without a window, so simply enter the number of lux that suits your room. The values dark and daylight then follow your setting instead of the default of 90 lux.
If you do not select a sensor and use the node configuration in this way, the node works in the so-called "universal mode". In this mode, the node receives and outputs all status messages of the same type. You can also apply settings in universal mode to a specific sensor by transferring the corresponding sensor ID as a string in msg.topic together with your settings.
Outputs the current status of the sensor as soon as a msg.payload object with the following content has been transferred to the node. Alternatively, you can also press the button in the Node-RED interface without having to pass a message to the node beforehand.
| Property | Description |
|---|---|
| status (boolean) | Returns the current status of the sensor |
If necessary, the sensor can be turned on and off remotely. If the sensor has been turned off, it no longer registers any changes in light level and accordingly no longer outputs them. To do this, pass an object with the following content:
| Property | Description |
|---|---|
| payload (boolean) | true switches the sensor on, false switches it off |
As soon as the sensor has detected a change in the light level, the following status message is returned:
| Property | Description |
|---|---|
| active (boolean) | Indicates whether the sensor is turned on or off |
| reachable (boolean / string) | true if the sensor is connected to the bridge, unknown if the connection status deviates |
| connectionStatus (string) | The current connection status with the bridge in the form of a string. Can contain connected, disconnected, connectivity_issue or unidirectional_incoming as a value |
| lux (int) | Indicates the real LUX value of the light level |
| lightLevel (int) | Indicates the light intensity of the sensor |
| dark (boolean) | true, if darkness was registered |
| daylight (boolean) | true, if daylight was registered |
| darkThreshold (int) | The light level in lux below which the node reports darkness |
| updated (string) | Time of the last update of the resource by HueMagic (ISO 8601) |
| Property | Description |
|---|---|
| id (string) | Indicates the new ID of the sensor |
| idV1 (string / boolean) | Indicates the old ID of the sensor |
| uniqueId (string) | The unique ID of the sensor |
| deviceId (string) | The unique ID of the device |
| name (string) | The currently set name of the sensor |
| type (string) | The type of the sensor (always light_level) |
| softwareVersion (string) | The current firmware of the sensor |
| battery (float) | The current battery level of the sensor |
| batteryState (string) | The current status of the battery level. Can contain normal, low or critical as a value |
| model (object) | Contains the model information of the sensor under id, manufacturer, name, type and certified |
Lists individual parameters in the form of an object that have changed compared to the last state of the sensor. If no changes have been registered, this object is empty.
Contains the complete status object (see output values above) of the last status before the last registered change. If the last state of HueMagic has not yet been registered, it will output false.
If the status of the node has changed via a certain command, the entire command that was executed is also output. Otherwise this object will not be output by the node.
The "Hue Speaker" node can play the sounds of a Hue Secure chime and use it as an indoor siren.
Select the pre-configured Hue Bridge and click the search button to find all the available speakers. If you already know the ID of the speaker, you can also enter it here manually. You can either assign a new name for the speaker internally or choose the predefined name of the speaker. Optionally, you can also deactivate all automatic status messages for this node by clicking the setting "Skip events from node". The node will then no longer issue device updates. Alternatively, you can also choose whether the node's initialization message should not be suppressed when Node-RED is started. If you activate this setting, you will receive a status message for the currently selected speaker after each deployment. If you would rather have the node stay silent until you send it something, activate "Only report after a command". It then ignores changes from the app or a switch and only answers your own commands.
If you do not select a speaker and use the node configuration in this way, the node works in the so-called "universal mode". In this mode, the node receives and outputs all status messages of the same type. You can also apply settings in universal mode to a specific speaker by transferring the corresponding speaker ID as a string in msg.topic together with your settings.
Outputs the current status of the speaker as soon as a msg.payload object with the following content has been transferred to the node. Alternatively, you can also press the button in the Node-RED interface without having to pass a message to the node beforehand.
| Property | Description |
|---|---|
| status (boolean) | Returns the current status of the speaker |
A speaker knows three separate channels. The chime is the doorbell sound, the alarm is the siren and the alert is a short notification. Which sounds a device actually knows is listed under msg.info.sounds. Transfer the following parameters to an msg.payload object:
| Property | Description |
|---|---|
| chime (string / object / boolean) | Name of the doorbell sound, false stops it again |
| alarm (string / object / boolean) | Name of the siren sound, false stops it again |
| alert (string / object / boolean) | Name of the notification sound, false stops it again |
| mute (boolean) | true mutes the speaker, false unmutes it again |
Instead of a plain sound name you can also pass an object to control volume and duration:
| Property | Description |
|---|---|
| sound (string) | Name of the sound, e.g. ding_dong_classic or siren |
| volume (int) | Volume in percent (0-100) |
| duration (float) | Playback time in seconds |
As soon as the speaker starts or stops playing, the following status message is returned by the node. Please note that the bridge reports the sound that was played last and only clears it well after playback has finished, so these values lag a little behind the audio.
| Property | Description |
|---|---|
| reachable (boolean / string) | true if the speaker is connected to the bridge, unknown if the connection status deviates |
| connectionStatus (string) | The current connection status with the bridge in the form of a string. Can contain connected, disconnected, connectivity_issue or unidirectional_incoming as a value |
| playing (boolean) | true while the speaker is playing any sound |
| chime (string / boolean) | Name of the doorbell sound that is playing or false |
| alarm (string / boolean) | Name of the siren sound that is playing or false |
| alert (string / boolean) | Name of the notification sound that is playing or false |
| muted (boolean) | Indicates whether the speaker is muted |
| updated (string) | Time of the last update of the resource by HueMagic (ISO 8601) |
| Property | Description |
|---|---|
| id (string) | Indicates the new ID of the speaker |
| idV1 (string / boolean) | Indicates the old ID of the speaker |
| uniqueId (string) | The unique ID of the speaker |
| deviceId (string) | The unique ID of the device |
| name (string) | The currently set name of the speaker |
| type (string) | The type of the device (always speaker) |
| softwareVersion (string) | The current firmware of the speaker |
| battery (float / boolean) | The current battery level of the speaker, false when there is no battery |
| batteryState (string / boolean) | The current status of the battery level. Can contain normal, low or critical as a value, false when there is no battery |
| sounds (object) | Contains the sounds this device knows under chime, alarm and alert |
| model (object) | Contains the model information of the speaker under id, manufacturer, name, type and certified |
Lists individual parameters in the form of an object that have changed compared to the last state of the speaker. If no changes have been registered, this object is empty.
Contains the complete status object (see output values above) of the last status before the last registered change. If the last state of HueMagic has not yet been registered, it will output false.
If the status of the node has changed via a certain command, the entire command that was executed is also output. Otherwise this object will not be output by the node.
The "Hue Automation" node can enable and disable the automations you have created in the Philips Hue app.
Select the pre-configured Hue Bridge and click the search button to find all the available automations. If you already know the ID of the automation, you can also enter it here manually. You can either assign a new name for the automation internally or choose the predefined name. Optionally, you can also deactivate all automatic status messages for this node by clicking the setting "Skip events from node". The node will then no longer issue any updates. Alternatively, you can also choose whether the node's initialization message should not be suppressed when Node-RED is started. If you activate this setting, you will receive a status message for the currently selected automation after each deployment. If you would rather have the node stay silent until you send it something, activate "Only report after a command". It then ignores changes from the app or a switch and only answers your own commands.
If you do not select an automation and use the node configuration in this way, the node works in the so-called "universal mode". In this mode, the node receives and outputs all status messages of the same type. You can also apply settings in universal mode to a specific automation by transferring the corresponding automation ID as a string in msg.topic together with your settings.
An automation that has been disabled stays on the bridge and can be enabled again at any time. To do this, pass an object with the following content:
| Property | Description |
|---|---|
| payload (boolean) | true enables the automation, false disables it |
| enabled (boolean) | Same as above, if you prefer to pass an object |
| toggle (boolean / any) | Toggles between enabled and disabled, depending on the previous status |
As soon as the automation changes, the following status message is returned by the node:
| Property | Description |
|---|---|
| enabled (boolean) | Indicates whether the automation is enabled |
| running (boolean) | true while the bridge is actually executing the automation |
| status (string / boolean) | The current status. Can contain initializing, running, disabled or errored as a value |
| lastError (string / boolean) | The last error reported by the bridge or false |
| updated (string) | Time of the last update of the resource by HueMagic (ISO 8601) |
| Property | Description |
|---|---|
| id (string) | Indicates the ID of the automation |
| idV1 (string / boolean) | Indicates the old ID of the automation |
| name (string / boolean) | The name you gave the automation in the Philips Hue app |
| type (string) | The type of the resource (always automation) |
| script (string / boolean) | The ID of the behaviour script behind the automation |
Contains the settings of the automation as they were stored by the Philips Hue app. The structure depends on the type of the automation and is passed through unchanged.
Lists individual parameters in the form of an object that have changed compared to the last state of the automation. If no changes have been registered, this object is empty.
Contains the complete status object (see output values above) of the last status before the last registered change. If the last state of HueMagic has not yet been registered, it will output false.
If the status of the node has changed via a certain command, the entire command that was executed is also output. Otherwise this object will not be output by the node.
The "Hue Rule" node can activate or deactivate rules saved in the bridge and call up their settings.
Select the pre-configured Hue Bridge and hit the search button to find all the available rules. If you already know the ID of the rule, you can also enter it here manually. Alternatively, you can also assign a new name or choose the predefined name of the rule. Optionally, you can also deactivate all automatic status messages for this node by clicking the setting "Skip events from node". The node will then no longer issue any updates. Alternatively, you can also choose whether the node's initialization message should not be suppressed when Node-RED is started. If you would rather have the node stay silent until you send it something, activate "Only report after a command". It then ignores changes from the app or a switch and only answers your own commands.
If you do not select a rule and use the node configuration in this way, the node works in the so-called "universal mode". In this mode, the node receives and outputs all status messages of the same type. You can also apply settings in universal mode to a specific rule by transferring the corresponding rule ID as a string in msg.topic together with your settings.
Outputs the current properties of the rule as soon as a msg.payload object with the following content has been passed to the node. Alternatively, you can also press the button in the Node-RED interface without having to pass a message to the node beforehand.
| Property | Description |
|---|---|
| status (boolean) | Returns the current status of the rule |
The rule can be activated and deactivated if necessary. If the rule has been deactivated, it will no longer run in the bridge until you reactivate it. To do this, pass an object with the following content:
| Property | Description |
|---|---|
| payload (boolean) | true activates the rule, false deactivates it |
As soon as the status (activated / deactivated) of a rule changes, the following status message is returned by the node:
| Property | Description |
|---|---|
| enabled (boolean) | Indicates whether the rule is activated or deactivated |
| triggered (string) | Time of the last execution (ISO 8601) |
| Property | Description |
|---|---|
| id (string) | The unique ID of the rule |
| created (string) | Date of creation of the rule (ISO 8601) |
| name (string) | Name of the rule on the bridge |
| timesTriggered (int) | Number of times the rule was executed on the bridge |
| owner (string) | ID of the owner of this rule |
| status (string) | Status of the rule in the form of a string |
| Property | Description |
|---|---|
| address (string) | Path to an attribute of a sensor |
| operator (string) | operator |
| value (string) | The value to be checked |
| Property | Description |
|---|---|
| address (string) | The destination address of the resource |
| method (string) | The query method |
| body (object) | The action to be taken |
Lists individual parameters in the form of an object that have changed compared to the last state of the rule. If no changes have been registered, this object is empty.
Contains the complete object (see output values above) of the last status before the last registered change of the rule. If the last state of HueMagic has not yet been registered, it will output false.
If the status of the node has changed via a certain command, the entire command that was executed is also output. Otherwise this object will not be output by the node.
The "Hue Sync Box" node controls a Philips Hue Play HDMI Sync Box and reports what it is currently doing.
The sync box is not connected to your Hue Bridge but speaks its own local API, so it needs its own configuration. Enter the IP address of your sync box and click the button next to the access token field. Then press and hold the button on the sync box until its LED blinks green — HueMagic keeps asking the box for a minute and stores the token as soon as it answers.
Since the sync box does not push its state, HueMagic asks it regularly. You can set how often in the configuration, the default is every 10 seconds. Optionally, you can also deactivate all automatic status messages for this node by clicking the setting "Skip events from node". The node will then no longer issue any updates. Alternatively, you can also choose whether the node's initialization message should not be suppressed when Node-RED is started. If you would rather have the node stay silent until you send it something, activate "Only report after a command". It then ignores changes from the app or a switch and only answers your own commands.
Outputs the current status of the sync box as soon as a msg.payload object with the following content has been transferred to the node. Alternatively, you can also press the button in the Node-RED interface without having to pass a message to the node beforehand.
| Property | Description |
|---|---|
| status (boolean) | Returns the current status of the sync box |
To quickly switch the sync box on or off, pass an object with the following content to the node. Switching it on returns to the sync mode that was used last.
| Property | Description |
|---|---|
| payload (boolean) | true starts syncing, false puts the box into power save |
Transfer the following parameters to an msg.payload object to control the sync box in more detail:
| Property | Description |
|---|---|
| mode (string) | One of powersave, passthrough, video, game, music or ambient |
| sync (boolean) | true starts the synchronisation, false stops it |
| toggle (boolean / any) | Toggles the synchronisation, depending on the previous state |
| passthrough (boolean) | true passes the picture through to your TV without syncing |
| intensity (string) | How strongly the lights follow the picture. One of subtle, moderate, high or intense |
| brightness (int) | Percentage value of the brightness (0-100) |
| brightnessLevel (int) | Numerical value of the brightness as the box counts it (0-200, where 100 is the baseline) |
| incrementBrightness (int / boolean) | Specifies by how many percent the sync box should be made brighter or true for 10% steps |
| decrementBrightness (int / boolean) | Specifies by how many percent the sync box should be made darker or true for 10% steps |
| input (string / int) | The HDMI input to show, either input1 to input4 or simply 1 to 4 |
| entertainmentArea (string) | The entertainment area the box should drive, e.g. groups/13 |
Whenever the state of the sync box changes, the following status message is returned by the node:
| Property | Description |
|---|---|
| on (boolean) | false while the box is in power save |
| syncing (boolean) | true while the lights follow the picture |
| passthrough (boolean) | true while the box passes the picture through |
| mode (string) | The currently active mode |
| lastSyncMode (string) | The sync mode that was used last |
| intensity (string / boolean) | Intensity of the currently active mode |
| brightness (int / boolean) | Brightness in percent |
| brightnessLevel (int / boolean) | Brightness as the box counts it (0-200) |
| input (string / boolean) | The HDMI input that is currently shown |
| inputs (object) | All four HDMI inputs with their name, type, status (unplugged, plugged, linked or unknown) and whether they are active |
| entertainmentArea (string / boolean) | The entertainment area the box drives |
| updated (string) | Time of the last update of the resource by HueMagic (ISO 8601) |
| Property | Description |
|---|---|
| id (string / boolean) | The unique ID of the sync box |
| name (string / boolean) | The currently set name of the sync box |
| type (string) | The type of the device (always syncbox) |
| ipAddress (string / boolean) | The IP address the box reports for itself |
| softwareVersion (string / boolean) | The current firmware of the sync box |
| apiLevel (int / boolean) | The API level of the sync box |
| ledMode (int / boolean) | The currently set LED mode |
| wifi (object / boolean) | Contains ssid and strength of the wireless connection |
| model (object) | Contains the model information of the sync box under id, manufacturer and name |
Lists individual parameters in the form of an object that have changed compared to the last state of the sync box. If no changes have been registered, this object is empty.
Contains the complete status object (see output values above) of the last status before the last registered change. If the last state of HueMagic has not yet been registered, it will output false.
If the status of the node has changed via a certain command, the entire command that was executed is also output. Otherwise this object will not be output by the node.
Attention! HueMagic v5 requires Node.js 18+ and Node-RED v3+. The "Hue Group" node now speaks the CLIP/v2 API instead of the legacy API, and the alert effect on the "Hue Light" & "Hue Group" nodes is now played by the bridge itself, which also restores the previous state on its own. Your existing flows keep working as they are — no reconfiguration needed.
New devices and features
- New "Hue Speaker" node plays the sounds of a Hue Secure chime and can use it as an indoor siren
- New "Hue Automation" node enables and disables the automations you created in the Philips Hue app — the modern successor to the rules of the legacy API
- The "Hue Motion" node now also covers Hue Secure cameras and, on the Hue Bridge Pro, the MotionAware areas that turn your lights into motion sensors
- Cameras and MotionAware areas can be made more or less sensitive
- The "Hue Buttons" node now also reports the Hue Secure video doorbell
- The Hue wall switch module can be switched between rocker and pushbutton mode (#331) (thx @KGS501)
- The "Hue Light" node can play the built-in effects of a light (
candle,fire,sparkle,prismand more) - The "Hue Light" node can play the
sunriseandsunsetsimulation of a light for up to six hours - The behaviour of a light after a power cut can now be configured (
safety,powerfail,last_on_stateorcustom) - The mode of a gradient can now be set, so the colors are spread as an interpolated, mirrored, pixelated or segmented palette
- The "Hue Motion" and "Hue Brightness" nodes now also read the grouped sensors the bridge aggregates for a room or zone
- New "Hue Sync Box" node controls a Philips Hue Play HDMI Sync Box over its own local API — modes, intensity, brightness, HDMI input and entertainment area (#195) (thx @masterfish1)
- The "Hue Scene" node can now recall a scene with its own transition time and brightness, so the same scene can be applied slowly or dimmed depending on the time of day (#392) (thx @guenter-ms)
- Scenes in the node configuration are now sorted by room or zone first and then by name, so the scenes of one room stay together (#259) (thx @hendersj)
- The "Hue Brightness" node lets you set the light level below which a room counts as dark instead of insisting on a fixed value (#279) (thx @kazzyUK)
- The "Hue Temperature" node can correct the measured value with an offset, so a sensor that reads too warm can finally be calibrated (#205) (thx @tutenchamun)
- Every node that reports events can now be set to "Only report after a command", so it stays silent when a light is changed in the app or by a switch and only answers your own commands (#247) (thx @adams-family)
- New example flows for the "Hue Speaker", "Hue Automation" and "Hue Sync Box" nodes
Philips Hue Bridge Pro
- Support for the Philips Hue Bridge Pro: the API key is now requested over HTTPS, because modern bridges no longer answer on plain HTTP (#454) (#452) (thx @ozdeadmeat & @JGoor)
- Requesting the API key now keeps asking the bridge for a minute instead of guessing a single moment
- Fixed a crash that took down the whole Node-RED instance as soon as a Bridge Pro streamed an unknown service type (#453) (thx @lmuser22)
- Bridges are now also discovered when they run on a port other than 443
Stability
- HueMagic no longer takes Node-RED down with it — all known uncaught exceptions and unhandled promise rejections have been closed (#435) (#398) (#388) (#366) (#336) (#326) (#321) (#312) (#306) (#304) (#270) (thx @MarkRoks, @TerryMcgurk, @CyrielRct, @Wombosvideo, @Zootopie-LG, @ddlsmurf, @nibbsification, @Darkman1900, @bmdevx & @McFozzy75)
- Commands are now paced to what the bridge actually accepts (about 10 light and 1 group command per second), so the worker setting no longer has to be turned down to 1 to avoid 429/503 errors (#295) (#350) (#404) (#431) (#276) (thx @Brewj, @ralfhille, @hazymat, @bevrat & @hurenkam)
- The connection to the bridge is now rebuilt with a backoff instead of a reconnect storm, and a single failed request no longer restarts the whole bridge (#372) (#353) (thx @develmac & @Jai-Gogineni)
- The watchdog no longer tears down the event subscription every ten seconds, which stopped sensors and switches from reporting after a short while (#384) (#396) (#358) (#344) (thx @spacewalker0815, @bobhobelman, @otoivanen & @isaac-the-newt)
- Nodes now detach from the bridge when they are removed, so a re-deploy no longer makes them receive every event twice, three times, … (#297) (#301) (#412) (thx @FreeTechNick, @ScottBevin & @FredBlo)
- One event in a batch that could not be assigned no longer discards all the following ones
- Devices that are added to or removed from the bridge are now picked up without restarting Node-RED
- Requests to the bridge never go through a configured HTTP proxy anymore, which broke the TLS connection on some setups (#436) (#265) (thx @rsch90 & @HonestJohn61)
- Timers and event listeners are properly cleaned up when a node is removed
Nodes
- The "Hue Group" node now speaks CLIP/v2, which brings back
incrementBrightness&decrementBrightnessand fixes groups without a legacy identifier (#380) (#400) (#405) (thx @peterbaker, @SierraLimaOscar & @guenter-ms) - The "Hue Group" node now also reports
brightness,brightnessLeveland the current color (#292) (thx @Schmetterfliege) - Universal mode no longer fails on every other message and the "Hue Group" node finally receives messages in it (#300) (#305) (#418) (thx @oxivanisher, @aL1aL7 & @vongomben)
- "The group is not yet available" is gone — groups, zones and third party devices are resolved correctly again (#373) (#374) (#376) (#314) (#378) (#377) (#407) (#395) (thx @Eggn1n3, @MarkRoks, @marsjupiter1, @andesse, @djiwondee, @Stieger81, @McFozzy75, @otoivanen & @traverseda)
- Turning a light or group off now always reaches the bridge, even if the cached state claimed it was already off (#334) (thx @dewenni)
- Nodes no longer get stuck on "executing command…" after a command that changed nothing (#315) (#345) (#382) (#394) (thx @BlaM, @NodeRedFan & @adb336)
- The alert effect is no longer capped at 15 seconds and the bridge now restores the previous state itself, so groups no longer stay dark afterwards (#451) (#294) (thx @biosmanager & @spudje)
- The "Hue Buttons" node now reports the rotation of the Hue Tap Dial Switch and the Lutron Aurora (#385) (#275) (thx @WhiteSockedDancer & @hurenkam)
- The "Hue Buttons" node now also recognizes
long_press,long_releaseanddouble_short_release(#129) (thx @Tscherno) - Sensors read their values from the reports of the current API, so motion, temperature and brightness stay correct on new firmwares (#384) (#396) (#279) (thx @spacewalker0815, @bobhobelman & @kazzyUK)
- Devices without a battery (e.g. mains powered sensors) no longer break their node (#446) (thx @DangersTR)
- The "Hue Contact" node now also reports whether the sensor has been tampered with and finally got its documentation and example flow
- The "Hue Scene" node supports smart scenes and no longer fails on scenes whose group has been deleted (#447) (#386) (#449) (#316) (thx @Himola, @danieldaeschle, @stijnbrocker & @andesse)
- The searches in the node configuration now report the real error instead of a generic one (#449) (#274) (thx @stijnbrocker & @TomGeoDK)
msg.lastStatenow really contains the previous state instead of a reference to the current one (#322) (thx @valiquette)- Fixed the random color option, which threw an error instead of picking a color
- Fixed
brightnessLevel: 0not turning a light or group off - Fixed the state restoration after an animation on the "Hue Group" node
- Lights and groups no longer flicker when an animation restores their previous state
Localization
- All error messages, node states and log outputs are now translated instead of being hardcoded in English
- HueMagic now speaks ten languages: English, German, Spanish, French, Italian, Dutch, Portuguese, Polish, Turkish and Greek — node configuration, status texts, error messages and the complete node documentation
- The example flows are translated as well and live in one folder per language, so you can import them in your own language
- Completed the German translation, which was missing several texts in the node configuration
- The node icons are now rendered from the SVG versions that have been shipped since v4 but were never used
Under the hood
- Requires Node.js 18+ and Node-RED v3+, tested against Node-RED v5 on Node.js 24
- The event stream is now spoken directly instead of through the
eventsourcedependency, which had dropped support for older Node.js versions - Connections to the bridge are kept alive instead of renegotiating TLS for every single request
- The HTTP endpoints of the node configuration now require an authenticated Node-RED editor session
- Updated all dependencies to their latest versions
- Added a test suite (
npm test) that also guards the translations - Published again, so all the fixes that were sitting on master since 2022 finally reach everyone (#414) (thx @AleksCee)
- HueMagic can now be installed again on older Node-RED versions without official support
- Fixed an issue for Hue Group nodes not getting/updating their current status (#342) (thx @bmdevx)
- Fixed an error with non-functioning node configurations
The full changelog changelog can be viewed here…
If you like HueMagic, I appreciate a star or rating on this page! HueMagic is and will remain free. You can support the further development of the project with a small donation.
Alternatively, you can support the project if you have an old device that is compatible with the Philips Hue bridge (or a device that is not officially supported by HueMagic) and want to get rid of it. Please contact me at huemagic@foddy.io to get an address where you can send your old device. The following devices could currently be considered: Gradient lights, Tap / Button devices or table / floor lights. These types of devices have not been extensively tested during HueMagic's development.
HueMagic for Node-RED is sponsored by DGTL.ONE, JetBrains and BrowserStack.
Released under the Apache License 2.0.