node-red-contrib-huemagic 2.8.6 → 4.0.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +229 -0
- package/README.md +807 -766
- package/examples/Hue Bridge.json +189 -35
- package/examples/Hue Brightness.json +124 -14
- package/examples/Hue Buttons.json +88 -0
- package/examples/Hue Group.json +575 -63
- package/examples/Hue Light.json +805 -58
- package/examples/Hue Magic.json +69 -24
- package/examples/Hue Motion.json +110 -42
- package/examples/Hue Rules.json +105 -37
- package/examples/Hue Scene.json +145 -28
- package/examples/Hue Temperature.json +124 -14
- package/huemagic/animations/001-sunny.json +22 -22
- package/huemagic/animations/002-cloudy.json +46 -46
- package/huemagic/animations/003-nightsky.json +20 -20
- package/huemagic/animations/004-sunrise.json +54 -54
- package/huemagic/animations/005-sunset.json +46 -46
- package/huemagic/animations/006-fireplace.json +74 -74
- package/huemagic/animations/007-spring.json +31 -31
- package/huemagic/animations/008-autmn.json +23 -23
- package/huemagic/animations/009-winter.json +23 -23
- package/huemagic/animations/010-dirtyfog.json +23 -23
- package/huemagic/animations/011-lgbt.json +49 -50
- package/huemagic/animations/012-rasta.json +28 -29
- package/huemagic/animations/013-strobo.json +30 -31
- package/huemagic/animations/014-randomrainbow.json +30 -31
- package/huemagic/animations/015-sos.json +158 -159
- package/huemagic/animations/016-milkyway.json +83 -0
- package/huemagic/animations/017-beach.json +40 -0
- package/huemagic/animations/018-forest.json +43 -0
- package/huemagic/animations/019-christmas.json +30 -0
- package/huemagic/animations/020-superhero.json +56 -0
- package/huemagic/animations/021-neoncity.json +52 -0
- package/huemagic/animations/previews/001-sunny.gif +0 -0
- package/huemagic/animations/previews/002-cloudy.gif +0 -0
- package/huemagic/animations/previews/003-nightsky.gif +0 -0
- package/huemagic/animations/previews/004-sunrise.gif +0 -0
- package/huemagic/animations/previews/005-sunset.gif +0 -0
- package/huemagic/animations/previews/006-fireplace.gif +0 -0
- package/huemagic/animations/previews/007-spring.gif +0 -0
- package/huemagic/animations/previews/008-autmn.gif +0 -0
- package/huemagic/animations/previews/009-winter.gif +0 -0
- package/huemagic/animations/previews/010-dirtyfog.gif +0 -0
- package/huemagic/animations/previews/011-lgbt.gif +0 -0
- package/huemagic/animations/previews/012-rasta.gif +0 -0
- package/huemagic/animations/previews/013-strobo.gif +0 -0
- package/huemagic/animations/previews/014-randomrainbow.gif +0 -0
- package/huemagic/animations/previews/015-sos.gif +0 -0
- package/huemagic/animations/previews/016-milkyway.gif +0 -0
- package/huemagic/animations/previews/017-beach.gif +0 -0
- package/huemagic/animations/previews/018-forest.gif +0 -0
- package/huemagic/animations/previews/019-christmas.gif +0 -0
- package/huemagic/animations/previews/020-superhero.gif +0 -0
- package/huemagic/animations/previews/021-neoncity.gif +0 -0
- package/huemagic/hue-bridge-config.html +105 -61
- package/huemagic/hue-bridge-config.js +629 -320
- package/huemagic/hue-bridge.html +41 -21
- package/huemagic/hue-bridge.js +191 -398
- package/huemagic/hue-brightness.html +130 -49
- package/huemagic/hue-brightness.js +131 -35
- package/huemagic/hue-buttons.html +197 -0
- package/huemagic/hue-buttons.js +152 -0
- package/huemagic/hue-group.html +137 -60
- package/huemagic/hue-group.js +394 -368
- package/huemagic/hue-light.html +133 -59
- package/huemagic/hue-light.js +551 -337
- package/huemagic/hue-magic.html +91 -240
- package/huemagic/hue-magic.js +57 -27
- package/huemagic/hue-motion.html +128 -50
- package/huemagic/hue-motion.js +116 -87
- package/huemagic/hue-rules.html +121 -50
- package/huemagic/hue-rules.js +84 -64
- package/huemagic/hue-scene.html +96 -115
- package/huemagic/hue-scene.js +65 -96
- package/huemagic/hue-temperature.html +130 -49
- package/huemagic/hue-temperature.js +136 -32
- package/huemagic/icons/hue-bridge.png +0 -0
- package/huemagic/icons/hue-bridge.svg +3 -0
- package/huemagic/icons/hue-brightness.png +0 -0
- package/huemagic/icons/hue-brightness.svg +11 -0
- package/huemagic/icons/hue-buttons.png +0 -0
- package/huemagic/icons/hue-buttons.svg +4 -0
- package/huemagic/icons/hue-group.png +0 -0
- package/huemagic/icons/hue-group.svg +12 -0
- package/huemagic/icons/hue-light.png +0 -0
- package/huemagic/icons/hue-light.svg +3 -0
- package/huemagic/icons/hue-magic.png +0 -0
- package/huemagic/icons/hue-magic.svg +3 -0
- package/huemagic/icons/hue-motion.png +0 -0
- package/huemagic/icons/hue-motion.svg +9 -0
- package/huemagic/icons/hue-rules.png +0 -0
- package/huemagic/icons/hue-rules.svg +4 -0
- package/huemagic/icons/hue-scene.png +0 -0
- package/huemagic/icons/hue-scene.svg +5 -0
- package/huemagic/icons/hue-temperature.png +0 -0
- package/huemagic/icons/hue-temperature.svg +7 -0
- package/huemagic/locales/de/hue-bridge-config.html +17 -12
- package/huemagic/locales/de/hue-bridge-config.json +7 -5
- package/huemagic/locales/de/hue-bridge.html +64 -145
- package/huemagic/locales/de/hue-bridge.json +6 -17
- package/huemagic/locales/de/hue-brightness.html +52 -38
- package/huemagic/locales/de/hue-brightness.json +7 -2
- package/huemagic/locales/de/hue-buttons.html +58 -0
- package/huemagic/locales/de/{hue-button.json → hue-buttons.json} +8 -8
- package/huemagic/locales/de/hue-group.html +46 -122
- package/huemagic/locales/de/hue-group.json +4 -2
- package/huemagic/locales/de/hue-light.html +68 -116
- package/huemagic/locales/de/hue-light.json +5 -2
- package/huemagic/locales/de/hue-magic.html +65 -57
- package/huemagic/locales/de/hue-magic.json +2 -1
- package/huemagic/locales/de/hue-motion.html +48 -44
- package/huemagic/locales/de/hue-motion.json +6 -3
- package/huemagic/locales/de/hue-rules.html +68 -73
- package/huemagic/locales/de/hue-rules.json +5 -2
- package/huemagic/locales/de/hue-scene.html +23 -32
- package/huemagic/locales/de/hue-scene.json +5 -2
- package/huemagic/locales/de/hue-temperature.html +53 -36
- package/huemagic/locales/de/hue-temperature.json +7 -2
- package/huemagic/locales/en-US/hue-bridge-config.html +17 -12
- package/huemagic/locales/en-US/hue-bridge-config.json +5 -3
- package/huemagic/locales/en-US/hue-bridge.html +64 -145
- package/huemagic/locales/en-US/hue-bridge.json +5 -16
- package/huemagic/locales/en-US/hue-brightness.html +52 -38
- package/huemagic/locales/en-US/hue-brightness.json +10 -3
- package/huemagic/locales/en-US/hue-buttons.html +58 -0
- package/huemagic/locales/en-US/{hue-button.json → hue-buttons.json} +11 -5
- package/huemagic/locales/en-US/hue-group.html +46 -122
- package/huemagic/locales/en-US/hue-group.json +7 -3
- package/huemagic/locales/en-US/hue-light.html +68 -116
- package/huemagic/locales/en-US/hue-light.json +8 -3
- package/huemagic/locales/en-US/hue-magic.html +65 -57
- package/huemagic/locales/en-US/hue-magic.json +3 -1
- package/huemagic/locales/en-US/hue-motion.html +48 -44
- package/huemagic/locales/en-US/hue-motion.json +9 -4
- package/huemagic/locales/en-US/hue-rules.html +68 -73
- package/huemagic/locales/en-US/hue-rules.json +5 -2
- package/huemagic/locales/en-US/hue-scene.html +23 -32
- package/huemagic/locales/en-US/hue-scene.json +5 -2
- package/huemagic/locales/en-US/hue-temperature.html +53 -36
- package/huemagic/locales/en-US/hue-temperature.json +10 -3
- package/huemagic/utils/api.js +290 -0
- package/huemagic/utils/color.js +382 -0
- package/{utils → huemagic/utils}/merge.js +9 -6
- package/huemagic/utils/messages.js +447 -0
- package/package.json +11 -12
- package/examples/Hue Switch.json +0 -40
- package/examples/Hue Tap.json +0 -40
- package/huemagic/assets/anime.js +0 -8
- package/huemagic/hue-button.html +0 -119
- package/huemagic/hue-button.js +0 -94
- package/huemagic/hue-switch.html +0 -119
- package/huemagic/hue-switch.js +0 -113
- package/huemagic/hue-tap.html +0 -119
- package/huemagic/hue-tap.js +0 -74
- package/huemagic/icons/hue-button.png +0 -0
- package/huemagic/icons/hue-switch.png +0 -0
- package/huemagic/icons/hue-tap.png +0 -0
- package/huemagic/locales/de/hue-button.html +0 -50
- package/huemagic/locales/de/hue-switch.html +0 -50
- package/huemagic/locales/de/hue-switch.json +0 -31
- package/huemagic/locales/de/hue-tap.html +0 -41
- package/huemagic/locales/de/hue-tap.json +0 -23
- package/huemagic/locales/en-US/hue-button.html +0 -50
- package/huemagic/locales/en-US/hue-switch.html +0 -50
- package/huemagic/locales/en-US/hue-switch.json +0 -31
- package/huemagic/locales/en-US/hue-tap.html +0 -41
- package/huemagic/locales/en-US/hue-tap.json +0 -23
- package/utils/color.js +0 -9
- package/utils/messages.js +0 -658
- package/utils/rgb.js +0 -188
package/README.md
CHANGED
|
@@ -1,837 +1,878 @@
|
|
|
1
|
-
[](https://flows.nodered.org/node/node-red-contrib-huemagic)
|
|
2
2
|
|
|
3
3
|
# HueMagic - Philips Hue nodes for Node-RED
|
|
4
4
|
|
|
5
|
-
[](https://github.com/foddy/node-red-contrib-huemagic/) [](https://raw.githubusercontent.com/Foddy/node-red-contrib-huemagic/master/LICENSE) [](https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=LUQ7CWBWQ3Q4U) [](https://www.npmjs.com/package/node-red-contrib-huemagic)
|
|
6
6
|
|
|
7
|
-
HueMagic provides several input and output nodes for Node-RED and is the most in-depth and easy to use solution to control Philips Hue bridges, lights, groups, scenes, rules,
|
|
7
|
+
HueMagic provides several input and output nodes for Node-RED and is the most in-depth and easy to use solution to control Philips Hue bridges, lights, groups, scenes, rules, buttons/switches, motion sensors, temperature sensors and light level sensors.
|
|
8
8
|
|
|
9
9
|
### Features
|
|
10
10
|
* Simple and comprehensive control of the Hue Bridge and connected devices
|
|
11
11
|
* Automatic discovery of Philips Hue bridges as well as devices, scenes & groups…
|
|
12
|
-
*
|
|
13
|
-
*
|
|
12
|
+
* Output and input of multiple color code definitions *(HEX, RGB & human readable color names)*
|
|
13
|
+
* Automatic color temperature & brightness setting based on the current time
|
|
14
14
|
* Event-based status messages for all devices connected to the Hue Bridge
|
|
15
|
-
*
|
|
16
|
-
*
|
|
17
|
-
* Programmatic pairing of new devices without app enforcement (TouchLink)
|
|
15
|
+
* Virtual pressing of the Hue Bridge button (Link Button)
|
|
16
|
+
* Pairing of new devices without app enforcement (TouchLink)
|
|
18
17
|
* Automatic firmware updates to the Hue Bridge and connected devices
|
|
19
|
-
*
|
|
20
|
-
*
|
|
21
|
-
* A large selection of animations and the
|
|
18
|
+
* Activating / deactivating of sensors & rules on the Hue Bridge
|
|
19
|
+
* Extended alarm and colorloop effects on light bulbs and whole groups
|
|
20
|
+
* A large selection of animations and the option to create custom animations
|
|
22
21
|
* Additive state settings on all nodes with multiple commands
|
|
23
|
-
*
|
|
24
|
-
*
|
|
22
|
+
* Change states even if the corresponding devices are offline or turned off
|
|
23
|
+
* Real-time status messages for each node & in the Node-RED UI (SSE)
|
|
24
|
+
* Uses the latest CLIP/v2 API version of the Philips Hue Bridge
|
|
25
|
+
* Extensively documented in English & German
|
|
25
26
|
|
|
26
27
|
### Installation
|
|
27
|
-
HueMagic was written for **Node.js
|
|
28
|
-
_Please make sure, that you deactivate / remove other Philips Hue related Node-RED nodes before installing HueMagic!_
|
|
28
|
+
HueMagic was written for **Node.js 14+** and **Node-RED v2.1+**. It supports the square-shaped Hue Bridge with the **FW 1948086000+** or higher. You can install HueMagic directly via the [Node-RED Palette Manager](https://nodered.org/docs/user-guide/editor/palette/manager) or manually using [yarn / npm](https://nodered.org/docs/user-guide/runtime/adding-nodes).
|
|
29
29
|
|
|
30
30
|
`npm install node-red-contrib-huemagic`
|
|
31
31
|
|
|
32
|
+
_Please make sure that you deactivate other Hue-related nodes in Node-RED and meet the minimum requirements of Node.js and the Philips Hue Bridge firmware!_
|
|
33
|
+
|
|
32
34
|
### Available Nodes
|
|
33
35
|
|
|
34
|
-
- [Hue
|
|
36
|
+
- [Hue Bridge](#hue-bridge)
|
|
35
37
|
- [Hue Magic](#hue-magic)
|
|
36
|
-
- [Hue
|
|
37
|
-
- [Hue
|
|
38
|
-
- [Hue Scenes](#hue-
|
|
39
|
-
- [Hue
|
|
40
|
-
- [Hue
|
|
41
|
-
- [Hue
|
|
42
|
-
- [Hue
|
|
43
|
-
- [Hue
|
|
44
|
-
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
|
|
48
|
-
|
|
49
|
-
|
|
50
|
-
|
|
38
|
+
- [Hue Light](#hue-light)
|
|
39
|
+
- [Hue Group](#hue-group)
|
|
40
|
+
- [Hue Scenes](#hue-scene)
|
|
41
|
+
- [Hue Buttons](#hue-buttons)
|
|
42
|
+
- [Hue Motion](#hue-motion)
|
|
43
|
+
- [Hue Temperature](#hue-temperature)
|
|
44
|
+
- [Hue Brightness](#hue-brightness)
|
|
45
|
+
- [Hue Rule](#hue-rule)
|
|
46
|
+
|
|
47
|
+
### Examples
|
|
48
|
+
|
|
49
|
+
HueMagic provides a large selection of full featured sample flows for all nodes. You can find these examples in the "[examples](https://github.com/Foddy/node-red-contrib-huemagic/tree/master/examples)" folder on GitHub or directly in Node-RED. To import a full featured example into your Node-RED interface, click on the Node-RED menu icon, then select "Import" and navigate to "Examples" in the sidebar of the popup. Then select the HueMagic folder and your desired node to import a sample flow.
|
|
50
|
+
|
|
51
|
+
<img alt="Instructions to import examples in Node-RED" src="https://user-images.githubusercontent.com/5302050/148696808-f730ad36-8d0b-4b5b-99b2-1917831f8916.gif" width="100%">
|
|
52
|
+
|
|
53
|
+
## Hue Bridge
|
|
54
|
+
The "Hue Bridge" node is a universal node that can output all settings of the bridge and status messages from other nodes.
|
|
55
|
+
|
|
56
|
+

|
|
57
|
+
|
|
58
|
+
### Node-RED Setup Instructions
|
|
59
|
+
|
|
60
|
+
First select the desired Hue Bridge. You can optionally deactivate all automatic status messages for this node by clicking the setting “Skip global device updates / messages on this node”. The node will then no longer issue device updates.
|
|
61
|
+
|
|
62
|
+
Alternatively, you can also choose whether the initialization messages of all nodes should not be suppressed when Node-RED is started. If you activate this setting, you will receive a status message from all resources connected to the bridge after each deployment.
|
|
51
63
|
|
|
52
64
|
### Get settings / status
|
|
53
|
-
|
|
54
|
-
|
|
55
|
-
|
|
56
|
-
|
|
57
|
-
|
|
58
|
-
|
|
59
|
-
|
|
60
|
-
|
|
61
|
-
|
|
62
|
-
|
|
63
|
-
|
|
64
|
-
|
|
|
65
|
-
|
|
66
|
-
|
|
67
|
-
|
|
68
|
-
|
|
69
|
-
|
|
70
|
-
|
|
71
|
-
|
|
72
|
-
|
|
|
73
|
-
|
|
74
|
-
|
|
|
75
|
-
|
|
76
|
-
|
|
77
|
-
|
|
78
|
-
|
|
79
|
-
|
|
80
|
-
|
|
|
81
|
-
|
|
82
|
-
|
|
83
|
-
|
|
84
|
-
Changes the
|
|
85
|
-
|
|
86
|
-
|
|
|
87
|
-
|
|
88
|
-
|
|
|
89
|
-
|
|
|
90
|
-
|
|
|
91
|
-
|
|
92
|
-
|
|
93
|
-
|
|
94
|
-
|
|
95
|
-
|
|
96
|
-
|
|
97
|
-
|
|
98
|
-
|
|
99
|
-
|
|
100
|
-
|
|
101
|
-
|
|
|
102
|
-
|
|
103
|
-
|
|
|
104
|
-
|
|
|
105
|
-
|
|
|
106
|
-
|
|
|
107
|
-
|
|
|
108
|
-
|
|
|
109
|
-
|
|
|
110
|
-
|
|
|
111
|
-
|
|
|
112
|
-
|
|
|
113
|
-
|
|
|
114
|
-
|
|
|
115
|
-
|
|
|
116
|
-
|
|
|
117
|
-
|
|
|
118
|
-
|
|
|
119
|
-
|
|
|
120
|
-
|
|
|
121
|
-
|
|
|
122
|
-
|
|
|
123
|
-
|
|
|
124
|
-
|
|
|
125
|
-
|
|
|
126
|
-
|
|
|
127
|
-
|
|
128
|
-
|
|
129
|
-
|
|
130
|
-
|
|
131
|
-
|
|
132
|
-
|
|
133
|
-
|
|
134
|
-
|
|
65
|
+
|
|
66
|
+
Outputs the current status / settings of the bridge as soon as the following message has been sent to the node. Alternatively, you can also press the button in the Node-RED interface without having to pass a message to the node beforehand.
|
|
67
|
+
|
|
68
|
+
|Property|Description|
|
|
69
|
+
|--|--|
|
|
70
|
+
| payload (boolean) | Returns the current status of the bridge |
|
|
71
|
+
|
|
72
|
+
### Trigger TouchLink scan
|
|
73
|
+
|
|
74
|
+
You can couple new or old devices to the bridge using a "TouchLink scan" (e.g. after a reset). To do this, transfer the object `msg.payload` with the following content:
|
|
75
|
+
|
|
76
|
+
|Property|Description|
|
|
77
|
+
|--|--|
|
|
78
|
+
| touchLink (boolean) | Couples old or new devices with the bridge |
|
|
79
|
+
|
|
80
|
+
### Get all devices and resources
|
|
81
|
+
|
|
82
|
+
With the "fetch" command you can output a list of specific devices that are currently connected to the bridge. To do this, transfer the object `msg.payload` with the following content:
|
|
83
|
+
|
|
84
|
+
|Property|Description|
|
|
85
|
+
|--|--|
|
|
86
|
+
| fetch (string / array [string, ...]) | Can accept `light`, `group`, `button`, `motion`, `temperature`, `light_level` or `rule` as value(s) |
|
|
87
|
+
|
|
88
|
+
### Change Hue Bridge settings
|
|
89
|
+
|
|
90
|
+
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:
|
|
91
|
+
|
|
92
|
+
|Property|Description|
|
|
93
|
+
|--|--|
|
|
94
|
+
| name (string) | Changes the name of the bridge and must contain at least 4 to a maximum of 16 characters |
|
|
95
|
+
| zigbeeChannel (int) | Changes the current ZigBee channel (either `11`, `15`, `20`, `25` or `0`) |
|
|
96
|
+
| ipAddress (string) | Changes the IP address in the network settings |
|
|
97
|
+
| dhcpEnabled (boolean) | `true`, activates DHCP in the network settings, `false`, deactivates the setting |
|
|
98
|
+
| netmask (string) | Changes the network mask in the network settings |
|
|
99
|
+
| gateway (string) | Specifies the gateway in the network settings |
|
|
100
|
+
| proxyAddress (string) | Sets a proxy address in the network settings |
|
|
101
|
+
| proxyPort (string / int) | Specifies the port of the proxy in the network settings |
|
|
102
|
+
| timeZone (string) | Changes the currently set time zone on the bridge |
|
|
103
|
+
|
|
104
|
+
### Status messages from the node
|
|
105
|
+
|
|
106
|
+
The status reports of the "Hue Bridge" node are dynamic. Although they follow a certain pattern, their output can vary depending on what action has just been carried out on the node.
|
|
107
|
+
|
|
108
|
+
#### Status object under `msg.payload`
|
|
109
|
+
|
|
110
|
+
|Property|Description|
|
|
111
|
+
|--|--|
|
|
112
|
+
| id (string) | Unique ID of the Hue Bridge |
|
|
113
|
+
| name (string) | Currently set name |
|
|
114
|
+
| factoryNew (boolean) | Indicator whether the bridge is brand new |
|
|
115
|
+
| replacesBridgeId (string / boolean) | Outputs the old bridge ID (if a migration was carried out) or outputs `false` |
|
|
116
|
+
| dataStoreVersion (string) | Version of the data store |
|
|
117
|
+
| starterKitId (string / boolean) | Name of the starter kit created in the factory or `false` |
|
|
118
|
+
| softwareVersion (string) | Software version of the bridge |
|
|
119
|
+
| apiVersion (string) | API version of the bridge |
|
|
120
|
+
| zigbeeChannel (int) | Currently used ZigBee channel |
|
|
121
|
+
| macAddress (string) | MAC address of the bridge |
|
|
122
|
+
| ipAddress (string) | IP address of the bridge |
|
|
123
|
+
| dhcpEnabled (boolean) | Indicates whether DHCP is enabled |
|
|
124
|
+
| netmask (string) | Netmask of the bridge |
|
|
125
|
+
| gateway (string) | Gateway of the bridge |
|
|
126
|
+
| proxyAddress (string / boolean) | Currently used proxy address or `false` |
|
|
127
|
+
| proxyPort (string) | Currently used proxy port |
|
|
128
|
+
| utcTime (string) | UTC time on the bridge |
|
|
129
|
+
| timeZone (string) | Currently set time zone on the bridge |
|
|
130
|
+
| localTime (string) | Local time zone |
|
|
131
|
+
| portalServicesEnabled (boolean) | Indicates whether portal services are enabled |
|
|
132
|
+
| portalConnected (boolean) | Indicates whether the bridge is connected to the portal |
|
|
133
|
+
| linkButtonEnabled (boolean) | Indicates whether the link button is enabled |
|
|
134
|
+
| touchlinkEnabled (boolean) | Indicates whether TouchLink is enabled |
|
|
135
|
+
| autoUpdatesEnabled (boolean) | Indicates whether the HueMagic will automatically check for updates |
|
|
136
|
+
| users (array [object, ...]) | List of all users on the bridge (array with objects) |
|
|
137
|
+
| updated (string) | Time of the last update of the resource by HueMagic (ISO 8601) |
|
|
138
|
+
| model (object) | Contains the model information of the bridge under `id`, `manufacturer` and `name` |
|
|
139
|
+
|
|
140
|
+
#### Fetch results under `msg.results` (optional)
|
|
141
|
+
|
|
142
|
+
If the "fetch" command has been used on the node, the bridge outputs the corresponding results under the `msg.results` object. The object contains the queried resource groups, which in turn contain all the corresponding resources in the form of an array.
|
|
143
|
+
|
|
144
|
+
#### Global status messages under `msg.updated` (optional)
|
|
145
|
+
|
|
146
|
+
Unless deactivated, the node outputs an updated status message for each resource on the bridge. The status message under * msg.updated * follows the pattern of the respective resource and varies depending on the type of device that was last updated.
|
|
147
|
+
|
|
148
|
+
#### Last command under `msg.command` (optional)
|
|
149
|
+
|
|
150
|
+
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.
|
|
135
151
|
|
|
136
152
|
## Hue Magic
|
|
137
|
-
|
|
153
|
+
The "Hue Magic" node can apply complex and custom animations to lights and groups.
|
|
154
|
+
|
|
155
|
+

|
|
138
156
|
|
|
139
|
-
|
|
157
|
+
### Node-RED Setup Instructions
|
|
140
158
|
|
|
141
|
-
|
|
142
|
-
Starts or stops an animation on the passed in **msg** values of:
|
|
159
|
+
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.
|
|
143
160
|
|
|
144
|
-
|
|
145
|
-
|:-----------:|:-------:|:-------------------------------------------------------:|
|
|
146
|
-
| **payload** | boolean | True to start the animation, false to stop |
|
|
161
|
+
Below you can choose from pre-made animations from HueMagic. Click on your desired animation to set it.
|
|
147
162
|
|
|
148
163
|
### Included animations
|
|
149
|
-
Choose one of the included animations to apply to a Hue Light or Hue Group node.
|
|
164
|
+
Choose one of the included animations to apply to a Hue Light or Hue Group node.
|
|
150
165
|
|
|
151
166
|

|
|
152
167
|
|
|
153
|
-
###
|
|
154
|
-
|
|
168
|
+
### Start / stop animation
|
|
169
|
+
|
|
170
|
+
To play or stop an animation, pass an object with the following content to the node:
|
|
171
|
+
|
|
172
|
+
|Property|Description|
|
|
173
|
+
|--|--|
|
|
174
|
+
| payload (boolean) | `true`, starts the animation, `false`, stops the animation |
|
|
175
|
+
|
|
176
|
+
### Own animations
|
|
177
|
+
|
|
178
|
+
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).
|
|
179
|
+
|
|
180
|
+
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`.
|
|
181
|
+
|
|
182
|
+
|Property|Description|
|
|
183
|
+
|--|--|
|
|
184
|
+
| delay (int) | Number of milliseconds to wait until this step is carried out |
|
|
185
|
+
| 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 |
|
|
155
186
|
|
|
156
|
-
|
|
157
|
-
|
|
158
|
-
|
|
159
|
-
|
|
187
|
+
If you have created your own animation that you would like to share with others, add it at `/huemagic/animations/XXX-youranimationname.json` and create a pull request. Take a look at [this directory](https://github.com/Foddy/node-red-contrib-huemagic/tree/master/huemagic/animations) for structure help.
|
|
188
|
+
|
|
189
|
+
### Example of your own animation
|
|
190
|
+
|
|
191
|
+
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.
|
|
192
|
+
|
|
193
|
+
If you have set the animation to play indefinitely, this process is repeated indefinitely until you manually stop the animation or redeploy the node.
|
|
194
|
+
|
|
195
|
+
Pass the following object in `msg.payload` to play the example animation.
|
|
196
|
+
|
|
197
|
+
{
|
|
198
|
+
"animate": true,
|
|
199
|
+
"steps": [
|
|
200
|
+
{
|
|
201
|
+
"delay": 500,
|
|
202
|
+
"animation": {
|
|
203
|
+
"hex": "#FF0000",
|
|
204
|
+
"transitionTime": 1
|
|
205
|
+
}
|
|
206
|
+
},
|
|
207
|
+
{
|
|
208
|
+
"delay": 500,
|
|
209
|
+
"animation": {
|
|
210
|
+
"hex": "#0000FF",
|
|
211
|
+
"transitionTime": 1
|
|
212
|
+
}
|
|
213
|
+
}
|
|
214
|
+
]
|
|
215
|
+
}
|
|
160
216
|
|
|
161
217
|
### Special commands
|
|
162
|
-
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 **msg.payload.specials** with the following parameters.
|
|
163
|
-
|
|
164
|
-
| Property | Type | Information |
|
|
165
|
-
|:---------------:|:-------:|:-----------------------------:|
|
|
166
|
-
| **randomOrder** | boolean | Execute steps in random order |
|
|
167
|
-
|
|
168
|
-
## Hue Lights
|
|
169
|
-
Use the Hue Light node to control the lights and receive light bulb events.
|
|
170
|
-
|
|
171
|
-

|
|
172
|
-
|
|
173
|
-
### Turn on / off (simple mode)
|
|
174
|
-
Changes the light on / off state based on the passed in **msg** values of:
|
|
175
|
-
|
|
176
|
-
| Property | Type | Information |
|
|
177
|
-
|:-----------:|:-------:|:-----------------------------------------------------------------------------------------:|
|
|
178
|
-
| **payload** | boolean | Will turn on or turn off the light with its previous configuration (color and brightness) |
|
|
179
|
-
|
|
180
|
-
### Turn On / Off (extended mode)
|
|
181
|
-
Changes the light state, effect, color, brightness and other states based on the passed in **msg.payload** values of:
|
|
182
|
-
|
|
183
|
-
| Property | Type | Information |
|
|
184
|
-
|:-----------------------:|:------------------:|-----------------------------------------------------------------------------------------------------------------------------------|
|
|
185
|
-
| **on** | boolean | Will turn on or turn off the light with its previous configuration (color and brightness) |
|
|
186
|
-
| **brightness** | int | Optionally configurable brightness of the light in percent (0-100) |
|
|
187
|
-
| **brightnessLevel** | int | Optionally configurable brightness of the light (0-254) |
|
|
188
|
-
| **incrementBrightness** | int | Increment brightness by given percentage value |
|
|
189
|
-
| **decrementBrightness** | int | Decrement brightness by given percentage value |
|
|
190
|
-
| **rgb** | array[int,int,int] | Optionally configurable RGB color value of the light bulb. You don't need to pass the RGB value if you already passed a HEX value |
|
|
191
|
-
| **hex** | string | Optionally configurable HEX color value of the light bulb. You don't need to pass the HEX value if you already passed a RGB value |
|
|
192
|
-
| **color** | string | Optionally configurable human readable color name in english like "red" or "random" for a random color |
|
|
193
|
-
| **image** | string | Optionally configurable image path (remote or local) to apply the most dominant color to the light |
|
|
194
|
-
| **transitionTime** | float | Optionally configurable temporary value which eases transition of an effect (value in seconds, 0 for instant, 5 for five seconds) |
|
|
195
|
-
| **colorloop** | float / boolean | Optionally configurable color loop effect. Float = disables the effect after x seconds / Boolean to turn on / off the effect |
|
|
196
|
-
| **colorTemp** | int | Optionally configurable color temperature of the light from 153 to 500 |
|
|
197
|
-
| **incrementColorTemp** | int | Increment/decrement color temperature by given value |
|
|
198
|
-
| **saturation** | int | Optionally configurable color saturation of the light in percent (from 0 to 100) |
|
|
199
|
-
| **status** | any | Returns the current status message of the node without taking any action |
|
|
200
|
-
|
|
201
|
-
### Toggle on / off (auto)
|
|
202
|
-
Turns the light on or off depending on the current state based on the passed in **msg.payload** value of:
|
|
203
|
-
|
|
204
|
-
| Property | Type | Information |
|
|
205
|
-
|:-----------:|:-------:|:-----------------------------------------------------------------------------------------:|
|
|
206
|
-
| **toggle** | any | Will turn on or turn off the light with the previous configuration (color and brightness) |
|
|
207
|
-
|
|
208
|
-
### Special Alert Effect
|
|
209
|
-
Plays an alert effect based on the passed in **msg.payload** values of:
|
|
210
|
-
|
|
211
|
-
| Property | Type | Information |
|
|
212
|
-
|:---------:|:------------------:|------------------------------------------------------------------------------------------------------------------------------------------------------|
|
|
213
|
-
| **alert** | int *(required)* | Configurable amount of seconds to play the alert effect (max 30) |
|
|
214
|
-
| **rgb** | array[int,int,int] | Optionally configurable RGB color value of the alert effect. You don't need to pass the RGB value if you already passed a HEX value |
|
|
215
|
-
| **hex** | string | Optionally configurable HEX color value of the alert effect. You don't need to pass the HEX value if you already passed a RGB value |
|
|
216
|
-
| **color** | string | Optionally configurable human readable color name in english like "red" or "random" for a random color effect |
|
|
217
|
-
|
|
218
|
-
|
|
219
|
-
### Light Events
|
|
220
|
-
The event message that the light bulb sends contains the following data in the **msg.payload** object. Events will only be sent if the light bulb state is changed.
|
|
221
|
-
|
|
222
|
-
| Property | Type | Information |
|
|
223
|
-
|:-------------------:|:------------------:|:----------------------------------------------------------:|
|
|
224
|
-
| **on** | boolean | True for on, false for off |
|
|
225
|
-
| **brightness** | int | Current brightness of the light bulb in percent |
|
|
226
|
-
| **brightnessLevel** | int | Current brightness of the light bulb (0-254) |
|
|
227
|
-
| **rgb** | array[int,int,int] | Current RGB color value of the light bulb (if supported) |
|
|
228
|
-
| **hex** | string | Current HEX color value of the light bulb (if supported) |
|
|
229
|
-
| **color** | string | Current color name of the light bulb (if supported) |
|
|
230
|
-
| **colorTemp** | int | Current color temperature of the light bulb (if supported) |
|
|
231
|
-
| **updated** | string | ISO 8601 date string of the last light state update |
|
|
232
|
-
|
|
233
|
-
### Additional Light Bulb Information
|
|
234
|
-
The event message that the light bulb sends also contains the following data in the **msg.info** object.
|
|
235
|
-
|
|
236
|
-
| Property | Type | Information |
|
|
237
|
-
|:-------------------:|:------:|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
|
238
|
-
| **id** | int | Numerical id of the light as registered on the bridge |
|
|
239
|
-
| **uniqueId** | string | Unique Id of the light (typically hardware id) |
|
|
240
|
-
| **name** | string | Name for the light |
|
|
241
|
-
| **type** | string | Type of light (e.g. Extended Color Light, Dimmable Light) |
|
|
242
|
-
| **softwareVersion** | float | Software version of the light |
|
|
243
|
-
| **model** | object | The model object of the light includes model specific information like the model.id, model.manufacturer, model.name, model.type, model.colorGamut and model.friendsOfHue |
|
|
244
|
-
|
|
245
|
-
### Universal Mode (optional)
|
|
246
|
-
Defines the light Id on the Hue Bridge manually if not configured in the node properties (deactivates light update events):
|
|
247
|
-
|
|
248
|
-
| Property | Type | Information |
|
|
249
|
-
|:-------------:|:----:|:--------------------------------------:|
|
|
250
|
-
| **msg.topic** | int | Manual definition of the light bulb Id |
|
|
251
|
-
|
|
252
|
-
### Last State Information
|
|
253
|
-
This node also sends the entire last state data (before the update) in the **msg.lastState** 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.
|
|
254
|
-
|
|
255
|
-
## Hue Groups
|
|
256
|
-
Use the Hue Group node to control whole groups containing lights and receive group events.
|
|
257
|
-
|
|
258
|
-

|
|
259
|
-
|
|
260
|
-
### Turn on / off (simple mode)
|
|
261
|
-
Changes the group on / off state based on the passed in **msg** values of:
|
|
262
|
-
|
|
263
|
-
| Property | Type | Information |
|
|
264
|
-
|:-----------:|:-------:|:-------------------------------------------------------------------------------------------------------------:|
|
|
265
|
-
| **payload** | boolean | Will turn on or turn off all lights inside the group with their previous configuration (color and brightness) |
|
|
266
|
-
|
|
267
|
-
### Turn On / Off (extended mode)
|
|
268
|
-
Changes the group state, effect, color, brightness and other states based on the passed in **msg.payload** values of:
|
|
269
|
-
|
|
270
|
-
| Property | Type | Information |
|
|
271
|
-
|:-----------------------:|:------------------:|------------------------------------------------------------------------------------------------------------------------------------------------|
|
|
272
|
-
| **on** | boolean | True to turn on all the lights inside the group, false to turn them off |
|
|
273
|
-
| **brightness** | int | Optionally configurable brightness of the lights in percent (0-100) |
|
|
274
|
-
| **brightnessLevel** | int | Optionally configurable brightness of the lights (0-254) |
|
|
275
|
-
| **incrementBrightness** | int | Increment brightness by given percentage value |
|
|
276
|
-
| **decrementBrightness** | int | Decrement brightness by given percentage value |
|
|
277
|
-
| **ignoreOffLights** | boolean | If the option is set, turned off lights in the group are ignored when "incrementBrightness / decrementBrightness" is set |
|
|
278
|
-
| **rgb** | array[int,int,int] | Optionally configurable RGB color value of all lights inside the group. You don't need to pass the RGB value if you already passed a HEX value |
|
|
279
|
-
| **hex** | string | Optionally configurable HEX color value of all lights inside the group. You don't need to pass the HEX value if you already passed a RGB value |
|
|
280
|
-
| **color** | string | Optionally configurable human readable color name in english like "red" or "random" for a random color |
|
|
281
|
-
| **image** | string | Optionally configurable image path (remote or local) to apply the most dominant color to the group |
|
|
282
|
-
| **transitionTime** | float | Optionally configurable temporary value which eases transition of an effect (value in seconds, 0 for instant, 5 for five seconds) |
|
|
283
|
-
| **colorloop** | float / boolean | Optionally configurable color loop effect. Float = disables the effect after x seconds / Boolean to turn on / off the effect |
|
|
284
|
-
| **colorTemp** | int | Optionally configurable color temperature of the group lights from 153 to 500 |
|
|
285
|
-
| **incrementColorTemp** | int | Increment/decrement color temperature by given value |
|
|
286
|
-
| **saturation** | int | Optionally configurable color saturation of the group in percent (from 0 to 100) |
|
|
287
|
-
| **status** | any | Returns the current status message of the node without taking any action |
|
|
288
|
-
|
|
289
|
-
### Toggle on / off (auto)
|
|
290
|
-
Turns the lights on or off depending on the current state based on the passed in **msg.payload** value of:
|
|
291
|
-
|
|
292
|
-
| Property | Type | Information |
|
|
293
|
-
|:-----------:|:-------:|:-----------------------------------------------------------------------------------------:|
|
|
294
|
-
| **toggle** | any | Will turn on or turn off all lights inside the group with their previous configuration (color and brightness) |
|
|
295
|
-
|
|
296
|
-
### Special Alert Effect
|
|
297
|
-
Plays an alert effect based on the passed in **msg.payload** values of:
|
|
298
|
-
|
|
299
|
-
| Property | Type | Information |
|
|
300
|
-
|:---------:|:------------------:|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
|
301
|
-
| **alert** | int *(required)* | Configurable amount of seconds to play the alert effect (max 30) |
|
|
302
|
-
| **rgb** | array[int,int,int] | Optionally configurable RGB color value of the alert effect. You don't need to pass the RGB value if you already passed a HEX value |
|
|
303
|
-
| **hex** | string | Optionally configurable HEX color value of the alert effect. You don't need to pass the HEX value if you already passed a RGB value |
|
|
304
|
-
| **color** | string | Optionally configurable human readable color name in english like "red" or "random" for a random color |
|
|
305
|
-
|
|
306
|
-
### Group Events
|
|
307
|
-
The event message that the group sends contains the following data in the **msg.payload** object. Events will only be sent if the group state is changed.
|
|
308
|
-
|
|
309
|
-
| Property | Type | Information |
|
|
310
|
-
|:-------------------:|:------------------:|:-------------------------------------------------------------------:|
|
|
311
|
-
| **on** | boolean | True for on, false for off |
|
|
312
|
-
| **allOn** | boolean | True if all lights in the group are on, false if not |
|
|
313
|
-
| **anyOn** | boolean | True if any lights in the group are on, false if none are on |
|
|
314
|
-
| **brightness** | int | Current brightness of all lights in the whole group in percent |
|
|
315
|
-
| **brightnessLevel** | int | Current brightness of all lights in the whole group (0-254) |
|
|
316
|
-
| **rgb** | array[int,int,int] | Current RGB color value of all lights in the group (if supported) |
|
|
317
|
-
| **hex** | string | Current HEX color value of all lights in the group (if supported) |
|
|
318
|
-
| **color** | string | Current color name of all lights in the group (if supported) |
|
|
319
|
-
| **colorTemp** | int | Current color temperature of all lights in the group (if supported) |
|
|
320
|
-
| **updated** | string | ISO 8601 date string of the last group state update |
|
|
321
|
-
|
|
322
|
-
### Additional Group Information
|
|
323
|
-
The event message that the group sends also contains the following data in the **msg.info** object.
|
|
324
|
-
|
|
325
|
-
| Property | Type | Information |
|
|
326
|
-
|:------------:|:------:|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|
|
|
327
|
-
| **id** | int | Group Id, generated automatically by the bridge |
|
|
328
|
-
| **lightIds** | array | An array of light ids associated with the group |
|
|
329
|
-
| **name** | string | Name for the group |
|
|
330
|
-
| **type** | string | Type of group (e.g. LightGroup, Luminaire, LightSource, Room) |
|
|
331
|
-
| **model** | object | [Huejay](https://github.com/sqmk/huejay) *(the API behind HueMagic)* maintains a list of Philips Hue supported luminaire models. The Group model attribute returns optionally a GroupModel object. This object contains more information about the model like the model.id, model.manufacturer, model.name, model.type, model.colorGamut and model.friendsOfHue |
|
|
332
|
-
|
|
333
|
-
### Universal Mode (optional)
|
|
334
|
-
Defines the group Id on the Hue Bridge manually if not configured in the node properties (deactivates group update events):
|
|
335
|
-
|
|
336
|
-
| Property | Type | Information |
|
|
337
|
-
|:-------------:|:----:|:---------------------------------:|
|
|
338
|
-
| **msg.topic** | int | Manual definition of the group Id |
|
|
339
|
-
|
|
340
|
-
### Last State Information
|
|
341
|
-
This node also sends the entire last state data (before the update) in the **msg.lastState** 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.
|
|
342
|
-
|
|
343
|
-
## Hue Scenes
|
|
344
|
-
Use the Hue Scene node to recall / activate preconfigured scenes on the bridge and receive scene information.
|
|
345
|
-
|
|
346
|
-

|
|
347
|
-
|
|
348
|
-
### Recall / Activate Scene
|
|
349
|
-
**Any** passed in value on the scene node activates the preconfigured scene. Please note that recalling animated scenes may not work properly due to some restrictions.
|
|
350
|
-
|
|
351
|
-
### Apply scenes dynamically
|
|
352
|
-
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 **msg.payload**.
|
|
353
|
-
|
|
354
|
-
| Property | Type | Information |
|
|
355
|
-
|:---------:|:------:|:--------------------------------------------------:|
|
|
356
|
-
| **scene** | string | Will activate the scene given by its name or id. |
|
|
357
|
-
| **group** | int | Will recall a scene on a specific group by its id. |
|
|
358
|
-
|
|
359
|
-
### Scene Events
|
|
360
|
-
The event message that the scene node sends contains the following data in the **msg.payload** object. Events will only be sent if a scene receives any command.
|
|
361
|
-
|
|
362
|
-
| Property | Type | Information |
|
|
363
|
-
|:---------------:|:-----------:|:----------------------------------------------------------------:|
|
|
364
|
-
| **id** | string | The unique scene id |
|
|
365
|
-
| **name** | string | The scene name |
|
|
366
|
-
| **lightIds** | array[int…] | Array of associated light ids in the scene |
|
|
367
|
-
| **owner** | string | User who created the scene |
|
|
368
|
-
| **appData** | object | Object consisting of appData.version and appData.data properties |
|
|
369
|
-
| **lastUpdated** | string | ISO 8601 date string when scene was last updated |
|
|
370
|
-
| **version** | float | Version number of the scene |
|
|
371
|
-
|
|
372
|
-
## Hue Tap
|
|
373
|
-
Use the Hue Tap node to receive button events.
|
|
374
|
-
|
|
375
|
-

|
|
376
|
-
|
|
377
|
-
### Button Events
|
|
378
|
-
The event message that the Hue Tap device sends contains the following data in the **msg.payload** object. Events will only sent on deploy (once) and if a button is pressed.
|
|
379
|
-
|
|
380
|
-
| Property | Type | Information |
|
|
381
|
-
|:-------------:|:------:|:------------------------------------------------------------:|
|
|
382
|
-
| **button** | int | Pressed button number from 1-4 |
|
|
383
|
-
| **buttonAlt** | int | Alternative pressed button number (unparsed from the bridge) |
|
|
384
|
-
| **updated** | string | ISO 8601 date string of the last button event |
|
|
385
|
-
|
|
386
|
-
### Additional Hue Tap Information
|
|
387
|
-
The event message that the Hue Tap device sends also contains the following data in the **msg.info** object.
|
|
388
|
-
|
|
389
|
-
| Property | Type | Information |
|
|
390
|
-
|:------------:|:------:|:-----------------------------------------------------------------------------------------------------------------------------------:|
|
|
391
|
-
| **id** | int | Numerical id of the sensor as registered on the bridge |
|
|
392
|
-
| **uniqueId** | string | Unique Id of the sensor (typically hardware id) |
|
|
393
|
-
| **name** | string | Name for the sensor |
|
|
394
|
-
| **type** | string | Sensor type (e.g. Daylight, CLIPTemperature, ZGPSwitch) |
|
|
395
|
-
| **model** | object | The model object of the sensor includes model specific information like the model.id, model.manufacturer, model.name and model.type |
|
|
396
|
-
|
|
397
|
-
### Last State Information
|
|
398
|
-
This node also sends the entire last state data (before the update) in the **msg.lastState** 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.
|
|
399
|
-
|
|
400
|
-
## Hue Switch
|
|
401
|
-
Use the Hue Switch node to receive button events.
|
|
402
|
-
|
|
403
|
-

|
|
404
|
-
|
|
405
|
-
### Button Events
|
|
406
|
-
The event message that the Hue Wireless Dimmer Switch sends contains the following data in the **msg.payload** object. Events will only sent on deploy (once) and if a button is pressed.
|
|
407
|
-
|
|
408
|
-
| Property | Type | Information |
|
|
409
|
-
|:-----------:|:------:|:-------------------------------------------------------------------------------------------------------------------------------------:|
|
|
410
|
-
| **button** | int | Pressed button id ([more information under 1.2 ZLL Switch](https://developers.meethue.com/documentation/supported-sensors#zgpSwitch)) |
|
|
411
|
-
| **name** | string | Human readable pressed button name *(On, Dim Up, Dim Down, Off)* |
|
|
412
|
-
| **action** | string | Human readable pressed button action *(pressed, holded, short released, long released)* |
|
|
413
|
-
| **updated** | string | ISO 8601 date string of the last button event |
|
|
414
|
-
|
|
415
|
-
### Additional Hue Switch Information
|
|
416
|
-
The event message that the Hue Wireless Dimmer Switch device sends also contains the following data in the **msg.info** object.
|
|
417
|
-
|
|
418
|
-
| Property | Type | Information |
|
|
419
|
-
|:------------:|:------:|:-----------------------------------------------------------------------------------------------------------------------------------:|
|
|
420
|
-
| **id** | int | Numerical id of the sensor as registered on the bridge |
|
|
421
|
-
| **uniqueId** | string | Unique Id of the sensor (typically hardware id) |
|
|
422
|
-
| **name** | string | Name for the sensor |
|
|
423
|
-
| **type** | string | Sensor type (e.g. Daylight, CLIPTemperature, ZGPSwitch) |
|
|
424
|
-
| **battery** | int | Current battery level of the Hue Switch in percent |
|
|
425
|
-
| **model** | object | The model object of the sensor includes model specific information like the model.id, model.manufacturer, model.name and model.type |
|
|
426
|
-
|
|
427
|
-
### Last State Information
|
|
428
|
-
This node also sends the entire last state data (before the update) in the **msg.lastState** 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.
|
|
429
|
-
|
|
430
|
-
## Hue Button
|
|
431
|
-
Use the Hue Button node to receive button events.
|
|
432
|
-
|
|
433
|
-

|
|
434
|
-
|
|
435
|
-
### Button Events
|
|
436
|
-
The event message that the Hue Smart Button sends contains the following data in the **msg.payload** object.
|
|
437
|
-
|
|
438
|
-
| Property | Type | Information |
|
|
439
|
-
|:-----------:|:------:|:-------------------------------------------------------------------------------------------------------------------------------------:|
|
|
440
|
-
| **button** | int | Pressed button id, 1002 for normal press, 1003 for long press (release) and 1001 during long press. |
|
|
441
|
-
| **name** | string | Human readable pressed button name *(always On)* |
|
|
442
|
-
| **action** | string | Human readable pressed button action *(short released, long released, holded)* |
|
|
443
|
-
| **updated** | string | ISO 8601 date string of the last button event |
|
|
444
|
-
|
|
445
|
-
### Additional Hue Button Information
|
|
446
|
-
The event message that the Hue Button device sends also contains the following data in the **msg.info** object.
|
|
447
|
-
|
|
448
|
-
| Property | Type | Information |
|
|
449
|
-
|:------------:|:------:|:-----------------------------------------------------------------------------------------------------------------------------------:|
|
|
450
|
-
| **id** | int | Numerical id of the sensor as registered on the bridge |
|
|
451
|
-
| **uniqueId** | string | Unique Id of the sensor (typically hardware id) |
|
|
452
|
-
| **name** | string | Name for the sensor |
|
|
453
|
-
| **type** | string | Sensor type (e.g. Daylight, CLIPTemperature, ZGPSwitch) |
|
|
454
|
-
| **battery** | int | Current battery level of the Hue Switch in percent |
|
|
455
|
-
| **model** | object | The model object of the sensor includes model specific information like the model.id, model.manufacturer, model.name and model.type |
|
|
456
|
-
|
|
457
|
-
### Last State Information
|
|
458
|
-
This node also sends the entire last state data (before the update) in the **msg.lastState** 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.
|
|
459
|
-
|
|
460
|
-
## Hue Motion Sensor
|
|
461
|
-
Use the Hue Motion node to control the motion sensor and receive motion events.
|
|
462
|
-
|
|
463
|
-

|
|
464
|
-
|
|
465
|
-
### Activate / Deactivate Sensor
|
|
466
|
-
Activates or deactivates the motion sensor based on the passed in **msg** values of:
|
|
467
|
-
|
|
468
|
-
| Property | Type | Information |
|
|
469
|
-
|:-----------:|:-------:|:------------------------------------------------------------------------:|
|
|
470
|
-
| **payload** | boolean | True to activate the motion sensor, false to deactivate |
|
|
471
|
-
| **status** | any | Returns the current status message of the node without taking any action |
|
|
472
|
-
|
|
473
|
-
### Motion Events
|
|
474
|
-
The event message that the motion sensor sends contains the following data in the **msg.payload** object. Events will only be sent if a motion is detected, if a motion stops or if the motion sensor receives the *Activate / Deactivate* command.
|
|
475
|
-
|
|
476
|
-
| Property | Type | Information |
|
|
477
|
-
|:-----------:|:-------:|:------------------------------------------------:|
|
|
478
|
-
| **active** | boolean | Current sensor state |
|
|
479
|
-
| **motion** | boolean | Indicates if a motion is detected or not |
|
|
480
|
-
| **updated** | string | ISO 8601 date string of the last detected motion |
|
|
481
|
-
|
|
482
|
-
### Additional Motion Sensor Information
|
|
483
|
-
The event message that the motion sensor sends also contains the following data in the **msg.info** object.
|
|
484
|
-
|
|
485
|
-
| Property | Type | Information |
|
|
486
|
-
|:-------------------:|:------:|:-----------------------------------------------------------------------------------------------------------------------------------:|
|
|
487
|
-
| **id** | int | Numerical id of the sensor as registered on the bridge |
|
|
488
|
-
| **uniqueId** | string | Unique Id of the sensor (typically hardware id) |
|
|
489
|
-
| **name** | string | Name for the sensor |
|
|
490
|
-
| **type** | string | Sensor type (e.g. Daylight, CLIPTemperature, ZGPSwitch) |
|
|
491
|
-
| **softwareVersion** | float | Software version of the sensor |
|
|
492
|
-
| **battery** | int | Current battery level of the temperature sensor in percent |
|
|
493
|
-
| **model** | object | The model object of the sensor includes model specific information like the model.id, model.manufacturer, model.name and model.type |
|
|
494
|
-
|
|
495
|
-
### Last State Information
|
|
496
|
-
This node also sends the entire last state data (before the update) in the **msg.lastState** 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.
|
|
497
|
-
|
|
498
|
-
## Hue Temperature Sensor
|
|
499
|
-
Use the Hue Temperature node to receive current (room) temperature in Celsius and Fahrenheit.
|
|
500
|
-
|
|
501
|
-

|
|
502
|
-
|
|
503
|
-
### Temperature Events
|
|
504
|
-
The event message that the temperature sensor sends contains the following data in the **msg.payload** object. Events will only sent on deploy (once) and if the temperature changes.
|
|
505
|
-
|
|
506
|
-
| Property | Type | Information |
|
|
507
|
-
|:---------------:|:------:|:---------------------------------------------------:|
|
|
508
|
-
| **celsius** | float | Temperature in Celsius |
|
|
509
|
-
| **fahrenheit** | float | Temperature in Fahrenheit |
|
|
510
|
-
| **deviceValue** | int | Temperature value of the sensor (original value) |
|
|
511
|
-
| **updated** | string | ISO 8601 date string of the last temperature change |
|
|
512
|
-
|
|
513
|
-
### Additional Temperature Sensor Information
|
|
514
|
-
The event message that the temperature sensor sends also contains the following data in the **msg.info** object.
|
|
515
|
-
|
|
516
|
-
| Property | Type | Information |
|
|
517
|
-
|:-------------------:|:------:|:-----------------------------------------------------------------------------------------------------------------------------------:|
|
|
518
|
-
| **id** | int | Numerical id of the sensor as registered on the bridge |
|
|
519
|
-
| **uniqueId** | string | Unique Id of the sensor (typically hardware id) |
|
|
520
|
-
| **name** | string | Name for the sensor |
|
|
521
|
-
| **type** | string | Sensor type (e.g. Daylight, CLIPTemperature, ZGPSwitch) |
|
|
522
|
-
| **softwareVersion** | float | Software version of the sensor |
|
|
523
|
-
| **battery** | int | Current battery level of the temperature sensor in percent |
|
|
524
|
-
| **model** | object | The model object of the sensor includes model specific information like the model.id, model.manufacturer, model.name and model.type |
|
|
525
|
-
|
|
526
|
-
### Last State Information
|
|
527
|
-
This node also sends the entire last state data (before the update) in the **msg.lastState** 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.
|
|
528
|
-
|
|
529
|
-
## Hue Lux Sensor
|
|
530
|
-
Use the Hue Brightness node to receive the current light level in Lux and daylight / darkness.
|
|
531
|
-
|
|
532
|
-

|
|
533
|
-
|
|
534
|
-
### Light Level Events
|
|
535
|
-
The event message that the light sensor sends contains the following data in the **msg.payload** object. Events will only be sent on deploy (once) and if the light level changes.
|
|
536
|
-
|
|
537
|
-
| Property | Type | Information |
|
|
538
|
-
|:--------------:|:-------:|:---------------------------------------------------:|
|
|
539
|
-
| **lux** | int | Real lux value |
|
|
540
|
-
| **lightlevel** | int | Light level |
|
|
541
|
-
| **dark** | boolean | True if it's dark |
|
|
542
|
-
| **daylight** | boolean | True if daylight recognized |
|
|
543
|
-
| **updated** | string | ISO 8601 date string of the last light level update |
|
|
544
|
-
|
|
545
|
-
### Additional Lux Sensor Information
|
|
546
|
-
The event message that the lux sensor sends also contains the following data in the **msg.info** object.
|
|
547
|
-
|
|
548
|
-
| Property | Type | Information |
|
|
549
|
-
|:-------------------:|:------:|:-----------------------------------------------------------------------------------------------------------------------------------:|
|
|
550
|
-
| **id** | int | Numerical id of the sensor as registered on the bridge |
|
|
551
|
-
| **uniqueId** | string | Unique Id of the sensor (typically hardware id) |
|
|
552
|
-
| **name** | string | Name for the sensor |
|
|
553
|
-
| **type** | string | Sensor type (e.g. Daylight, CLIPTemperature, ZGPSwitch) |
|
|
554
|
-
| **softwareVersion** | float | Software version of the sensor |
|
|
555
|
-
| **battery** | int | Current battery level of the temperature sensor in percent |
|
|
556
|
-
| **model** | object | The model object of the sensor includes model specific information like the model.id, model.manufacturer, model.name and model.type |
|
|
557
|
-
|
|
558
|
-
### Last State Information
|
|
559
|
-
This node also sends the entire last state data (before the update) in the **msg.lastState** 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.
|
|
560
|
-
|
|
561
|
-
## Hue Rules
|
|
562
|
-
Hue rule node to receive rule events or to enable / disable rules.
|
|
563
|
-
|
|
564
|
-

|
|
565
|
-
|
|
566
|
-
### Enable / Disable Rule
|
|
567
|
-
Activates or deactivates the rule based on the passed in **msg** values of:
|
|
568
|
-
|
|
569
|
-
| Property | Type | Information |
|
|
570
|
-
|:-----------:|:-------:|:-------------------------------------------------------:|
|
|
571
|
-
| **payload** | boolean | True to enable the rule, false to disable |
|
|
572
|
-
|
|
573
|
-
### Trigger events
|
|
574
|
-
The event message that the rule node sends contains the following data in the **msg.payload** object.
|
|
575
|
-
|
|
576
|
-
| Property | Type | Information |
|
|
577
|
-
|:-------------:|:------:|:--------------------------------------------------------:|
|
|
578
|
-
| **triggered** | string | ISO 8601 date string of the last time rule was triggered |
|
|
579
|
-
|
|
580
|
-
### Additional Rule Info
|
|
581
|
-
Additional information about the rule is going to be sent to the **msg.info** object.
|
|
582
|
-
|
|
583
|
-
| Property | Type | Information |
|
|
584
|
-
|:------------------:|:------:|:-----------------------------------------------------:|
|
|
585
|
-
| **id** | int | Numerical id of the rule as registered on the bridge |
|
|
586
|
-
| **created** | string | ISO 8601 date string of the creation date of the rule |
|
|
587
|
-
| **name** | string | Name of the rule |
|
|
588
|
-
| **timesTriggered** | int | Number of times rule was triggered |
|
|
589
|
-
| **owner** | string | User who created the rule |
|
|
590
|
-
| **status** | string | enabled or disabled, rule is triggerable on enabled |
|
|
591
|
-
|
|
592
|
-
### Rule Conditions
|
|
593
|
-
An array of objects representing the rule conditions is going to be sent to the **msg.conditions** array.
|
|
594
218
|
|
|
595
|
-
|
|
596
|
-
|:------------:|:------:|:----------------------------------------------------:|
|
|
597
|
-
| **address** | string | The sensor resource/state location for the condition |
|
|
598
|
-
| **operator** | string | The operator for the condition |
|
|
599
|
-
| **value** | string | The value used in conjunction with operator |
|
|
600
|
-
|
|
601
|
-
### Rule Actions
|
|
602
|
-
An array of objects representing the rule actions is going to be sent to **msg.actions** array.
|
|
603
|
-
|
|
604
|
-
| Property | Type | Information |
|
|
605
|
-
|:-----------:|:------:|:---------------------------------------------:|
|
|
606
|
-
| **address** | string | The actionable resource location |
|
|
607
|
-
| **method** | string | Type of method for the action (e.g. GET, PUT) |
|
|
608
|
-
| **body** | object | The body of the action |
|
|
609
|
-
|
|
610
|
-
### Last State Information
|
|
611
|
-
This node also sends the entire last state data (before the update) in the **msg.lastState** 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.
|
|
219
|
+
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`:
|
|
612
220
|
|
|
613
|
-
|
|
221
|
+
|Property|Description|
|
|
222
|
+
|--|--|
|
|
223
|
+
| randomOrder (boolean / any) | `true`, activates the random playback of the individual animation steps |
|
|
614
224
|
|
|
615
|
-
###
|
|
616
|
-
* Optimized random color mode for Hue Magic, Hue Light & Hue Group nodes ([#190](https://github.com/Foddy/node-red-contrib-huemagic/pull/190))
|
|
617
|
-
* New Hue Button node ([#190](https://github.com/Foddy/node-red-contrib-huemagic/pull/191))
|
|
618
|
-
* Updated README and Hue Button node docs (+ localized in German)
|
|
225
|
+
### Tips and hints
|
|
619
226
|
|
|
620
|
-
|
|
621
|
-
* Fixed an issue with Hue Light & Hue Group nodes on extended mode ([#179](https://github.com/Foddy/node-red-contrib-huemagic/issues/179))
|
|
622
|
-
* Dependency updates
|
|
227
|
+
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.
|
|
623
228
|
|
|
624
|
-
|
|
625
|
-
|
|
229
|
+
## Hue Light
|
|
230
|
+
The "Hue Light" node can control lights connected to the bridge and receive their status messages.
|
|
626
231
|
|
|
627
|
-
|
|
628
|
-
* Hue Light & Hue Group nodes can now receive commands even if the devices are off ([#110](https://github.com/Foddy/node-red-contrib-huemagic/issues/110) & [#155](https://github.com/Foddy/node-red-contrib-huemagic/issues/155))
|
|
629
|
-
* Hue Light nodes now set their status to switched off when they are not reachable ([#170](https://github.com/Foddy/node-red-contrib-huemagic/issues/170))
|
|
232
|
+

|
|
630
233
|
|
|
631
|
-
###
|
|
632
|
-
* Fixed an issue with Hue Group nodes ([#178](https://github.com/Foddy/node-red-contrib-huemagic/issues/178))
|
|
234
|
+
### Node-RED Setup Instructions
|
|
633
235
|
|
|
634
|
-
|
|
635
|
-
* Fixed a problem with "0" as topic in Hue Group nodes ([#166](https://github.com/Foddy/node-red-contrib-huemagic/issues/166))
|
|
636
|
-
* Fixed an issue with the active property on Hue Motion nodes ([#172](https://github.com/Foddy/node-red-contrib-huemagic/issues/172))
|
|
637
|
-
* Fixed a problem with "random" as a color command on Hue Group & Light nodes ([#167](https://github.com/Foddy/node-red-contrib-huemagic/issues/167))
|
|
638
|
-
* Dependency & readme updates
|
|
236
|
+
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.
|
|
639
237
|
|
|
640
|
-
|
|
641
|
-
* Fixed an error on Hue Scene nodes ([#164](https://github.com/Foddy/node-red-contrib-huemagic/issues/164))
|
|
642
|
-
* New "lastState" property on every node (except Hue Magic & Hue Scene) with the last state before the update
|
|
238
|
+
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.
|
|
643
239
|
|
|
644
|
-
|
|
645
|
-
* Fixed an error on Hue Group & Hue Light nodes ([#161](https://github.com/Foddy/node-red-contrib-huemagic/issues/161))
|
|
646
|
-
* The colorloop effect in Hue Group & Hue Light nodes can now be activated and deactivated manually ([#158](https://github.com/Foddy/node-red-contrib-huemagic/pull/158))
|
|
647
|
-
* New status property for Hue Light, Hue Group & Hue Motion nodes to request the current status of the devices ([#154](https://github.com/Foddy/node-red-contrib-huemagic/issues/154) & [#156](https://github.com/Foddy/node-red-contrib-huemagic/issues/156))
|
|
648
|
-
* Dependency updates
|
|
240
|
+
If you do not select a light and use the node configuration in this way, the node works in the so-called "universal mode". In this mode, the node receives and outputs all status messages of the same type. You can also apply settings in universal mode to a specific light by transferring the corresponding light ID as a string in `msg.topic` together with your settings.
|
|
649
241
|
|
|
650
|
-
###
|
|
651
|
-
* New original temperature parameter on Hue Temperature nodes
|
|
652
|
-
* Nodes are now sending their status once after passing an action ([#150](https://github.com/Foddy/node-red-contrib-huemagic/issues/150) & [#153](https://github.com/Foddy/node-red-contrib-huemagic/issues/153))
|
|
653
|
-
* Fixed an issue on the Hue Motion node ([#145](https://github.com/Foddy/node-red-contrib-huemagic/issues/145))
|
|
654
|
-
* Dependency updates
|
|
242
|
+
### Get status
|
|
655
243
|
|
|
656
|
-
|
|
657
|
-
* New option "incrementColorTemp" and "decrementBrightness" for Hue Light & Hue Group nodes ([#142](https://github.com/Foddy/node-red-contrib-huemagic/pull/142) / [#141](https://github.com/Foddy/node-red-contrib-huemagic/issues/141))
|
|
658
|
-
* Fixed an issue on the Hue Scene node ([#139](https://github.com/Foddy/node-red-contrib-huemagic/issues/139))
|
|
659
|
-
* Fixed an issue on the Hue Switch node ([#138](https://github.com/Foddy/node-red-contrib-huemagic/issues/138))
|
|
660
|
-
* Removed brightness layer on Hue Magic animation previews due to performance issues
|
|
661
|
-
|
|
662
|
-
### v2.6.0
|
|
663
|
-
* Hue Bridge node can now fetch "Portal" and "Internet Services" information
|
|
664
|
-
* Global device updates are now also pushed to the Hue Bridge node (check docs under "Global update events")
|
|
665
|
-
* Removed software update logs on the Bridge (#93)
|
|
666
|
-
* Message structures from each node are now outsourced
|
|
667
|
-
|
|
668
|
-
### v2.5.5
|
|
669
|
-
* Full German help docs translation of every node
|
|
670
|
-
* Delay between bridge requests has been reduced to 500ms from 700ms
|
|
671
|
-
* New "Strobo", "Random Rainbow" & "SOS" animations for the Hue Magic node
|
|
672
|
-
* Hue Magic previews now also display brightness animations
|
|
673
|
-
* Dependency updates
|
|
244
|
+
Outputs the current status of the light as soon as a `msg.payload` object with the following content has been passed to the node. Alternatively, you can also press the button in the Node-RED interface without having to pass a message to the node beforehand.
|
|
674
245
|
|
|
675
|
-
|
|
676
|
-
|
|
677
|
-
|
|
678
|
-
* Fixed an error on Hue Magic node and Hue Magic examples (#136)
|
|
679
|
-
|
|
680
|
-
### v2.5.2
|
|
681
|
-
* Fixed an error with the brightness and transitionTime params on Hue Light & Hue Group nodes (#131)
|
|
682
|
-
* New option "ignoreOffLights" for Hue Group nodes to ignore state changes on turned off lights (#128)
|
|
683
|
-
|
|
684
|
-
### v2.5.1
|
|
685
|
-
* HueMagic nodes are now available in German
|
|
686
|
-
* All HueMagic nodes are now compatible with the new Node-RED "complete" & "catch" nodes (Node-RED v1.0+)
|
|
687
|
-
* Hue Bridge fetch actions now also send out an "info" object with further bridge information
|
|
688
|
-
* New Hue Bridge sample flow can be imported directly from Node-RED
|
|
689
|
-
* Fixed an issue with light & group nodes (#122)
|
|
690
|
-
* Code optimizations and clean up
|
|
691
|
-
|
|
692
|
-
### v2.2.6
|
|
693
|
-
* Hue scenes can now be applied on specific groups
|
|
694
|
-
* Hue Group nodes now support the option to select all groups / lights
|
|
695
|
-
* Optimized Hue Magic node to load dependencies locally
|
|
696
|
-
|
|
697
|
-
### v2.2.3
|
|
698
|
-
* API requests are called again via the absolute path
|
|
699
|
-
|
|
700
|
-
### v2.2.2
|
|
701
|
-
* New "Hue Magic" node with 12 animations included (check docs and examples)
|
|
702
|
-
* Sample flows for each node are now available and can be imported directly from Node-RED
|
|
703
|
-
* Fixed an issue which prevented output events on the nodes (#116)
|
|
704
|
-
|
|
705
|
-
### v2.1.1
|
|
706
|
-
* Fixed an issue with the new option "skip events" on each node
|
|
707
|
-
|
|
708
|
-
### v2.1.0
|
|
709
|
-
* Node updates can now be deactivated individually or globally (check node settings or Hue Bridge configuration)
|
|
710
|
-
* The "pressButton" option has been removed due to API restrictions on newer Hue Bridge firmwares (1.31+)
|
|
711
|
-
|
|
712
|
-
### v2.0.5
|
|
713
|
-
* A delay has been added to minimize API limit problems to the Hue Bridge
|
|
714
|
-
* The color parameter now supports random colors via "any" or "random" as input (Hue Light & Group nodes)
|
|
715
|
-
|
|
716
|
-
### v2.0.4
|
|
717
|
-
* Support of the Hue Smart plug (BETA)
|
|
718
|
-
* Support of alternative dimmer switches (check node docs, new property available)
|
|
719
|
-
* Fixed a problem in recheck loop ([#96](https://github.com/Foddy/node-red-contrib-huemagic/issues/96#issuecomment-530469447))
|
|
720
|
-
* Dependency updates
|
|
246
|
+
|Property|Description|
|
|
247
|
+
|--|--|
|
|
248
|
+
| status (boolean) | Returns the current status of the light |
|
|
721
249
|
|
|
722
|
-
###
|
|
723
|
-
* New "Hue Rule" node (check node docs)
|
|
724
|
-
* New "fetch" command for the Hue Bridge node to get various information
|
|
725
|
-
* New "toggle" and "image" command for Hue Light and Group nodes
|
|
726
|
-
* Transitions and colorloop effects now support millisecond values (comma values)
|
|
727
|
-
* Optimized sequential requests to the bridge to avoid API limit errors
|
|
728
|
-
* Fixed validation errors when group or light nodes are used in universal mode
|
|
729
|
-
* Fixed a problem with human readable color names ([e354c0b](https://github.com/Foddy/node-red-contrib-huemagic/pull/84/commits/e354c0b3596d169fb25bd1e830df39adaf04dc73))
|
|
730
|
-
* Updated readme
|
|
731
|
-
* Dependency updates
|
|
250
|
+
### Turn light on / off (simple)
|
|
732
251
|
|
|
733
|
-
|
|
734
|
-
* New "Hue Bridge" node (check node docs)
|
|
735
|
-
* New event-based algorithm improves the stability of all nodes
|
|
736
|
-
* New option to specify your own, alternative Hue Bridge port has been added (check node docs)
|
|
737
|
-
* Fixed Hue Bridge API limit errors for bridges with a large number of devices
|
|
738
|
-
* Other improvements
|
|
739
|
-
* Dependency updates
|
|
252
|
+
To quickly switch a light on or off in simple mode, pass an object with the following content to the node:
|
|
740
253
|
|
|
741
|
-
|
|
742
|
-
|
|
743
|
-
|
|
744
|
-
* Added colorTemp property to Hue Light event outputs ([f8d237d](https://github.com/Foddy/node-red-contrib-huemagic/pull/52/commits/f8d237d6edf6772dbb73d9bd408e81a4ad4bd99a))
|
|
745
|
-
* Manipulation of the update interval setting to avoid API errors with many devices
|
|
746
|
-
* Fixed some annoying typos
|
|
747
|
-
* Dependency updates
|
|
254
|
+
|Property|Description|
|
|
255
|
+
|--|--|
|
|
256
|
+
| payload (boolean) | `true` switches the light on, `false` switches it off |
|
|
748
257
|
|
|
749
|
-
###
|
|
750
|
-
* Dependency updates
|
|
258
|
+
### Light commands (extended)
|
|
751
259
|
|
|
752
|
-
|
|
753
|
-
* Fixed a typo in Hue Temperature node
|
|
754
|
-
|
|
755
|
-
### v1.5.2
|
|
756
|
-
* Added option to disable color naming in Hue Light & Hue Group config
|
|
757
|
-
* Fixed hex color conversion for Hue Light and Hue Group nodes
|
|
758
|
-
* More accurate color handling for light bulbs
|
|
759
|
-
* Added reachable attribute to Hue Light node
|
|
760
|
-
* Hue Tap can now send the same button action twice
|
|
761
|
-
* Fixed Hue Brightness event trigger when lux is 0
|
|
762
|
-
* UTC formatted "updated" date for Hue Brightness node
|
|
763
|
-
* Better error handling for all nodes
|
|
764
|
-
* Dependency updates
|
|
260
|
+
In addition to simply switching it on and off, there are also many other options available for controlling the light. All nodes in HueMagic can be controlled with additive commands. This means that you can first pass one setting and then another setting in a later command without discarding the previous setting. Transfer the following parameters to a `msg.payload` object to make more extensive settings on the light:
|
|
765
261
|
|
|
766
|
-
|
|
767
|
-
|
|
768
|
-
|
|
769
|
-
|
|
770
|
-
|
|
771
|
-
|
|
262
|
+
|Property|Description|
|
|
263
|
+
|--|--|
|
|
264
|
+
| on (boolean) | `true` switches the light on, `false` switches it off |
|
|
265
|
+
| toggle (boolean / any) | Toggles between switching on and off, depending on the previous status of the light |
|
|
266
|
+
| brightness (int / string) | Percentage value of the light brightness (0-100) or a string with the value `auto` to automatically set the brightness based on the current time |
|
|
267
|
+
| brightnessLevel (int) | Numerical value of the light brightness (0-254) |
|
|
268
|
+
| incrementBrightness (int / boolean) | Specifies by how many percent the light should be made brighter or `true` to make the light brighter in 10% steps |
|
|
269
|
+
| decrementBrightness (int / boolean) | Specifies the percentage by which the light should be made darker or `true` to make the light darker in 10% steps |
|
|
270
|
+
| color (string) | `random` to set a random color or an English color name (e.g. `red`) |
|
|
271
|
+
| hex (string) | Color value in hexadecimal in the form of a string |
|
|
272
|
+
| rgb (array [0,0,0]) | Color value in RGB format in the form of an array |
|
|
273
|
+
| xyColor (object {x [float], y [float]}) | Color value in the XY color format in the form of an object |
|
|
274
|
+
| gradient (object {hex […]}) | An object with a supported color object (e.g. `hex`,` rgb`, ...) and several colors to set a gradient to supported lights |
|
|
275
|
+
| 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 |
|
|
276
|
+
| 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 |
|
|
277
|
+
| saturation (int) | percentage of the saturation of the current color (beta) |
|
|
278
|
+
| colorTemp (int / string) | Value between 153 and 500 to set the color temperature of the light or the values `cold`, `normal`, `warm`, `hot` and `auto` - where `auto` is the color temperature based on the current time |
|
|
279
|
+
| incrementColorTemp (int / boolean) | Value by how much the color temperature should be warmer or `true` to make the color temperature warmer in steps of 50 |
|
|
280
|
+
| decrementColorTemp (int / boolean) | Value by how much the color temperature should be colder or `true` to make the color temperature colder in steps of 50 |
|
|
281
|
+
| transitionTime (float) | Transition time of the current setting in seconds. If `0` is entered, the light changes to the desired setting immediately. If `3` is entered, the light changes to the desired setting with a slight transition in the next 3 seconds |
|
|
282
|
+
| colorloop (float) | Plays a "colorloop" animation for the selected duration in seconds and then switches back to the original state of the light |
|
|
283
|
+
| alert (float) | Plays an "alert" animation for the selected duration in seconds and then switches back to the original state of the light |
|
|
772
284
|
|
|
773
|
-
###
|
|
774
|
-
* Improved status messages for transition commands
|
|
775
|
-
* Dependency updates
|
|
285
|
+
### Status messages from the node
|
|
776
286
|
|
|
777
|
-
|
|
778
|
-
|
|
779
|
-
|
|
780
|
-
|
|
781
|
-
|
|
782
|
-
|
|
783
|
-
|
|
784
|
-
|
|
785
|
-
|
|
786
|
-
|
|
787
|
-
|
|
788
|
-
|
|
789
|
-
|
|
790
|
-
|
|
791
|
-
|
|
792
|
-
|
|
793
|
-
|
|
794
|
-
|
|
795
|
-
|
|
796
|
-
|
|
797
|
-
|
|
798
|
-
|
|
287
|
+
As soon as a change in the light settings has been detected (regardless of whether via Node-RED or externally), the following status message is returned by the node:
|
|
288
|
+
|
|
289
|
+
#### Status object under `msg.payload`
|
|
290
|
+
|
|
291
|
+
|Property|Description|
|
|
292
|
+
|--|--|
|
|
293
|
+
| on (boolean) | State of the light, where `true` stands for on and `false` for off |
|
|
294
|
+
| brightness (int / boolean) | Current brightness in percent or `false`, if the light does not support a brightness setting |
|
|
295
|
+
| brightnessLevel (int / boolean) | Current brightness from 0-254 or `false`, if the light does not support a brightness setting |
|
|
296
|
+
| reachable (boolean / string) | `true` if the light is connected to the bridge, `unknown` if the connection status deviates |
|
|
297
|
+
| 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 |
|
|
298
|
+
| rgb (array [int, int, int] / optional) | Current light color in the form of an RGB value, if the light can display colors |
|
|
299
|
+
| hex (string / optional) | Current light color in the form of a hexadecimal value if the light can display colors |
|
|
300
|
+
| xyColor (object {x [float], y [float]} / optional) | Current light color in the form of an XY value, if the light can display colors |
|
|
301
|
+
| color (string / optional) | Current light name in English, if the light can display colors and the corresponding setting of the node has been activated |
|
|
302
|
+
| gradient (object / optional) | Current gradient setting with all available color units in the form of an array, if the light supports gradient settings, where `colors` outputs the colors, `numColors` the number of set colors in the gradient and `totalColors` the maximum possible Number of colors the resource can support in the gradient |
|
|
303
|
+
| colorTemp (int / boolean / optional) | Current color temperature of the light, if the light can display color temperatures and a color temperature has been set |
|
|
304
|
+
| colorTempName (string / optional) | Current color temperature of the light in the form of a descriptive string with the values `cold`,`normal`, `warm` or `hot`, if the light can display color temperatures and a color temperature has been set. Otherwise `unknown` is output |
|
|
305
|
+
| updated (string) | Time of the last update of the resource by HueMagic (ISO 8601) |
|
|
306
|
+
|
|
307
|
+
#### Information about the light under `msg.info`
|
|
308
|
+
|
|
309
|
+
|Property|Description|
|
|
310
|
+
|--|--|
|
|
311
|
+
| id (string) | Indicates the new ID of the light |
|
|
312
|
+
| idV1 (string / boolean) | Indicates the old ID of the light |
|
|
313
|
+
| uniqueId (string) | The unique ID of the light |
|
|
314
|
+
| deviceId (string) | The unique ID of the device |
|
|
315
|
+
| name (string) | The currently set name of the light |
|
|
316
|
+
| type (string) | The type of light (always `light`) |
|
|
317
|
+
| softwareVersion (string) | The current firmware of the light |
|
|
318
|
+
| model (object) | Contains the model information of the light under `id`, `manufacturer`, `name`, `type`, `certified`, `friendsOfHue`, `colorGamut` and `colorGamutType` |
|
|
319
|
+
|
|
320
|
+
#### Status changes under `msg.updated`
|
|
321
|
+
|
|
322
|
+
Lists individual parameters in the form of an object that have changed compared to the last state of the light. If no changes have been registered, this object is empty.
|
|
323
|
+
|
|
324
|
+
#### Last status of the light under `msg.lastState`
|
|
325
|
+
|
|
326
|
+
Contains the complete status object (see output values above) of the last status before the last change. If the last state of HueMagic has not yet been registered, it will output `false`.
|
|
327
|
+
|
|
328
|
+
#### Last command under `msg.command` (optional)
|
|
329
|
+
|
|
330
|
+
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.
|
|
331
|
+
|
|
332
|
+
## Hue Group
|
|
333
|
+
The "Hue Group" node can control several lights behind a group on the bridge at the same time.
|
|
334
|
+
|
|
335
|
+

|
|
336
|
+
|
|
337
|
+
### Node-RED Setup Instructions
|
|
338
|
+
|
|
339
|
+
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.
|
|
340
|
+
|
|
341
|
+
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.
|
|
342
|
+
|
|
343
|
+
### Get status
|
|
344
|
+
|
|
345
|
+
Outputs the current status of the group as soon as a `msg.payload` object with the following content has been passed to the node. Alternatively, you can also press the button in the Node-RED interface without having to pass a message to the node beforehand.
|
|
346
|
+
|
|
347
|
+
|Property|Description|
|
|
348
|
+
|--|--|
|
|
349
|
+
| status (boolean) | Returns the current status of the group |
|
|
350
|
+
|
|
351
|
+
### Turn on / off (simple)
|
|
352
|
+
|
|
353
|
+
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.
|
|
354
|
+
|
|
355
|
+
|Property|Description|
|
|
356
|
+
|--|--|
|
|
357
|
+
| payload (boolean) | `true` switches the whole group on, `false` switches them off |
|
|
358
|
+
|
|
359
|
+
### Group commands (extended)
|
|
360
|
+
|
|
361
|
+
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:
|
|
362
|
+
|
|
363
|
+
|Property|Description|
|
|
364
|
+
|--|--|
|
|
365
|
+
| on (boolean) | `true` switches the entire group on, `false` switches it off (please note the note above) |
|
|
366
|
+
| toggle (boolean / any) | Toggles between switching on and off, depending on the previous status of the group |
|
|
367
|
+
| 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 |
|
|
368
|
+
| brightnessLevel (int) | Numerical value of the light brightness (0-254) |
|
|
369
|
+
| color (string) | `random` to set a random color or an English color name (e.g. `red`) |
|
|
370
|
+
| hex (string) | Color value in hexadecimal in the form of a string |
|
|
371
|
+
| rgb (array [0,0,0]) | Color value in RGB format in the form of an array |
|
|
372
|
+
| xyColor (object {x [float], y [float]}) | Color value in the XY color format in the form of an object |
|
|
373
|
+
| image (string) | Path of an image (local or on the web) to set the current color of the group to the average color of the image |
|
|
374
|
+
| colorTemp (int / string) | Value between 153 and 500 to set the color temperature of the group or the values `cold`, `normal`, `warm`, `hot` and `auto` - where `auto` is the color temperature based on the current time |
|
|
375
|
+
| transitionTime (float) | Transition time of the current setting in seconds. If `0` is passed, the group changes to the desired setting immediately. If you pass it to `3`, the group changes to the desired setting with a slight transition in the next 3 seconds |
|
|
376
|
+
| colorloop (float) | Plays a “colorloop” animation for the selected duration in seconds and then changes back to the group's original state |
|
|
377
|
+
| alert (float) | Plays an "alert" animation for the selected duration in seconds and then switches back to the original status of the group |
|
|
378
|
+
|
|
379
|
+
### Status messages from the node
|
|
380
|
+
|
|
381
|
+
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).
|
|
382
|
+
|
|
383
|
+
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.
|
|
384
|
+
|
|
385
|
+
#### Status object under `msg.payload`
|
|
386
|
+
|
|
387
|
+
|Property|Description|
|
|
388
|
+
|--|--|
|
|
389
|
+
| on (boolean) | State of the group, where `true` stands for on and `false` for off |
|
|
390
|
+
| updated (string) | Time of the last update of the resource by HueMagic (ISO 8601) |
|
|
391
|
+
|
|
392
|
+
#### Information about the group under `msg.info`
|
|
393
|
+
|
|
394
|
+
|Property|Description|
|
|
395
|
+
|--|--|
|
|
396
|
+
| id (string) | Indicates the new ID of the group |
|
|
397
|
+
| idV1 (string / boolean) | Indicates the old ID of the group |
|
|
398
|
+
| name (string) | The currently set name of the group |
|
|
399
|
+
| type (string) | The type of the group (always `group`) |
|
|
400
|
+
|
|
401
|
+
#### Status changes under `msg.updated`
|
|
402
|
+
|
|
403
|
+
Lists individual parameters in the form of an object that have changed compared to the last state of the group. If no changes have been registered, this object is empty.
|
|
404
|
+
|
|
405
|
+
#### Last status of the light under `msg.lastState`
|
|
406
|
+
|
|
407
|
+
Contains the complete status object (see output values above) of the last status before the last change. If the last state of HueMagic has not yet been registered, it will output `false`.
|
|
408
|
+
|
|
409
|
+
#### Last command under `msg.command` (optional)
|
|
410
|
+
|
|
411
|
+
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.
|
|
412
|
+
|
|
413
|
+
## Hue Scene
|
|
414
|
+
The "Hue Scene" node can resume scenes saved in the bridge and apply them to certain groups.
|
|
415
|
+
|
|
416
|
+

|
|
417
|
+
|
|
418
|
+
### Node-RED Setup Instructions
|
|
419
|
+
|
|
420
|
+
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.
|
|
421
|
+
|
|
422
|
+
### Activate scene
|
|
423
|
+
|
|
424
|
+
You can activate a predefined scene by transferring an object with the following content:
|
|
425
|
+
|
|
426
|
+
|Property|Description|
|
|
427
|
+
|--|--|
|
|
428
|
+
| payload (boolean) | Activates a preconfigured scene |
|
|
429
|
+
|
|
430
|
+
### Activate scene in universal mode
|
|
431
|
+
|
|
432
|
+
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:
|
|
433
|
+
|
|
434
|
+
|Property|Description|
|
|
435
|
+
|--|--|
|
|
436
|
+
| scene (string) | ID of the scene to be activated on the bridge |
|
|
437
|
+
|
|
438
|
+
### Activate scene on certain groups
|
|
439
|
+
|
|
440
|
+
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:
|
|
441
|
+
|
|
442
|
+
|Property|Description|
|
|
443
|
+
|--|--|
|
|
444
|
+
| 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 |
|
|
445
|
+
|
|
446
|
+
### More information about the Node
|
|
447
|
+
|
|
448
|
+
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.
|
|
449
|
+
|
|
450
|
+
## Hue Buttons
|
|
451
|
+
The "Hue Buttons" node receives switching events from input devices connected to the bridge.
|
|
452
|
+
|
|
453
|
+

|
|
454
|
+
|
|
455
|
+
### Node-RED Setup Instructions
|
|
456
|
+
|
|
457
|
+
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 switch, you can also enter it here manually. You can either assign a new name for the switch 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 switch after each deployment.
|
|
799
458
|
|
|
800
|
-
|
|
801
|
-
* Improved alert function with configurable amount of seconds
|
|
802
|
-
* Several fixes and optimizations
|
|
459
|
+
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.
|
|
803
460
|
|
|
804
|
-
###
|
|
805
|
-
* New "universal mode" for Hue Light and Hue Group nodes
|
|
461
|
+
### Get status
|
|
806
462
|
|
|
807
|
-
|
|
808
|
-
* Replacing "superagent" dependency with "request" due to security vulnerabilities
|
|
809
|
-
* Several small fixes and optimizations for hue bridge node
|
|
463
|
+
Outputs the current status of the switch/button as soon as a `msg.payload` object with the following content has been passed to the node. Alternatively, you can also press the button in the Node-RED interface without having to pass a message to the node beforehand.
|
|
810
464
|
|
|
811
|
-
|
|
812
|
-
|
|
465
|
+
|Property|Description|
|
|
466
|
+
|--|--|
|
|
467
|
+
| status (boolean) | Returns the current status of the switch/button |
|
|
813
468
|
|
|
814
|
-
###
|
|
815
|
-
* Fixed block-scoped declarations for Node.js below version 6.x
|
|
469
|
+
### Status messages from the node
|
|
816
470
|
|
|
817
|
-
|
|
818
|
-
* Support of Hue Scenes (new scene node)!
|
|
819
|
-
* Removed "id, "lightIds" and "battery" parameter in msg.payload of sensors / lights / groups
|
|
820
|
-
* Added msg.info object on all node events with extended device information
|
|
471
|
+
As soon as a key has been pressed, the following status message is returned by the node:
|
|
821
472
|
|
|
822
|
-
|
|
823
|
-
* Typo corrections and small improvements
|
|
473
|
+
#### Status object under `msg.payload`
|
|
824
474
|
|
|
825
|
-
|
|
826
|
-
|
|
475
|
+
|Property|Description|
|
|
476
|
+
|--|--|
|
|
477
|
+
| reachable (boolean / string) | `true` if the switch/button is connected to the bridge, `unknown` if the connection status deviates |
|
|
478
|
+
| 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 |
|
|
479
|
+
| button (int / boolean) | Numeric ID of the key that was last pressed or `false` if no key was pressed |
|
|
480
|
+
| 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 |
|
|
481
|
+
| updated (string) | Time of the last update of the resource by HueMagic (ISO 8601) |
|
|
482
|
+
|
|
483
|
+
#### Information about the switch/button under `msg.info`
|
|
484
|
+
|
|
485
|
+
|Property|Description|
|
|
486
|
+
|--|--|
|
|
487
|
+
| id (string) | Indicates the new ID of the switch/button |
|
|
488
|
+
| idV1 (string / boolean) | Indicates the old ID of the switch/button |
|
|
489
|
+
| uniqueId (string) | The unique ID of the switch/button |
|
|
490
|
+
| deviceId (string) | The unique ID of the device |
|
|
491
|
+
| name (string) | The currently set name of the switch/button |
|
|
492
|
+
| type (string) | The type of the switch/button (always `button`) |
|
|
493
|
+
| softwareVersion (string) | The current firmware of the switch/button |
|
|
494
|
+
| battery (float / boolean) | The current battery level of the switch/button, `false`, when there is no battery |
|
|
495
|
+
| 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 |
|
|
496
|
+
| model (object) | Contains the model information of the switch/button under `id` , `manufacturer`, `name`, `type` and `certified` |
|
|
497
|
+
|
|
498
|
+
#### Status changes under `msg.updated`
|
|
499
|
+
|
|
500
|
+
Lists individual parameters in the form of an object that have changed compared to the last state of the switch/button. If no changes have been registered, this object is empty.
|
|
501
|
+
|
|
502
|
+
#### Last status of the switch/button under `msg.lastState`
|
|
503
|
+
|
|
504
|
+
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`.
|
|
505
|
+
|
|
506
|
+
#### Last command under `msg.command` (optional)
|
|
507
|
+
|
|
508
|
+
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.
|
|
509
|
+
|
|
510
|
+
## Hue Motion
|
|
511
|
+
The "Hue motion" node can register and report movements from a suitable sensor on the bridge.
|
|
512
|
+
|
|
513
|
+

|
|
514
|
+
|
|
515
|
+
### Node-RED Setup Instructions
|
|
516
|
+
|
|
517
|
+
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.
|
|
518
|
+
|
|
519
|
+
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.
|
|
520
|
+
|
|
521
|
+
### Get status
|
|
522
|
+
|
|
523
|
+
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.
|
|
524
|
+
|
|
525
|
+
|Property|Description|
|
|
526
|
+
|--|--|
|
|
527
|
+
| status (boolean) | Returns the current status of the sensor |
|
|
528
|
+
|
|
529
|
+
### Turn the sensor on / off
|
|
530
|
+
|
|
531
|
+
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:
|
|
532
|
+
|
|
533
|
+
|Property|Description|
|
|
534
|
+
|--|--|
|
|
535
|
+
| payload (boolean) | `true` turns the sensor on,` false` turns it off |
|
|
536
|
+
|
|
537
|
+
### Status messages from the node
|
|
538
|
+
|
|
539
|
+
As soon as the sensor has registered a movement, the following status message is returned by the node:
|
|
540
|
+
|
|
541
|
+
#### Status object under `msg.payload`
|
|
542
|
+
|
|
543
|
+
|Property|Description|
|
|
544
|
+
|--|--|
|
|
545
|
+
| active (boolean) | Indicates whether the sensor is switched on or off |
|
|
546
|
+
| reachable (boolean / string) | `true` if the sensor is connected to the bridge, `unknown` if the connection status deviates |
|
|
547
|
+
| 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 |
|
|
548
|
+
| motion (boolean) | Indicates whether a motion has been registered |
|
|
549
|
+
| updated (string) | Time of the last update of the resource by HueMagic (ISO 8601) |
|
|
550
|
+
|
|
551
|
+
#### Information about the sensor under `msg.info`
|
|
552
|
+
|
|
553
|
+
|Property|Description|
|
|
554
|
+
|--|--|
|
|
555
|
+
| id (string) | Indicates the new ID of the sensor |
|
|
556
|
+
| idV1 (string / boolean) | Indicates the old ID of the sensor |
|
|
557
|
+
| uniqueId (string) | The unique ID of the sensor |
|
|
558
|
+
| deviceId (string) | The unique ID of the device |
|
|
559
|
+
| name (string) | The currently set name of the sensor |
|
|
560
|
+
| type (string) | The type of the sensor (always `motion`) |
|
|
561
|
+
| softwareVersion (string) | The current firmware of the sensor |
|
|
562
|
+
| battery (float) | The current battery level of the sensor |
|
|
563
|
+
| batteryState (string) | The current status of the battery level. Can contain `normal`, `low` or `critical` as a value |
|
|
564
|
+
| model (object) | Contains the model information of the sensor under `id`, `manufacturer`, `name`, `type` and `certified` |
|
|
565
|
+
|
|
566
|
+
#### Status changes under `msg.updated`
|
|
567
|
+
|
|
568
|
+
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.
|
|
569
|
+
|
|
570
|
+
#### Last status of the sensor under `msg.lastState`
|
|
571
|
+
|
|
572
|
+
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`.
|
|
573
|
+
|
|
574
|
+
#### Last command under `msg.command` (optional)
|
|
575
|
+
|
|
576
|
+
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.
|
|
577
|
+
|
|
578
|
+
## Hue Temperature
|
|
579
|
+
The "Hue Temperature" node can call up and report the current ambient temperature from a suitable sensor on the bridge.
|
|
580
|
+
|
|
581
|
+

|
|
582
|
+
|
|
583
|
+
### Node-RED Setup Instructions
|
|
584
|
+
|
|
585
|
+
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.
|
|
586
|
+
|
|
587
|
+
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.
|
|
588
|
+
|
|
589
|
+
### Get status
|
|
590
|
+
|
|
591
|
+
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.
|
|
592
|
+
|
|
593
|
+
|Property|Description|
|
|
594
|
+
|--|--|
|
|
595
|
+
| status (boolean) | Returns the current status of the sensor |
|
|
596
|
+
|
|
597
|
+
### Switch the sensor on / off
|
|
598
|
+
|
|
599
|
+
If necessary, the sensor can be switched on and off remotely. If the sensor has been switched off, it no longer registers any temperature changes and accordingly no longer outputs them. To do this, pass an object with the following content:
|
|
600
|
+
|
|
601
|
+
|Property|Description|
|
|
602
|
+
|--|--|
|
|
603
|
+
| payload (boolean) | `true` switches the sensor on, `false` switches it off |
|
|
604
|
+
|
|
605
|
+
### Status messages from the node
|
|
606
|
+
|
|
607
|
+
As soon as the sensor has registered a temperature change, the following status message is returned by the node:
|
|
608
|
+
|
|
609
|
+
#### Status object under `msg.payload`
|
|
610
|
+
|
|
611
|
+
|Property|Description|
|
|
612
|
+
|--|--|
|
|
613
|
+
| active (boolean) | Indicates whether the sensor is switched on or off |
|
|
614
|
+
| reachable (boolean / string) | `true` if the sensor is connected to the bridge, `unknown` if the connection status deviates |
|
|
615
|
+
| 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 |
|
|
616
|
+
| celsius (float) | Indicates the current ambient temperature in °C (degrees Celsius) |
|
|
617
|
+
| fahrenheit (float) | Indicates the current ambient temperature in °F (degrees Fahrenheit) |
|
|
618
|
+
| temperatureIs (string) | Describes the current temperature with the values ´very cold´, ´cold´, ´slightly cold´, ´comfortable´, ´slightly warm´, ´warm´, ´hot´ or ´very hot´ |
|
|
619
|
+
| deviceValue (float) | The original value of the temperature from the sensor |
|
|
620
|
+
| updated (string) | Time of the last update of the resource by HueMagic (ISO 8601) |
|
|
621
|
+
|
|
622
|
+
#### Information about the sensor under `msg.info`
|
|
623
|
+
|
|
624
|
+
|Property|Description|
|
|
625
|
+
|--|--|
|
|
626
|
+
| id (string) | Indicates the new ID of the sensor |
|
|
627
|
+
| idV1 (string / boolean) | Indicates the old ID of the sensor |
|
|
628
|
+
| uniqueId (string) | The unique ID of the sensor |
|
|
629
|
+
| deviceId (string) | The unique ID of the device |
|
|
630
|
+
| name (string) | The currently set name of the sensor |
|
|
631
|
+
| type (string) | The type of the sensor (always `temperature`) |
|
|
632
|
+
| softwareVersion (string) | The current firmware of the sensor |
|
|
633
|
+
| battery (float) | The current battery level of the sensor |
|
|
634
|
+
| batteryState (string) | The current status of the battery level. Can contain `normal`, `low` or `critical` as a value |
|
|
635
|
+
| model (object) | Contains the model information of the sensor under `id`, `manufacturer`, `name`, `type` and `certified` |
|
|
636
|
+
|
|
637
|
+
#### Status changes under `msg.updated`
|
|
638
|
+
|
|
639
|
+
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.
|
|
640
|
+
|
|
641
|
+
#### Last status of the sensor under `msg.lastState`
|
|
642
|
+
|
|
643
|
+
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`.
|
|
644
|
+
|
|
645
|
+
#### Last command under `msg.command` (optional)
|
|
646
|
+
|
|
647
|
+
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.
|
|
648
|
+
|
|
649
|
+
## Hue Brightness
|
|
650
|
+
The "Hue Brightness" node can read the current light level from a suitable sensor on the bridge.
|
|
651
|
+
|
|
652
|
+

|
|
653
|
+
|
|
654
|
+
### Node-RED Setup Instructions
|
|
655
|
+
|
|
656
|
+
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.
|
|
657
|
+
|
|
658
|
+
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.
|
|
659
|
+
|
|
660
|
+
### Get status
|
|
661
|
+
|
|
662
|
+
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.
|
|
663
|
+
|
|
664
|
+
|Property|Description|
|
|
665
|
+
|--|--|
|
|
666
|
+
| status (boolean) | Returns the current status of the sensor |
|
|
667
|
+
|
|
668
|
+
### Turn the sensor on / off
|
|
669
|
+
|
|
670
|
+
If necessary, the sensor can be turned on and off remotely. If the sensor has been turned off, it no longer registers any changes in light level and accordingly no longer outputs them. To do this, pass an object with the following content:
|
|
671
|
+
|
|
672
|
+
|Property|Description|
|
|
673
|
+
|--|--|
|
|
674
|
+
| payload (boolean) | `true` switches the sensor on, `false` switches it off |
|
|
675
|
+
|
|
676
|
+
### Status messages from the node
|
|
677
|
+
|
|
678
|
+
As soon as the sensor has detected a change in the light level, the following status message is returned:
|
|
679
|
+
|
|
680
|
+
#### Status object under `msg.payload`
|
|
681
|
+
|
|
682
|
+
|Property|Description|
|
|
683
|
+
|--|--|
|
|
684
|
+
| active (boolean) | Indicates whether the sensor is turned on or off |
|
|
685
|
+
| reachable (boolean / string) | `true` if the sensor is connected to the bridge, `unknown` if the connection status deviates |
|
|
686
|
+
| 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 |
|
|
687
|
+
| lux (int) | Indicates the real LUX value of the light level |
|
|
688
|
+
| lightLevel (int) | Indicates the light intensity of the sensor |
|
|
689
|
+
| dark (boolean) | `true`, if darkness was registered |
|
|
690
|
+
| daylight (boolean) | `true`, if daylight was registered |
|
|
691
|
+
| updated (string) | Time of the last update of the resource by HueMagic (ISO 8601) |
|
|
692
|
+
|
|
693
|
+
#### Information about the sensor under `msg.info`
|
|
694
|
+
|
|
695
|
+
|Property|Description|
|
|
696
|
+
|--|--|
|
|
697
|
+
| id (string) | Indicates the new ID of the sensor |
|
|
698
|
+
| idV1 (string / boolean) | Indicates the old ID of the sensor |
|
|
699
|
+
| uniqueId (string) | The unique ID of the sensor |
|
|
700
|
+
| deviceId (string) | The unique ID of the device |
|
|
701
|
+
| name (string) | The currently set name of the sensor |
|
|
702
|
+
| type (string) | The type of the sensor (always `light_level`) |
|
|
703
|
+
| softwareVersion (string) | The current firmware of the sensor |
|
|
704
|
+
| battery (float) | The current battery level of the sensor |
|
|
705
|
+
| batteryState (string) | The current status of the battery level. Can contain `normal`, `low` or `critical` as a value |
|
|
706
|
+
| model (object) | Contains the model information of the sensor under `id`, `manufacturer`, `name`, `type` and `certified` |
|
|
707
|
+
|
|
708
|
+
#### Status changes under `msg.updated`
|
|
709
|
+
|
|
710
|
+
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.
|
|
711
|
+
|
|
712
|
+
#### Last status of the sensor under `msg.lastState`
|
|
713
|
+
|
|
714
|
+
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`.
|
|
715
|
+
|
|
716
|
+
#### Last command under `msg.command` (optional)
|
|
717
|
+
|
|
718
|
+
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.
|
|
719
|
+
|
|
720
|
+
## Hue Rule
|
|
721
|
+
The "Hue Rule" node can activate or deactivate rules saved in the bridge and call up their settings.
|
|
722
|
+
|
|
723
|
+

|
|
724
|
+
|
|
725
|
+
### Node-RED Setup Instructions
|
|
726
|
+
|
|
727
|
+
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.
|
|
728
|
+
|
|
729
|
+
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.
|
|
730
|
+
|
|
731
|
+
### Get properties / settings
|
|
732
|
+
|
|
733
|
+
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.
|
|
734
|
+
|
|
735
|
+
|Property|Description|
|
|
736
|
+
|--|--|
|
|
737
|
+
| status (boolean) | Returns the current status of the rule |
|
|
738
|
+
|
|
739
|
+
### Activate / deactivate rule
|
|
740
|
+
|
|
741
|
+
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:
|
|
742
|
+
|
|
743
|
+
|Property|Description|
|
|
744
|
+
|--|--|
|
|
745
|
+
| payload (boolean) | `true` activates the rule, `false` deactivates it |
|
|
746
|
+
|
|
747
|
+
### Status messages from the node
|
|
748
|
+
|
|
749
|
+
As soon as the status (activated / deactivated) of a rule changes, the following status message is returned by the node:
|
|
750
|
+
|
|
751
|
+
#### Status object under `msg.payload`
|
|
752
|
+
|
|
753
|
+
|Property|Description|
|
|
754
|
+
|--|--|
|
|
755
|
+
| enabled (boolean) | Indicates whether the rule is activated or deactivated |
|
|
756
|
+
| triggered (string) | Time of the last execution (ISO 8601) |
|
|
757
|
+
|
|
758
|
+
#### Information about the rule under `msg.info`
|
|
759
|
+
|
|
760
|
+
|Property|Description|
|
|
761
|
+
|--|--|
|
|
762
|
+
| id (string) | The unique ID of the rule |
|
|
763
|
+
| created (string) | Date of creation of the rule (ISO 8601) |
|
|
764
|
+
| name (string) | Name of the rule on the bridge |
|
|
765
|
+
| timesTriggered (int) | Number of times the rule was executed on the bridge |
|
|
766
|
+
| owner (string) | ID of the owner of this rule |
|
|
767
|
+
| status (string) | Status of the rule in the form of a string |
|
|
768
|
+
|
|
769
|
+
#### Rule conditions under `msg.conditions` (array)
|
|
770
|
+
|
|
771
|
+
|Property|Description|
|
|
772
|
+
|--|--|
|
|
773
|
+
| address (string) | Path to an attribute of a sensor |
|
|
774
|
+
| operator (string) | operator |
|
|
775
|
+
| value (string) | The value to be checked |
|
|
776
|
+
|
|
777
|
+
#### Rule actions under `msg.actions` (array)
|
|
778
|
+
|
|
779
|
+
|Property|Description|
|
|
780
|
+
|--|--|
|
|
781
|
+
| address (string) | The destination address of the resource |
|
|
782
|
+
| method (string) | The query method |
|
|
783
|
+
| body (object) | The action to be taken |
|
|
784
|
+
|
|
785
|
+
#### Status changes under `msg.updated`
|
|
786
|
+
|
|
787
|
+
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.
|
|
788
|
+
|
|
789
|
+
#### Last status of the rule under `msg.lastState`
|
|
790
|
+
|
|
791
|
+
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`.
|
|
792
|
+
|
|
793
|
+
#### Last command under `msg.command` (optional)
|
|
794
|
+
|
|
795
|
+
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.
|
|
796
|
+
|
|
797
|
+
# Changelog
|
|
798
|
+
|
|
799
|
+
### v4.0.2 (latest)
|
|
800
|
+
|
|
801
|
+
> **Attention!** HueMagic v4 + has been almost completely rewritten under the hood and requires at least the (square-shaped) Philips Hue Bridge firmware 1948086000+ from November 1st, 2021 ([Upgrade instructions](https://www.lighting.philips.com/content/B2C/en_US/microsites/meethue/marketing-catalog/huewireless_ca/support/security-advisory/general/where-and-how-can-i-update-my-hue-system-with-the-latest-software.html)) and Node-RED v1+ ([Upgrade instructions](https://nodered.org/docs/getting-started/local#upgrading-node-red)). If you are upgrading from a previous HueMagic version to the v4, you will have to reconfigure (not completely rebuild) all nodes by clicking them and selecting the appropriate device from the list. This also applies to nodes / functions that are operated in universal mode, as the numeric identifiers of the latest Philips Hue API version have been replaced in UUIDs. The nodes "Hue Switch", "Hue Button" & "Hue Tap" have been replaced in v4 by the universal and uniform node "Hue Buttons", which works with all button / switch devices that are connected to the Hue Bridge (please note here also the new API in the documentation). The request and return objects of the individual nodes are largely compatible with older HueMagic versions - with the exception of the nodes "Hue Bridge", "Hue Buttons", "Hue Scene" & "Hue Group". These need to be adjusted in the v4. Make sure that you meet the minimum technical requirements and have a quiet minute for the migration before upgrading to the v4.
|
|
802
|
+
|
|
803
|
+
* HueMagic speaks now directly with the bridge without any submodules *(huejay dependency removed)*
|
|
804
|
+
* Migrated to the newest CLIP/v2 API version from the Philips Hue bridge
|
|
805
|
+
* Nodes are now updated via push notifications (SSE) from the bridge instead of periodic polling
|
|
806
|
+
* Instant "current status" queries on each node with no loading time
|
|
807
|
+
* "Hue Buttons" node supports all new Philips Hue buttons/switches (e.g. Dimmer Switch v2, Hue Wall Switch…)
|
|
808
|
+
* All nodes provide additional property information in the output (check docs)
|
|
809
|
+
* New universal node "Hue Buttons" replaces the following nodes: "Hue Switch", "Hue Button", "Hue Tap"
|
|
810
|
+
* New "updated" object for all nodes, which only contains the properties that have been updated since the last state
|
|
811
|
+
* New configuration option to suppress first message after node initialization (for all nodes)
|
|
812
|
+
* New gradient color setting for compatible light sources (in "Hue Light" node)
|
|
813
|
+
* New inject button for almost all nodes, which triggers the current status of a node
|
|
814
|
+
* New "universal mode" support for the "Hue Rule" node
|
|
815
|
+
* New SVG-version of each node icon for higher quality rendering in the Node-RED UI
|
|
816
|
+
* New and full featured examples for each node right inside Node-RED
|
|
817
|
+
* New color mix feature in "Hue Light" nodes with the ability to mix the current light color with another
|
|
818
|
+
* New automatic brightness support based on the current time for "Hue Light" & "Hue Group" nodes
|
|
819
|
+
* New "Superhero", "Neon City" & "Christmas" (for next year, sorry) animations in "Hue Magic" node
|
|
820
|
+
* The custom alert effect on "Hue Light" & "Hue Group" nodes can now also be configured in brightness
|
|
821
|
+
* All nodes will now also forward the last command that has been applied ([#249](https://github.com/Foddy/node-red-contrib-huemagic/issues/249))
|
|
822
|
+
* "Hue Temperature" & "Hue Brightness" nodes can now also be activated & deactivated
|
|
823
|
+
* "Hue Light" & "Hue Group" nodes can now also receive XY color settings
|
|
824
|
+
* "Hue Light" & "Hue Group" can now also receive a named color temperature setting
|
|
825
|
+
* "Hue Light" & "Hue Group" nodes can now receive future brightness states in "turned off" mode ([#244](https://github.com/Foddy/node-red-contrib-huemagic/issues/244))
|
|
826
|
+
* Automatic light temperature setting outputs now values from 153 (coldest) to 500 (warmest)
|
|
827
|
+
* Automatic color correction based on the light´s capabilities for more accurate color settings
|
|
828
|
+
* Optimized node editor configuration UI to better match the current Node-RED´s UI
|
|
829
|
+
* The option for "automatic firmware updates" on the bridge moved to the bridge configuration node
|
|
830
|
+
* "Hue Group" node does no longer contain the "msg.info.model" & "msg.info.class" property
|
|
831
|
+
* Fixed timeout connection issues to the bridge
|
|
832
|
+
* Fixed an issue with non stopping custom animations ([#222](https://github.com/Foddy/node-red-contrib-huemagic/issues/222)), ([#224](https://github.com/Foddy/node-red-contrib-huemagic/issues/224)) & ([#226](https://github.com/Foddy/node-red-contrib-huemagic/pull/226)) (thx)
|
|
833
|
+
* Node-RED will no longer crash if there is no active connection to the bridge ([#237](https://github.com/Foddy/node-red-contrib-huemagic/issues/237))
|
|
834
|
+
* Fixed an issue that prevented the light / group from not reporting its own status when queried & node events were deactivated ([#248](https://github.com/Foddy/node-red-contrib-huemagic/issues/248))
|
|
835
|
+
* Fixed an issue with nodes in universal mode ([#245](https://github.com/Foddy/node-red-contrib-huemagic/issues/245))
|
|
836
|
+
* A possible attack target has been fixed ([#217](https://github.com/Foddy/node-red-contrib-huemagic/issues/217))
|
|
837
|
+
* Moved away from "moment.js" to "Day.js" for date/time formatting inside the nodes
|
|
838
|
+
* Updated README and help section on each node
|
|
839
|
+
* Updated dependencies to the latest version
|
|
840
|
+
|
|
841
|
+
### v3.0.0
|
|
842
|
+
* Hue Motion, Hue Brightness, Hue Tap, Hue Switch & Hue Button nodes can now receive a status request
|
|
843
|
+
* New "Universal Mode" for the Hue Motion, Hue Brightness, Hue Tap, Hue Switch & Hue Button nodes
|
|
844
|
+
* The "colorTemp" property for Hue Light & Hue Group nodes can now also be set to "cold", "normal", "warm" or "auto"
|
|
845
|
+
* New dynamic and automatically calculated color temperature based on the current time ("auto" mode in "colorTemp" property)
|
|
846
|
+
* Nodes in "Universal Mode" are now also able to receive all events from devices of its type (optional)
|
|
847
|
+
* Hue Magic animations are now prerendered to improve performance
|
|
848
|
+
* 3 new Hue Magic animations ("Milkyway", "Beach" & "Forest")
|
|
849
|
+
* New (simple) Hue Button example flow
|
|
850
|
+
* Updated docs for almost all nodes and README
|
|
851
|
+
* Fixed an error with future states and the HTTP request node ([#200](https://github.com/Foddy/node-red-contrib-huemagic/pull/200))
|
|
852
|
+
* Other optimizations, dependency updates and clean up
|
|
853
|
+
|
|
854
|
+
### v2.8.6
|
|
855
|
+
* Optimized random color mode for Hue Magic, Hue Light & Hue Group nodes ([#190](https://github.com/Foddy/node-red-contrib-huemagic/pull/190))
|
|
856
|
+
* New Hue Button node ([#191](https://github.com/Foddy/node-red-contrib-huemagic/pull/191))
|
|
857
|
+
* Updated README and Hue Button node docs (+ localized in German)
|
|
858
|
+
|
|
859
|
+
### v2.8.2
|
|
860
|
+
* Fixed an issue with Hue Light & Hue Group nodes on extended mode ([#179](https://github.com/Foddy/node-red-contrib-huemagic/issues/179))
|
|
861
|
+
* Dependency updates
|
|
862
|
+
|
|
863
|
+
### Previous versions
|
|
864
|
+
A complete overview of the updates can be viewed in the [changelog](https://github.com/Foddy/node-red-contrib-huemagic/blob/master/CHANGELOG.md)…
|
|
827
865
|
|
|
828
866
|
|
|
829
867
|
***
|
|
830
|
-
|
|
868
|
+
### Made with a pinch of magic in Stuttgart, Germany.
|
|
869
|
+
|
|
870
|
+
If you like HueMagic, I appreciate a star or rating on this page! HueMagic is and will remain free. You can support the further development of the project with a small donation.
|
|
871
|
+
|
|
872
|
+
Alternatively, you can support the project if you have an old device that is compatible with the Philips Hue bridge (or a device that is not officially supported by HueMagic) and want to get rid of it. Please contact me at huemagic@foddy.io to get an address where you can send your old device. The following devices could currently be considered: Gradient lights, Tap / Button devices or table / floor lights. These types of devices have not been extensively tested during HueMagic's development.
|
|
831
873
|
|
|
832
|
-
Do you like HueMagic? If so, make sure to give this project a star! If you want to support the development, you can also do so with a donation. HueMagic remains completely free for everyone - even without a donation. Thank you! :)
|
|
833
874
|
***
|
|
834
875
|
<a href="https://www.jetbrains.com/?from=HueMagic"><img src="https://gistcdn.githack.com/Foddy/062045775c28f5993ad646aba80e678c/raw/c84ea4ad31c72dde0883638fc9eaa2b51bba9962/jb.svg" height="50"></a> <a href="https://www.browserstack.com?from=HueMagic"><img src="https://gistcdn.githack.com/Foddy/062045775c28f5993ad646aba80e678c/raw/c84ea4ad31c72dde0883638fc9eaa2b51bba9962/browserstack.svg" height="50"></a>
|
|
835
876
|
|
|
836
877
|
HueMagic for Node-RED is sponsored by [JetBrains](https://www.jetbrains.com/?from=HueMagic) and [BrowserStack](https://www.browserstack.com?from=HueMagic).<br>
|
|
837
|
-
*Released under the [Apache License 2.0](https://tldrlegal.com/license/apache-license-2.0-(apache-2.0)).*
|
|
878
|
+
*Released under the [Apache License 2.0](https://tldrlegal.com/license/apache-license-2.0-(apache-2.0)).*
|