🚌 Route (jov)

If you've grabbed a workflow off the internet and it won't load because of a node called "🚌 Route (jov)", this is your answer: it's Jovimetrix's pass-through node, and in current installs it's now called ROUTE (JOV) 🚌. Same idea, slightly fancier name. The node does one thing - it takes whatever data you plug into it and hands it to whatever you plug the output into - but it exists because ComfyUI's wires can get genuinely unusable in big graphs.

Why a pass-through node exists at all

When a workflow sprawls past a few dozen nodes, routing lines get tangled across the canvas, and dragging wires through the middle of unrelated node stacks is how you accidentally connect the wrong thing. A route node is a "bus stop" you drop on the wire: data goes in, data comes out, and the physical wire gets a clean break you can drag around without pulling the whole connection. It's the same reason rgthree's Reroute nodes are everywhere in large workflows - organizing the graph is a real job, and Jovimetrix's Route is that tool for its own types.

There's a second use that's more Jovimetrix-specific. Because the pack is so type-agnostic (any input accepts IMAGE, MASK, numbers, vectors, you name it), a Route node in the middle makes it explicit what is flowing through, which helps when you're chaining Jovimetrix's *-typed ports and want a sanity check point.

Inputs and output

The old node is minimal:

• o (any type) - the data to route. Just pass it through.
• 🚌 output (any type) - what comes out the other side.

That's the whole surface. Current ROUTE (JOV) 🚌 expands on this with a BUS input and collects extra inputs as tuples, but the beginner-relevant behavior is identical: wire something in, wire it out.

Installing it

You don't install "Route (jov)" by itself - it's part of Jovimetrix:

• ComfyUI Manager - search "Jovimetrix" and install.
• Manual - git clone https://github.com/Amorano/Jovimetrix.git into ComfyUI/custom_nodes/, then pip install -r requirements.txt.

No model downloads. Dependencies are numpy, OpenCV, Pillow, matplotlib and the author's cozy_comfyui library (pulled from GitHub by the requirements file). The pack wants ComfyUI 0.1.3+.

The trap in the name

The one genuinely confusing thing here is naming. The -Route-jov slug and the lowercase "Route (jov)" display name are the old node name, captured by comfy.icu from an earlier Jovimetrix release. As of Jovimetrix 2.x the node is "ROUTE (JOV) 🚌" - the emoji and all-caps came along with the author's 2.0 renaming pass, and a bunch of other nodes got the same treatment (ADJUST, BLEND, CONSTANT all have this split personality). If your old workflow references the lowercase name and ComfyUI says the node is missing, you haven't lost anything: the current pack installs the renamed version, and you rewire the two ends. The README warns this rename migration is manual - connections don't follow along - so budget five minutes when upgrading an old workflow that used Route.