We've all run into this: a junction node sits right on top of a wire — visually it looks like part of the flow — but it isn't actually connected to it. Finding these cases currently takes a lot of effort, because nothing in the editor distinguishes a junction that's properly wired from one that mere…

This has come up a few times and I too have fallen for that trap. There is a fan node - node-red-contrib-fan - which was the father of this. Things I have learnt: 1 - don't put junction nodes over existing wires so as to make it look like it is using those wires. 2 - When connecting to a junctio…

[image] Trying_to_learn: ... 2 - When connecting to a junctionnode: after connecting to it, drag the node to be sure all observed wires move too. This then detects any wires not connected. ... That's prevention, not detection — the request is about detecting existing cases. The drag-test do…

How are you expecting the editor to know that you want wires connected to a junction node or not? That the node is on top of the wire doesn't mean a thing to the editor. I fear you have your work cut out for yourself.

[image] Trying_to_learn: That the node is on top of the wire doesn't mean a thing to the editor. Why could the editor not detect a wire passing directly under a node I/O connection?

This JSONata expression will return all junction Id's that have one in or out wire and with no wires at all connected eg [{"id":"7e18efe9337808ab","type":"inject","z":"613df62afc8a16bf","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":…

[image] E1cid: This JSONata expression will return all junction Id's that have no in or out wire and with no wires at all connected Nice, that's much closer to what I'm after — thanks! Two caveats I hit when doing the same via a script, though: wires[0] only checks the first output (so a ju…

Junctions only have one output, this is what wires[0] is searching for on the output of only the junction nodes. Once you have the id's you can search for them in the info sidebar. Looks like the search issue was not fixed my mistake. How to find a Junction - #11 by cymplecy

Nice use of Jsonata once again @E1cid . I've been struggling all morning to get chatgpt to give me a working Jsonata expression! Edit: The flow I first posted failed to notice junctions linked to from the second output of a node. I think this is better, no Jsonata any more :sweat_smile: [image] …

[image] jf64: But the bigger point: this still only tells me which junction IDs are affected — it doesn't help me locate them on the canvas, That is indeed a problem. I've also played around with orphan nodes (as I called them) but in my implementation, I ignored junctions for exactly that r…

Node-RED lint ( GitHub - node-red/nrlint: Node-RED Flow Linter · GitHub ) does already have a rule to report unconnected nodes...

Unconnected junction nodes

Core Development Feature Requests

gregorius 1 July 2026 09:50 10

That is indeed a problem. I've also played around with orphan nodes (as I called them) but in my implementation, I ignored junctions for exactly that reason - there was no way to highlight them.

There is also no jQuery triggery to hack around that because junction nodes do not have an identifying id within the workspace, i.e. $('#<node-id>') will give you access to any node but not junction.

Topic		Replies	Views
:tada: Node-RED 3.0.0-beta.1 released News	73	8749	13 May 2022
How to find a Junction General	18	279	26 November 2024
How Do I Find Lost Junctions General	15	483	16 March 2023
Hide connections Feature Requests	17	1788	23 August 2021
Add opt-in property that allows specifying the types of nodes that a given node can connect to Feature Requests	28	245	1 February 2025

Unconnected junction nodes

Related topics