node-red-contrib-huemagic 4.2.2 → 5.0.0

package/README.md

@@ -1,10 +1,10 @@
-[![Hue Magic Logo](https://gist.githubusercontent.com/Foddy/9b647b910d03a31cee40f97c3988dd1c/raw/7ee635bd958ad04d7ba53c6c40ec401f879bffc2/huemagic-logo.svg)](https://flows.nodered.org/node/node-red-contrib-huemagic)
+[![Hue Magic Logo](https://raw.githubusercontent.com/Foddy/node-red-contrib-huemagic/master/docs/images/huemagic-logo.svg)](https://flows.nodered.org/node/node-red-contrib-huemagic)
 
 # HueMagic - Philips Hue nodes for Node-RED
 
 [![npm](https://img.shields.io/npm/v/node-red-contrib-huemagic.svg?style=flat-square)](https://github.com/foddy/node-red-contrib-huemagic/) [![GitHub license](https://img.shields.io/badge/license-Apache%202-blue.svg?style=flat-square)](https://raw.githubusercontent.com/Foddy/node-red-contrib-huemagic/master/LICENSE) [![Donate via PayPal](https://img.shields.io/badge/Donate-PayPal-blue.svg?style=flat-square)](https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=LUQ7CWBWQ3Q4U) [![npm](https://img.shields.io/npm/dt/node-red-contrib-huemagic.svg?style=flat-square)](https://www.npmjs.com/package/node-red-contrib-huemagic)
 
-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, buttons/switches, motion sensors, temperature sensors and light level sensors.
+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.
 
 ### Features
 * Simple and comprehensive control of the Hue Bridge and connected devices
@@ -14,17 +14,27 @@ HueMagic provides several input and output nodes for Node-RED and is the most in
 * 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 on the Hue Bridge
+* 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
-* Extensively documented in English & German
+* 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
 
 ### Installation
-HueMagic was written for **Node.js 14+** and **Node-RED v2.1+**. It supports the square-shaped Hue Bridge with the **firmware 1948086000+** or higher. You can install HueMagic directly via the [Node-RED Palette Manager](https://nodered.org/docs/user-guide/editor/palette/manager) or manually using [npm / yarn](https://nodered.org/docs/user-guide/runtime/adding-nodes).
+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](https://nodered.org/docs/user-guide/editor/palette/manager) or manually using [npm / yarn](https://nodered.org/docs/user-guide/runtime/adding-nodes).
 
 `npm install node-red-contrib-huemagic`
 
@@ -39,20 +49,24 @@ _Please make sure that you deactivate other Hue-related nodes in Node-RED and me
 - [Hue Scenes](#hue-scene)
 - [Hue Buttons](#hue-buttons)
 - [Hue Motion](#hue-motion)
+- [Hue Contact](#hue-contact)
 - [Hue Temperature](#hue-temperature)
 - [Hue Brightness](#hue-brightness)
+- [Hue Speaker](#hue-speaker)
+- [Hue Automation](#hue-automation)
 - [Hue Rule](#hue-rule)
+- [Hue Sync Box](#hue-sync-box)
 
 ### Examples
 
-HueMagic provides a large selection of full featured sample flows for all nodes. You can find these examples in the [examples folder on GitHub](https://github.com/Foddy/node-red-contrib-huemagic/tree/master/examples) 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 and your desired node to import a sample flow.
+HueMagic provides a large selection of full featured sample flows for all nodes. You can find these examples in the [examples folder on GitHub](https://github.com/Foddy/node-red-contrib-huemagic/tree/master/examples) 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.
 
-<a href="https://github.com/Foddy/node-red-contrib-huemagic/tree/master/examples"><img alt="Instructions to import examples in Node-RED" src="https://user-images.githubusercontent.com/5302050/148696808-f730ad36-8d0b-4b5b-99b2-1917831f8916.gif" width="100%"></a>
+<a href="https://github.com/Foddy/node-red-contrib-huemagic/tree/master/examples"><img alt="Instructions to import examples in Node-RED" src="https://raw.githubusercontent.com/Foddy/node-red-contrib-huemagic/master/docs/images/import-examples.gif" width="100%"></a>
 
 ## Hue Bridge
 The "Hue Bridge" node is a universal node that can output all settings of the bridge and status messages from other nodes.
 
-![Hue Bridge Example](https://user-images.githubusercontent.com/5302050/148696503-428cf1d0-8376-49fe-b677-979070fc92b9.png)
+![Hue Bridge Example](https://raw.githubusercontent.com/Foddy/node-red-contrib-huemagic/master/docs/images/nodes/hue-bridge.png)
 
 ### Node-RED Setup Instructions
 
@@ -82,7 +96,7 @@ With the "fetch" command you can output a list of specific devices that are curr
 
 |Property|Description|
 |--|--|
-| fetch (string / array [string, ...]) | Can accept `light`, `group`, `button`, `motion`, `temperature`, `light_level` or `rule` as value(s) |
+| fetch (string / array [string, ...]) | Can accept `light`, `group`, `button`, `motion`, `contact`, `temperature`, `light_level` or `rule` as value(s) |
 
 ### Change Hue Bridge settings
 
@@ -151,7 +165,7 @@ If the status of the node has changed via a certain command, the entire command
 ## Hue Magic
 The "Hue Magic" node can apply complex and custom animations to lights and groups.
 
-![Hue Magic Example](https://user-images.githubusercontent.com/5302050/148696508-51db24ea-722e-402c-9c49-8d728e036488.png)
+![Hue Magic Example](https://raw.githubusercontent.com/Foddy/node-red-contrib-huemagic/master/docs/images/nodes/hue-magic.png)
 
 ### Node-RED Setup Instructions
 
@@ -162,7 +176,7 @@ Below you can choose from pre-made animations from HueMagic. Click on your desir
 ### Included animations
 Choose one of the included animations to apply to a Hue Light or Hue Group node.
 
-![Some included animations](https://user-images.githubusercontent.com/5302050/71556018-30e16d00-2a33-11ea-8c03-45211767ee98.gif)
+![Some included animations](https://raw.githubusercontent.com/Foddy/node-red-contrib-huemagic/master/docs/images/animations.gif)
 
 ### Start / stop animation
 
@@ -228,11 +242,11 @@ This node does not output any status messages. Please connect the output of the
 ## Hue Light
 The "Hue Light" node can control lights connected to the bridge and receive their status messages.
 
-![Hue Light Example](https://user-images.githubusercontent.com/5302050/148696507-bea62f97-e9ec-496a-b7a2-8bf1942a3192.png)
+![Hue Light Example](https://raw.githubusercontent.com/Foddy/node-red-contrib-huemagic/master/docs/images/nodes/hue-light.png)
 
 ### Node-RED Setup Instructions
 
-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.
+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.
 
@@ -270,7 +284,7 @@ In addition to simply switching it on and off, there are also many other options
 | 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 |
+| 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) |
@@ -278,6 +292,11 @@ In addition to simply switching it on and off, there are also many other options
 | 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 |
 
@@ -301,6 +320,9 @@ As soon as a change in the light settings has been detected (regardless of wheth
 | 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) |
 
 #### Information about the light under `msg.info`
@@ -331,11 +353,11 @@ If the status of the node has changed via a certain command, the entire command
 ## Hue Group
 The "Hue Group" node can control several lights behind a group on the bridge at the same time.
 
-![Hue Group Example](https://user-images.githubusercontent.com/5302050/148696506-e5c52750-39e1-43bc-a749-056d7a8718fc.png)
+![Hue Group Example](https://raw.githubusercontent.com/Foddy/node-red-contrib-huemagic/master/docs/images/nodes/hue-group.png)
 
 ### Node-RED Setup Instructions
 
-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.
+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.
 
@@ -349,7 +371,7 @@ Outputs the current status of the group as soon as a `msg.payload` object with t
 
 ### Turn on / off (simple)
 
-To quickly turn an entire group on or off in simple mode, pass an object with the following content to the node. Please note that the command will only be executed if the current status of the group does not match your desired status. This means that all lights have to be switched off before you can switch them on with the `true` command.
+To quickly turn an entire group on or off in simple mode, pass an object with the following content to the node.
 
 |Property|Description|
 |--|--|
@@ -361,10 +383,12 @@ In addition to simply switching it on and off, there are also many other options
 
 |Property|Description|
 |--|--|
-| on (boolean) | `true` switches the entire group on, `false` switches it off (please note the note above) |
+| 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 |
@@ -377,15 +401,22 @@ In addition to simply switching it on and off, there are also many other options
 
 ### Status messages from the node
 
-If a change in the group is detected, the following status message is returned from the node. Please note that the group only outputs status messages when either the last light is switched off or when the first light is switched on (if all were switched off beforehand).
+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 much less status information available here, as a group can contain many different device types with different values that cannot be combined.
+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.
 
 #### Status object under `msg.payload`
 
 |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) |
 
 #### Information about the group under `msg.info`
@@ -413,11 +444,11 @@ If the status of the node has changed via a certain command, the entire command
 ## Hue Scene
 The "Hue Scene" node can resume scenes saved in the bridge and apply them to certain groups.
 
-![Hue Scene Example](https://user-images.githubusercontent.com/5302050/148696512-c9cf3800-935f-44b3-a5e6-8c5e70a71357.png)
+![Hue Scene Example](https://raw.githubusercontent.com/Foddy/node-red-contrib-huemagic/master/docs/images/nodes/hue-scene.png)
 
 ### Node-RED Setup Instructions
 
-Select the pre-configured Hue Bridge and hit the search button to find all the available scenes. 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.
+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.
 
 ### Activate scene
 
@@ -426,6 +457,10 @@ You can activate a predefined scene by transferring an object with the following
 |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._
 
 ### Activate scene in universal mode
 
@@ -448,13 +483,13 @@ Connect the output of this node to one or more groups to apply a scene to specif
 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.
 
 ## Hue Buttons
-The "Hue Buttons" node receives switching events from input devices connected to the bridge.
+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.
 
-![Hue Buttons Example](https://user-images.githubusercontent.com/5302050/148696505-026a3eaf-b5a6-4438-ad71-57d62830799f.png)
+![Hue Buttons Example](https://raw.githubusercontent.com/Foddy/node-red-contrib-huemagic/master/docs/images/nodes/hue-buttons.png)
 
 ### Node-RED Setup Instructions
 
-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.
+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.
 
@@ -466,9 +501,17 @@ Outputs the current status of the switch/button as soon as a `msg.payload` objec
 |--|--|
 | status (boolean) | Returns the current status of the switch/button |
 
+### Change the switch mode
+
+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` |
+
 ### Status messages from the node
 
-As soon as a key has been pressed, the following status message is returned by the node:
+As soon as a key has been pressed or a dial has been turned, the following status message is returned by the node:
 
 #### Status object under `msg.payload`
 
@@ -477,9 +520,24 @@ As soon as a key has been pressed, the following status message is returned by t
 | 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_release` or `double_short_release` in the form of a string |
+| 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) |
 
+#### The rotation of a dial under `msg.payload.rotation`
+
+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 |
+
 #### Information about the switch/button under `msg.info`
 
 |Property|Description|
@@ -493,6 +551,8 @@ As soon as a key has been pressed, the following status message is returned by t
 | 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` |
 
 #### Status changes under `msg.updated`
@@ -508,13 +568,13 @@ Contains the complete status object (see output values above) of the last status
 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.
 
 ## Hue Motion
-The "Hue motion" node can register and report movements from a suitable sensor on the bridge.
+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.
 
-![Hue Motion Example](https://user-images.githubusercontent.com/5302050/148696510-c6bfcad3-cd4e-4b6a-a73f-29bef1ac6961.png)
+![Hue Motion Example](https://raw.githubusercontent.com/Foddy/node-red-contrib-huemagic/master/docs/images/nodes/hue-motion.png)
 
 ### Node-RED Setup Instructions
 
-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.
+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.
 
@@ -534,6 +594,14 @@ If necessary, the sensor can be turned on and off remotely. If the sensor has be
 |--|--|
 | payload (boolean) | `true` turns the sensor on, `false` turns it off |
 
+### Change the sensitivity
+
+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 |
+
 ### Status messages from the node
 
 As soon as the sensor has registered a movement, the following status message is returned by the node:
@@ -546,6 +614,8 @@ As soon as the sensor has registered a movement, the following status message is
 | 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) |
 
 #### Information about the sensor under `msg.info`
@@ -557,7 +627,7 @@ As soon as the sensor has registered a movement, the following status message is
 | 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 `motion`) |
+| 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 |
@@ -575,14 +645,86 @@ Contains the complete status object (see output values above) of the last status
 
 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.
 
+## Hue Contact
+The "Hue Contact" node reports whether a contact sensor (e.g. Hue Secure) is currently open or closed.
+
+![Hue Contact Example](https://raw.githubusercontent.com/Foddy/node-red-contrib-huemagic/master/docs/images/nodes/hue-contact.png)
+
+### Node-RED Setup Instructions
+
+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.
+
+### Get status
+
+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 |
+
+### Turn the sensor on / off
+
+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 |
+
+### Status messages from the node
+
+As soon as the contact changes, the following status message is returned by the node:
+
+#### Status object under `msg.payload`
+
+|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) |
+
+#### Information about the sensor under `msg.info`
+
+|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` |
+
+#### Status changes under `msg.updated`
+
+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.
+
+#### Last status of the sensor under `msg.lastState`
+
+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`.
+
+#### Last command under `msg.command` (optional)
+
+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.
+
 ## Hue Temperature
 The "Hue Temperature" node can call up and report the current ambient temperature from a suitable sensor on the bridge.
 
-![Hue Temperature Example](https://user-images.githubusercontent.com/5302050/148696513-0a3afec5-e85b-40fb-be77-1fbfdc1fad35.png)
+![Hue Temperature Example](https://raw.githubusercontent.com/Foddy/node-red-contrib-huemagic/master/docs/images/nodes/hue-temperature.png)
 
 ### Node-RED Setup Instructions
 
-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.
+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.
 
@@ -649,11 +791,13 @@ If the status of the node has changed via a certain command, the entire command
 ## Hue Brightness
 The "Hue Brightness" node can read the current light level from a suitable sensor on the bridge.
 
-![Hue Brightness Example](https://user-images.githubusercontent.com/5302050/148696504-7d447ea8-bbe3-41e3-9a69-ac8e97ac8d90.png)
+![Hue Brightness Example](https://raw.githubusercontent.com/Foddy/node-red-contrib-huemagic/master/docs/images/nodes/hue-brightness.png)
 
 ### Node-RED Setup Instructions
 
-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.
+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.
 
@@ -683,11 +827,12 @@ As soon as the sensor has detected a change in the light level, the following st
 |--|--|
 | 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 |
+| 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) |
 
 #### Information about the sensor under `msg.info`
@@ -717,14 +862,158 @@ Contains the complete status object (see output values above) of the last status
 
 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.
 
+## Hue Speaker
+The "Hue Speaker" node can play the sounds of a Hue Secure chime and use it as an indoor siren.
+
+![Hue Speaker Example](https://raw.githubusercontent.com/Foddy/node-red-contrib-huemagic/master/docs/images/nodes/hue-speaker.png)
+
+### Node-RED Setup Instructions
+
+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.
+
+### Get status
+
+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 |
+
+### Play a sound
+
+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 |
+
+### Status messages from the node
+
+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.
+
+#### Status object under `msg.payload`
+
+|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) |
+
+#### Information about the speaker under `msg.info`
+
+|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` |
+
+#### Status changes under `msg.updated`
+
+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.
+
+#### Last status of the speaker under `msg.lastState`
+
+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`.
+
+#### Last command under `msg.command` (optional)
+
+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.
+
+## Hue Automation
+The "Hue Automation" node can enable and disable the automations you have created in the Philips Hue app.
+
+![Hue Automation Example](https://raw.githubusercontent.com/Foddy/node-red-contrib-huemagic/master/docs/images/nodes/hue-automation.png)
+
+### Node-RED Setup Instructions
+
+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.
+
+### Enable / disable the automation
+
+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 |
+
+### Status messages from the node
+
+As soon as the automation changes, the following status message is returned by the node:
+
+#### Status object under `msg.payload`
+
+|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) |
+
+#### Information about the automation under `msg.info`
+
+|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 |
+
+#### Configuration under `msg.configuration`
+
+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.
+
+#### Status changes under `msg.updated`
+
+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.
+
+#### Last status of the automation under `msg.lastState`
+
+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`.
+
+#### Last command under `msg.command` (optional)
+
+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.
+
 ## Hue Rule
 The "Hue Rule" node can activate or deactivate rules saved in the bridge and call up their settings.
 
-![Hue Rule Example](https://user-images.githubusercontent.com/5302050/148696511-2bbd6940-2b38-40a0-a68a-ad52631add26.png)
+![Hue Rule Example](https://raw.githubusercontent.com/Foddy/node-red-contrib-huemagic/master/docs/images/nodes/hue-rules.png)
 
 ### Node-RED Setup Instructions
 
-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.
+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.
 
@@ -794,96 +1083,190 @@ Contains the complete object (see output values above) of the last status before
 
 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.
 
+## Hue Sync Box
+The "Hue Sync Box" node controls a Philips Hue Play HDMI Sync Box and reports what it is currently doing.
+
+![Hue Sync Box Example](https://raw.githubusercontent.com/Foddy/node-red-contrib-huemagic/master/docs/images/nodes/hue-syncbox.png)
+
+### Node-RED Setup Instructions
+
+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.
+
+### Get status
+
+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 |
+
+### Turn on / off (simple)
+
+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 |
+
+### Sync box commands (extended)
+
+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` |
+
+### Status messages from the node
+
+Whenever the state of the sync box changes, the following status message is returned by the node:
+
+#### Status object under `msg.payload`
+
+|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) |
+
+#### Information about the sync box under `msg.info`
+
+|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` |
+
+#### Status changes under `msg.updated`
+
+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.
+
+#### Last status of the sync box under `msg.lastState`
+
+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`.
+
+#### Last command under `msg.command` (optional)
+
+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.
+
 # Changelog
 
-### v4.2.2 (latest)
+### v5.0.0 (latest)
+
+> **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](https://github.com/Foddy/node-red-contrib-huemagic/issues/331)) (thx @KGS501)
+* The "Hue Light" node can play the built-in effects of a light (`candle`, `fire`, `sparkle`, `prism` and more)
+* The "Hue Light" node can play the `sunrise` and `sunset` simulation 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_state` or `custom`)
+* 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](https://github.com/Foddy/node-red-contrib-huemagic/issues/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](https://github.com/Foddy/node-red-contrib-huemagic/issues/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](https://github.com/Foddy/node-red-contrib-huemagic/issues/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](https://github.com/Foddy/node-red-contrib-huemagic/issues/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](https://github.com/Foddy/node-red-contrib-huemagic/issues/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](https://github.com/Foddy/node-red-contrib-huemagic/issues/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](https://github.com/Foddy/node-red-contrib-huemagic/issues/454)) ([#452](https://github.com/Foddy/node-red-contrib-huemagic/issues/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](https://github.com/Foddy/node-red-contrib-huemagic/issues/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](https://github.com/Foddy/node-red-contrib-huemagic/issues/435)) ([#398](https://github.com/Foddy/node-red-contrib-huemagic/issues/398)) ([#388](https://github.com/Foddy/node-red-contrib-huemagic/issues/388)) ([#366](https://github.com/Foddy/node-red-contrib-huemagic/issues/366)) ([#336](https://github.com/Foddy/node-red-contrib-huemagic/issues/336)) ([#326](https://github.com/Foddy/node-red-contrib-huemagic/issues/326)) ([#321](https://github.com/Foddy/node-red-contrib-huemagic/issues/321)) ([#312](https://github.com/Foddy/node-red-contrib-huemagic/issues/312)) ([#306](https://github.com/Foddy/node-red-contrib-huemagic/issues/306)) ([#304](https://github.com/Foddy/node-red-contrib-huemagic/issues/304)) ([#270](https://github.com/Foddy/node-red-contrib-huemagic/issues/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](https://github.com/Foddy/node-red-contrib-huemagic/issues/295)) ([#350](https://github.com/Foddy/node-red-contrib-huemagic/issues/350)) ([#404](https://github.com/Foddy/node-red-contrib-huemagic/issues/404)) ([#431](https://github.com/Foddy/node-red-contrib-huemagic/issues/431)) ([#276](https://github.com/Foddy/node-red-contrib-huemagic/issues/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](https://github.com/Foddy/node-red-contrib-huemagic/issues/372)) ([#353](https://github.com/Foddy/node-red-contrib-huemagic/issues/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](https://github.com/Foddy/node-red-contrib-huemagic/issues/384)) ([#396](https://github.com/Foddy/node-red-contrib-huemagic/issues/396)) ([#358](https://github.com/Foddy/node-red-contrib-huemagic/issues/358)) ([#344](https://github.com/Foddy/node-red-contrib-huemagic/issues/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](https://github.com/Foddy/node-red-contrib-huemagic/issues/297)) ([#301](https://github.com/Foddy/node-red-contrib-huemagic/issues/301)) ([#412](https://github.com/Foddy/node-red-contrib-huemagic/pull/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](https://github.com/Foddy/node-red-contrib-huemagic/issues/436)) ([#265](https://github.com/Foddy/node-red-contrib-huemagic/issues/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` & `decrementBrightness` and fixes groups without a legacy identifier ([#380](https://github.com/Foddy/node-red-contrib-huemagic/issues/380)) ([#400](https://github.com/Foddy/node-red-contrib-huemagic/issues/400)) ([#405](https://github.com/Foddy/node-red-contrib-huemagic/issues/405)) (thx @peterbaker, @SierraLimaOscar & @guenter-ms)
+* The "Hue Group" node now also reports `brightness`, `brightnessLevel` and the current color ([#292](https://github.com/Foddy/node-red-contrib-huemagic/issues/292)) (thx @Schmetterfliege)
+* Universal mode no longer fails on every other message and the "Hue Group" node finally receives messages in it ([#300](https://github.com/Foddy/node-red-contrib-huemagic/issues/300)) ([#305](https://github.com/Foddy/node-red-contrib-huemagic/issues/305)) ([#418](https://github.com/Foddy/node-red-contrib-huemagic/issues/418)) (thx @oxivanisher, @aL1aL7 & @vongomben)
+* "The group is not yet available" is gone — groups, zones and third party devices are resolved correctly again ([#373](https://github.com/Foddy/node-red-contrib-huemagic/issues/373)) ([#374](https://github.com/Foddy/node-red-contrib-huemagic/issues/374)) ([#376](https://github.com/Foddy/node-red-contrib-huemagic/issues/376)) ([#314](https://github.com/Foddy/node-red-contrib-huemagic/issues/314)) ([#378](https://github.com/Foddy/node-red-contrib-huemagic/issues/378)) ([#377](https://github.com/Foddy/node-red-contrib-huemagic/issues/377)) ([#407](https://github.com/Foddy/node-red-contrib-huemagic/issues/407)) ([#395](https://github.com/Foddy/node-red-contrib-huemagic/issues/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](https://github.com/Foddy/node-red-contrib-huemagic/issues/334)) (thx @dewenni)
+* Nodes no longer get stuck on "executing command…" after a command that changed nothing ([#315](https://github.com/Foddy/node-red-contrib-huemagic/issues/315)) ([#345](https://github.com/Foddy/node-red-contrib-huemagic/issues/345)) ([#382](https://github.com/Foddy/node-red-contrib-huemagic/issues/382)) ([#394](https://github.com/Foddy/node-red-contrib-huemagic/issues/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](https://github.com/Foddy/node-red-contrib-huemagic/issues/451)) ([#294](https://github.com/Foddy/node-red-contrib-huemagic/issues/294)) (thx @biosmanager & @spudje)
+* The "Hue Buttons" node now reports the rotation of the Hue Tap Dial Switch and the Lutron Aurora ([#385](https://github.com/Foddy/node-red-contrib-huemagic/issues/385)) ([#275](https://github.com/Foddy/node-red-contrib-huemagic/issues/275)) (thx @WhiteSockedDancer & @hurenkam)
+* The "Hue Buttons" node now also recognizes `long_press`, `long_release` and `double_short_release` ([#129](https://github.com/Foddy/node-red-contrib-huemagic/issues/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](https://github.com/Foddy/node-red-contrib-huemagic/issues/384)) ([#396](https://github.com/Foddy/node-red-contrib-huemagic/issues/396)) ([#279](https://github.com/Foddy/node-red-contrib-huemagic/issues/279)) (thx @spacewalker0815, @bobhobelman & @kazzyUK)
+* Devices without a battery (e.g. mains powered sensors) no longer break their node ([#446](https://github.com/Foddy/node-red-contrib-huemagic/issues/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](https://github.com/Foddy/node-red-contrib-huemagic/issues/447)) ([#386](https://github.com/Foddy/node-red-contrib-huemagic/issues/386)) ([#449](https://github.com/Foddy/node-red-contrib-huemagic/issues/449)) ([#316](https://github.com/Foddy/node-red-contrib-huemagic/issues/316)) (thx @Himola, @danieldaeschle, @stijnbrocker & @andesse)
+* The searches in the node configuration now report the real error instead of a generic one ([#449](https://github.com/Foddy/node-red-contrib-huemagic/issues/449)) ([#274](https://github.com/Foddy/node-red-contrib-huemagic/issues/274)) (thx @stijnbrocker & @TomGeoDK)
+* `msg.lastState` now really contains the previous state instead of a reference to the current one ([#322](https://github.com/Foddy/node-red-contrib-huemagic/issues/322)) (thx @valiquette)
+* Fixed the random color option, which threw an error instead of picking a color
+* Fixed `brightnessLevel: 0` not 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 `eventsource` dependency, 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](https://github.com/Foddy/node-red-contrib-huemagic/issues/414)) (thx @AleksCee)
+
+### v4.2.2
 
 * 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](https://github.com/Foddy/node-red-contrib-huemagic/issues/342)) (thx @bmdevx)
 * Fixed an error with non-functioning node configurations
 
-### v4.2.1
-
-* Commands are now re-executed up to three times if they fail due to a bridge timeout
-* The "image" option on the "Hue Light" node will now set the corresponding gradient colors on supported resources
-* Better handling of broken connections to the bridge ([#309](https://github.com/Foddy/node-red-contrib-huemagic/pull/309)) (thx)
-* Fixed an error with the "Hue Scenes" node on newer bridge firmwares ([#335](https://github.com/Foddy/node-red-contrib-huemagic/issues/335)) ([#339](https://github.com/Foddy/node-red-contrib-huemagic/pull/339)) (thx)
-* Fixed an uncaught exception on newer bridge firmwares ([#302](https://github.com/Foddy/node-red-contrib-huemagic/issues/302)) ([#309](https://github.com/Foddy/node-red-contrib-huemagic/pull/309)) (thx)
-* Updated dependencies to the latest versions
-* Fixed some typos here and there
-
-### v4.1.0
-
-* New queue worker throttles the number of parallel requests to the bridge to avoid 503 API limit errors (can be configured in the Bridge configuration)
-* Resources are now alphabetically sorted in the node´s configuration interface ([#282](https://github.com/Foddy/node-red-contrib-huemagic/pull/282)) (thx)
-* "Hue Brightness" node was optimized to output more accurate "dark" and "dayLight" values
-* Several optimizations in the documentation of some nodes
-
-### v4.0.5
-
-* The "Hue Group" node now contains the "resources" information with all linked resources behind the group/zone
-* Fixed an issue that caused Node-RED to restart if a command was sent before a node was initialized
-
-### v4.0.4
-
-* Fixed an issue with the bridge config node checking for updates too frequently ([#246](https://github.com/Foddy/node-red-contrib-huemagic/issues/246#issuecomment-1009376442))
-* Fixed an issue with multiple bridges configured
-
-### v4.0.3
-
-> **Attention!** HueMagic v4+ has been almost completely rewritten under the hood and requires at least the (square-shaped) Philips Hue Bridge firmware 1948086000+ from November 1st, 2021 ([Upgrade instructions](https://www.lighting.philips.com/content/B2C/en_US/microsites/meethue/marketing-catalog/huewireless_ca/support/security-advisory/general/where-and-how-can-i-update-my-hue-system-with-the-latest-software.html)) and Node-RED v1+ ([Upgrade instructions](https://nodered.org/docs/getting-started/local#upgrading-node-red)). If you are upgrading from a previous HueMagic version to the v4, you will have to reconfigure (not completely rebuild) all nodes by clicking them and selecting the appropriate device from the list. This also applies to nodes / functions that are operated in universal mode, as the numeric identifiers of the latest Philips Hue API version have been replaced in UUIDs. The nodes "Hue Switch", "Hue Button" & "Hue Tap" have been replaced in v4 by the universal and uniform node "Hue Buttons", which works with all button / switch devices that are connected to the Hue Bridge (please note here also the new API in the documentation). The request and return objects of the individual nodes are largely compatible with older HueMagic versions - with the exception of the nodes "Hue Bridge", "Hue Buttons", "Hue Scene" & "Hue Group". These need to be adjusted in the v4. Make sure that you meet the minimum technical requirements and have a quiet minute for the migration before upgrading to the v4.
-
-* HueMagic speaks now directly with the bridge without any submodules *(huejay dependency removed)*
-* Migrated to the newest CLIP/v2 API version from the Philips Hue bridge
-* Nodes are now updated via push notifications (SSE) from the bridge instead of periodic polling
-* Instant "current status" queries on each node with no loading time
-* "Hue Buttons" node supports all new Philips Hue buttons/switches (e.g. Dimmer Switch v2, Hue Wall Switch…)
-* All nodes provide additional property information in the output (check docs)
-* New universal node "Hue Buttons" replaces the following nodes: "Hue Switch", "Hue Button", "Hue Tap"
-* New "updated" object for all nodes, which only contains the properties that have been updated since the last state
-* New configuration option to suppress first message after node initialization (for all nodes)
-* New gradient color setting for compatible light sources (in "Hue Light" node)
-* New inject button for almost all nodes, which triggers the current status of a node
-* New "universal mode" support for the "Hue Rule" node
-* New SVG-version of each node icon for higher quality rendering in the Node-RED UI
-* New and full featured examples for each node right inside Node-RED
-* New color mix feature in "Hue Light" nodes with the ability to mix the current light color with another
-* New automatic brightness support based on the current time for "Hue Light" & "Hue Group" nodes
-* New "Superhero", "Neon City" & "Christmas" (for next year, sorry) animations in "Hue Magic" node
-* The custom alert effect on "Hue Light" & "Hue Group" nodes can now also be configured in brightness
-* All nodes will now also forward the last command that has been applied ([#249](https://github.com/Foddy/node-red-contrib-huemagic/issues/249))
-* "Hue Temperature" & "Hue Brightness" nodes can now also be activated & deactivated
-* "Hue Light" & "Hue Group" nodes can now also receive XY color settings
-* "Hue Light" & "Hue Group" can now also receive a named color temperature setting
-* "Hue Light" & "Hue Group" nodes can now receive future brightness states in "turned off" mode ([#244](https://github.com/Foddy/node-red-contrib-huemagic/issues/244))
-* Automatic light temperature setting outputs now values from 153 (coldest) to 500 (warmest)
-* Automatic color correction based on the light´s capabilities for more accurate color settings
-* Optimized node editor configuration UI to better match the current Node-RED´s UI
-* The option for "automatic firmware updates" on the bridge moved to the bridge configuration node
-* "Hue Group" node does no longer contain the "msg.info.model" & "msg.info.class" property
-* Fixed timeout connection issues to the bridge
-* Fixed an issue with non stopping custom animations ([#222](https://github.com/Foddy/node-red-contrib-huemagic/issues/222)), ([#224](https://github.com/Foddy/node-red-contrib-huemagic/issues/224)) & ([#226](https://github.com/Foddy/node-red-contrib-huemagic/pull/226)) (thx)
-* Node-RED will no longer crash if there is no active connection to the bridge ([#237](https://github.com/Foddy/node-red-contrib-huemagic/issues/237))
-* Fixed an issue that prevented the light / group from not reporting its own status when queried & node events were deactivated ([#248](https://github.com/Foddy/node-red-contrib-huemagic/issues/248))
-* Fixed an issue with nodes in universal mode ([#245](https://github.com/Foddy/node-red-contrib-huemagic/issues/245))
-* A possible attack target has been fixed ([#217](https://github.com/Foddy/node-red-contrib-huemagic/issues/217))
-* Moved away from "moment.js" to "Day.js" for date/time formatting inside the nodes
-* Updated README and help section on each node
-* Updated dependencies to the latest version
-
-### v3.0.0
-* Hue Motion, Hue Brightness, Hue Tap, Hue Switch & Hue Button nodes can now receive a status request
-* New "Universal Mode" for the Hue Motion, Hue Brightness, Hue Tap, Hue Switch & Hue Button nodes
-* The "colorTemp" property for Hue Light & Hue Group nodes can now also be set to "cold", "normal", "warm" or "auto"
-* New dynamic and automatically calculated color temperature based on the current time ("auto" mode in "colorTemp" property)
-* Nodes in "Universal Mode" are now also able to receive all events from devices of its type (optional)
-* Hue Magic animations are now prerendered to improve performance
-* 3 new Hue Magic animations ("Milkyway", "Beach" & "Forest")
-* New (simple) Hue Button example flow
-* Updated docs for almost all nodes and README
-* Fixed an error with future states and the HTTP request node ([#200](https://github.com/Foddy/node-red-contrib-huemagic/pull/200))
-* Other optimizations, dependency updates and clean up
-
 ### Previous versions
 The full changelog [changelog](https://github.com/Foddy/node-red-contrib-huemagic/blob/master/CHANGELOG.md) can be viewed here…
 
@@ -896,7 +1279,7 @@ If you like HueMagic, I appreciate a star or rating on this page! HueMagic is an
 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.
 
 ***
-<a href="https://www.jetbrains.com/?from=HueMagic"><img src="https://gistcdn.githack.com/Foddy/062045775c28f5993ad646aba80e678c/raw/c84ea4ad31c72dde0883638fc9eaa2b51bba9962/jb.svg" height="50"></a> <a href="https://www.browserstack.com?from=HueMagic"><img src="https://gistcdn.githack.com/Foddy/062045775c28f5993ad646aba80e678c/raw/c84ea4ad31c72dde0883638fc9eaa2b51bba9962/browserstack.svg" height="50"></a>
+<a href="https://www.jetbrains.com/?from=HueMagic"><img src="https://raw.githubusercontent.com/Foddy/node-red-contrib-huemagic/master/docs/images/sponsors/jetbrains.svg" height="50"></a><a href="https://dgtl.one/?from=HueMagic"><img src="https://raw.githubusercontent.com/Foddy/node-red-contrib-huemagic/master/docs/images/sponsors/dgtl-one.svg" height="50"> <a href="https://www.browserstack.com?from=HueMagic"><img src="https://raw.githubusercontent.com/Foddy/node-red-contrib-huemagic/master/docs/images/sponsors/browserstack.svg" height="50"></a>
 
-HueMagic for Node-RED is sponsored by [JetBrains](https://www.jetbrains.com/?from=HueMagic) and [BrowserStack](https://www.browserstack.com?from=HueMagic).<br>
+HueMagic for Node-RED is sponsored by [DGTL.ONE](https://dgtl.one/?from=HueMagic), [JetBrains](https://www.jetbrains.com/?from=HueMagic) and [BrowserStack](https://www.browserstack.com?from=HueMagic).<br>
 *Released under the [Apache License 2.0](https://tldrlegal.com/license/apache-license-2.0-(apache-2.0)).*