foddy / node-red-contrib-huemagic Goto Github PK

There is a small typo regarding the capital L in lightLevel.
The info and the webpage describes lightlevel, while the msg.payload contains lightLevel.

Hi. I am having an issue where "Hue Light" can handle 1 payload.msg before it reports

"Error: Philips Hue: 3, resource, /lights/NaN, not available"

"Hue Group" also works fine the first time, but subsequent messages change the id to 0

After first inject:

{"id":2,"lightIds":"3, 4","name":"Hallway","type":"Room"}

After subsequent injects:

{"id":0,"lightIds":"1, 2, 3, 4, 5, 6, 7","name":"Group 0","type":"LightGroup"}

On both cases I am injecting a payload with only a boolean value.

{"_msgid":"486dee22.8b5fb","topic":"","payload":false}

Running on rpi1 with Node-red v0.17.5 and node v6.12.1

Hi,

Is it possible to read the status of a light based on an input trigger? (Every x-minutes or when a flow is started). Currently I use ttb-node-hue which works fine, but it I like to use the other Huemagic functionality and therefore I need to switch over.

i.e. When I get home a flow is started to check each of my hue lights one by one. If any of the lights is on, nothing is changed to not mess with the light settings of my family members. If all lights are off, then some lights are turned on to welcome me home.

Best Regards,
Alexander

I have a number of Switch nodes reading my Hue switch status. After the update to 1.4 I get a slew of errors as follows:
7/02/2018, 18:06:38node: MainSwitch
msg : error
"Error: Huejay: read ECONNRESET"
17/02/2018, 18:06:38node: KitchenCabinets
msg : error
"Error: Huejay: read ECONNRESET"
17/02/2018, 18:06:38node: Porch
msg : error
"Error: Huejay: read ECONNRESET"
17/02/2018, 18:06:40node: KitchenCabinets
msg : error
"Error: Huejay: read ECONNRESET"
17/02/2018, 18:06:40node: Porch
msg : error
"Error: Huejay: read ECONNRESET"
17/02/2018, 18:06:46node: Porch
msg : error
"Error: Huejay: read ECONNRESET"

The nodes themselves now sit in a 'waiting' state. Pressing the switches makes no difference. The nodes themselves are currently used to check the battery state, but I had planned to possibly read the last button pressed to activate other devices.

Hi there,

i have seen the already closed issues, but i still have the problems with the latest version. I am running Docker on my Synology NAS and till down everything worked absolutely nicely, at least till i have added more Hue Motion sensors. Before i had 5 lamps and one motion sensor and everything worked great. Then i have added two additional motion sensors and all went downhill. I have connection errors with the motion sensors and even with one of the lamps now. I have fiddled around with the polling interval between 1000 and 10000, but nothing seems to work. Are 3 motion sensors too much? Btw in the Hue iPhone app everything is fine and the motion sensors function properly when i have added rules in the motion app (lights on when dark and movement).

Anyone an idea?

Thank you and best regards,
S

Hi,
I just made a small Node with a Hue Light and Hue Group and somehow the output rgb and hex code is wrong.
For example:
Hue Group/Light input is rgb(255,0,0) or hex code: #ff0000 the reading output is rgb(255,254,88).

Seems that after a few hours the motion sensor (including subsensors like lightlevel) loses connection. Node red shows "disconnected" for these nodes. When I redeploy node red they get connected again. Would it be possible to have some reconnect mechanism implemented?

Rather than force the choice of a bulb ID in the node could you make this an input such as Topic. This can be chosen if the ID is left as zero in the node. This allows the node to be driven from a SQL database where Hue is but one of the types of light that the database might simultaneously select. It also allows the light to be selected from an MQTT message.

It seems like it's not possible to get a message if you press more than 1 time on the button of a tap, you need to press one of the other buttons to have the original button retriggered. It would be useful to allow this as we could program toggle switches.
Thanks !

Hi, i've installed huemagic, but nothing shows in the flow designer.
This is on windows
npm 2.15.9
node 4.6.1

After restarting node-red, i see this in the logfile

9 Sep 03:40:29 - [warn] [rpi-gpio] Info : Ignoring Raspberry Pi specific node
19 Sep 03:40:29 - [warn] [tail] Not currently supported on Windows.
19 Sep 03:40:29 - [warn] [hue-bridge] SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
19 Sep 03:40:29 - [warn] [hue-light] SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
19 Sep 03:40:29 - [warn] [hue-group] SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
19 Sep 03:40:29 - [warn] [hue-scene] SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
19 Sep 03:40:29 - [warn] [hue-motion] SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
19 Sep 03:40:29 - [warn] [hue-temperature] SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
19 Sep 03:40:29 - [warn] [hue-brightness] SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode

Hello,

i have a Problem finding any of my lights. I have configured my bridge. API Key all is well. But the software doens't find any lights. Why? Thanks

Hello, i have a Problem with my new and now second Motion-Sensor in Node-Red.
The Device give me no "Battery-Status", only this Information over the Debug-Node:

18.9.2017, 20:13:32node: 60fc994.ba3b9e8
msg.payload : Object
object
lightLevel: 0
dark: true
daylight: false
updated: "2017-09-18T18:05:17"

My first give me the Battery-Status.
The two Devices have the Same Part/Model-Number on back.
9290012607

Some Ideas?

9 nodes were added but only one is visible in the palette.

Hi,

I have my node red running on a synology conatiner
when i type the hue bridge ip i recive the key
but when i try to find the light bulbs it getting a error

`

`

I've just installed and tried this:

1. Thanks, fantastic!
2. I think 'Hue Dimmer' coresponds better with the Philips terminology?
3. I had difficulty with installation, I didn't get an upgrade option? The module didn't go in my User modules after an NPM install and produced a couple of WARN messages
4. I get a 'connection error' from the .catch statement even though the setup/config seemed ok?
   Haven't tried the 'Tap' yet but the other revised nodes for the sensor seem to still be working.

Just loaded huemagic up today to try it out. v1.3.4.

I can action scenes, but cannot action lights or groups.

When node-red restarts the following error is thrown highlighting hue-group as containing a syntax error. I ran a validator over the code and couldn't find the error in the syntax. (NB: ** added by me)

Any ideas?

Jan 18 22:38:36 thecollector Node-RED[1479]: 18 Jan 22:38:36 - [info] Linux 4.9.59-v7+ arm LE
Jan 18 22:38:37 thecollector Node-RED[1479]: 18 Jan 22:38:37 - [info] Loading palette nodes
Jan 18 22:38:41 thecollector Node-RED[1479]: 18 Jan 22:38:41 - [info] Settings file : /home/pi/.node-red/settings.js
Jan 18 22:38:41 thecollector Node-RED[1479]: 18 Jan 22:38:41 - [info] User directory : /home/pi/.node-red
Jan 18 22:38:41 thecollector Node-RED[1479]: 18 Jan 22:38:41 - [info] Flows file : /home/pi/.node-red/flows_thecollector.json
Jan 18 22:38:41 thecollector Node-RED[1479]: 18 Jan 22:38:41 - [info] Server now running at http://127.0.0.1:1880/
Jan 18 22:38:41 thecollector Node-RED[1479]: 18 Jan 22:38:41 - [info] Starting flows
Jan 18 22:38:42 thecollector Node-RED[1479]: 18 Jan 22:38:42 - [error] [hue-group:7ba1b057.dea88] SyntaxError: Unexpected token =
Jan 18 22:38:42 thecollector Node-RED[1479]: 18 Jan 22:38:42 - [info] Started flows
Jan 18 22:38:42 thecollector Node-RED[1479]: 18 Jan 22:38:42 - [info] [mqtt-broker:650c0fee.7aed4] Connected to broker: mqtt://localhost:1883

Hello,

i just downloaded 1.3.4 and i have the same "SyntaxError: Unexpected token =" Problem like vBiggles.

I only can action scenes, but no lights and groups.
I updated NPM to Version 5.6.0, but doesn't help.
Can you or vBiggles please help me with the Problem and describe your solution? I'm not so firm with Linux, NPM and the details of Node-Red

thx

Hey there, great node for NR!!

I originally used node-red-contrib-node-hue for my lights, but after I saw this node I gave it a shot. I could not get it running after install. Upon trying to find my hub it would produce a bunch of popup errors in NR.

Found out that your node conflicts with the node-red-contrib-node-hue node. I had to remove the old node from NR completely (disable may work) to get yours to work properly. Not really a big deal as I don't need two hue nodes running at the same time, but it did take me a minute to figure out. I figured I'd let you know (and others) in case they run into this issue also.

Thanks again!

I have a few nodes in my hue network that are shown as "unreachable", e.g. devices from Osram. However, there is no issue controlling them via the Hue app on my iOS devices.

With Huemagic it seems as if commands are not being sent to devices shown as "not reachable" - at least I've never been able to get such a devices activated, even though there are no issues with the Hue app.

According to info: "msg.payload values of: on boolean, True to turn on the light bulb, false to turn it off"

msg.payload.on=off results in "Error: Philips Hue: 7, invalid value, null}, for parameter, bri"

Adding a bri parameter does eliminate the error, but does not turn the light off.

Luckily, msg.payload=off does work

Hi there,

i am fumbling around with this since days and i assume i am making it too complicated and lost myself somewhere. I wanted to control my HUE lights with via the node-red dashboard ui. Its a a color lamp and i want to use the switch, the slider and the color picker. I have splitted the payload, i have joined the payload and i got it working with switch and slider, but no chance with color somehow. Now my flow is so HUGE that it looks ridiculous. I would be very grateful if you could give me a hint somehow what i am doing wrong and how it can be done much much simpler. I am sure its possible.

Thank you! Much appreciated!

As far as i understand the code, this is not implemented?

Hi, great project!
Would it be possible to detect a second press of the same button of a tap? Wen I press button 1, the tap node sends the corresponding json object, if I press it again nothing happens until I press a different button.
Thanks!

Hello,

I am having trouble using this node. I am able to connect to the bridge and can search for my lights on the light node. When I deploy I get this error in the debug window whether or not I have a debug node attached to the light. Any idea what I'm doing wrong?
Latest firmware on my bridge and lights.

4/1/2018, 1:22:27 AMnode: Tall lamp
msg : error
"SyntaxError: Unexpected token ="

After updating to v1.4 I have noticed a 10x performance degradation in the sendGroupStatus function in hue-group.js. Based on my own timings it was taking on average 600ms to execute this function. Once I remove the colornamer call it is reduced to 60ms on average.
This has a noticeable impact on my toggle lightswitches as my flow checks if the light is on or off before determining if it need to switch the group off or on.

Hello,

great Nodes. One Problem i have switching to huemagic:
If i a Node of one Lamp or Group in more than one flow, i got a connection error.

I would be nice if the Node would output the Lamp/Group config (as name, Lighttype ...)
not only the id.

Foddy, just got round to putting this together with my flow and although I send in various light ids the net result is always that light "1" is controlled. I made a slight mod to the node result text and added in the light ID and that always shows "1" (obviously).

Hi Foddy,

First I'd like to say thanks for developing this. It's a fantastic little node-red plugin!

So my issue is as follows...

First, I've wired up an input switch to disable / enable the motion sensors. I have 10 sensors, if I wire the switch directly into the sensors I get the following...

Then I read somewhere about an issue with API limits, so I create a bunch of hue bridges all connecting to the same IP address but with different user keys, still the same, so finally I put a bunch of random timers between the switch and the sensors, that seems to work fine (guessing the hue rejects requests if fired at the same time)

So that's one thing. The other is the Lux / Temp sensors.

As you can see I added in one temp sensor. It worked once, then just failed....

So on my bridge I have the following:

Motion Sensors: 10
Dimmer Switches: 12
Hue Colour Bulbs: 14
Hue White Bulbs: 20 (need to add 5 more)
Light Strip: 1 (need to add another 2)

I'm not sure if it's the size of my setup that has issues. I'm hoping to have little node-red flows for almost all of the elements at some point.

If you need me to run / debug anything we can set something up. I'm a developer, but it's been about 4 years since I've done anything in node, so I might need a little hand-holding, but I've been doing this stuff for 20 years, so shouldn't take me long!

Thanks,

James.

I'm trying to add a saved state to my colour white ambience lights, but when I change the colour temperature through the app, I do not get a change notification from the Hue light node. Is it possible to add this?
Without this I can only restore the brightness that the light was last at, not the colour temperature as well.

Sending a message with payload a json string for the lamp
but also properties like topic and retain (from an mqtt message)
makes the lamp throw an exception:
"Error: Philips Hue: 3, resource, /lights/NaN, not available"

If i make a new message with the same json-payload, all is working ok.

Do you plan to support these ?

After adding my motion sensor, i see 3 extra devices when i call the api:
http://10.0.250.54/api/----user----/sensors

These are the devices: (didn't include the bridge)

"2":{"state":{"temperature":2021,"lastupdated":"2017-09-20T12:25:16"},"config":{"on":true,"battery":100,"reachable":true,"alert":"none"},"name":"Thermostat 1","type":"ZLLTemperature","modelid":"SML001","manufacturername":"Philips","swversion":"6.1.0.18912","uniqueid":"00:17:88:01:02:03:0e:44-02-0402"},

"3":{"state":{"presence":false,"lastupdated":"2017-09-20T12:23:08"},"config":{"on":true,"battery":100,"reachable":true,"alert":"none"},"name":"Hue motion sensor 1","type":"ZLLPresence","modelid":"SML001","manufacturername":"Philips","swversion":"6.1.0.18912","uniqueid":"00:17:88:01:02:03:0e:44-02-0406"},

"4":{"state":{"lightlevel":0,"dark":true,"daylight":false,"lastupdated":"2017-09-20T12:28:08"},"config":{"on":true,"battery":100,"reachable":true,"alert":"none","tholddark":16000,"tholdoffset":7000},"name":"Hue ambient light sensor 1","type":"ZLLLightLevel","modelid":"SML001","manufacturername":"Philips","swversion":"6.1.0.18912","uniqueid":"00:17:88:01:02:03:0e:44-02-0400"}

Just to discuss.

Brightness' lightLevel is now the INT16 defined by Philips to make Lux more understandable. Lux is in real life not a linear value. "Light level in 10000 log10 (lux) +1 measured by sensor. Logarithm scale used because the human eye adjusts to light levels and small changes at low lux levels are more noticeable than at high lux levels." HUE-API documentation of Philips.

Is it an option to create an extra output LUX or an extra node?
The formula is Math.pow(10, (INT16 - 1)/10000);
Or

lux = lightLevel - 1
lux = lux / 10000
lux = Math.pow(10, lux)

msg.payload = Math.round(lux)
return msg;

Before I create one and suggest as a pull, I rather discuss. :)

If I send the following payload to a light node, it always changes to a specific blue (004bff) instead of the provided color.

Example:

{ payload: { hex: "55fc65" } }

Change-event for the new color is always:

msg.payload {
  on: true
  brightness: 100
  rgb: [0, 75, 255]
  hex: "004bff"
  updated: "2018-02-11T15:57:47+00:00"
}

What is going on here? Using NodeRed 0.17.5 and node v6.11.3

Is it possible to add a node to provide the last setting/press of tap and dimmer switches. As far as I can tell this ought to be possible and is the one piece of missing Hue functionality that would make the switches finally really useful? I know it is possible to follow the state of a dependant light but that is an unnecessary complication.

Change detection would be ideal but (for me) polling of switches is the next best alternative and it would be possible to locate all the switches on their own bridge to limit the affect on the overall system.

I found some problems trying to use the extended mode function. Simple mode is fine.

1. Setting ‘on’ to false has no effect the only action seems to be on (extended mode)

2. It would be good to add in some more range checking. Brightness values greater than 100 produce a library error?
   "Error: Philips Hue: 7, invalid value, 508,, for parameter, bri”

3. Brightness 0 isn’t off (I think that’s a Hue bridge limitation) but IMHO I think zero should be off also if you use 0 to 100 rather than 0 to 254 then the possible range of brightness levels is reduced?

4. ct is fine using megakelvin !!! but weird IMHO but what about saturation etc?

5. I wonder whether the excellent info might be improved a bit to explain whether commands are additive. So if I send ‘on' without colour and follow up with a colour setting without ‘on’ what is the result?

6. Would it be better to match the parameter names to the Philips ones (even if they are cryptic)?

Hey foddy,
since I put in the new functionality with dimmer switches I get a lot of connection errors through all of the huemagic-nodes. I can`t see a rule behind that behavior. The only thing is a constantly : "Error: Huejay: read ECONNRESET" and after a while : "Error: Huejay: timeout of 15000ms exceeded".

Have you got any idea? I think it appeared first time , after putting in a dimmer switch in my project.
Thanks again for your support :-)

Edit: Yes I am sure now, that the error is thrown cause of my dimmer switch. Obviously if I am pushing a button while there is that connection error, I can solve that behaviour. Until it is starting again after some time by itself.

Any chance this node could be enhanced like the Light and Group for 'universal mode'. I just started to try this and found I needed to create a lot of nodes and a switch to select them, whereas if I could pass in the scene name it would be much simpler?

Hi,
my motion sensors and obviously all the other hue nodes are loosing connection all the time. Actually everything is working fine, but after some time the hue motion sensors just dont interact with motion any more. When Im havin a look in node-red all the nodes are havin a connection error, until Im deploying again all my nodes. If I´m checking the motion sensors in the hue app, I cannot see any abnormal behaviour. My system is uptodate, so Im using the latest software versions on my raspberry pi 3.
Maybe you have any suggestions, why I get the connection errors all the time.
Thanks for your help in advance.

Hi!

I am currently running node-red on a Rpi with Raspbee deCONZ as zigbee gateway.
I am using deconz web GUI (phoscon) to include new lights, sensors etc to my mesh-network.

When I use huemagic light-nodes in node-red, it automatically locates my deconz gateway, and I am able to press the "search" button which then again finds all lamps that are configured in the gateway.

Everything with lamps is working fine.

However, when I am trying to include a motion sensor using the huemagic motion-node in node-red, it is unable to find the motion sensor which actually is attached to the network. The motion sensor is working fine and I'm actually fine with configuring its operation in phoscon (it's just turning on some lamps when I enter the room), but I would like to have the motion sensor included in node-red just to read the status from it (like motion detected, temperature, lux etc).

So that's really the question; Any idea why the hue-motion node is not able to see the motion sensor, even though the motion sensor is configured in the network and working as intended? I just get "no motion sensors found" when doing a search within the hue-motion node.

Thanks for the update!

I haven't done extensive testing but I think that if a Transition time is set (I have five seconds), then the status response will give an intermediate value for brightness, somewhere between start and target? I think this is just worthy of a note as what happens is obviously ok-ish?

Whether other parameters are affected I haven't checked but I guess they would B?

Is there a way i can dynamically set the scene to be triggered as I can with lights & groups using msg.topic? I don't see anything in the docs

(node:7671) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 144)
(node:7671) UnhandledPromiseRejectionWarning: ReferenceError: score is not defined
at client.sensors.getById.then.catch.error (/home/nodered/.node-red/node_modules/node-red-contrib-huemagic/red/hue-motion.js:105:5)
at
at process._tickCallback (internal/process/next_tick.js:188:7)

node -v = v8.11.1
node-red = 0.18.4

same problem with node 9.x

Hi,

pls add toggle msg to ON/OFF light with one stateless button in node-red.

Hi, i just installed version 1.1.1 but still don't see the new nodes.
The log shows the same errors as in my previous post:

19 Sep 14:32:25 - [warn] ------------------------------------------------------
19 Sep 14:32:25 - [warn] [rpi-gpio] Info : Ignoring Raspberry Pi specific node
19 Sep 14:32:25 - [warn] [tail] Not currently supported on Windows.
19 Sep 14:32:25 - [warn] [hue-bridge] SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
19 Sep 14:32:25 - [warn] [hue-light] SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
19 Sep 14:32:25 - [warn] [hue-group] SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
19 Sep 14:32:25 - [warn] [hue-scene] SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
19 Sep 14:32:25 - [warn] [hue-motion] SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
19 Sep 14:32:25 - [warn] [hue-temperature] SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
19 Sep 14:32:25 - [warn] [hue-brightness] SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
19 Sep 14:32:25 - [warn] ------------------------------------------------------

I am experiencing errors with my bridge when utilizing groups, lux / motion sensors and more than 10 lights in a single flow. I was wondering if there was a way to control the poll intervals dependent on the type of device it is or if this feature can be added. I am not a coder but I am confused as to why the group node needs to be polled every 500ms, but if i nerf my bridge interval rate the lights and motion sensors become sluggish to react.

Hi,
Would it be possible to define a separate category e.g. huemagic instead of input and output

Hello,
The alert message doesn't reset the state of the light.
This is message I send to the Light
**msg.payload = {
"alert": 1,
"rgb": [0,255,0]
};
**
The light stay green forever after

In Hue groups there is an issue with allOn and anyOne, which does not allow to separate groups. They are always set to true which influence all the lights instead of only the Hue group.

Hmmm.. after some further testing it looks like 1 group (living room) is tying all the lights together ?!?! I have recreated the group, but same results...

When trying to change the color of hue lights by sending RGB to the hue light, the resulted output of the hue light varies in the RGB values. See attached Node-Red Flow as well as the debug output.
Anything wrong in my flow or is there a bug in huemagic?

Node-Red Flow:
[{"id":"107d276c.8ccc29","type":"debug","z":"51b5b710.9656e8","name":"Empfangen","active":true,"console":"false","complete":"payload","x":1510,"y":820,"wires":[]},{"id":"4b6eb2db.69714c","type":"hue-light","z":"51b5b710.9656e8","name":"Couch (Hue Go)","bridge":"e7b6a026.08bf4","lightid":"3","x":1320,"y":820,"wires":[["107d276c.8ccc29"]]},{"id":"2381830e.45626c","type":"function","z":"51b5b710.9656e8","name":"HueCouchChillen","func":"msg.payload={\n\t\"on\":true,\n\t\"brightness\":57,\n\t\"rgb\":[255,187,92]\n};\nreturn msg;","outputs":1,"noerr":0,"x":1090,"y":820,"wires":[["4b6eb2db.69714c","d0d667e1.4f00b8"]]},{"id":"ffb7044.9e6bff8","type":"link in","z":"51b5b710.9656e8","name":"hue-chouch-chillen","links":["413932d5.eac6cc","c6202c30.62ead","619b769d.3f5938"],"x":695,"y":780,"wires":[["2381830e.45626c"]]},{"id":"d0d667e1.4f00b8","type":"debug","z":"51b5b710.9656e8","name":"Senden","active":true,"console":"false","complete":"payload","x":1320,"y":760,"wires":[]},{"id":"e7b6a026.08bf4","type":"hue-bridge","z":"","name":"Philips hue neu","bridge":"192.168.186.40","key":"xxx","interval":"3000"}]