Device Node (alpha)

[zachowj]

Placeholder

[nmsousa76]

None of my ZHA lights are showing up as devices nodes in NodeRed. All other lights show up fine. (zwave, tuya, hue). Is this something specific to ZHA

[nmsousa76]

Devices show up on on flow, but not on node object. See screenshot

[nmsousa76]

I think I figured out what is wrong, but would need someone to fix it. It looks like the node is using "name" rather than "name_by_user". As you can see all my ledvance bulbs are showing up as the same name. As you can see this would be problematic for many devices of the same brand. This is not specific to lights either as I noticed the same issue on my Orbit faucets.

[zachowj]

Didn't know name_by_user was a thing. I'll have to look into that.

[zachowj]

It will use name_by_user if it exists in the next release

[nmsousa76]

Thank you

[joryvd]

I have some Ikea tradfri wireless dimmers connected through Zigbee. I am using them with the ZHA integration in Home Assistant. When I listen to ZHA events and output this in debug I can see the messages coming in.
When I add them as a device --> trigger --> turn on pressed and connect this to the debug window nothing comes up. Not for any of the button presses that come out of it. I tried an automation via the Home Assistant GUI using the same triggers and that works. So something is not getting passed through to the device in Node-red. If any further info is needed I'm glad to supply.

[zachowj]

Does the property event on the device node look the same as the automation in HA?

[nilsi]

Got the same issue with an Ikea Tradfri On/Off button. Trying to trigger on "Turn off pressed" event but it doesn't come through to node red.

I can see the event triggered in HA:

But nothing in node-red when I connect a debug node:

[nilsi]

If I connect a debug node to events all nodes I can see this event in node-red so it gets an event at least.

[SpeedyDog14]

Hi zachowj,

Do you have any plans to

1. Add option to output on any trigger
2. Add option to have multiple outputs with selectable trigger options against each output

Thanks in advance

[zachowj]

1. Add option to output on any trigger

Probably not because all the logic is handled by HA for the device node.

2. Add option to have multiple outputs with selectable trigger options against each output

Initially, I had planned to be able to register multiple device actions under one node but wanted to test out a single one to start. I think I had planned to have them all output out a single node not multiple. Do you think multiple outputs would be better? I feel if you wanted multiple outputs you would using multiple nodes.

[SpeedyDog14]

Hi zachowj and thanks for your reply,

My example use case is where I have a Zigbee Aqara Opple 6 button battery powered stateless remote switch.

Currently in Node-Red I can capture the Zigbee event for this particular type of Switch in one ZHA Event Node that then output to a single Switch Node with 6 outputs (one output for each of the 6 buttons) I can then add a suitable Action/service Node to the output of each of the node switch outputs.

The only way I can see to do this with your new Device Node is to have a separate Device Node for each trigger (button press). This becomes untidy especially if I decide to expand and fully utilise double/triple clicks/hold actions of each button. I would potentially need 24 Device Nodes to cater for all the triggers instead of just one.

If you can't cater to trigger on any device event then it is what it is and is really not an issue for me. I was just wondered what your road map was so I can make the right decisions moving forward with my flows.

Cheers

[zachowj]

At this point, I would recommend staying with what you have. Any changes I plan to make to the device are not going to simplify how you are currently doing things.

[dirk2947]

Hey there, just wanted to say thank you. Came across it by chance and it was super intuitive with my aliexpress 4 button zigbee switches.

[jlsjonas]

Having some strange behavior using the new tradfri buttons with it...

a single tap seems to consistently equal to 3 events in NODE-RED 🤔 Anything I could check to help? (before this it was hooked to a regular HA automation, where I didn't experience this behavior
switch is connected via ZHA

[zachowj]

Is the payload data the exact same in all three events?

[jlsjonas]

🤔 almost... everything is exactly the same, apart from the payload.event.context.id (ids remain the same every time I click)
I've just put a 50ms debounce after it for my purposes (although that does cause some issues with double-tap handling), but it still feels like something to investigate before moving the device node to stable :)

-- let me know if I can help out here

[redhawk07]

I have the same issue, but the event is fired 5 times.
The data of the message object only differs in these parts:

• msg.event.time_fired
• msg.event.context.id
• msg._msgid

Everything else of the msg object is 100 % same.
Using version 0.43.0 of node-red-contrib-home-assistant-websocket.

[han9over]

I'm trying to use Action type to send a notification to my phone and I can do that by hardcoding Title and Message. However, I want to use single node and dynamically change the title and message used. How can I achieve that as I can't use msg.payload

[zachowj]

Currently, this is not possible with the device node. You should be able to call service node in its place.

[han9over]

Thanks. Will try that out.

[Apflkuacha]

I really find it great this Device Node, but as @SpeedyDog14 already mentioned an option to output all triggers. In my case I do use a function to react to events from a remote button and all the triggers should be forwarded to my function, the information what was pressed is in the payload.
If I do use the events:state Node I do get a single click and double click event when I only do a single click, so I prefer this Device Node.

[motionist]

When using the device for a Styrbar switch (Connected through deConz), the text does not match the actual buttons - instead the assignment is according to the codes sent by deConz (1002, 1001, 1003, 2002, 2001, 2003, 3002, 3001, 3003, 4002, 4001, 4003) - basically having the switch with Increase brightness/turn on upwards the order is anti-clock wise

[zachowj]

NR uses data for the device node directly from Home Assistant. Test it as a Home Assistant automation device trigger and see if you get the same results. If so, then you would need to report to the repo of the deconz integration.

[bravehand]

First off, thanks for this! I'm using it with some homeseer switches to trigger on central scene activation but getting some odd behavior in the "Value" field. When I create/save the node it's set to the 4th option in the dropdown (KeyPressed2x):

but when i open the node again it's set to the first value in the dropdown (KeyPressed):

If I don't reopen the node after saving, things seem to work ok for a while but eventually start triggering on the first option (KeyPressed). I haven't tested to confirm, but I suspect it's on a restart of HA and/or node-red.

And this has to potentially to really simplify central scene triggers, just look at how I'm doing it without this node:

[mltiede]

I'm fairly new to Synology, reasonably new to Home Assistant (thanks to Insteon), and totally new with Node-Red. I got Node-Red installed in a docker container and am able to run it. Then I added HACS to Home Assistant and added the HA part for Node-Red. Now when I try to put a node on the Node-Red panel, and go to Edit Device Node and Edit Server Node dialog and fill in the IP address and port to Home Assistant and press Update, I get an error that says "Error retrieving translations".

I presume this is something to do with permissions in the node-red folder on the NAS. I see that "root" is the owner. Should I make it something else somehow? Or is something else going on?

... time passes ...

I changed owner from root to my adminstrator user. Still doesn't work. (and I don't see how to change it back to "root" in case that matters)

... time passes ...

FWIW, when I entered the IP and port in the browser, I get a prompt for user and password and then for 2 factor authentication. Could that be causing a problem? Node-Red isn't prompting and doesn't provide a place to put that information.

... time passes ...

How can I tell what user Home Assistant and Node-Red are using in their docker containers? I see that I set up a special Home Assistant User, but I must have determined that it wasn't being used because its permissions are DENY for the config and subfolders. I tried giving it full permissions, but it didn't make any difference.

[TrickShow]

I just wanted to say this is awesome and has been working so well for me. Thank you for all that you do!

[johan-beemsterboer]

I'm struggling to get the node working, anyone here who can help me?

I have a remote here ('Afstandsbediening') with 8 buttons. The node says it's running:

But when I push the button, nothing happens. What am I doing wrong?

[zachowj]

Do you have the custom component installed in HA? It should say "registered" under the node after you deploy if everything is set up correctly.

[johan-beemsterboer]

Been a while, but managed to fix it with installing the custom component. That was the one, thanks!

[tamueller]

I'm new to node red, but I can't get this to work. I installed node-red in homeassistant and use zigbee2mqtt. When using a state_changed node I get the events from z2m, but not for the device node. What am I doing wrong?

As you can see, debug 7 gets fired, debug 6 not.

[zachowj]

The device node requires the NR custom component. https://github.com/zachowj/hass-node-red

When that is installed in HA the status text of the device node will show 'registered' and this

will go away from the device editor.

[tamueller]

Thanks, that was the problem.

[tamueller]

@zachowj: The device node is working mostly fine now, but in my case all of the device triggers show up in HA as a switch, which clutters my auto-generated dashboard. Is it possible to add a switch, whether to expose it to HA, and set the default to false. I can see some cases where this might be useful, but I think in most cases, you don't need the trigger to be exposed to HA.

[LordMike]

This device node is awesome. The help provided by autocompletions and dropdowns is great and greatly simplifies the troubleshooting part of my setup..

In order to better use f.ex. function nodes (because I'd like to do some custom scripting), I find myself needing to be able to react to multiple devices, multiple triggers etc.. in order to handle the events in my own code. So my suggestion is that the Value, Trigger or Device dropdowns support multiple values, that'd be awesome.

I'm intending to use it for multiple devices of the same make/model, so my Trigger/Value dropdowns will be identical, but I have no idea how to make great UX with different sets of values... Maybe only show values/triggers that overlap?

So I have two use cases really:

• I'd like to trigger a flow, when a specific button is pressed on one of many switches - ie., I want to select multiple devices, but keep the same Trigger/Value combination
• I'd like to trigger a flow, when a specific button is pressed either once or twice on one of my switches - ie., I want to select multiple Value's (KeyPress, KeyPress2, ...), for one trigger.

Example, these three trigger the one the same device and trigger, but for different values. And I'd like to duplicate this for about 4 or 5 switches, so that currently makes for ~15 nodes total.. :)

[ivanlofgren]

Device Node crash Node Red when selecting unavailable device

Recreation procedure
Add device node to node red
Edit the node and select an unavailable device (for me eg shelly plug that's been offline for a long time)
This crashes node red integration, which then restart.
During restart, opening device nodes gives translation error message below. During restart, node red publishing also isn't possible, resulting in a 502 bad gateway error.

[LordMike]

If I make a device trigger on the Node status changed, it seems I must choose a from and to. So this means if I just want to know if a device becomes dead/unavailable, I have to make 2-3 triggers, for each From-To pair?

Other Node Red nodes use blank values to indicate that the value is irrelevant.

[zachowj]

Yes, this should be added.

[bednim]

Is DEVICE node the to use when it comes to binary_sensor (like contact sensors etc etc)? I have noticed these are now gone from event_state. thanks!

[DennisGaida]

Using the device node for the first time. Do I need to use multiple nodes for multiple triggers?

I have one device that has triggers such as on/off/up/down and stop. I'd love to use a switch node to do different things depending on trigger/button press. The device node seems to only allow one trigger?

[zachowj]

Yes, you need one node for each trigger.

[DennisGaida]

Thanks for your answer, thought as much. I don't like device triggers then ;-) I suppose because you have to register for each handler with HA to receive events? Wish we could register for (*) then...

[catduckgnaf]

Under Device Node, "Brightness Increase" and "Brightness Decrease" do not work. I was looking for an easy way out of adjusting brightness. Is this known issue?

[yameiko]

since installation of hacs update node companion: node with aqara switch devices doesnt work anymore. ha automation with this devices still work. does anyone have the same problem

[zachowj]

If you're not running v0.57.0 beta of the HA nodes revert back to version 2.2.0

[catduckgnaf]

Is this a planned breaking change? Or will it be fixed? And what should we do instead? (Other then not update)

[zachowj]

https://github.com/zachowj/hass-node-red/releases/tag/v3.0.0

[catduckgnaf]

I guess I meant, is there a solution? Other then staying on an old version. If that makes sense (or not using node-red for these devices?)

[tangrasmus]

Had the same problem with aqara buttom uninstalled 3.0.0 went back to 2.2.0 and it works again.

[JonnySpruce]

I have a presence sensor set up to trigger when the attribute changes to "Approch". Using this node it's multiple seconds slower than if using a HA automation. Is that expected and is there anything I can do about it?