Device Node (beta)

[zachowj]

[KevinHurts]

Since I've updated my device node triggers are greyed out and disabled. They still seem to work and on create I can select a trigger just fine but once I click on "done" and edit the node again the trigger is greyed out again. Is this intended or is this a feature I can turn off?

[zachowj]

Are you accessing the Node-RED UI through the Home Assistant UI? Try accessing it directly via port 1880 to see if the issue persists.

[KevinHurts]

Yes the issue still persists if I acces node-red directly

[Jaymian-Lee]

My device nodes are colored green instead of red. They also display the message:

"Beta version: Config should be stable and hopefully without too many bugs.
Found an issue? Post it in the issues. Have questions or comments? Post them here."

Since they turned green and this message appeared, I can no longer use the nodes. When I select "trigger," the part where I can choose the trigger is greyed out, and the same applies to "action." I was working on my nodes, and after a deployment, this issue occurred. For reference, please see the images below.

[KevinHurts]

Seems like you have the same issue as me. What happens if you select another device or create a new device node? When I do that the trigger is available untill you save the node and edit again.

[zachowj]

If you open your browser’s developer tools and switch to the Network tab, do you see any error status codes (anything that doesn’t start with 2xx or 3xx) when you open the node in the editor?

[Jaymian-Lee]

@KevinHurts The trigger is always grey, even when i select or create a new node

@zachowj Nope, i see no errors. Every status code is 200 and the response and request headers state nothing that is out of the ordinary as far as i know.

These 4 generated when selected a node:

These were the only error codes generated when starting node red:

Hope this helps!

[Gizmopower1]

Same happened to me. Changed the device to another then back again and it fixed it.
Edit: But now it´s gone again :/

[miky-boy]

Hi, I suffer the same as you. Sometimes I need to open/close the device to appear the dropdown again :(

[miky-boy]

Hi,
Even with the issue above I also cannot have any sucess on get output. I was using the version Node-red 4.0.3 and using the compaing. My flows are working based on automation, but I would like to get the trigger directly from the source.. in case by the entity.
Someone have the same issue? I tested everything.. even action.. and nothing :(
Prints and details below



Thanks and Regards

[samlinville]

Hi, I'm also having difficulties; when I set up the Device node to trigger on a lightswitch press, and hook the output up to a debug node, nothing ever prints out, and the node doesn't seem to actually trigger when I push the button on the lightswitch. For reference, this is my configuration:

[mapap2]

I'm having the exact same problem, did you solve this?

[jam-hur]

Same for me. Any solution?

[NicholasLambell]

Hey there,
Really like the tighter integration from the new node and haven't really run into any of the issues other than than the list of type options sometimes being out of sync from the selected Type. That's on the latest versions of everything: HA, plugins, palette, etc, and Node-RED v4.0.2.
The ability to just pick an option from the dropdown when setting values for select entities has been awesome but I've run into a bit of a limitation when using a select entity as a trigger. Currently you always have to pick a 'From' and 'To' value which works great for cases where you want that but the option to have either or both of those be blank or some kind of any option so that you can just listen for value changes to or from a given option would be awesome.

Also, not sure if it's something that's already planned but an equivilent 'entity' node that had the same level of integration would be great for deviceless entities like helpers or those from custom integrations 😄

e.g. The 'Any Option' example below would listen for any value change to 'B', regardless of the previous value.

Current	Any Option

[cmprmsd]

Hey there!
I really like the dropdown being filled according to the device's functionality. Had to do this manually before.

<politics> The new Zigbee2mqtt update (2.0+) kind of forces users to drop their legacy stuff and I'm happy with that as it keeps the project at speed and it's a PITA for developers to keep legacy code that has proper replacements. </politics>

I noticed one bug though. I had this event state trigger set up, where there were eight actions (4 way remote with click and hold) where I would just drag and drop from the outputs:

When I use the new device trigger, it offers the detected actions, which is great!

The only problem is now that I have to create eight triggers and when I copy this configured the field gets disabled as it's not being republished after being configured. It seems populating the trigger drop down only happens when a new device is selected.

When I'm in the same configuration window you see that the update takes place when I change the device:

I hope you can confirm this is a bug you'll be able to fix. Thanks for the great work! :)

[JEReinhart]

Hello, I wanted to ask here before posting it as an issue.
Has anyone else used this with a phillips hue dimmer switch?

I've been using this with aqara mini switches without any issue.

I recently added the hue dimmer switch, and I have not been able to get it to work.

It seems the node identifies the device as it gives me all of the options I would expect:

However, I've tried "pressed" for all buttons, as well as "doubled clicked" and "continously pressed" for the turn on button, but no event is ever triggered from any of them when I try.

Any thoughts or suggestions?

Thanks