node-red-contrib-huemagic 4.2.2 → 5.0.0

package/huemagic/locales/en/hue-bridge-config.json

@@ -0,0 +1,40 @@
+{
+	"hue-bridge-config": {
+		"config": {
+			"name": "Name",
+			"apikey": "API Key",
+			"missing-ip": "Missing Hue Bridge IP…",
+			"disable-events": "Disable events",
+			"disable-events-info": "Disable events on all nodes",
+			"searching": "Searching for Hue Bridges…",
+			"none-found": "No Hue Bridges found!",
+			"unknown-error": "Something went wrong. Please retry.",
+			"invalid": "Sorry. Your selected Hue Bridge is invalid: ",
+			"error-select-first": "Please select your Hue Bridge before trying to create a new user!",
+			"waiting": "waiting for the link button…",
+			"new-user-press": "Please press the button on your Hue Bridge now to create a new user!",
+			"retry": "No button press detected. Please retry…",
+			"success": "User created successfully!",
+			"connecting": "Connecting with the bridge…",
+			"autoupdates": "Activate automatic firmware updates",
+			"bridge-ip": "Bridge IP",
+			"worker": "Worker"
+		},
+		"node": {
+			"title": "Hue Bridge",
+			"statusmsg": "Status queried successfully…",
+			"initializing": "Initializing the bridge (__bridge__)…",
+			"connected": "Connected to bridge",
+			"processing": "Processing bridge resources…",
+			"initial-emit": "Initial emit of resource states…",
+			"keep-updated": "Keeping nodes up-to-date…",
+			"subscribing": "Subscribing to bridge events…",
+			"unsubscribing": "Unsubscribing from bridge events…",
+			"no-legacy-api": "The bridge does not answer on the legacy API, continuing without its configuration…",
+			"request-error": "Error requesting info from the bridge (__error__)",
+			"connection-lost": "Connection to the bridge lost (__reason__). Trying to reconnect in __seconds__ seconds…",
+			"resources-changed": "Resources on the bridge have changed. Reloading…",
+			"not-connected": "The bridge is not connected."
+		}
+	}
+}

package/huemagic/locales/{en-US → en}/hue-bridge.html

@@ -27,7 +27,10 @@ With the "fetch" command you can output a list of specific devices that are curr
 
 ### Change Hue Bridge settings
 
-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:
+You can use the following command to change specific settings on the bridge. Transfer the object `msg.payload.settings` with the following setting options to the node:
+
+> [!WARNING]
+> Changing the network settings requires reconfiguring the bridge on HueMagic.
 
 : 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`)
@@ -89,5 +92,5 @@ If the status of the node has changed via a certain command, the entire command
 
 HueMagic provides some sample configurations for this node. 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.
 
-![examples](https://user-images.githubusercontent.com/5302050/148681840-2275c15a-7c0c-4a37-b817-199608e571d2.gif)
+![examples](hue/assets/huemagic-examples.gif)
 </script>

package/huemagic/locales/{en-US → en}/hue-bridge.json

@@ -1,15 +1,13 @@
 {
-	"hue-bridge":
-	{
-		"config":
-		{
+	"hue-bridge": {
+		"config": {
 			"name": "Name",
 			"input-name": "Hue Bridge name",
 			"skipglobalevents-info": "Skip global device updates / messages on this node",
-			"sendinitevents-node": "Do not suppress initialization event"
+			"sendinitevents-node": "Do not suppress initialization event",
+			"bridge": "Bridge"
 		},
-		"node":
-		{
+		"node": {
 			"title": "Hue Bridge",
 			"not-configured": "not configured",
 			"connecting": "connecting…",
@@ -21,7 +19,8 @@
 			"settings-updated": "settings updated",
 			"input": "settings / fetch",
 			"output": "bridge information",
-			"statusmsg": "Status queried successfully…"
+			"statusmsg": "Status queried successfully…",
+			"error-not-available": "The bridge is not yet available. Please wait until HueMagic has established a connection with the bridge."
 		}
 	}
-}
+}

package/huemagic/locales/{en-US → en}/hue-brightness.html

@@ -3,7 +3,9 @@ The "Hue Brightness" node can read the current light level from a suitable senso
 
 ### Setup
 
-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.
 
@@ -27,11 +29,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`
@@ -63,5 +66,5 @@ If the status of the node has changed via a certain command, the entire command
 
 HueMagic provides some sample configurations for this node. 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.
 
-![examples](https://user-images.githubusercontent.com/5302050/148681840-2275c15a-7c0c-4a37-b817-199608e571d2.gif)
+![examples](hue/assets/huemagic-examples.gif)
 </script>

package/huemagic/locales/{en-US → en}/hue-brightness.json

@@ -1,22 +1,22 @@
 {
-	"hue-brightness":
-	{
-		"config":
-		{
+	"hue-brightness": {
+		"config": {
 			"name": "Name",
 			"input-name": "Brightness sensor name",
 			"skipevents-node": "Skip events from node",
 			"sendinitevents-node": "Do not suppress initialization event",
+			"onlycommands-node": "Only report after a command",
 			"searching": "Searching sensors…",
 			"none-found": "No brightness sensors found!",
 			"unknown-error": "Something went wrong. Please retry.",
 			"sensor": "Sensor",
 			"all": "All groups / lights",
 			"universalevents": "Universal Events",
-			"universalevents-node": "Receives all messages from other nodes of the same type (only in universal mode)"
+			"universalevents-node": "Receives all messages from other nodes of the same type (only in universal mode)",
+			"bridge": "Bridge",
+			"darkthreshold": "Dark below"
 		},
-		"node":
-		{
+		"node": {
 			"title": "Hue Brightness",
 			"not-configured": "not configured",
 			"deactivated": "deactivated",
@@ -29,7 +29,9 @@
 			"output": "brightness (changed)",
 			"universal": "universal mode",
 			"command": "executing command…",
-			"statusmsg": "Status queried successfully…"
+			"statusmsg": "Status queried successfully…",
+			"error-no-id": "Please submit a valid sensor ID.",
+			"error-not-available": "The sensor is not yet available. Please wait until HueMagic has established a connection with the bridge or check whether the resource ID in the configuration is valid."
 		}
 	}
-}
+}

package/huemagic/locales/{en-US → en}/hue-buttons.html

@@ -3,7 +3,7 @@ The "Hue Buttons" node receives switching events from input devices connected to
 
 ### Setup
 
-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.
 
@@ -22,7 +22,8 @@ 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 with `action` (`start` or `repeat`), `direction` (`clock_wise` or `counter_clock_wise`), `clockwise` (boolean), `steps` (1000 steps are a full rotation), `degrees` and `duration` in milliseconds
 : updated (string): Time of the last update of the resource by HueMagic (ISO 8601)
 
 #### Information about the switch/button under `msg.info`
@@ -54,5 +55,5 @@ If the status of the node has changed via a certain command, the entire command
 
 HueMagic provides some sample configurations for this node. 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.
 
-![examples](https://user-images.githubusercontent.com/5302050/148681840-2275c15a-7c0c-4a37-b817-199608e571d2.gif)
+![examples](hue/assets/huemagic-examples.gif)
 </script>

package/huemagic/locales/en/hue-buttons.json

@@ -0,0 +1,42 @@
+{
+	"hue-buttons": {
+		"config": {
+			"name": "Name",
+			"input-name": "Button name",
+			"skipevents-node": "Skip events from node",
+			"sendinitevents-node": "Do not suppress initialization event",
+			"onlycommands-node": "Only report after a command",
+			"searching": "Searching Hue Buttons…",
+			"none-found": "No Hue Button found!",
+			"unknown-error": "Something went wrong. Please retry.",
+			"button": "Button",
+			"universalevents": "Universal Events",
+			"universalevents-node": "Receives all messages from other nodes of the same type (only in universal mode)",
+			"bridge": "Bridge"
+		},
+		"node": {
+			"title": "Hue Buttons",
+			"not-configured": "not configured",
+			"waiting": "waiting…",
+			"button-on": "On",
+			"action-pressed": "pressed",
+			"action-holded": "held",
+			"action-shortreleased": "short released",
+			"action-longreleased": "long released",
+			"input": "status query",
+			"output": "pressed button",
+			"universal": "universal mode",
+			"command": "executing command…",
+			"statusmsg": "Status queried successfully…",
+			"error-no-id": "Please submit a valid button ID.",
+			"error-not-available": "The button/switch is not yet available. Please wait until HueMagic has established a connection with the bridge or check whether the resource ID in the configuration is valid.",
+			"action-repeated": "repeated",
+			"action-doublepressed": "double pressed",
+			"dial-clockwise": "Dial ↻ __degrees__°",
+			"dial-counterclockwise": "Dial ↺ __degrees__°",
+			"button-status": "Button #__button__ (__action__)",
+			"error-no-switchmode": "This device has no configurable switch mode.",
+			"error-invalid-switchmode": "Invalid switch mode. This device supports: __modes__"
+		}
+	}
+}

package/huemagic/locales/en/hue-contact.html

@@ -0,0 +1,67 @@
+<script type="text/markdown" data-help-name="hue-contact">
+The "Hue Contact" node reports whether a contact sensor (e.g. Hue Secure) is currently open or closed.
+
+### Setup
+
+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.
+
+: 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:
+
+: 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`
+
+: 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`
+
+: 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.
+
+### Examples from HueMagic
+
+HueMagic provides some sample configurations for this node. 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.
+
+![examples](hue/assets/huemagic-examples.gif)
+
+</script>

package/huemagic/locales/en/hue-contact.json

@@ -0,0 +1,35 @@
+{
+	"hue-contact": {
+		"config": {
+			"name": "Name",
+			"input-name": "Sensor name",
+			"skipevents-node": "Skip events from node",
+			"sendinitevents-node": "Do not suppress initialization event",
+			"onlycommands-node": "Only report after a command",
+			"searching": "Searching contact sensors…",
+			"none-found": "No contact sensors found!",
+			"unknown-error": "Something went wrong. Please retry.",
+			"sensor": "Sensor",
+			"universalevents": "Universal Events",
+			"universalevents-node": "Receives all messages from other nodes of the same type (only in universal mode)",
+			"bridge": "Bridge"
+		},
+		"node": {
+			"title": "Hue Contact",
+			"not-configured": "not configured",
+			"not-reachable": "not reachable",
+			"contact": "contact",
+			"no-contact": "no contact",
+			"activated": "activated",
+			"deactivated": "deactivated",
+			"input": "activate / deactivate / status",
+			"output": "contact",
+			"universal": "universal mode",
+			"command": "executing command…",
+			"statusmsg": "Status queried successfully…",
+			"error-no-id": "Please submit a valid sensor ID.",
+			"error-not-available": "The sensor is not yet available. Please wait until HueMagic has established a connection with the bridge or check whether the resource ID in the configuration is valid.",
+			"tampered": "tampered"
+		}
+	}
+}

package/huemagic/locales/{en-US → en}/hue-group.html

@@ -3,7 +3,7 @@ The "Hue Group" node can control several lights behind a group on the bridge at
 
 ### Setup
 
-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.
 
@@ -15,7 +15,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.
 
 : payload (boolean): `true` switches the whole group on, `false` switches them off
 
@@ -23,10 +23,12 @@ To quickly turn an entire group on or off in simple mode, pass an object with th
 
 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:
 
-: 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): Percentage value of a relative brightness change. Valid range is from -100% to +100%. Positive values will increase brightness. Default is +10%
+: decrementBrightness (int): Percentage value of a relative brightness change. Valid range is from -100% to +100%. Positive values will decrease brightness. Default is +10%
 : 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
@@ -39,13 +41,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.
+
+> [!NOTE]
+> 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).
 
 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.
 
 #### Status object under `msg.payload`
 
 : 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)
+: 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`
@@ -72,5 +83,5 @@ If the status of the node has changed via a certain command, the entire command
 
 HueMagic provides some sample configurations for this node. 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.
 
-![examples](https://user-images.githubusercontent.com/5302050/148681840-2275c15a-7c0c-4a37-b817-199608e571d2.gif)
+![examples](hue/assets/huemagic-examples.gif)
 </script>

package/huemagic/locales/{en-US → en}/hue-group.json

@@ -1,12 +1,11 @@
 {
-	"hue-group":
-	{
-		"config":
-		{
+	"hue-group": {
+		"config": {
 			"name": "Name",
 			"input-name": "Group name",
 			"skipevents-node": "Skip events from node",
 			"sendinitevents-node": "Do not suppress initialization event",
+			"onlycommands-node": "Only report after a command",
 			"searching": "Searching groups…",
 			"none-found": "No groups found!",
 			"unknown-error": "Something went wrong. Please retry.",
@@ -15,10 +14,10 @@
 			"colornamer-info": "Activate color naming",
 			"all": "All groups / lights",
 			"universalevents": "Universal Events",
-			"universalevents-node": "Receives all messages from other nodes of the same type (only in universal mode)"
+			"universalevents-node": "Receives all messages from other nodes of the same type (only in universal mode)",
+			"bridge": "Bridge"
 		},
-		"node":
-		{
+		"node": {
 			"title": "Hue Group",
 			"not-configured": "not configured",
 			"init": "initializing…",
@@ -31,11 +30,17 @@
 			"error-input": "input error",
 			"error-no-id": "No group Id specified.",
 			"error-invalid-sat": "Invalid saturation setting. Only 0 - 254 allowed.",
-			"error-invalid-temp": "Invalid color temprature. Only 153 - 500 allowed.",
+			"error-invalid-temp": "Invalid color temperature. Only 153 - 500 allowed.",
 			"input": "turn on / off",
 			"output": "status",
 			"command": "executing command…",
-			"statusmsg": "Status queried successfully…"
+			"statusmsg": "Status queried successfully…",
+			"error-not-available": "The group is not yet available. Please wait until HueMagic has established a connection with the bridge or check whether the resource ID in the configuration is valid.",
+			"error-invalid-brightness": "Invalid brightness setting. Only 0 - 100 percent allowed.",
+			"error-invalid-brightness-level": "Invalid brightness setting. Only 0 - 254 allowed.",
+			"error-invalid-increment": "Invalid incrementBrightness setting. Only -100% to 100% allowed.",
+			"error-invalid-decrement": "Invalid decrementBrightness setting. Only -100% to 100% allowed.",
+			"error-no-colorloop": "The colorloop effect is not available for this group."
 		}
 	}
-}
+}

package/huemagic/locales/{en-US → en}/hue-light.html

@@ -3,7 +3,7 @@ The "Hue Light" node can control lights connected to the bridge and receive thei
 
 ### Setup
 
-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.
 
@@ -35,7 +35,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
 : 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)
@@ -93,5 +93,5 @@ If the status of the node has changed via a certain command, the entire command
 
 HueMagic provides some sample configurations for this node. 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.
 
-![examples](https://user-images.githubusercontent.com/5302050/148681840-2275c15a-7c0c-4a37-b817-199608e571d2.gif)
+![examples](hue/assets/huemagic-examples.gif)
 </script>

package/huemagic/locales/en/hue-light.json

@@ -0,0 +1,44 @@
+{
+	"hue-light": {
+		"config": {
+			"name": "Name",
+			"input-name": "Light name",
+			"skipevents-node": "Skip events from node",
+			"sendinitevents-node": "Do not suppress initialization event",
+			"onlycommands-node": "Only report after a command",
+			"searching": "Searching lights…",
+			"none-found": "No lights found!",
+			"unknown-error": "Something went wrong. Please retry.",
+			"light": "Light",
+			"colornamer": "Colornamer",
+			"colornamer-info": "Activate color naming",
+			"universalevents": "Universal Events",
+			"universalevents-node": "Receives all messages from other nodes of the same type (only in universal mode)",
+			"bridge": "Bridge"
+		},
+		"node": {
+			"title": "Hue Light",
+			"not-configured": "not configured",
+			"init": "initializing…",
+			"not-reachable": "not reachable",
+			"universal": "universal mode",
+			"turned-on": "turned on",
+			"turned-on-percent": "turned on (__percent__%)",
+			"turned-off": "turned off",
+			"error-no-id": "No light Id defined. Please check the docs.",
+			"error-input": "input error",
+			"error-invalid-temp": "Invalid color temperature. Only 153 - 500 allowed.",
+			"input": "turn on / off",
+			"output": "status",
+			"command": "executing command…",
+			"statusmsg": "Status queried successfully…",
+			"error-not-available": "The light is not yet available. Please wait until HueMagic has established a connection with the bridge or check whether the resource ID in the configuration is valid.",
+			"error-invalid-brightness": "Invalid brightness setting. Only 0 - 100 percent allowed.",
+			"error-invalid-brightness-level": "Invalid brightness setting. Only 0 - 254 allowed.",
+			"error-invalid-sat": "Invalid saturation setting. Only 0 - 100 allowed.",
+			"error-no-colorloop": "The colorloop effect is not available for this light.",
+			"error-invalid-effect": "Invalid effect. This light supports: __effects__",
+			"error-invalid-powerup": "Invalid power up setting. Allowed presets are: __presets__"
+		}
+	}
+}

package/huemagic/locales/{en-US → en}/hue-magic.html

@@ -64,5 +64,5 @@ This node does not output any status messages. Please connect the output of the
 
 HueMagic provides some sample configurations for this node. 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.
 
-![examples](https://user-images.githubusercontent.com/5302050/148681840-2275c15a-7c0c-4a37-b817-199608e571d2.gif)
+![examples](hue/assets/huemagic-examples.gif)
 </script>

package/huemagic/locales/{en-US → en}/hue-motion.html

@@ -3,7 +3,7 @@ The "Hue motion" node can register and report movements from a suitable sensor o
 
 ### Setup
 
-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.
 
@@ -60,5 +60,5 @@ If the status of the node has changed via a certain command, the entire command
 
 HueMagic provides some sample configurations for this node. 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.
 
-![examples](https://user-images.githubusercontent.com/5302050/148681840-2275c15a-7c0c-4a37-b817-199608e571d2.gif)
+![examples](hue/assets/huemagic-examples.gif)
 </script>

package/huemagic/locales/{en-US → en}/hue-motion.json

@@ -1,21 +1,20 @@
 {
-	"hue-motion":
-	{
-		"config":
-		{
+	"hue-motion": {
+		"config": {
 			"name": "Name",
 			"input-name": "Sensor name",
 			"skipevents-node": "Skip events from node",
 			"sendinitevents-node": "Do not suppress initialization event",
+			"onlycommands-node": "Only report after a command",
 			"searching": "Searching motion sensors…",
 			"none-found": "No motion sensors found!",
 			"unknown-error": "Something went wrong. Please retry.",
 			"sensor": "Sensor",
 			"universalevents": "Universal Events",
-			"universalevents-node": "Receives all messages from other nodes of the same type (only in universal mode)"
+			"universalevents-node": "Receives all messages from other nodes of the same type (only in universal mode)",
+			"bridge": "Bridge"
 		},
-		"node":
-		{
+		"node": {
 			"title": "Hue Motion",
 			"not-configured": "not configured",
 			"not-reachable": "not reachable",
@@ -27,7 +26,11 @@
 			"output": "motion detected",
 			"universal": "universal mode",
 			"command": "executing command…",
-			"statusmsg": "Status queried successfully…"
+			"statusmsg": "Status queried successfully…",
+			"error-no-id": "Please submit a valid sensor ID.",
+			"error-not-available": "The sensor is not yet available. Please wait until HueMagic has established a connection with the bridge or check whether the resource ID in the configuration is valid.",
+			"error-no-sensitivity": "This motion source has no adjustable sensitivity.",
+			"error-invalid-sensitivity": "Invalid sensitivity. Only 0 - __max__ allowed."
 		}
 	}
-}
+}

package/huemagic/locales/{en-US → en}/hue-rules.html

@@ -3,7 +3,7 @@ The "Hue Rule" node can activate or deactivate rules saved in the bridge and cal
 
 ### Setup
 
-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.
 
@@ -65,5 +65,5 @@ If the status of the node has changed via a certain command, the entire command
 
 HueMagic provides some sample configurations for this node. 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.
 
-![examples](https://user-images.githubusercontent.com/5302050/148681840-2275c15a-7c0c-4a37-b817-199608e571d2.gif)
+![examples](hue/assets/huemagic-examples.gif)
 </script>