Nodes for Hue switch not responsive

General
1

I am using the Hue switch node from node-red-contrib-huemagic wired straight into a debug node to capture responses. At most the node will send responses with a significant delay if any. I have configured the switch on the bridge to turn on/off one light and the bridge acts immediately.
Using the Light node I can capture the lights response. While with delays, I can get the light state reliably.
The current behavior makes it impossible to use Hue switches in node red to control as in my case a mqqt message.

The question I have, is this just me or are the hue nodes generally acting with significant delays? I am keen to hear from anyone who is using Hue switches via node red.

2

Try changing the poll frequency in the config node.

3

Thanks. I tried it and it did not solve the issue.

I did had a look at the logs and found these:

31 Oct 07:06:33 - [debug] [hue-bridge:Philips hue] TypeError: Cannot read property 'lastUpdated' of undefined
    at HueBridge.getUpdates (/home/pi/.node-red/node_modules/node-red-contrib-huemagic/red/hue-bridge-config.js:120:34)
    at scope.client.rules.getAll.then.then.results (/home/pi/.node-red/node_modules/node-red-contrib-huemagic/red/hue-bridge-config.js:59:31)
    at process._tickCallback (internal/process/next_tick.js:68:7)
31 Oct 07:06:34 - [debug] [hue-bridge:Philips hue] TypeError: Cannot read property 'lastUpdated' of undefined
    at HueBridge.getUpdates (/home/pi/.node-red/node_modules/node-red-contrib-huemagic/red/hue-bridge-config.js:120:34)
    at scope.client.rules.getAll.then.then.results (/home/pi/.node-red/node_modules/node-red-contrib-huemagic/red/hue-bridge-config.js:59:31)
    at process._tickCallback (internal/process/next_tick.js:68:7)
4

The hue magic nodes are made to do this.
I have no problems with hue-magic at all, works instantly. But I don't use the switches.

If you add a switch to the flow and capture the output in a debug node and press the button ? What is the delay ?

5

I have no issues with any other devices than sensors (switches, motion). Poll time has been reduced. Everything else works fine.
The delay is massive and messages are not reliable. So far that it is not usable.
Openhab is working fine. My plan was to replace Openhab with NodeRed but this is off the table now.

6

If you have checked the recommended nodejs version in the ReadMe and that you have the latest version of the node, you can open an issue on the nodes page on github to communicate directly with the nodes author

7

Openhab is working fine.

Are you using the same API key for OH and NR ? ie. interference. And indeed I would open een issue on github if you can replicate it.

8

Good point. It is a fresh install using the NodeRed recommended approach, so I assume it is the latest.
I checked on GitHub after I posted here and someone already raised an issue. I was curious if anyone else is seeing the same. I now know I am not alone.

Thanks anyway.

9

No. I created a new key. Even turned off OH completely but will go back and used the OH nodes to interface.

10

That would give you the latest version of Node-RED, to see if you have the latest version of the node you can check in the “Manage palette” option in the menu

11

Yes it is 1.0.2.

12

@ukmoose was referring to the nodejs/npm versions.

13

Actually I wasn’t!

The nodes ReadMe lists recoomended versions of nodejs

The latest version of the node is v2.0.4

14

Node.js version: v10.17.0

15

How do I check this in "Manage palette"? I can't spot it there.
I am learning fast but I am pretty new to NodeRed,

16

In managed palette you can see all your installed nodes on one tab

image
image.png1154×590 44 KB

17

It is 2.0.4.

I have given top on this and I am using the OH nodes to connect to Hue switches. While it adds a component it is at least reliable.