node-red-contrib-huemagic 4.2.2 → 5.0.0

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

@@ -1,19 +1,18 @@
 {
-	"hue-rules":
-	{
-		"config":
-		{
+	"hue-rules": {
+		"config": {
 			"name": "Name",
 			"input-name": "Rule name",
 			"skipevents-node": "Skip events from node",
 			"sendinitevents-node": "Do not suppress initialization event",
+			"onlycommands-node": "Only report after a command",
 			"searching": "Searching rules…",
 			"none-found": "No rules found!",
 			"unknown-error": "Something went wrong. Please retry.",
-			"rule": "Rule"
+			"rule": "Rule",
+			"bridge": "Bridge"
 		},
-		"node":
-		{
+		"node": {
 			"title": "Hue Rule",
 			"no-rule": "no rule selected",
 			"init": "initializing…",
@@ -23,7 +22,9 @@
 			"input": "enable / disable",
 			"universal": "universal mode",
 			"command": "executing command…",
-			"statusmsg": "Status queried successfully…"
+			"statusmsg": "Status queried successfully…",
+			"error-no-id": "Please submit a valid rule ID.",
+			"error-not-available": "The rule 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-scene.html

@@ -3,13 +3,18 @@ The "Hue Scene" node can resume scenes saved in the bridge and apply them to cer
 
 ### Setup
 
-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
 
 You can activate a predefined scene by transferring an object with the following content:
 
 : 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
+
+> [!NOTE]
+> 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
 
@@ -25,11 +30,14 @@ Connect the output of this node to one or more groups to apply a scene to specif
 
 ### 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.
+This node does not issue any status messages.
+
+> [!IMPORTANT]
+> 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)
+![examples](hue/assets/huemagic-examples.gif)
 </script>

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

@@ -1,8 +1,6 @@
 {
-	"hue-scene":
-	{
-		"config":
-		{
+	"hue-scene": {
+		"config": {
 			"name": "Name",
 			"input-name": "Scene name",
 			"skipevents-node": "Skip events from node",
@@ -14,10 +12,10 @@
 			"group": "Group",
 			"group-none-found": "No groups found!",
 			"group-searching": "Searching groups…",
-			"groups-all": "All groups / lights"
+			"groups-all": "All groups / lights",
+			"bridge": "Bridge"
 		},
-		"node":
-		{
+		"node": {
 			"title": "Hue Scene",
 			"not-configured": "not configured",
 			"recalled": "scene recalled",
@@ -26,7 +24,9 @@
 			"input": "activate scene",
 			"output": "Target group(s)",
 			"command": "executing command…",
-			"statusmsg": "Recalling scene…"
+			"statusmsg": "Recalling scene…",
+			"error-not-available": "The scene 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."
 		}
 	}
-}
+}

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

@@ -0,0 +1,80 @@
+<script type="text/markdown" data-help-name="hue-speaker">
+The "Hue Speaker" node can play the sounds of a Hue Secure chime and use it as an indoor siren.
+
+### Setup
+
+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.
+
+: 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:
+
+: 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:
+
+: 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.
+
+> [!NOTE]
+> 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`
+
+: 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`
+
+: 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.
+
+### 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-speaker.json

@@ -0,0 +1,38 @@
+{
+	"hue-speaker": {
+		"config": {
+			"name": "Name",
+			"input-name": "Speaker name",
+			"skipevents-node": "Skip events from node",
+			"sendinitevents-node": "Do not suppress initialization event",
+			"onlycommands-node": "Only report after a command",
+			"searching": "Searching speakers…",
+			"none-found": "No speakers found!",
+			"unknown-error": "Something went wrong. Please retry.",
+			"speaker": "Speaker",
+			"bridge": "Bridge",
+			"universalevents": "Universal Events",
+			"universalevents-node": "Receives all messages from other nodes of the same type (only in universal mode)"
+		},
+		"node": {
+			"title": "Hue Speaker",
+			"not-configured": "not configured",
+			"not-reachable": "not reachable",
+			"silent": "silent",
+			"muted": "muted",
+			"playing-alarm": "alarm (__sound__)",
+			"playing-chime": "chime (__sound__)",
+			"playing-alert": "alert (__sound__)",
+			"universal": "universal mode",
+			"input": "play sound / status",
+			"output": "speaker",
+			"command": "executing command…",
+			"statusmsg": "Status queried successfully…",
+			"error-no-id": "Please submit a valid speaker ID.",
+			"error-not-available": "The speaker 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-channel": "This speaker has no __channel__ sound.",
+			"error-invalid-sound": "Invalid __channel__ sound. Allowed are: __sounds__",
+			"error-invalid-volume": "Invalid volume setting. Only 0 - 100 allowed."
+		}
+	}
+}

package/huemagic/locales/en/hue-syncbox-config.html

@@ -0,0 +1,19 @@
+<script type="text/markdown" data-help-name="hue-syncbox-config">
+Connects to a Philips Hue Play HDMI Sync Box.
+
+### Name
+
+You can either assign an alternative, internal name for the sync box or keep the default name.
+
+### Sync Box IP
+
+The IP address of your sync box in your local network. As soon as you have entered it, HueMagic tries to read the name of the box and fills it in for you.
+
+### Access Token
+
+The sync box is not part of your Hue Bridge and needs its own token. Click the button next to the field and 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.
+
+### Refresh
+
+The sync box does not push its state, so HueMagic asks it regularly. This setting defines how many seconds lie between two requests. The default of 10 seconds is a good compromise between a responsive status and network traffic — do not set it lower than you actually need.
+</script>

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

@@ -0,0 +1,25 @@
+{
+	"hue-syncbox-config": {
+		"config": {
+			"name": "Name",
+			"syncbox-ip": "Sync Box IP",
+			"token": "Access Token",
+			"pollinterval": "Refresh (s)",
+			"missing-ip": "Missing Hue Sync Box IP…",
+			"connecting": "Connecting with the sync box…",
+			"invalid": "Sorry. Your selected Hue Sync Box is invalid: ",
+			"error-select-first": "Please enter the IP of your Hue Sync Box before trying to create a new token!",
+			"waiting": "waiting for the button…",
+			"new-user-press": "Please press and hold the button on your Hue Sync Box until the LED blinks green!",
+			"retry": "No button press detected. Please retry…",
+			"success": "Access token created successfully!"
+		},
+		"node": {
+			"title": "Hue Sync Box",
+			"initializing": "Initializing the sync box (__syncbox__)…",
+			"connected": "Connected to sync box",
+			"request-error": "Error requesting info from the sync box (__error__)",
+			"statusmsg": "Status queried successfully…"
+		}
+	}
+}

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

@@ -0,0 +1,86 @@
+<script type="text/markdown" data-help-name="hue-syncbox">
+The "Hue Sync Box" node controls a Philips Hue Play HDMI Sync Box and reports what it is currently doing.
+
+### Setup
+
+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". 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.
+
+: 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.
+
+: 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:
+
+: 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`
+
+: 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`
+
+: 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.
+
+### 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-syncbox.json

@@ -0,0 +1,30 @@
+{
+	"hue-syncbox": {
+		"config": {
+			"name": "Name",
+			"input-name": "Sync Box name",
+			"syncbox": "Sync Box",
+			"skipevents-node": "Skip events from node",
+			"sendinitevents-node": "Do not suppress initialization event",
+			"onlycommands-node": "Only report after a command"
+		},
+		"node": {
+			"title": "Hue Sync Box",
+			"not-configured": "not configured",
+			"connecting": "connecting…",
+			"powersave": "switched off",
+			"passthrough": "passthrough",
+			"syncing": "__mode__ (__intensity__)",
+			"input": "control the sync box",
+			"output": "sync box",
+			"command": "executing command…",
+			"statusmsg": "Status queried successfully…",
+			"error-not-available": "The sync box is not yet available. Please wait until HueMagic has established a connection with it.",
+			"error-invalid-mode": "Invalid mode. Allowed are: __modes__",
+			"error-invalid-intensity": "Invalid intensity. Allowed are: __intensities__",
+			"error-invalid-brightness": "Invalid brightness setting. Only 0 - 100 percent allowed.",
+			"error-invalid-brightness-level": "Invalid brightness setting. Only 0 - 200 allowed.",
+			"error-invalid-input": "Invalid HDMI input. Only input1 - input4 allowed."
+		}
+	}
+}

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

@@ -3,7 +3,9 @@ The "Hue Temperature" node can call up and report the current ambient temperatur
 
 ### 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.
+
+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.
 
@@ -63,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>

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

@@ -1,21 +1,21 @@
 {
-	"hue-temperature":
-	{
-		"config":
-		{
+	"hue-temperature": {
+		"config": {
 			"name": "Name",
 			"sensor": "Sensor",
 			"skipevents-node": "Skip events from node",
 			"sendinitevents-node": "Do not suppress initialization event",
+			"onlycommands-node": "Only report after a command",
 			"input-name": "Sensor name",
 			"searching": "searching temperature sensors…",
 			"none-found": "No temperature sensors found.",
 			"unknown-error": "Something went wrong. Please retry.",
 			"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",
+			"offset": "Offset"
 		},
-		"node":
-		{
+		"node": {
 			"title": "Hue Temperature",
 			"not-configured": "not configured",
 			"init": "initializing…",
@@ -25,7 +25,9 @@
 			"universal": "universal mode",
 			"command": "executing command…",
 			"deactivated": "deactivated",
-			"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/es/hue-automation.html

@@ -0,0 +1,59 @@
+<script type="text/markdown" data-help-name="hue-automation">
+El nodo «Hue Automatización» puede activar y desactivar las automatizaciones que haya creado en la app de Philips Hue.
+
+### Configuración
+
+Seleccione el Hue Bridge preconfigurado y haga clic en el botón de búsqueda para encontrar todas las automatizaciones disponibles. Si ya conoce el ID de la automatización, también puede introducirlo aquí manualmente. Puede asignar internamente un nombre nuevo a la automatización o utilizar el nombre predefinido. De forma opcional, puede desactivar todos los mensajes de estado automáticos de este nodo mediante el ajuste «Omitir los mensajes del nodo». El nodo dejará entonces de emitir actualizaciones. También puede elegir que el mensaje de inicialización del nodo no se suprima al iniciar Node-RED. Si activa este ajuste, recibirá un mensaje de estado de la automatización seleccionada después de cada despliegue. Si prefiere que el nodo permanezca en silencio hasta que usted le envíe algo, active «Informar solo tras un comando». En ese caso ignorará los cambios realizados desde la app o desde un interruptor y solo responderá a sus propios comandos.
+
+Si no selecciona ninguna automatización y utiliza así la configuración del nodo, el nodo funciona en el llamado «modo universal». En este modo, el nodo recibe y emite todos los mensajes de estado del mismo tipo. También puede aplicar ajustes en modo universal a una automatización concreta pasando el ID de la automatización correspondiente como cadena en `msg.topic` junto con sus ajustes.
+
+### Activar / desactivar la automatización
+
+Una automatización desactivada permanece en el bridge y puede volver a activarse en cualquier momento. Para ello, pase un objeto con el siguiente contenido:
+
+: payload (boolean): `true` activa la automatización, `false` la desactiva
+: enabled (boolean): Igual que arriba, si prefiere pasar un objeto
+: toggle (boolean | any): Alterna entre activada y desactivada, según el estado anterior
+
+### Mensajes de estado del nodo
+
+En cuanto cambia la automatización, el nodo devuelve el siguiente mensaje de estado:
+
+#### Objeto de estado en `msg.payload`
+
+: enabled (boolean): Indica si la automatización está activada
+: running (boolean): `true` mientras el bridge está ejecutando realmente la automatización
+: status (string | boolean): El estado actual. Puede contener `initializing`, `running`, `disabled` o `errored` como valor
+: lastError (string | boolean): El último error comunicado por el bridge o `false`
+: updated (string): Momento de la última actualización del recurso por parte de HueMagic (ISO 8601)
+
+#### Información sobre la automatización en `msg.info`
+
+: id (string): Indica el ID de la automatización
+: idV1 (string | boolean): Indica el ID antiguo de la automatización
+: name (string | boolean): El nombre que ha dado a la automatización en la app de Philips Hue
+: type (string): El tipo de recurso (siempre `automation`)
+: script (string | boolean): El ID del script de comportamiento que hay detrás de la automatización
+
+#### Configuración en `msg.configuration`
+
+Contiene los ajustes de la automatización tal como los guardó la app de Philips Hue. La estructura depende del tipo de automatización y se transmite sin modificar.
+
+#### Cambios de estado en `msg.updated`
+
+Enumera en forma de objeto los parámetros concretos que han cambiado con respecto al último estado de la automatización. Si no se ha registrado ningún cambio, este objeto está vacío.
+
+#### Último estado de la automatización en `msg.lastState`
+
+Contiene el objeto de estado completo (véanse los valores de salida anteriores) del último estado antes del último cambio registrado. Si HueMagic aún no ha registrado el último estado, se emite `false`.
+
+#### Último comando en `msg.command` (opcional)
+
+Si el estado del nodo ha cambiado mediante un comando concreto, también se emite el comando completo que se ha ejecutado. De lo contrario, el nodo no emite este objeto.
+
+### Ejemplos de HueMagic
+
+HueMagic pone a su disposición algunas configuraciones de ejemplo para este nodo. Para importar un ejemplo completo en su interfaz de Node-RED, haga clic en el icono de menú de Node-RED, seleccione «Importar» y navegue hasta «Ejemplos» en la barra lateral de la ventana emergente. A continuación, seleccione la carpeta HueMagic y el nodo que desee para importar un flujo de ejemplo.
+
+![examples](hue/assets/huemagic-examples.gif)
+</script>

package/huemagic/locales/es/hue-automation.json

@@ -0,0 +1,33 @@
+{
+	"hue-automation": {
+		"config": {
+			"name": "Nombre",
+			"skipevents-node": "Omitir los mensajes del nodo",
+			"sendinitevents-node": "No suprimir el evento de inicialización",
+			"onlycommands-node": "Informar solo tras un comando",
+			"unknown-error": "Algo ha salido mal. Inténtelo de nuevo.",
+			"bridge": "Bridge",
+			"universalevents": "Eventos universales",
+			"universalevents-node": "Recibe todos los mensajes de otros nodos del mismo tipo (solo en modo universal)",
+			"input-name": "Nombre de la automatización",
+			"searching": "Buscando automatizaciones…",
+			"none-found": "¡No se ha encontrado ninguna automatización!",
+			"automation": "Automatización"
+		},
+		"node": {
+			"not-configured": "sin configurar",
+			"init": "inicializando…",
+			"universal": "modo universal",
+			"command": "ejecutando comando…",
+			"statusmsg": "Estado consultado correctamente…",
+			"title": "Hue Automatización",
+			"enabled": "activada",
+			"disabled": "desactivada",
+			"errored": "error",
+			"input": "activar / desactivar",
+			"output": "automatización",
+			"error-no-id": "Indique un ID de automatización válido.",
+			"error-not-available": "La automatización aún no está disponible. Espere hasta que HueMagic haya establecido la conexión con el bridge o compruebe si el ID del recurso indicado en la configuración es válido."
+		}
+	}
+}

package/huemagic/locales/es/hue-bridge-config.html

@@ -0,0 +1,31 @@
+<script type="text/markdown" data-help-name="hue-bridge">
+Se conecta a un Philips Hue Bridge.
+
+### Nombre
+
+Puede asignar al bridge un nombre interno alternativo o conservar el nombre predeterminado.
+
+### IP y puerto del bridge
+
+Introduzca manualmente la dirección IP del Hue Bridge o pulse el botón para consultar todos los bridges disponibles localmente (se recomienda una configuración de IP estática en el Hue Bridge). De forma opcional, también puede definir un puerto alternativo para el bridge añadiendo dos puntos a la dirección IP.
+
+### Clave API
+
+Introduzca manualmente la clave API del Hue Bridge o pulse el botón para crear una clave nueva. Si desea crear una clave nueva, debe pulsar el botón físico del bridge dentro de un plazo de 20 segundos para completar el proceso.
+
+### Procesos
+
+El valor «Procesos» determina cuántos comandos paralelos puede enviar HueMagic al bridge al mismo tiempo. Según la documentación oficial del Philips Hue Bridge no deberían enviarse más de 10 comandos por segundo; de lo contrario existe el riesgo de que el bridge no pueda procesar las peticiones con la suficiente rapidez y devuelva errores.
+
+Si se envían al mismo tiempo más comandos que el valor configurado aquí, HueMagic ejecutará los comandos de forma secuencial en cuanto vuelva a ser posible.
+
+Ajuste este valor por debajo de 10 (p. ej. de 4 a 7) si también envía comandos al bridge fuera de HueMagic, para respetar el rendimiento de comandos por segundo recomendado por Philips Hue.
+
+### Actualizaciones automáticas de firmware
+
+HueMagic comprueba periódicamente si hay actualizaciones de firmware de Philips Hue disponibles y las instala automáticamente cuando existen. Puede desactivar este comportamiento marcando la casilla correspondiente.
+
+### Desactivar las notificaciones
+
+Si activa este ajuste, todos los nodos que dependan de este bridge dejarán de recibir mensajes de estado automáticos.
+</script>

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

@@ -0,0 +1,40 @@
+{
+	"hue-bridge-config": {
+		"config": {
+			"name": "Nombre",
+			"apikey": "Clave API",
+			"missing-ip": "Falta la IP del Hue Bridge…",
+			"disable-events": "Desactivar eventos",
+			"disable-events-info": "Desactivar los eventos en todos los nodos",
+			"searching": "Buscando Hue Bridges…",
+			"none-found": "¡No se ha encontrado ningún Hue Bridge!",
+			"unknown-error": "Algo ha salido mal. Inténtelo de nuevo.",
+			"invalid": "Lo sentimos. El Hue Bridge seleccionado no es válido: ",
+			"error-select-first": "¡Seleccione su Hue Bridge antes de crear un nuevo usuario!",
+			"waiting": "esperando al botón de vinculación…",
+			"new-user-press": "¡Pulse ahora el botón de su Hue Bridge para crear un nuevo usuario!",
+			"retry": "No se ha detectado ninguna pulsación. Inténtelo de nuevo…",
+			"success": "¡Usuario creado correctamente!",
+			"connecting": "Conectando con el bridge…",
+			"autoupdates": "Activar las actualizaciones automáticas de firmware",
+			"bridge-ip": "IP del bridge",
+			"worker": "Procesos"
+		},
+		"node": {
+			"title": "Hue Bridge",
+			"statusmsg": "Estado consultado correctamente…",
+			"initializing": "Inicializando el bridge (__bridge__)…",
+			"connected": "Conectado al bridge",
+			"processing": "Procesando los recursos del bridge…",
+			"initial-emit": "Emisión inicial de los estados de los recursos…",
+			"keep-updated": "Manteniendo los nodos actualizados…",
+			"subscribing": "Suscribiéndose a los eventos del bridge…",
+			"unsubscribing": "Cancelando la suscripción a los eventos del bridge…",
+			"no-legacy-api": "El bridge no responde en la API antigua, se continúa sin su configuración…",
+			"request-error": "Error al solicitar información al bridge (__error__)",
+			"connection-lost": "Se ha perdido la conexión con el bridge (__reason__). Nuevo intento en __seconds__ segundos…",
+			"resources-changed": "Los recursos del bridge han cambiado. Recargando…",
+			"not-connected": "El bridge no está conectado."
+		}
+	}
+}