node-red-contrib-huemagic 2.8.2 → 4.0.0

package/huemagic/locales/en-US/hue-magic.html

@@ -1,60 +1,68 @@
-<script type="text/x-red" data-help-name="hue-magic">
-    <p>Hue Magic node for animations</p>
-
-    <h3>Setup</h3>
-    <p>Select whether the animation should be looped indefinitely and / or whether the previous state should be restored after the animation has ended / stopped. Select one of the included animations and connect the node to a group or a light.</p>
-
-    <h3>Start / Stop</h3>
-    <p>Starts or stops an animation based on the passed in <b>msg.payload</b> values of:</p>
-    <dl class="message-properties">
-        <dt>true<span class="property-type">boolean</span></dt>
-        <dd>Starts the animation</dd>
-
-        <dt>false<span class="property-type">boolean</span></dt>
-        <dd>Stops the animation</dd>
-    </dl>
-
-    <h3>Custom animations</h3>
-    <p>Alternatively, you can create and use your own animations. To do this, create an array and pass it to <b>msg.payload.steps</b> with the following parameters.</p>
-    <dl class="message-properties">
-        <dt>delay<span class="property-type">int</span></dt>
-        <dd>Execute this frame after the delay (in ms)</dd>
-
-        <dt>animation<span class="property-type">object</span></dt>
-        <dd>Insert all parameters that should be animated here. Supports all values of "Hue Light" and "Hue Group" node.</dd>
-    </dl>
-
-    <h3>Special commands</h3>
-    <p>Sometimes it makes sense for animations to be played out in disorder. For example, to imitate fire more realistically. To do this, create an object and pass it to <b>msg.payload.specials</b> with the following parameters.</p>
-    <dl class="message-properties">
-        <dt>randomOrder<span class="property-type">boolean</span></dt>
-        <dd>Execute steps in random order</dd>
-    </dl>
-
-    <h4>Example (custom animation)</h4>
-<code>
-<pre>
-{
-    "animate": true,
-    "steps": [
-        {
-            "delay": 500,
-            "animation": {
-                "hex": "#FF0000",
-                "transitionTime": 1
-            }
-        },
-        {
-            "delay": 500,
-            "animation": {
-                "hex": "#0000FF",
-                "transitionTime": 1
+<script type="text/markdown" data-help-name="hue-magic">
+The "Hue Magic" node can apply complex and custom animations to lights and groups.
+
+### Setup
+
+First give the node a name in order to clearly classify your animation in the Node-RED interface. You then have the choice between the options "Loop" and "Restore". Select the loop option if you want your animation to run endlessly on a light or group until you manually stop it. If you want to restore the previous state of the target resource (light / group) after the animation has ended, check the "Restore" option. Otherwise the last frame of the animation remains on the respective resource.
+
+Below you can choose from pre-made animations from HueMagic. Click on your desired animation to set it.
+
+### Start / stop animation
+
+To play or stop an animation, pass an object with the following content to the node:
+
+: payload (boolean): `true`, starts the animation, `false`, stops the animation
+
+### Own animations
+
+If you pass your own animation to the node, the preselected, pre-defined animation (if set) will be temporarily replaced by yours. Own HueMagic animations are a sequence of commands that have been combined in an array. Each array element forms a step - whereby a step can also consist of several frames (transition effects).
+
+Create an `array` with the respective animation steps in the form of an object and transfer it to the HueMagic node under `msg.payload.steps`.
+
+: delay (int): Number of milliseconds to wait until this step is carried out
+: animation (object): The object contains the action(s) to be carried out in this step. Identical parameters as for the "Hue Light" & "Hue Group" nodes
+
+### Example of your own animation
+
+This example shows what a simple animation could look like. In the first step, the delay of 500 milliseconds is waited for. The color of the light is then slowly changed to red over a period of one second. As soon as the light has completely changed to red, the second step is carried out, which also has a delay of 500 milliseconds. Finally the color changes to blue.
+
+If you have set the animation to play indefinitely, this process is repeated indefinitely until you manually stop the animation or redeploy the node.
+
+Pass the following object in `msg.payload` to play the example animation.
+
+    {
+        "animate": true,
+        "steps": [
+            {
+                "delay": 500,
+                "animation": {
+                    "hex": "#FF0000",
+                    "transitionTime": 1
+                }
+            },
+            {
+                "delay": 500,
+                "animation": {
+                    "hex": "#0000FF",
+                    "transitionTime": 1
+                }
             }
-        }
-    ]
-}</pre>
-</code>
+        ]
+    }
+
+### Special commands
+
+Sometimes it makes sense to play an animation in a disorderly manner - e.g. if fire should be imitated more realistically. To play the individual steps randomly, you can pass the following command to `msg.payload.specials`:
+
+: randomOrder (boolean | any): `true`, activates the random playback of the individual animation steps
+
+### Tips and hints
+
+This node does not output any status messages. Please connect the output of the node with a group instead of individual lights if you want to animate several lights at the same time with the same animation. The previews of the pre-made animations are simulations and may differ slightly (timing, colors) from the actual animation on a resource.
+
+### 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.
 
-    <h3>Tips & Hints</h3>
-    <p>Connect the Hue Magic node to only one light or a whole group node to save API requests on the Hue Bridge. The animation previews can differ slightly from the real result on a lamp / group.</p>
+![examples](https://user-images.githubusercontent.com/5302050/148681840-2275c15a-7c0c-4a37-b817-199608e571d2.gif)
 </script>

package/huemagic/locales/en-US/hue-magic.json

@@ -21,7 +21,9 @@
 			"animating": "animating…",
 			"stopped": "stopped",
 			"input": "run / stop animation",
-			"output": "light or group"
+			"output": "light or group",
+			"command": "executing command…",
+			"playmsg": "Animation started…"
 		}
 	}
 }

package/huemagic/locales/en-US/hue-motion.html

@@ -1,60 +1,64 @@
-<script type="text/x-red" data-help-name="hue-motion">
-    <p>Hue motion node to control the motion sensor and receive motion events.</p>
+<script type="text/markdown" data-help-name="hue-motion">
+The "Hue motion" node can register and report movements from a suitable sensor on the bridge.
 
-    <h3>Setup</h3>
-    <p>Select the preconfigured Hue Bridge and hit the search button to find all available motion sensors. Type in the name of the sensor manually or keep the default device name. Note that events will only be sent if a motion is detected, if a motion stops or if the motion sensor receives the "Activate / Deactivate" command. If necessary, all status updates of this node can be ignored by activating the "Skip events" option.</p>
+### Setup
 
-    <h3>Activate / Deactivate</h3>
-    <p>Activates or deactivates the motion sensor based on the passed in <b>msg</b> values of:</p>
-    <dl class="message-properties">
-        <dt>true<span class="property-type">boolean</span></dt>
-        <dd>Activates the motion sensor</dd>
+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.
 
-        <dt>false<span class="property-type">boolean</span></dt>
-        <dd>Deactivates the motion sensor</dd>
+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.
 
-        <dt class="optional">status<span class="property-type">any</span></dt>
-        <dd>Returns the current status message of the node without taking any action</dd>
-    </dl>
+### Get status
 
-    <h3>Motion Events</h3>
-    <p>The event message that the motion sensor sends contains the following data in the <b>msg.payload</b> object:</p>
-    <dl class="message-properties">
-        <dt>active<span class="property-type">boolean</span></dt>
-        <dd>Current sensor state</dd>
+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.
 
-        <dt>motion<span class="property-type">boolean</span></dt>
-        <dd>Indicates if a motion is detected or not</dd>
+: status (boolean): Returns the current status of the sensor
 
-        <dt>updated<span class="property-type">string</span></dt>
-        <dd>ISO 8601 date string of the last detected motion</dd>
-    </dl>
+### Turn the sensor on / off
 
-    <h3>Additional Sensor Info</h3>
-    <p>Additional information about the sensor is going to be sent to the <b>msg.info</b> object:</p>
-    <dl class="message-properties">
-        <dt>id<span class="property-type">int</span></dt>
-        <dd>Numerical id of the sensor as registered on the bridge</dd>
+If necessary, the sensor can be turned on and off remotely. If the sensor has been turned off, it no longer registers any movements and accordingly no longer outputs them. To do this, pass an object with the following content:
 
-        <dt>uniqueId<span class="property-type">string</span></dt>
-        <dd>Unique Id of the sensor (typically hardware id)</dd>
+: payload (boolean): `true` turns the sensor on,` false` turns it off
 
-        <dt>name<span class="property-type">string</span></dt>
-        <dd>Name for the sensor</dd>
+### Status messages from the node
 
-        <dt>type<span class="property-type">string</span></dt>
-        <dd>Sensor type (e.g. Daylight, CLIPTemperature, ZGPSwitch)</dd>
+As soon as the sensor has registered a movement, the following status message is returned by the node:
 
-        <dt>softwareVersion<span class="property-type">float</span></dt>
-        <dd>Software version of the sensor</dd>
+#### Status object under `msg.payload`
 
-        <dt>battery<span class="property-type">int</span></dt>
-        <dd>Current battery level of the sensor in percent</dd>
+: active (boolean): Indicates whether the sensor is switched on or off
+: reachable (boolean | string): `true` if the sensor is connected to the bridge, `unknown` if the connection status deviates
+: connectionStatus (string): The current connection status with the bridge in the form of a string. Can contain `connected`, `disconnected`, `connectivity_issue` or `unidirectional_incoming` as a value
+: motion (boolean): Indicates whether a motion has been registered
+: updated (string): Time of the last update of the resource by HueMagic (ISO 8601)
 
-        <dt>model<span class="property-type">object</span></dt>
-        <dd>The model object of the sensor includes model specific information like the model.id, model.manufacturer, model.name and model.type</dd>
-    </dl>
+#### Information about the sensor under `msg.info`
 
-    <h3>Last State Information</h3>
-    <p>This node also sends the entire last state data (before the update) in the <b>msg.lastState</b> object. It can either contain false (boolean) or the objects payload (msg.lastState.payload) and info (msg.lastState.info). The return value "false" is only sent if there was no last state, e.g. when the node was newly created or restarted.</p>
+: 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 `motion`)
+: softwareVersion (string): The current firmware of the sensor
+: battery (float): The current battery level of the sensor
+: batteryState (string): The current status of the battery level. Can contain `normal`, `low` or `critical` as a value
+: model (object): Contains the model information of the sensor under `id`, `manufacturer`, `name`, `type` and `certified`
+
+#### 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](https://user-images.githubusercontent.com/5302050/148681840-2275c15a-7c0c-4a37-b817-199608e571d2.gif)
 </script>

package/huemagic/locales/en-US/hue-motion.json

@@ -5,12 +5,14 @@
 		{
 			"name": "Name",
 			"input-name": "Sensor name",
-			"skipevents": "Skip events",
 			"skipevents-node": "Skip events from node",
+			"sendinitevents-node": "Do not suppress initialization event",
 			"searching": "Searching motion sensors…",
 			"none-found": "No motion sensors found!",
 			"unknown-error": "Something went wrong. Please retry.",
-			"sensor": "Sensor"
+			"sensor": "Sensor",
+			"universalevents": "Universal Events",
+			"universalevents-node": "Receives all messages from other nodes of the same type (only in universal mode)"
 		},
 		"node":
 		{
@@ -21,8 +23,11 @@
 			"no-motion": "no motion",
 			"activated": "activated",
 			"deactivated": "deactivated",
-			"input": "activate / deactivate",
-			"output": "motion detected"
+			"input": "activate / deactivate / status",
+			"output": "motion detected",
+			"universal": "universal mode",
+			"command": "executing command…",
+			"statusmsg": "Status queried successfully…"
 		}
 	}
 }

package/huemagic/locales/en-US/hue-rules.html

@@ -1,74 +1,69 @@
-<script type="text/x-red" data-help-name="hue-rules">
-    <p>Hue rule node to receive rule events or to enable / disable rules.</p>
-
-    <h3>Setup</h3>
-    <p>Select the preconfigured Hue Bridge and hit the search button to find all available rules on the bridge. Type in the name of the rule manually or keep the default name. Note that events will only be sent on deploy (once) and if the rule is triggered on the bridge. If necessary, all status updates of this node can be ignored by activating the "Skip events" option.</p>
-
-    <h3>Enable / Disable</h3>
-    <p>Activates or deactivates the rule based on the passed in <b>msg.payload</b> values of:</p>
-    <dl class="message-properties">
-        <dt>true<span class="property-type">boolean</span></dt>
-        <dd>Enables the rule</dd>
-
-        <dt>false<span class="property-type">boolean</span></dt>
-        <dd>Disables the rule</dd>
-    </dl>
-
-    <h3>Trigger events</h3>
-    <p>The event message that the rule node sends contains the following data in the <b>msg.payload</b> object:</p>
-    <dl class="message-properties">
-        <dt>triggered<span class="property-type">string</span></dt>
-        <dd>ISO 8601 date string of the last time rule was triggered</dd>
-    </dl>
-
-    <h3>Additional Rule Info</h3>
-    <p>Additional information about the rule is going to be sent to the <b>msg.info</b> object:</p>
-    <dl class="message-properties">
-        <dt>id<span class="property-type">int</span></dt>
-        <dd>Numerical id of the rule as registered on the bridge</dd>
-
-        <dt>created<span class="property-type">string</span></dt>
-        <dd>ISO 8601 date string of the creation date of the rule</dd>
-
-        <dt>name<span class="property-type">string</span></dt>
-        <dd>Name of the rule</dd>
-
-        <dt>timesTriggered<span class="property-type">int</span></dt>
-        <dd>Number of times rule was triggered</dd>
-
-        <dt>owner<span class="property-type">string</span></dt>
-        <dd>User who created the rule</dd>
-
-        <dt>status<span class="property-type">string</span></dt>
-        <dd>enabled or disabled, rule is triggerable on enabled</dd>
-    </dl>
-
-    <h3>Rule Conditions</h3>
-    <p>An array of objects representing the rule conditions is going to be sent to the <b>msg.conditions</b> array:</p>
-    <dl class="message-properties">
-        <dt>address<span class="property-type">string</span></dt>
-        <dd>The sensor resource/state location for the condition</dd>
-
-        <dt>operator<span class="property-type">string</span></dt>
-        <dd>The operator for the condition</dd>
-
-        <dt>value<span class="property-type">string</span></dt>
-        <dd>The value used in conjunction with operator</dd>
-    </dl>
-
-    <h3>Rule Actions</h3>
-    <p>An array of objects representing the rule actions is going to be sent to the <b>msg.actions</b> array:</p>
-    <dl class="message-properties">
-        <dt>address<span class="property-type">string</span></dt>
-        <dd>The actionable resource location</dd>
-
-        <dt>method<span class="property-type">string</span></dt>
-        <dd>Type of method for the action (e.g. GET, PUT)</dd>
-
-        <dt>body<span class="property-type">object</span></dt>
-        <dd>The body of the action</dd>
-    </dl>
-
-    <h3>Last State Information</h3>
-    <p>This node also sends the entire last state data (before the update) in the <b>msg.lastState</b> object. It can either contain false (boolean) or the objects payload (msg.lastState.payload) and info (msg.lastState.info). The return value "false" is only sent if there was no last state, e.g. when the node was newly created or restarted.</p>
+<script type="text/markdown" data-help-name="hue-rules">
+The "Hue Rule" node can activate or deactivate rules saved in the bridge and call up their settings.
+
+### 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.
+
+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.
+
+### Get properties / settings
+
+Outputs the current properties of the rule as soon as a `msg.payload` object with the following content has been passed to the node. Alternatively, you can also press the button in the Node-RED interface without having to pass a message to the node beforehand.
+
+: status (boolean): Returns the current status of the rule
+
+### Activate / deactivate rule
+
+The rule can be activated and deactivated if necessary. If the rule has been deactivated, it will no longer run in the bridge until you reactivate it. To do this, pass an object with the following content:
+
+: payload (boolean): `true` activates the rule, `false` deactivates it
+
+### Status messages from the node
+
+As soon as the status (activated / deactivated) of a rule changes, the following status message is returned by the node:
+
+#### Status object under `msg.payload`
+
+: enabled (boolean): Indicates whether the rule is activated or deactivated
+: triggered (string): Time of the last execution (ISO 8601)
+
+#### Information about the rule under `msg.info`
+
+: id (string): The unique ID of the rule
+: created (string): Date of creation of the rule (ISO 8601)
+: name (string): Name of the rule on the bridge
+: timesTriggered (int): Number of times the rule was executed on the bridge
+: owner (string): ID of the owner of this rule
+: status (string): Status of the rule in the form of a string
+
+#### Rule conditions under `msg.conditions` (array)
+
+: address (string): Path to an attribute of a sensor
+: operator (string): operator
+: value (string): The value to be checked
+
+#### Rule actions under `msg.actions` (array)
+
+: address (string): The destination address of the resource
+: method (string): The query method
+: body (object): The action to be taken
+
+#### Status changes under `msg.updated`
+
+Lists individual parameters in the form of an object that have changed compared to the last state of the rule. If no changes have been registered, this object is empty.
+
+#### Last status of the rule under `msg.lastState`
+
+Contains the complete object (see output values above) of the last status before the last registered change of the rule. If the last state of HueMagic has not yet been registered, it will output `false`.
+
+#### 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](https://user-images.githubusercontent.com/5302050/148681840-2275c15a-7c0c-4a37-b817-199608e571d2.gif)
 </script>

package/huemagic/locales/en-US/hue-rules.json

@@ -5,8 +5,8 @@
 		{
 			"name": "Name",
 			"input-name": "Rule name",
-			"skipevents": "Skip events",
 			"skipevents-node": "Skip events from node",
+			"sendinitevents-node": "Do not suppress initialization event",
 			"searching": "Searching rules…",
 			"none-found": "No rules found!",
 			"unknown-error": "Something went wrong. Please retry.",
@@ -20,7 +20,10 @@
 			"enabled": "enabled",
 			"disabled": "disabled",
 			"output": "rule (triggered)",
-			"input": "enable / disable"
+			"input": "enable / disable",
+			"universal": "universal mode",
+			"command": "executing command…",
+			"statusmsg": "Status queried successfully…"
 		}
 	}
 }

package/huemagic/locales/en-US/hue-scene.html

@@ -1,44 +1,35 @@
-<script type="text/x-red" data-help-name="hue-scene">
-    <p>Hue Scene node to recall (activate) Hue Scenes.</p>
+<script type="text/markdown" data-help-name="hue-scene">
+The "Hue Scene" node can resume scenes saved in the bridge and apply them to certain groups.
 
-    <h3>Setup</h3>
-    <p>Select the preconfigured Hue Bridge and hit the search button to find all available scenes. Type in the name of the scene manually or keep the default scene name. Note that events will only be sent if the scene node receives any command. If necessary, all status updates of this node can be ignored by activating the "Skip events" option.</p>
+### Setup
 
-    <h3>Activate (preconfigured)</h3>
-    <p>When a scene is configured any passed in value on the scene node activates the preconfigured scene.</p>
+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.
 
-    <h3>Activate (dynamic)</h3>
-    <p>When no scene is configured a scene name or scene id must be passed in to activate that scene. It is also possible to pass a group ID dynamically to recall a scene on a specific group only. The following parameters can be passed manually in <b>msg.payload</b>.</p>
-    <dl class="message-properties">
-        <dt>scene<span class="property-type">string</span></dt>
-        <dd>Will activate the scene given by its name or id.</dd>
+### Activate scene
 
-        <dt>group<span class="property-type">int</span></dt>
-        <dd>Will recall a scene on a specific group by its id.</dd>
-    </dl>
+You can activate a predefined scene by transferring an object with the following content:
 
-    <h3>Scene Events</h3>
-    <p>The event message that the scene node sends contains the following data in the <b>msg.payload</b> object:</p>
-    <dl class="message-properties">
-        <dt>id<span class="property-type">string</span></dt>
-        <dd>The unique scene id</dd>
+: payload (boolean): Activates a preconfigured scene
 
-        <dt>name<span class="property-type">string</span></dt>
-        <dd>The scene name</dd>
+### Activate scene in universal mode
 
-        <dt>lightIds<span class="property-type">array[int…]</span></dt>
-        <dd>Array of associated light ids in the scene</dd>
+If you operate this node in the so-called "universal mode" and have not set a scene in the node configuration, you can also transfer your desired scene to the node as a command. To do this, pass a `msg.payload` object with the following content:
 
-        <dt>owner<span class="property-type">string</span></dt>
-        <dd>User who created the scene</dd>
+: scene (string): ID of the scene to be activated on the bridge
 
-        <dt>appData<span class="property-type">object</span></dt>
-        <dd>Object consisting of version and data properties</dd>
+### Activate scene on certain groups
 
-        <dt>lastUpdated<span class="property-type">string</span></dt>
-        <dd>ISO 8601 date string when scene was last updated</dd>
+Connect the output of this node to one or more groups to apply a scene to specific groups. Alternatively, you have the option of doing this "dynamically" by passing an `msg.payload` object with the following content to the node:
 
-        <dt>version<span class="property-type">float</span></dt>
-        <dd>Version number of the scene</dd>
-    </dl>
+: group (string | array [string,…]): ID of the group or an array with the IDs of several groups in order to limit the scene to these groups
+
+### More information about the Node
+
+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.
+
+### 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](https://user-images.githubusercontent.com/5302050/148681840-2275c15a-7c0c-4a37-b817-199608e571d2.gif)
 </script>

package/huemagic/locales/en-US/hue-scene.json

@@ -5,11 +5,12 @@
 		{
 			"name": "Name",
 			"input-name": "Scene name",
-			"skipevents": "Skip events",
 			"skipevents-node": "Skip events from node",
+			"sendinitevents-node": "Do not suppress initialization event",
 			"searching": "Searching scenes…",
 			"none-found": "No scenes found!",
 			"unknown-error": "Something went wrong. Please retry.",
+			"scene": "Scene",
 			"group": "Group",
 			"group-none-found": "No groups found!",
 			"group-searching": "Searching groups…",
@@ -23,7 +24,9 @@
 			"recalled-on-group": "scene recalled on group",
 			"no-id": "No scene Id.",
 			"input": "activate scene",
-			"output": "scene information"
+			"output": "Target group(s)",
+			"command": "executing command…",
+			"statusmsg": "Recalling scene…"
 		}
 	}
 }